Scenarist 2.6/2.7 & WinXP SP2

[Doom9]

Is anyone running Scenarist on that setup? It seems to work just fine when creating my own project, but trying to import from a script (pressing the new from script button) makes Scenarist freeze. Has anyone experienced similar behaviour? This is a rather new installation and so far the first problem I've encountered since I've installed the new service pack (RC1).

[osho]

I have exactly same problem,

if you please find the solution would you mind telling me ;)

[Doom9]

at least in my case I can rule out SP2 as the cause.. even a reinstall with good old SP1 didn't help, Scenarist always craps out when I want to import a script, and it also crashed during the last phase of compilation (creating the proper VOBs). Guess Scenarist has started to dislike my machine.

[RB]

Uninstall Adaptec ASPI. At least this solved the "freezes when trying to import from script" issue for me.

[wfn1]

running winxp sp1 (with a bunch of hotfixes from sp2) + scenarist nt 2.6

i've experienced a similar problem recently, except when i hit new from script the menu disappears and i end up with a scenarist.exe process eating up 99% of my cpu in the background.

i tried uninstalling the adaptec aspi layer that scenarist installs by default with killaspi.bat that comes with the forceaspi package. unfortunately that doesn't help and now when i start scenarist it gives me this window:

Scenarist.exe - Unable To Locate Component

This application failed to start because WNASPI32.dll was not found. Re-installing the application may fix this problem

Any ideas? I'm practically crippled now (in the big3 department for sure) :(

[Doom9]

@RB: I never installed forceaspi after my reinstall..

[wfn1]

ok, i know how to fix it now. just place a copy of wnaspi32.dll in your scenarist directory and voila! with a regular adaptec wnaspi32.dll (4.60, 4.71.2) it displays an error 0xE but works fine and if you use nero's aspi it doesn't even display the error.