(5) Error reading Inquiry Data for devices.

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

[gduns - with the Lord]

Bryan,

Fyi The computer I loaded last week, that me and dave had talked about, it was a new athalon 64. It also worked Flawlessly. That makes 3 total I have used the MTU Programs on. This problem has to be either a bios/chipset conflict problem. I have had no problems with the systems I put the software on.

[2forU]

It won't read either of my drives, the 2nd one being a LITE-ON DVDRW SOHW-16935. I know that one isn't CDG compatible but Microstudio won't even see it.

I tried unhooking the Plextor as suggested but no change there. I don't have another Plextor to try and judging by recent comments it may not improve the situation. The only thing I can think of doing is removing the winapsint.dll, if I can find it, or trying the drive in a spare PC on Windows 98!

What's the latest Plextor CD-RW drive that is definitley compatible with XP and Microstudio please? If it's cheap enough I may invest.

Cheers.

[admin]

Drives MTU sells and supports that work with Microstudio and XP.

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

Once Microstudio is upgraded, next 3-5 months this might be fixed. If the Hoster Demo will run under your System, then the new Microstudio should work, when it is finished.

[MTUSUPPORT]

Here is the Answer from the Programmer that we purchased our ASPI driver from:

Bryan,

That particular system vendor has a defective SCSI miniport driver loaded. Specifically, it rejects the IOCTL_SCSI_GET_INQUIRY_DATA command. I recall seeing this one time before, in a log file sent by you. That is the only time I have seen it, however. Bottom line is, I will not be able to provide you with a fix for this problem, because the fix lies outside of the things that I am able to fix. Was it NVIDIA? Whoever it was, their driver needs to handle the IOCTL mentioned above, or else the ASPI Manager software will not work.

Thanks,
Don

So the only way to fix this problem will be to wait for us to upgrade Micsrostudio to the new MMC code then it should work.

[horseshoe]

If this is after our one year free update, will you still honor it for us?