Help! WinXP Service Pack 1 + Nero 5.5.9.17 = Bad

[Vash]

Just did a clean reinstall of everything on my high end box, XP Pro, latest drivers; everything. Then I installed SP1 and tried to burn me a Utilities disk (was scheduled to repair in-laws' machine).

So, Nero freezes solid whenever I try to write anything. The app comes up just fine and I can create new compliations w/no problem, it's just when I try to write anything, it blows up - I have to *reboot* the computer because even killing the process doesn't do it. SO I downloaded the update for the newest version of Nero and install it, and I still have the same problem.


Anyone know what the problem might be? Here's my machine specs:


1.4 Tbird C
4x2x8 Mitsumi burner
ECS K7S5a mobo
Nero 5.5.9.17


In this case, I am using the mobo drivers that came w/XP. They worked very well pre-SP1, and I didn't see any reason to change it.


Thanks!

[The Baron]

ftp://ftp6.nero.com/wnaspi32.dll

Put it in C:\Windows\System32 and overwrite what's already there.

That SHOULD work...

[saturnotaku]

If that doesn't work, 5.5.9.14 has been running flawlessly on my machine. I can give that to you when you come over this weekend.

[The Baron]

Whaddoya know, I'm running 5.5.9.14 too, but I think the ASPI thing should fix it. Nero and all burning programs can get grumpy when the standard MS ASPI layer is used--when I removed and re-added the IDE controller that my optical drives are on in the Device Manager, CDex absolutely blew up. Instant crash, sometimes it hard locked, wasn't pretty. Switched out the ASPI layer, it ran fine (didn't have to reinstall CDex even).

So, that's Guess #1.

[saturnotaku]

Of course, I have the Adaptec ASPI layer installed on my system and I had that before I installed Nero so who knows if I'd be experiencing the same problems if I didn't have the ASPI layer installed. Whatever, as long as it works, I really don't care. :D

[Vash]

Thanks, I'll give this a spin. I had the MS ASPI layer installed in pre-SP1 and that worked fine, but I guess not in a post-SP1 world. Will brb, I'm gonna check this out.


Update: odd...moving the file into c:\windows\system32\ didn't overwrite anything...must test...


Update 2: no luck. I rebooted and then tried to burn me a disk, but it froze up just like before. Strangely enough, this time (but not any other time I'd rebooted - it only did this once) it threw up a memory leak error for nero.exe.

[saturnotaku]

Originally posted by Vash
Strangely enough, this time (but not any other time I'd rebooted - it only did this once) it threw up a memory leak error for nero.exe.

Then I'd have to point my finger at a problem with the software itself. I'll hook you up with the older version I'm running now. If 5.5.9.14 doesn't work for you, I have 5.5.8.2 handy as well, which didn't give me any trouble when I had the M$ ASPI layer installed.

[The Baron]

Maybe this then?

http://www.adaptec.com/worldwide/support/driverdetail.html?sess=no&cat=/Product/ASPI-4.70&filekey=aspi_v472a2.exe

[Vash]

Nope, no dice. I think that Ed's probably right - it's probably the program's fault.

[VeritechK7]

5.5.8.x loaded up faster for me than the 5.5.9.x

[eL_PuSHeR]

I thought Nero had its own internal aspi layer. I'm running Nero 5.5.1.17 under WinXP SP1 with no problems (No adaptec ASPI layer installed, btw). ONE WORD of advice though: You have to uninstall a previous version first even if the updater doesn't complain. Other than that, you'll run into problems.

[Vash]

Hmm, that may be the problem. Though Nero didn't work on a clean install of WinXP SP1, whatever that means. I'll try a clean reinstall and see what happens.