Dylan Penhale wrote:
CURRENT WINDOWS USER:
'\\na.fuel\share\projects\q\q_s245\q_245_176\setups\maya'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
netrender
Has anyone seen this before? It seems that the working directory is
incorrect but eventually the command works when it Defaults to the
windows directory. I'm wondering if it's to do with the direction of the
slashes, or if the working directory needs to be set elsewhere?
It's not the slashes, it's just DOS doesn't like the current working
directory to be a UNC path.
Indeed it's mostly a warning; the command will run anyway.
But it does change the current directory to the C:\ windows directory
before running the command.
Microsoft explains this error best:
http://support.microsoft.com/?kbid=156276
You can see a similar error pretty easily in DOS by typing:
cd \\some\unc\path
..which fails, where as:
dir \\some\unc\path
..works fine.
No other programming language or Windows shell scripting language
suffers from this problem; it's only when DOS becomes involved,
ie. when you use functions like system() or back-ticks.
According to the above Microsoft page, there's a registry tweak
to "fix" this. And there's something about 'Obtain the updated Cmd.exe',
though I'm not sure if I can believe them, as they say this was fixed
in WinNT 4.0, yet it 'Applies To' just about every release of windows
since then, and none of them have this fix either. In fact, they forgot
one; it applies to Windows 2000 Professional as well.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
** NOTE:
** I will be on vacation July 11th through July 20th.
** During that time, orders and email response may take over 24 hours.
**
|