abachmann Posted April 28, 2009 Posted April 28, 2009 Hi, I am using Imgburn for a long time now ... without any problems ... until now :-( Every BR iso stops burning at different positions ... example (see also attached screenshot): I 10:01:40 ImgBurn Version 2.4.4.0 started! I 10:01:40 Microsoft Windows Vista Ultimate Edition (6.0, Build 6001 : Service Pack 1) I 10:01:40 Total Physical Memory: 1.831.688 KB - Available: 1.061.304 KB I 10:01:40 Initialising SPTI... I 10:01:40 Searching for SCSI / ATAPI devices... I 10:01:40 Found 1 BD-ROM and 1 HD DVD-ROM/BD-RE! I 10:02:33 Operation Started! I 10:02:33 Source File: E:\output\xxxxxxxxxxxxxxxx.ISO I 10:02:33 Source File Sectors: 9.122.464 (MODE1/2048) I 10:02:33 Source File Size: 18.682.806.272 bytes I 10:02:33 Source File Volume Identifier: xxx xxxxxxxxxxxx xxx I 10:02:33 Source File Volume Set Identifier: 3A998C6F008B3222 I 10:02:33 Source File Application Identifier: ImgBurn v2.4.4.0 I 10:02:33 Source File Implementation Identifier: ImgBurn I 10:02:33 Source File File System(s): UDF (2.50) I 10:02:33 Destination Device: [2:0:0] HL-DT-ST BD-RE GGW-H20L YL05 (F:) (ATA) I 10:02:33 Destination Media Type: BD-R (Disc ID: VERBAT-IMa-00) (Speeds: 2x; 4x; 6x) I 10:02:33 Destination Media Sectors: 12.219.392 I 10:02:33 Write Mode: BD I 10:02:33 Write Type: DAO I 10:02:33 Write Speed: MAX I 10:02:33 BD-R FastWrite: No I 10:02:33 Link Size: Auto I 10:02:33 Lock Volume: Yes I 10:02:33 Test Mode: No I 10:02:33 OPC: No I 10:02:33 BURN-Proof: Enabled I 10:05:26 Filling Buffer... (40 MB) I 10:05:26 Writing LeadIn... I 10:05:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 9122463) I 10:05:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 9122463) Operating system: Windows Vista SP1 (all hofixes) ... virus scanner installed an up to date drive: HL-DT-ST BD-RE GGW-H20L with latest firmware Y05 i have tried different ISOs everything worked until I updated to 2.4.4 :-( I have to kill Imgburn from the taskmanger ... and the drive is locked until I reboot the pc ... (maybe I don't wait long enough) =============================================== Filter Driver Load Order - ImgBurn v2.4.4.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: [None Found] Lower Device Filter: [None Found] Any ideas ? Thx Andreas
mmalves Posted April 28, 2009 Posted April 28, 2009 Make sure you have the latest drivers available for the SATA controller where the drive is connected to. Also please post your Filter Driver Load Order (look in ImgBurn's Tools menu).
abachmann Posted April 28, 2009 Author Posted April 28, 2009 Make sure you have the latest drivers available for the SATA controller where the drive is connected to. Also please post your Filter Driver Load Order (look in ImgBurn's Tools menu). Filter Driver Load Order ist already posted ... look above I will double check the drivers ... I updated the southbridge drivers yesterday ... but still the same problem
LIGHTNING UK! Posted April 28, 2009 Posted April 28, 2009 Do you have any other burning software installed? Do you have any virtual drive programs installed? What does the status bar say when you attempt to Cancel the (hung) burn normally? (rather than terminating it via taskmanager). Does the same happen with a Verbatim BD-RE?
abachmann Posted April 28, 2009 Author Posted April 28, 2009 Do you have any other burning software installed? Do you have any virtual drive programs installed? What does the status bar say when you attempt to Cancel the (hung) burn normally? (rather than terminating it via taskmanager). Does the same happen with a Verbatim BD-RE? i had no other burning software installed ... but now I installed nero 9 to give that a try virtual clone drive is installed I am not really sure if there is any change in the status bar ... can't remember ... and it's a little bit expensive to try again ;-) DB-RE worked fine ... but only one test
LIGHTNING UK! Posted April 28, 2009 Posted April 28, 2009 What you have to know/understand is that once the burn has started, all the program is doing is issuing the same 'WRITE (10)' command over and over again. This is the same for all types of media. It's impossible for me to say why your machine decided to hang, sometimes these things just happen.
Recommended Posts