CDRW & Win2k problems

[bra1niac]

Ok, check this out. I'm not the only one having an issue with a cdrw and win2k, but I haven't seen any good advice on this yet.

Running Win2k Advanced Server with a Yamaha 8824ez, 256mb ram, etc. I can only get one app to burn disks with, which is Fireburner. And it took a whole lot of ASPI driver hopping to get just that working. Adaptec works, but it's rife with problems (2:1 coaster ratio) and that's about it. I have new copies of both cdrwin and Nero sitting here, which are the preferred apps, but if either even recognize the cdrw, they burn coasters.

This is a dev box. It's not an active server, but backing up projects is absolutely vital.

Now, here's the best part. After burning a cd, it cannot be read until after a reboot. Sometimes it might take several reboots (when all else fails...). The thing is this drive worked perfectly with any burning app with winME and does great with (most) apps in linux. This I think I understand, tho. Fireburner calls for it's own dll when it's started therefore overriding the aspi drivers that ran at startup. It's a twisted situation.

What am I missing? Is there anyway I can get this back to normal? "Absorb what is useful, discard what is not. Add what is uniquely your own." - Bruce Lee - The Tao of Jeet Kune Do

 

[lgebhart]

http://www.yamaha.com/ycaservice/group001/fgrop001.htm

There is a firmware update for windows 2000 on your CDRW at the above link. Don't know if it will work, but it is a different firmware then for 95/98/Me

Good luck,

Lori ggebhart@clover.net
I hope I never get too old or arrogant to learn something new!

 

[bra1niac]

Thanks for the response. Unfortunately, Yamaha's site isn't as forthcoming as it appears. I had tried that firmware update only to find that it's the exact version that the cdrw shipped with. Upon reflection of the yamaha online documentation does it become clear that Yamaha, thru their infinite ambiguity, was trying to tell me exactly that.

I know it has to be an aspi problem, but with everyone releasing their own aspi layer drivers with their apps and Microsoft just shrugging their shoulders about the issue, it's almost impossible to find some solid documentation on it, much less fix it. "Absorb what is useful, discard what is not. Add what is uniquely your own." - Bruce Lee - The Tao of Jeet Kune Do