New Scenarist Install Problem

[recoil47]

I purchased a new motherboard for my PC to fix a few issues I was having with some other stuff, and reformatted this weekend. After which, I re-installed Scenarist, and the other Big-3 applications. Everything appeared to install OK. However, when I ran my first backup on the newly formatted PC, things locked up in a big way when it came time for Scenaid to run Scenarist.

I've come to find that ANYTIME I try to run Scenarist and work via a new script, it locks up. I can get into Scenarist if I try to create a script from scratch. So it seems like only a part of the program isn't working, but its failure takes my entire system down and runs the CPU at almost 100 percent.

All I did was change motherboards, and reinstall WinXP. My new motherboard is an Asus A8N-32SLI. I have no idea why Scenarist would be acting this way.

Is anyone aware of any potential problems like this with Scenarist that would cause it to lock up? I'm running 2.7. Maybe its time for a newer version? Help!

Thanks

[recoil47]

OK,

Additional information:

I upgraded to Scenarist 3.01. Completely uninstalled Scenarist 2.7, uninstalled ScenAid, put Scenarist 3.01 on, then installed Scenaid 1.7.0.7 again. Ran the Scenarist Scan, and it detected Scenarist 3.0.

I'm having the SAME problem at the SAME place. Scenaid's last remarks are:

"Encoding Finished"
"Launching Scenarist"

Apparently things go back when Scenarist starts its import. I look at my Task Manager and Scenarist is running (I just can't see it). CPU Utilization for Scenarist is at 00 though. Automate_Scenarist is running with CPU at 11% spiking to 20%. Explorer.exe, however, is running at around 70% utilization.

So something is running, just not properly. I'm really tempted to blow away my OS Again and start over(since I just did so this weekend).

Is there a logfile that Automate_Scenarist or Scenarist uses that will help me find out what is causing this to happen??

Can anyone help? This didn't happen until I installed my new motherboard. I can't imagine its a conflict with the board type, but I don't know, or know how to tell.

Thanks

[recoil47]

Another odd point. I just used Task Manager to close explorer.exe, which was at 77%, once I did that, Automate_Scenarist jumped to 80% on the CPU. WTF?

[influenza]

I remember having problems with scenarist after installing the latest nvidia drivers for my MB (I believe some HD controller related drivers). Can't exactly recall what drivers, but I remember it didn't make me too happy.

[recoil47]

Thanks to your response Influenza, I widened my search, and found someone on this board found and posted the solution last year:

I found a working solution that works with the nForce IDE drivers.

I copied 3 files into the C:\Program Files\Sonic\Scenarist directory:
wnaspi32.dll (version 4.71.1.0 - my date stamp read 5/6/2002)
msvcp70.dll (version 7.0.9466.0 - my date stamp reads 6/20/2003)
msvcr70.dll (version 7.0.9466.0 - my date stamp reads 6/20/2003)
(most were found in system32)

I suspect default Scenarist+ASPI+nForce=the problem.

I'm using Scenarist 3.0

Thanks to JohnnyTaco!

Full link here: http://forum.doom9.org/showthread.php?p=770859

I will post to confirm that this works, however at first glance, I was able to get past the import screen, so I think I am set.

[influenza]

yeah I also remember now. Nice that you fixed it :)

[recoil47]

Looks like everything worked 100%, I'm back in business. That is a nice, elegant, fix to the problem. A lot better than trying to uninstall drivers, find working version, etc. Worked really well.