Screamernet LW9.6 64bit and .bat files

[Roadwarrior]

Issue with Screamernet LW9.6 64bit on Windows 7.
Tryed creating .Bat files and keep getting this error report:
the program or feature"\??\L:\Programs\lwsn.exe" cannot start or run due to incompatibility with 64bit version of windows.[/I]
L: being our network drive.
Anyone have a .bat file pointing to the content directory that
works under 64Bit they want to share or a workaround for this?

[djlithium]

I really need to get a copy of win7 up on one of these machines somewhere and see this for myself. It doesn't make sense that it would choke like that.

[Roadwarrior]

Screamernet Init can't find cpu's either
(Command folder problem i assume)
ive checked to see that the network rendering panel has the same "command directory" path set that the nodes are pointing to and it does...and the server has access to read and write to the folder.
The .bat Ms Dos Window flashes on and off real quick and fails to connect to the server on the user/render nodes. x2
Strange because this ".bat" runs fine on the server and starts talking the default "Can't open job file "\\Lw96x64\screamer_command\Job1
in the Ms Dos window.

The ones on the User\Render Nodes are a carbon copy except for the obvious change that has to be made in numbering to the.bat files ie: Job2 & Ack2 and Job3 Ack3 for it to talk to the server.
So Simple and yet so finicky!:devil:

[djlithium]

Screamernet Init can't find cpu's either
(Command folder problem i assume)
ive checked to see that the network rendering panel has the same "command directory" path set that the nodes are pointing to and it does...and the server has access to read and write to the folder.
The .bat Ms Dos Window flashes on and off real quick and fails to connect to the server on the user/render nodes. x2
Strange because this ".bat" runs fine on the server and starts talking the default "Can't open job file "\\Lw96x64\screamer_command\Job1
in the Ms Dos window.

The ones on the User\Render Nodes are a carbon copy except for the obvious change that has to be made in numbering to the.bat files ie: Job2 & Ack2 and Job3 Ack3 for it to talk to the server.
So Simple and yet so finicky!:devil:

It can be but once you have it working and figure out why its like "duhhhh!" and from there on in its awesome. I really suggest moving to actual mapped drives instead of UNC paths to get things sorted out. It will make your life simpler.

[Lewis]

something is probably missed in links/bat. I had Bat files for machines on 9.664bit until recently when i changed all to LW10 system/naming and it works. I'm rendering over 3-8 machines at work. If SNII can't find machines/CPUs then something is wrong in links definitely.

I'd like that we have much simpler setup of LWSN but we don't :(.

[djlithium]

Roadwarrior let me know he got it solved. Turns out it was spaces in the path or file names which of course breaks all kinds of stuff.