(5) Error reading Inquiry Data for devices.

[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.

[admin]

Horseshoe, I'm sorry we haven't posted. We have had a number of unusual events ranging from Stage 4 Cancer with a mother in law, a car accicent involving a wife and 2 kids, health issues, getting a new release of Keyrite, Vogone and KHPro out right after releasing Hoster 3.301.

On top of that, we have leased a dedicated Xeon raid-1 server to move MTU.com to as our business has outgrown a Virtual Private Server with others on it. We have been trying to cut live to it for over a week now. Next attempt is right now as a matter of fact!

Moving servers will take the wind out of your sails... believe me. Moving a site as complex as MTU.com is like giving birth to a baby. I've been pacing the floor for over a week now!

You are the first to attempt to put any MTU program on this super processor.

Anything goes.

MTU has no experience with this processor, so we and others here are in the same boat... not much to go on but past experience.

The more facts you post, the more we and others here (Gduns is the pioneer trying x64) can make suggestions. That's all we can do with no direct experience on this. Facts... grease the wheels of the diagnosis machine.

There is a rule of the Universe... Cheap - Fast - Good... pick any two. As soon as we get our site moved and stable, we'll add a $20 support call item to our store for those who demand Fast and Good. Then we'll cover all customer demands.

[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.

[gduns - with the Lord]

My question would be did you reuse the existing windows installation........ or did you completely reinstall windows, and all drivers.

If you reused your previous installation, That is probably a big problem. You wont have the correct chipset drivers, and it will hive you the problems you are seeing.

I have tried this before, and it does cause problems. also there is a driver out for the amd 64 processor that should be installed. This allows the 64 bit processer to work properly in the 32 bit environment. It supports hythreading and dual core as well you can find information at planetamd64.com.

[DarkMagic]

Attached is image showing Adaptec ASPI Installation Verification. I appear to have the correct files installed for XP (see yellow highlights).

However a search does not reveal any file specifically called "Wnapsint.dll" anywhere.

gduns, thanks for your information. When I changed computers it was a clean XP install. Used Files and Folders to move everything over. Per normal operating procedure, installed latest MB drivers first thing after windoz install. Nothing else seems to have broken.

Again note that of all the programs on my computer that read/write to my Plextor drives (including the one bought from MTU) are working perfectly. Only Microstudio is not recognizing the drives when it first starts up. Just the facts, not an indictment

So what else can we perhaps look for? Anything in the registry? Does the attached GIF help at all?

Regards,
Gene

[DarkMagic]

see posts in other thread "Still Waiting...". We've covered all this and more on that one...