xileF1337 Posted April 11, 2009 Posted April 11, 2009 Helly guys, For a while now it takes an unusual long time for ImgBurn to find my optical drive(s). "Searching for SCSI / ATAPI devices..." takes 23 seconds (this is reproduceable). In the past ImgBurn found my drive immediately. Here is the log: I 11:56:12 ImgBurn Version 2.4.4.0 started!I 11:56:12 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)I 11:56:12 Total Physical Memory: 2.095.528 KB - Available: 1.430.648 KBI 11:56:12 Initialising SPTI...I 11:56:12 Searching for SCSI / ATAPI devices...I 11:56:35 Found 1 DVD
LIGHTNING UK! Posted April 11, 2009 Posted April 11, 2009 If you search for devices again (via the tools menu) does it take another 20 odd seconds? If so, press F8 and then search again. Save the log window contents to a file and upload it.
xileF1337 Posted April 11, 2009 Author Posted April 11, 2009 Wow, your responding times are incredible If you search for devices again (via the tools menu) does it take another 20 odd seconds? Yes, it does. If so, press F8 and then search again. Save the log window contents to a file and upload it. Here you are. imgburnlog.txt
LIGHTNING UK! Posted April 11, 2009 Posted April 11, 2009 Ok so basically your drive/driver is only processing 1 command per second. I 12:22:48 [1:0:0] HL-DT-ST DVDRAM GSA-H42L SL01 (E:) (RAID)I 12:22:48 CDB: 46 02 00 03 00 00 00 00 10 00 I 12:22:48 CDB Interpretation: Get Configuration - Removable Medium I 12:22:49 BUFFER: 00 00 00 0C 00 00 00 00 00 03 03 04 29 00 00 00 I 12:22:49 [1:0:0] HL-DT-ST DVDRAM GSA-H42L SL01 (E:) (RAID) I 12:22:49 CDB: 46 02 01 02 00 00 00 00 10 00 I 12:22:49 CDB Interpretation: Get Configuration - Embedded Changer I 12:22:50 BUFFER: 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 I 12:22:50 [1:0:0] HL-DT-ST DVDRAM GSA-H42L SL01 (E:) (RAID) I 12:22:50 CDB: 46 02 00 1D 00 00 00 00 0C 00 I 12:22:50 CDB Interpretation: Get Configuration - Multi-Read I 12:22:51 BUFFER: 00 00 00 08 00 00 00 00 00 1D 00 00 I 12:22:51 [1:0:0] HL-DT-ST DVDRAM GSA-H42L SL01 (E:) (RAID) I 12:22:51 CDB: 46 02 00 1E 00 00 00 00 10 00 I 12:22:51 CDB Interpretation: Get Configuration - CD Read I 12:22:52 BUFFER: 00 00 00 0C 00 00 00 00 00 1E 04 04 03 00 00 00 I 12:22:52 [1:0:0] HL-DT-ST DVDRAM GSA-H42L SL01 (E:) (RAID) I 12:22:52 CDB: 46 02 00 1F 00 00 00 00 10 00 I 12:22:52 CDB Interpretation: Get Configuration - DVD Read I 12:22:53 BUFFER: 00 00 00 0C 00 00 00 00 00 1F 04 04 01 00 01 00 Go back to the WHQL driver if you're saying that one works ok (rather than the beta you're on now).
xileF1337 Posted April 11, 2009 Author Posted April 11, 2009 Ok, I went back to v.1.17.47WHQL and everything is fine again. Thank you! What do you think, is it a bug or a feature of the beta driver? And should I report it to JMicron?
LIGHTNING UK! Posted April 11, 2009 Posted April 11, 2009 Yeah it would appear to be a bug in their latest beta driver. If you can find a way to report it to them, by all means do it! You could also copy + paste what I put above so they can see the times involved and that clearly something isn't right!
xileF1337 Posted April 11, 2009 Author Posted April 11, 2009 I have sent them an e-mail. I just hope they will not send me a generic answer asking the same questions I already answered in my mail I doubt they will answer over the weekend, but I could report back what they say if you are interested.
LIGHTNING UK! Posted April 11, 2009 Posted April 11, 2009 Sure thing, I'm always interested to hear what 3rd parties have to say about such matters
xileF1337 Posted April 21, 2009 Author Posted April 21, 2009 OK I think it is time now for a status report I sent a mail to JMicron. They answered me one day later that my mail would be redirected to a dev. This guy told me another day later that they released an update which would have fixed "delay time issues" in version R1.17.48.07. So I installed update R1.17.48.09, happy about the quick response, but I had to realize that it would not solve my problem. ImgBurn still need 23 secs to find my drive. Furthermore my optical device was regonized as a removable drive since the update Yesterday update R1.17.48.10 was released which finally fixed my problems Thanks for your help
LIGHTNING UK! Posted April 21, 2009 Posted April 21, 2009 lol when I tried .09 I got a BSOD ! I haven't plucked up the courage/found the time to try .10 yet - mainly because I'm busy with the advanced Build mode interface Glad it's working again for you though.
Recommended Posts