OS conflicts on network rendering?

[-Vormav-]

From my experience with XP Home, backburner will work.
However, when you start doing net rendering, the usual thing to do is to setup a network drive, so that after a computer renders out whatever frames its been given, the output is sent to this network drive. This becomes a problem though, as XP Home can't connect to network drives (or at least I haven't been able to get it to). What this means is that you'd have to physically open up the xp home computer yourself, and transfer all of the output manually.
Maybe you can find a way around that, but I've never been able to. XP Home's networking sucks. =/

[j_p]

the main problem i had was making xphome share a folder. accessing ones shared on xppro machines that "know" the user on the xphome-machine (user exists there too with same password and password not empty) basically works i think.

[coltraIN]

Thanks for the replies. I did a google search on accessing network drives in xp home, and came across some solutions about "mapping" a drive or something like that. Anyone know if that would solve the potential problem? Thanks again.

[j_p]

mapping a drive is just an option that helps you to use normal paths like Z:\pictures\picture.png

but you have to map the drive/folder you want to render to identically on all machines
example:
comp1 renders&holds the renderdrive
comp2 renders

UNC path: \\comp1\sharedrenderfolder\picture.png (file://\comp1sharedrenderfolderpicture.png)

or you map that path to drive Z: (for example) on both comps
then your renderpath is Z:\picture.png
they both find that path and your pictures get delivered to one folder

doesnt quite matter in my opinion
if mapping works the UNC paths should work too

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.