On 3 Jul 2006 06:58:03 -0000, Dylan Penhale <dylan@(email surpressed).au> wrote:
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.
Hi Dylan,
I can replicate the same error here on Windows XP SP2 and as I recall
this have always been the case for most of the command line tools --
they don't do UNC.
I think "fixed" here means "we added a registry key to suppress the
error", unfortunately.
Custom Mel:
//print windows username
string $WIN_Username = `system("echo %USERNAME%")`;
print ("\nCURRENT WINDOWS USER:\n" + $WIN_Username);
You can get to environment variables through $ENV in perl, so the above
could be changed to string $WIN_Username = $ENV{'username'} and you could avoid
the problem altogether.
/Niklas
--
Swiss International | www.swiss.se
|