known issue, don't install to dir with spaces in it. bad idea.
Thanks, I'll move it to C:\JBoss3 so it doesn't fall over because of spaces.
By the way, if this is a known issue, why hasn't anyone on the JBoss development team fixed it yet? If the boot procedure would just use an environment variable or a properties file located in the /bin directory this would not be a problem at all. Seems like a fairly simple patch to me...
AFAIR, its an issue with the URL class -- or maybe its an issue with Windows not being able to correctly handle file: protocol with spaces in it when referring to Windows filesystem.
So even if the script is fixed, installing to a dir with spaces would still be a bad idea.
Ehr... does class URL change string representations like "c:/Progra~1" to something like "c:/Progra%381"? I'm sorry, I didn't know this behaviour was built in.
I would join you in the opinion that it's actually more of a Windows bug. After all, if I can type "cd\Program Files" in the CMD window, why on earth does Windows screw up when it says "cd \Program Files" in a BAT file? Some sort of Microsoft logic I guess...
Anyway, thanks again for pointing out the issue concerning spaces in path names.