MTU.Community

MTU.Community (http://forum.mtu.com/index.php)
-   Microstudio Help (http://forum.mtu.com/forumdisplay.php?f=6)
-   -   (5) Error reading Inquiry Data for devices. (http://forum.mtu.com/showthread.php?t=6899)

DarkMagic January 26th, 2006 11:20 PM

(5) Error reading Inquiry Data for devices.
 
Error = 1. under window entitled: WnAspiNT

I bought a drive from you. Installed it in first computer. Worked perfectly with software. Then just upgraded to newer faster computer. Moved the same drive over to new computer. Installation and activation went OK, but I get this error and none of my drives are recognized anymore.

Also get following error:
(35) Error reading Inquiry Data for devices. Error =1

Then these errors repeat before program finally boots up (I have 2 dvd drives in total. I think each pair of errors is for each drive).

"Detect Drives" window is blank.

Any ideas? THanks!

kayleigh January 30th, 2006 12:58 AM

Sounds like an ASPI layer problem. Try going through the FAQ at http://mtu.com/kb/index.php?page=index_v2&id=23&c=1 and see if that helps.

DarkMagic January 30th, 2006 11:03 AM

I've tried all three solutions, plus reinstalled the latest ASUS mb drivers. Still the exact same errors when starting up Microstudio, and no drives visable. Any other ideas? This is very strange indeed. Thanks for the help.

kayleigh January 31st, 2006 08:32 PM

Microsoft has a utility available called EnumCD.exe. It will simply scan for CD/DVD drives and return their properties. This will tell you whether Windows is seeing the drive correctly. This is the information it returns; I bolded information that could indicate an error.
*EDIT*
Sorry - forgot the download link :) :
http://support.microsoft.com/default...;EN-US;Q305184

Properties for Device 1

Device ID: IDE\CdRomLITE-ON_LTR-48246S______________________SS0B____

Adapter Properties
------------------
Bus Type : ATA
Max. Tr. Length: 0x20000
Max. Phy. Pages: 0xffffffff
Alignment Mask : 0x1

Device Properties
-----------------
SCSI Device Type: CDROM Device (0x5)
Media Type : CD-ROM (0x2)
Removable Media : Yes
Product ID : LITE-ON LTR-48246S
Product Revision: SS0B

Inquiry Data from Pass Through
------------------------------
Device Type: CDROM Device (0x5)
Vendor ID : LITE-ON
Product ID : LTR-48246S
Product Rev: SS0B
Vendor Str :

CD Drive Capabilities from Pass Through
---------------------------------------
Error: 121 The semaphore timeout period has expired.

Properties for Device 2

Device ID: IDE\CdRomPIONEER_DVD-ROM_DVD-120_________________1.21____

Adapter Properties
------------------
Bus Type : ATA
Max. Tr. Length: 0x20000
Max. Phy. Pages: 0xffffffff
Alignment Mask : 0x1

Device Properties
-----------------
SCSI Device Type: CDROM Device (0x5)
Media Type : DVD (0x33)
Removable Media : Yes
Product ID : PIONEER DVD-ROM DVD-120
Product Revision: 1.21

Inquiry Data from Pass Through
------------------------------
Device Type: CDROM Device (0x5)
Vendor ID : PIONEER
Product ID : DVD-ROM DVD-120
Product Rev: 1.21
Vendor Str : 2002/12/03PIONEER

CD Drive Capabilities from Pass Through
---------------------------------------
CD Reader : Yes
CD-R disc : Yes
CD-RW disc: Yes
CD writer : No
DVD Reader : Yes
DVD-ROM disc: Yes
DVD-R disc : Yes
DVD-RAM disc: No
DVD writer : No

DarkMagic January 31st, 2006 09:55 PM

Kayleigh, thanks for your response and the link. Following is the text from the EnumCD scan. I don't see anything wrong... do you? Many thanks for your help. I didn't expect to see any problem because no other program including Nero and Soundforge have any problem writing or reading cd/dvds, so windoz must be feeding them correctly.

I have two other ideas to share:

1) Perhaps, since I used the Files and Settings Transfer Wizard to move all my files to this new computer, it may have moved some common files or registry settings having to do with MTU and the OLD drives on the OLD computer, that are conflicting with my new install on this new computer.

2) I had a system boot failure that was solved by Microsoft Tech Support, but it required a manual roll back of several days.

Perhaps the registry or some common files are messed up by this rollback and not indicating what MTU is lexpecting. Perhaps if there's a way (other than uninstall/reinstall, which I've already tried) to manually check certain settings and files, the problem could be solved.

Anyway, follows is the EnumCD scan...

------------------------------------------------------------

C:\EnumCD>EnumCD
Properties for Device 1

Device ID: IDE\CdRomPLEXTOR_DVDR___PX-716A__________________1.08____

Adapter Properties
------------------
Bus Type : ATA
Max. Tr. Length: 0x20000
Max. Phy. Pages: 0x21
Alignment Mask : 0x1

Device Properties
-----------------
SCSI Device Type: CDROM Device (0x5)
Media Type : DVD (0x33)
Removable Media : Yes
Product ID : PLEXTOR DVDR PX-716A
Product Revision: 1.08
Serial Number : 2020202020202020202020202020393734383935

Inquiry Data from Pass Through
------------------------------
Device Type: CDROM Device (0x5)
Vendor ID : PLEXTOR
Product ID : DVDR PX-716A
Product Rev: 1.08
Vendor Str : 05/30/05 14:00


CD Drive Capabilities from Pass Through
---------------------------------------
CD Reader : Yes
CD-R disc : Yes
CD-RW disc: Yes

CD writer : Yes
CD-R disc : Yes
CD-RW disc: Yes

DVD Reader : Yes
DVD-ROM disc: Yes
DVD-R disc : Yes
DVD-RAM disc: No

DVD writer : Yes
DVD-R disc : Yes
DVD-RAM disc: No




Properties for Device 2

Device ID: IDE\CdRomPLEXTOR_DVDR___PX-740A__________________1.01____

Adapter Properties
------------------
Bus Type : ATA
Max. Tr. Length: 0x20000
Max. Phy. Pages: 0x21
Alignment Mask : 0x1

Device Properties
-----------------
SCSI Device Type: CDROM Device (0x5)
Media Type : DVD (0x33)
Removable Media : Yes
Product ID : PLEXTOR DVDR PX-740A
Product Revision: 1.01
Serial Number : 303530383438373232353938

Inquiry Data from Pass Through
------------------------------
Device Type: CDROM Device (0x5)
Vendor ID : PLEXTOR
Product ID : DVDR PX-740A
Product Rev: 1.01
Vendor Str : 06/15/05


CD Drive Capabilities from Pass Through
---------------------------------------
CD Reader : Yes
CD-R disc : Yes
CD-RW disc: Yes

CD writer : Yes
CD-R disc : Yes
CD-RW disc: Yes

DVD Reader : Yes
DVD-ROM disc: Yes
DVD-R disc : Yes
DVD-RAM disc: No

DVD writer : Yes
DVD-R disc : Yes
DVD-RAM disc: No




*** End of Device List ***

horseshoe February 1st, 2006 10:46 PM

I have the exact same problem. I updated my motherboard and processor to AMD 64 and the Microstudio will not work, no matter how many aspi drivers I move around it. It shows the two error codes for each drive, and then shows up blank. Nero works great on the computer, with no problem at all.

I tried to make it work a couple of months ago, and gave up and installed it on another computer. It works well, but when I try to get it to work on this one, I get the errors. I tried to re-install it, but now I get a message that I have used up my privilages by putting it on three computers. This is very frustrating, and from the lack of support, I will probably never buy this program or any other from MTU again, even though I have used it for over 5 years, and have continually updated and bought new versions as they came out.

I too updated the drivers and bios on the motherboard (Gigabyte Technology GA-K8NSC-939) to no avail.

It isn't only the problems I have had, but from reading the forum, no one seems to even monitor them to try to help us out. Personally, I am very frustrated, but will keep an open mind (sort of) for a couple more days.

DarkMagic February 1st, 2006 11:25 PM

Yes horseshoe, I am in total agreement. Get this, when I attempted to send my problem though email, they refused to comment and said to ONLY post on this thread... so exactly WHO is doing Customer Service here?? You and me??!? If MTU is broken for AMD motherboards/CPU's then dammit, be honest and tell us so we don't lose our valuable time on lame software.

My old computer was Intel 3 gig on an Intel board. This is ASUS board and FX-60, which screams on everything else.

:m:f:c

ddouglass February 2nd, 2006 03:32 PM

Just out of curiosity, have you guys looked at the Computer Requirements for Hoster? They are way down in the list of things MTU tells you about Hoster. It specifically says "Processor (Celeron, Pentium, 3 or 4, or AMD Duron or Athlon) 800MHz or faster speed" so if you don't have one of those then it may not work.

DarkMagic February 2nd, 2006 03:36 PM

Thanks DDouglas, the FX-60 is AMD's fastest CPU on the planet right now, in fact it's the fastest multi-proc out there period. There may be some incompatibility with the newer ASUS Nvidia motherboards perhaps... just guessing. But either way, some expert advice from the people who wrote MicroStudio would be more than helpful.

Regards,
Gene

gduns - with the Lord February 2nd, 2006 03:54 PM

Are you trying to use the windows xp64 ? I know for a fact hoster will never see the driver. I have a xp64 dual core, and it works fine with it and the nvidea chipset...... as long as you are using the regular xp pro.

ddouglass February 2nd, 2006 03:55 PM

Considering the problems they have been having with getting the upgrade to Hoster out and the store accounting corrected for it, there really is only so much these few people can get done in a 24 hour period. They are not a large company with a tech support center in India answering your questions. Both of guys who can answer your questions are the same ones who are trying to correct all the various registration problems with that update.

A little patience and kindness does go a long way to getting that support.

Now to your question, yes it could be a problem with the NVidia video, but that usually would be a display problem not a drive problem. Just be sure it supports DirectX 9.0 or greater.

I think your problem is the FX-60, because it is a dual processor. I don't believe they have even looked at the duals since they are relatively new.

My opinion would be why do you need such a super duper blinding speed processor to play a wav file and display a slowly (in terms of games) changing graphics display? That's a bit like shooting a 12 point buck with a cannon! :g :g :g

gduns - with the Lord February 2nd, 2006 03:59 PM

Btw the 716 should work, but the 740 will not work. It has not got hardware cd-rw support.

DarkMagic February 2nd, 2006 04:09 PM

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 :r. 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 February 2nd, 2006 06:55 PM

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 February 4th, 2006 07:40 PM

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 February 5th, 2006 08:53 AM

1 Attachment(s)
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? :c

horseshoe February 5th, 2006 10:54 AM

1 Attachment(s)
Here is the second error that occurs, right after the first one he posted.

DarkMagic February 5th, 2006 03:11 PM

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 February 6th, 2006 10:35 AM

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 February 6th, 2006 10:38 AM

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.


All times are GMT -4. The time now is 07:08 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2009 - 2024, Jelsoft Enterprises Ltd.
The contents of this forum are copyrighted by Micro Technology Unlimited, 2000-2008. Use of any material from these Forums is prohibited without written agreement from MTU.