From: Dylan Penhale <dylan@(email surpressed).au>
Subject: UNC paths are not supported when including some custom mel scripts
   Date: Mon, 03 Jul 2006 02:58:03 -0400
Msg# 1335
View Complete Thread (8 articles) | All Threads
Last Next
Hi there

We are running some custom mel when we submit a rush job and we get an error about UNC paths. I looked up the error and it appears to have been fixed a long time ago around the time of NT I think.

Custom Mel:

//print windows username
string $WIN_Username = `system("echo %USERNAME%")`;
print ("\nCURRENT WINDOWS USER:\n" + $WIN_Username);

Error:

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?



Regards

Dylan Penhale
Systems Administrator
Fuel International
65 King Street
Newtown
2042
Sydney
Australia
p. (Tel# suppressed)
f. (Tel# suppressed)



Last Next