ImgBurn and ASMEDIA 106x controller
#21
Posted 24 June 2012 - 11:52 PM
Looking at the log, I see no reason why you couldn't already be in Write mode when inserting the disc. Just insert it, wait the normal 10-30 seconds for the drive to finish initialising it, then press F5 to force ImgBurn to refresh the device. That'll ignore the fact the drive was already reported to be ready and attempt to read the disc from scratch.
The reason it's not automatic is because there's no difference in the response from the drive between it being empty or not empty.
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#22
Posted 25 June 2012 - 12:17 AM
Edited by dreamsat, 25 June 2012 - 12:27 AM.
#23
Posted 25 June 2012 - 07:23 AM
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#24
Posted 30 June 2012 - 04:45 PM
I have updated firmware from the link above. Tried IDE and AHCI mode all the same. Not working, only after pressing F5 I see change.
#25
Posted 30 June 2012 - 07:37 PM
Still, I guess it was worth trying various drivers first.
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#26
Posted 30 June 2012 - 07:40 PM
Edited by dreamsat, 30 June 2012 - 07:42 PM.
#27
Posted 30 June 2012 - 09:08 PM
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).
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#28
Posted 01 July 2012 - 11:02 AM
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.
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#29
Posted 03 July 2012 - 11:46 AM
Edited by dreamsat, 03 July 2012 - 11:59 AM.
#30
Posted 03 July 2012 - 12:10 PM
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.
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#31
Posted 03 July 2012 - 12:53 PM
Edited by dreamsat, 03 July 2012 - 12:56 PM.
#32
Posted 03 July 2012 - 01:48 PM
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#33
Posted 03 July 2012 - 01:55 PM
#34
Posted 03 July 2012 - 02:25 PM
I've been meaning to but haven't got round to it yet.
Replies to posts belong in the forum where everyone can read them. Please don't PM them.
In fact, don't PM me at all unless it's something I've asked to be told about!
Before asking questions, search the forum to see if someone else already has.
Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!
#35
Posted 03 July 2012 - 02:27 PM
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, 03 July 2012 - 02:59 PM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users











