(5) Error reading Inquiry Data for devices.

[DarkMagic]

gduns, I didn't expect the 740 to work, which is why I xfered the 716 over... thanks. I read elsewhere that there's a lag for the latest Plextors. And no on the XP64. I'm not going near that puppy until the driver base is MUCH larger.

Hey Dd, couple things. LOL on the horsepower issue. I also do extensive audio/video editing and Photoshop work, so the extra horsepower is very needed. The dual processor should not necessarily be a problem as Windoz usually just has one proc handle non multi-threaded processes, which I'm sure MicroStudio is. Also, by Nvidia, that refers to the chipset on the motherboard, not the videocard . There have been a couple of problems with this MB in the past.

Per another post, I'm going to try the registration forum and see if I get anywhere.

Thanks,
Gene

[horseshoe]

Thanks for the reply DDouglas. I appreciate you folks trying to help us out. I am not running Hoster, I am trying to run Microstudio Karaoke Suite.

I don't have a dual core 64, only a single core one.

I am using this computer for a lot more than playing a wave file. I am in the music and graphics business and need the horsepower.

I am not running Windows 64, I am running the 32 bit version of XP Pro.

It doesn't recognize either of my drives, but they work fine in every other application. I don't believe it's video related.

I only changed the motherboard and processor, the rest of the computer is the same one that Microstudio ran on for a couple of years until my fan burned up and cooked the CPU and board.

I don't expect the engineering folks to drop everything. But I would think anyone in business would check the forums daily and a little common courtesy such as saying "we are looking at it", or "we don't have time right now, but will get back to you shortly", or "go away and leave us alone", or something would only take a couple of minutes.

It seems as if some emergency has taken everyone away from their jobs, or something. I can fully understand that too, but why not let us know?

[kayleigh]

Sorry I was away for so long...

The only other thing I can think of is to check & see if you're using the MTU ASPI drivers or Windows ASPI drivers (I think you can check this under the Tools menu). I've had better luck with the MTU drivers; They don't conflict with any other applications or the Windows system ASPI layer.

Other than that, I'm tapped :(

[DarkMagic]

Afraid I tried that fix and it didn't work. The error occurs "before" the program shell actually runs. The program appears to scan for drives first, then starts the actual program window. The error is immediate and always the same, "Error (5)" and "Error (35)" for each drive installed. The Error (5) is attached as a GIF. Quite a mystery. Appreciate the effort. I think it's time to hear from the owners who've made the money on this doncha think?

[horseshoe]

Here is the second error that occurs, right after the first one he posted.

[DarkMagic]

Horseshoe, do you know what motherboard you're using? Mine is Asus A8N-SLI Premium. I've been wondering if the chipset has something to do with this error. Thanks.

[horseshoe]

Yes, it's a nForce 3 Motherboard Gigabyte K8 Triton GA-K8NSC-939 with a nForce 250Gb chipset. I, too feel it has something to do with the MB or the chipset. The computer was working fine until I had a cooling fan burn up on the chip and it burned out, along with the motherboard socket. When I upgraded the case, I put the best Motherboard and chip I could find in it, and BANG: no more Microstudio.

[MTUSUPPORT]

There may be something with the AMD chipset systems not liking our ASPI driver.

What version of the Wnapsint.dll do you have on your computers? Also try deleting this file and then try using the Adaptec ASPI driver and see if this will get rid of the error. It is possible that our Customer drive will not work on your specific systems.