Jump to content

ImgBurn and ASMEDIA 106x controller


dreamsat

Recommended Posts

As mentioned before, Nero may not rely on the 'TEST UNIT READY' command to detect if media has been inserted/is present and the drive is 'Ready'.... ImgBurn does :)

 

If you get ImgBurn working with a drive on the Intel controller (or any that actually work) and switch to Write mode, you'll notice the message in the status bar is actually the drive's response to the 'TEST UNIT READY' command.

 

Eject the disc/tray and the status bar will reflect that ('Medium Not Present - Tray Open'). Load the disc/tray and the status bar will reflect that too (various messages as the drive attempts to initialise the disc).

Link to comment
Share on other sites

Ok so I got my ASMedia chipset based PCIe card ... it works fine :/

 

I 11:58:26 Device: [5:0:0] Optiarc DVD RW AD-5280S 1.Z7 (G:) (SATA)

I 11:58:26 Family Tree:

I 11:58:26 -> ACPI x64-based PC

I 11:58:26 -> Microsoft ACPI-Compliant System

I 11:58:26 -> PCI bus

I 11:58:26 -> Intel® 6 Series/C200 Series Chipset Family PCI Express Root Port 1 - 1C10 (VEN_8086&DEV_1C10 - Intel - pci - v1.3.4.0)

I 11:58:26 -> Asmedia 106x SATA Controller (VEN_1B21&DEV_0612 - ASMedia - asahci64 - v1.3.4.0)

I 11:58:26 -> IDE Channel (ATA Channel 1)

I 11:58:26 -> CD-ROM Drive (Optiarc DVD RW AD-5280S ATA Device) (Channel 1, Target 0, Lun 0)

W 12:02:02 I/O Interface 'Debug Mode' has been Enabled!

I 12:02:03 [5:0:0] Optiarc DVD RW AD-5280S 1.Z7 (G:) (SATA)

I 12:02:03 CDB: 00 00 00 00 00 00

I 12:02:03 CDB Interpretation: Test Unit Ready

E 12:02:03 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 02 00 00 00 00

E 12:02:03 SENSE SK Interpretation: Not Ready

E 12:02:03 SENSE ASC/ASCQ Interpretation: Medium Not Present - Tray Open

I 12:02:04 [5:0:0] Optiarc DVD RW AD-5280S 1.Z7 (G:) (SATA)

I 12:02:04 CDB: 00 00 00 00 00 00

I 12:02:04 CDB Interpretation: Test Unit Ready

E 12:02:04 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 02 00 00 00 00

E 12:02:04 SENSE SK Interpretation: Not Ready

E 12:02:04 SENSE ASC/ASCQ Interpretation: Medium Not Present - Tray Open

 

The difference being, I'm running Windows 7 x64 SP1.

 

I guess I need to get XP x86 installed on a spare machine and put the card in that to test with.

Link to comment
Share on other sites

It gets interesting. I put same controller into other computer with older motherboard X48T. And there if you flash ide firmware IMGBURN works fine. If you flash AHCI firmware you've got error describing above. In ide mode no controller is visable as asmedia 106x in device tab but CDRW visable and working. No drivers needed and device shown as standart dual channel controller. That's strange because on newer motherboard Р61 there no difference between two modes and drivers always needed. XP 32bit. I will test it on X7 64 soon.

Edited by dreamsat
Link to comment
Share on other sites

My card came with the AHCI 0.89 firmware on it - that worked fine. I then flashed to AHCI 0.95 - that still worked fine. I won't bother with the IDE ones now I've seen AHCI works fine (and that's probably better).

 

Driver wise, I didn't *need* to install anything in Windows 7, it just picked it up as a standard AHCI controller. I still went ahead and installed the proper ASMedia drivers though.

 

Do you have any weird entries listed in your filter driver list on the XP machine that it didn't work with? Use the feature in the Tools menu to take a look and copy+paste the info. It doesn't really make sense that the same card/firmware/driver/OS would produce different results on different motherboards.

 

It might also be worth checking what it does when you boot into safe mode.

Link to comment
Share on other sites

How do you determine which version firmware in card? Mine not show it in post message. Maybe there is another way? I have two identical card. One I flashed other not. I can't see what version in stock card.

Edited by dreamsat
Link to comment
Share on other sites

Yes. 2 comp clean and 1 not so much. Effect the same. Maybe something wrong with xp drivers.

 

UPD: When I installed drivers 1.3.4 in win 7 64bit I had same error! This strange because you mentioned that you don't have this problem even when you update the drivers manually to 1.3.4. Controller appears in wrong section. Remove and installing drivers again solve the problem. All works perfect in W7 64bit even with 1.3.4 driver.

Edited by dreamsat
Link to comment
Share on other sites

  • 1 year later...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.