Batch File Nightmares!!!! Please Help!!!

[jesblood]

Hey all,

I've been following this easy to setup four part series on Youtube setting up and running Screamernet. I've got everything set on all four of my pcs. However when I went to run my batch files only 2 out of the four actually ran the files. My main computer and my fourth computer ran their files just fine. You know sending that alert over and over until you initialize Screamernet saying "can't access job file." But once I intialized Screamernet both of those pcs showed up perfectly in the listing. The other two were nowhere to be found.

I don't think anything went wrong with the instructions. I think it's a strange setting on my other two pcs. I tried copying their batch files for each malfunctioning computer to their individual hardrives just to see what would happen. Same thing each time. The command prompt window would open and then immediately shut down. They wouldn't run.

This is frustrating! The process works just fine. I was just hoping that maybe someone on here could help me figure out the cause to my problem or maybe somebody knows someone who can. Please if anyone can be of any help I would be eternally grateful.

I'm running all four pcs on Windows XP 2002 professional service pack 3. Thanks in advance.

[Matt]

You did make sure each of the batch files had unique 'job' and 'ack' numbers?

So for four nodes they would be:

job1
ack1

job2
ack2

job3
ack3

job4
ack4

Also, to stop the Command windows closing before you can read what the error was, put a 'pause' at the end of the Batch script.

Also, not sure if you've seen this, but I wrote a tutorial on ScreamerNet, might help:

ScreamerNet_Tutorial.pdf (http://www.newtek-europe.com/Stuff/LightWave/Misc/MattGorner_ScreamerNet_Tutorial.pdf)

[Phil]

This was fixed in another thread he posted. The issue is the requirement to have MSVC 2008 SP1 runtimes installed on Windows XP. He had a common folder shared across nodes, as was always possible prior to LW 10. It's a shame that this had to be broken in LW10, but I guess newer Windows versions come with the runtimes already available.

Installing the runtimes on each node is enough to fix this. Perhaps it should be added to the documentation or release notes - this is not the first person to run into this problem, after all.

[Matt]

Dang, multiple threads!

[Javaris Tharco]

Hi Matt,

I'm thread-jumping here, I know, but I wanted to ask if you had any experience using TequilaScreamerRunner in place of the bat files?

[jesblood]

I apologize Matt. I posted here first and nobody responded. Phil is correct. Once I installed the MSVC 2008 SP1 runtimes everything worked like a champ.