[4 HeRo]

Hi All

Right I've map a network drive, started the manager and all the servers
I then go to add a job from the networked drive on my local pc and get this error message

MXS seems to be a local file. only shared network paths will work properly. do you wish to continue?

I lost with it all now any help would be great

Thx in advance


John

[tanguy]

if you work on 3dsmax 9, you could in the preferences ask to convert all the path in UNC type or in relaive ...
Try this, like that all your path will be in network and not in local synthax...
Hope this help you

[toshi]

John,

When you add job, You have to input the .mxs file name in Network Path.
First time I got same error message everytime.

Like this


tosi

[4 HeRo]

Thx guys

I kind of understand what I'm doing i think now,
I have got it render on both machines but not with textures it keeps look on my local pc for the d:\

I'm confused, Back to test then for me.

Cheers

John...

[simmsimaging]

Not sure if it's the most elegant solution, but I've found a fairly simple way of getting around this issue.

I made a folder on the c:/ of all computers in the Maxwell nework and called it "MWR_Current". While working on a project I keep all the basic files in there on my main workstation. I use an xcopy dos command in a .bat file which duplicates the contents to another drive to keep the server machines up to date with my main workstation.

When I'm ready to do a network render I run the .bat file to update the render servers. When I add the network job I get the same error message, but just ignore it because the file *is* local on all machines, and the path is the same on all machines. When the render/job is done you can just dump the contents of the MXW_Current folder on the server machines.

This does mean full copies of the job files on all machines, but I don't mind having the temporary backups anyway, and updating my two server nodes is literally two clicks. Works like a charm for me.

b

[ricardo]

Not sure if it's the most elegant solution, but I've found a fairly simple way of getting around this issue.

I made a folder on the c:/ of all computers in the Maxwell nework and called it "MWR_Current". While working on a project I keep all the basic files in there on my main workstation. I use an xcopy dos command in a .bat file which duplicates the contents to another drive to keep the server machines up to date with my main workstation.

When I'm ready to do a network render I run the .bat file to update the render servers. When I add the network job I get the same error message, but just ignore it because the file *is* local on all machines, and the path is the same on all machines. When the render/job is done you can just dump the contents of the MXW_Current folder on the server machines.

This does mean full copies of the job files on all machines, but I don't mind having the temporary backups anyway, and updating my two server nodes is literally two clicks. Works like a charm for me.

b

An alternate to this is to map the folder as a network drive (i used m:) in all machines, including the host for the files. Then all systems will see it as the same path.

[simmsimaging]

I tried that, but for some reason I was unable to map a local folder as a network drive on my main workstation. I tried several times and just gave up. Is there a trick to it? Windows xp64 just wouldn't seem to let me map one, but it's likely something I'm doing wrong.

b

[4 HeRo]

Thx for all the help guys!

Well i got it sorted in the end. thanks to toshi pointing me
in the right direction with the network path, I managed to
render with any textures.
Then I tried with textures, after remapping the bitmaps
and it works a treat.

Its a pain in the backside that I will have to remapped all
my MXM's but I guess I'll only have to to this the once and
only keep them on my local pc.

Thx again for all the help

[ricardo]

I tried that, but for some reason I was unable to map a local folder as a network drive on my main workstation. I tried several times and just gave up. Is there a trick to it? Windows xp64 just wouldn't seem to let me map one, but it's likely something I'm doing wrong.

b

I'll see if there is a trick, It's long since I tried it.

Ricardo

[ricardo]

Hi,

I checked again, it't pretty straightforward (32bit)

Open explorer, tool, map network drives. Then browse to a folder in your computer.

There shouldn't be differences between 32 & 64 regarding this - seems it is some security thing blocking it.

Try the event viewer and see if there are any messages there after it falis.

Ricardo

[toshi]

Its a pain in the backside that I will have to remapped all
my MXM's but I guess I'll only have to to this the once and
only keep them on my local pc.

Try "Pack & Go" in Studio Comand.
And make the new folder in your Network Path.
next hit "OK".
mybe It will solve.

toshi

[simmsimaging]

Hi,
I checked again, it't pretty straightforward (32bit)

Open explorer, tool, map network drives. Then browse to a folder in your computer.

There shouldn't be differences between 32 & 64 regarding this - seems it is some security thing blocking it.

Try the event viewer and see if there are any messages there after it falis.

Ricardo
_________

Thanks Ricardo - it did work, I just had to go through "Windows Network" on down to the folder to make it work. I had tried just selecting the shared folder for the local drive but that doesn't work. Thanks for the help - this should be a lot easier to keep on top of!

b

[ricardo]

Hi Brett, nice it worked

My last toy for this kind os stuff is this:

http://www.ximeta.com/web/technology/nd ... ie1_en.php

Bought some networked HD cases that run free of a host computer, on raid setups. I've been using them for bakcup and other shared data. The only pitty is that I can't find those with gigabit ethernet here in Brazil.

Neat toys anyway.

Ricardo