(5) Error reading Inquiry Data for devices.

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

[admin]

Originally Posted by DarkMagic

Guess we'll have to just watch and wait... (Moody Blues anyone??)

What are you waiting for? We have made it clear that we can't create your problem, thus we can't solve it. A problem exists with AMD processors and something else on your systems. As Gduns has proven, others are running fine with AMD.

Factless complaints won't help anyone diagnose your problems.

Originally Posted by admin

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.

If you post facts about your systems in this Thread, we MIGHT be able to diagnose what is unique about them.

We are working on Microstudio 3.0, which will have completely new drive interface code. That may solve your problem, but we'd know better if we have facts about your systems so maybe we can diagnose what is wrong.

If you really want our help, post facts. I will delete further factless complaints.

[2forU]

I have provided facts before but here are more. I built the PC myself and did NOT use the settings and transfers wizard. All drivers to the best of my knowledge are up to date

OS: XP Professional (5.1 Build 2600)
System Manafacturer: NVIDIA
Model: AWRDAXCPI
BIOS: Award Modular BIOS v6.00PG
Processor: AMD 64 3500+, MMX, 3DNow, 2.2GHz (Venice)
1024MB RAM
Page file 42MB used, 2037MB available
DirectX: DirectX 9.0c (4.09.0000.0904)
Display: ATI RADEO X600 series
Optical drive: Plextor CD-R PX-W1610A
IDE ATA/ATAPI controllers: NVIDIA nForce4 ADMA Controller, NVIDIA nForce Parallel ATA Controller
Motherboard: Gigabyte GA-K8NXP-9 socket 939 Dual Power System PCI-E DDR400
ASPI drivers: ASPI32.sys v4.71.2, WOWPOST.exe v4.6 (1021), WINASPI.dll v4.6 (1021), WINASPI32.dll v4.71.2
Plextor drivers: Plextor_W1610A105.exe - 5.1.2535.0
NVIDIA drivers: nForce4_amd_6.70_winxp2k_english.exe - 5.10.2600.507

If there's anything else I can provide, please do let me know as I want to help anyone out there find a solution to this.

Thanks

[MTUSUPPORT]

With such a new system, you are using a Plextor drive with the latest firmware version dated 2002.

Do you have any other drive in the system, other than the Plextor 1610? If so maybe just unhook the Plextor and see if it will open with a newer drive attached in the system, not that it would work for CD+G, but see if it will open.


Can everyone having this problem post which Plextor drive you are using, and the Firmware installed on it?

[DarkMagic]

Originally Posted by admin

What are you waiting for? We have made it clear that we can't create your problem, thus we can't solve it. A problem exists with AMD processors and something else on your systems. As Gduns has proven, others are running fine with AMD.

Factless complaints won't help anyone diagnose your problems.


If you post facts about your systems in this Thread, we MIGHT be able to diagnose what is unique about them.


If you really want our help, post facts. I will delete further factless complaints.

Well now, thanks for your help there... I just saw this post tonight. I believe you've already read all the information I've posted elsewhere. I've followed EVERY suggestion you've made. I've posted a TON of GIFS showing every possible setting on my computer, in the drivers, and in the drives.

Why don't we consolidate all my info right now and reply only to the posts on the topic "Problems with AMD64 and RAID drives...et al". That's where I've been looking lately and it seems to have the most "informative" posts from everyone with this problem.

Sorry I didn't see this earlier, I might have gotten all emotional too

Regards,
Gene

[Glen Conaway]

I am experiencing the same problem, I have also tried to install all the different drivers recomended.
I have an AMD processer with a raid controller card with a raid 0 array that stripes 2 hard drives.
These 2 hard drives are my local (C) drive.
I have a Gigabyte motherboard (GA-K8NSC-939).
I expericend this problem with my old version of microstudio version 2.103, so I updated to the latest version (2.612), thinking it would solve the problem, but not so.
The strange think is that my old computer was a Asus A7V with a onboard raid controller configured to a raid 0 array as the local (C) drive, and the old version, (2.102) worked fine. My old computer had a AMD 1600 XP processer.
My old computer shorted out and got fried so I had to totally build a new computer salvaging only the case. Now I can't install Microstudio, everything else on my computer works great and it is a fresh install.

Help appreciated,
Glen Conaway

Check out my thread at:
http://forum.mtu.com/showthread.php?t=7351&goto=newpost

[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

[gduns - with the Lord]

Just for the Heck of it, Which version of microstudio are you using?

[DarkMagic]

version 2.612

[gduns - with the Lord]

That Is the same I am using. did you set that ide to Dma (vs PIO)..... dont know much more to say.

[DarkMagic]

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

[2forU]

I too have tried just about everything I can think of. I'm no techwiz but I have updated ASPI drivers, Plextor Drive firmware. Nvidia motherboard chipdet drivers, uninstalled Microstudio (and Nero/InCD just in case of a conflict) and I really am at a loss as to what to do now. I've been looking around at alternative software on the web and although there are ways of riping/burning CD+G files easily with ANY optical drive, Microstudio along with Keyrite does make it easy and convenient for my purposes.

I also upgraded to version 2.612 and paid extra for the privelege of it not working - well it was worth a try - and changing the APSI drivers to MTUs does not help either.

This was my earlier attempts at answers - http://forum.mtu.com/showthread.php?t=3134

What else have I got that may be conflicting? MusicMatch Jukebox? That's about it really. All the rest refer to my DVD drive and not my PX-W1610A.

Pleeeeeze can you come up with a solution?

Athlon 64 (Venice) 3500+ on XP pro with SP2 here, just in case it helps.

[DarkMagic]

Guess we'll have to just watch and wait... (Moody Blues anyone??)

Regards,

Gene