Microstudio will not write CDG

[Olbuffer]

I have microstudio 2.517. It has worked fine up until about a month ago. Now when I use it I get the following error message when I try to write.. Error: 'Write' command failed on device 4:0:0 Unexpected ASPI error (04h 00h 00h) .....Yesterday I tried solving the problem by following the instructions under your "List of all known microstudio error messages" - No. 6 - "Any error message dealing with ASPI" I deleted WNASPINT.dll, and then, with your help, installed Adaptec ASPI drivers per Solution #2 in FAQ. Now, my problem is that nothing shows in the Reading or Writing drive boxes in the Microstudio window and I can do nothing.

Should I try Solution #3.... reinstall Microstudio ... upgrade to a newer version?? I need your help on this. I really need to continue creating CDG's.

Buffalo Swanson Gateway 510G computer...Windows XP

[jahern]

Just a suggestion. Try going into the system folder and "removing" your burner. Then reboot. Sometimes errors that have crept in get erased that way. Good Luck

[MTUSUPPORT]

Olbuffer,
Try reinstalling the Microstudio, using the Upgrade Option to replace our ASPI driver. I had another client today that I talked to, there computer did the same thing that yours did with the Adaptec Driver. It would no longer show any drives in Microstudio, so it seems that the Adaptec drivers on some systems will not work at all.

Let us know what happens.

[Olbuffer]

Bryan, re this problem - today I reinstalled the WNASPINT.dll driver and subsequently, the Microstudio window once again showed the Plextor drive in the Read and Write Drive boxes at the bottom. Just for the heck of it, I also retried changing USB ports for this Drive.......... and once more, Microsoft started working like it is supposed to. I went ahead and created 3 discs using Custom Assembly. Two days ago, when I called, changing USB ports made no difference. Do you have any thoughts on this?

[Olbuffer]

Bryan - I meant Microstudio started working like it is supposed to.

[MTUSUPPORT]

I am not sure why this would happen. It seems that something on the computer was acting up and fixed itself. This is the only thing that I can think of.