Re^2: XP and slashes?

See answer earlier. As for being mistaken here is an example:

C:\>cd c:/perl
The system cannot find the path specified.

C:\>cd c:\perl
[download]

And while I would certainly never claim to not be mistaken early and often, I'm not about that. This only applies to the command line as near as I can tell so not relevant to my problem...

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."

Comment on Re^2: XP and slashes? Download Code

Replies are listed 'Best First'.
Re^3: XP and slashes? by ikegami (Patriarch) on Apr 05, 2009 at 05:45 UTC
This only applies to the command line as near as I can tell so not relevant to my problem... Indeed. Your example only shows that "cd" doesn't accept "/" as a separator. You'll find the same for most of MS's command-line tools because they use "/" to mark options. However, if it's quoted... `C:\>cd "c:/temp" C:\Temp>` [download] Update: Actually, it works unquoted for me too. `C:\>cd c:/temp C:\Temp>` [download] Even if the slash is the first character `C:\>cd /temp C:\Temp>` [download]	[reply] [d/l] [select]
Re^3: XP and slashes? by cdarke (Prior) on Apr 05, 2009 at 14:57 UTC
The underlying Win32 API accepts either / or \, and has done since at lease NT 3.1, however some applications only take \. cmd.exe is one of them, of which cd is a built-in. MS-DOS and PC-DOS used to be the same (although I doubt there can be many people using the 16-bit DOS VMs any more).	[reply]
Re^4: XP and slashes? by ikegami (Patriarch) on Apr 05, 2009 at 22:24 UTC
however some applications only take \. cmd.exe is one of them, of which cd is a built-in. I proved otherwise earlier.	[reply]