Jswerve Posted November 6, 2007 Share Posted November 6, 2007 I 14:12:00 ImgBurn Version 2.3.2.0 started! I 14:12:00 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 14:12:00 Total Physical Memory: 1,048,048 KB - Available: 521,988 KB I 14:12:00 Initialising SPTI... I 14:12:00 Searching for SCSI / ATAPI devices... I 14:12:00 Found 1 DVD±RW! I 14:12:03 Operation Started! I 14:12:03 Building Image Tree... I 14:12:03 Checking Directory Depth... I 14:12:03 Calculating Totals... I 14:12:03 Preparing Image... I 14:12:03 Checking Path Length... I 14:12:03 Image Size: 4,681,465,856 bytes I 14:12:03 Image Sectors: 2,285,872 I 14:12:03 Operation Successfully Completed! - Duration: 00:00:00 I 14:12:31 Operation Started! I 14:12:31 Building Image Tree... I 14:12:44 Checking Directory Depth... I 14:12:44 Calculating Totals... I 14:12:44 Preparing Image... I 14:12:44 Checking Path Length... I 14:12:44 Image Size: 4,681,465,856 bytes I 14:12:44 Image Sectors: 2,285,872 I 14:12:44 Operation Successfully Completed! - Duration: 00:00:13 I 14:12:44 Operation Started! I 14:12:44 Source File: -==/\/[bUILD IMAGE]\/\==- I 14:12:44 Source File Sectors: 2,285,872 (MODE1/2048) I 14:12:44 Source File Size: 4,681,465,856 bytes I 14:12:44 Source File Volume Identifier: Grindhouse:Planet Terror I 14:12:44 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER! I 14:12:45 Source File Implementation Identifier: ImgBurn I 14:12:45 Source File File System(s): ISO9660, UDF (1.02) I 14:12:45 Destination Device: [0:2:0] SONY DVD RW DW-D22A BYS2 (D:) (ATA) I 14:12:45 Destination Media Type: DVD+R (Disc ID: CMC MAG-M01-00) (Speeds: 4x, 6x, 8x, 12x, 14x, 16x) I 14:12:45 Destination Media Sectors: 2,295,104 I 14:12:45 Write Mode: DVD I 14:12:45 Write Type: DAO I 14:12:45 Write Speed: MAX I 14:12:45 Link Size: Auto I 14:12:45 Test Mode: No I 14:12:45 BURN-Proof: Enabled I 14:12:45 Filling Buffer... (40 MB) I 14:12:46 Writing LeadIn... I 14:13:32 Writing Image... (LBA: 0 - 2285871) I 14:18:54 Synchronising Cache... I 14:18:56 Closing Track... I 14:18:57 Finalising Disc... W 14:21:09 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out W 14:24:35 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead In W 14:27:35 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out W 14:33:43 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out E 14:35:41 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead Out I 14:35:41 Finalising Disc (Last Attempt!)... E 14:40:28 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead Out E 14:40:28 Failed to Write Image! E 14:40:31 Operation Failed! - Duration: 00:27:43 I 14:40:31 Average Write Rate: 14,242 KB/s (10.3x) - Maximum Write Rate: 16,436 KB/s (11.9x) Anyone having this problem? This has always worked wonderful for me. Link to comment Share on other sites More sharing options...
dontasciime Posted November 6, 2007 Share Posted November 6, 2007 try better media or flash drive and update firmware to BYS3 or search google on crossflashing to 1635s Link to comment Share on other sites More sharing options...
Jswerve Posted November 7, 2007 Author Share Posted November 7, 2007 try better media or flash drive and update firmware to BYS3 or search google on crossflashing to 1635s I have never had a media issue with these disks. What would your recommend? Is a firmware update a pain? Link to comment Share on other sites More sharing options...
polopony Posted November 7, 2007 Share Posted November 7, 2007 Verbatim or Taiyo Yuden discs they are the best .CMC MAG we've seen so many problems with them I wish I had a penny for every time we did . Its not hard to flash the drive, download the firmware ,and there will be a flashing tool with the dl ,make sure theres no discs in the drive. With IB you can right click the drive in the destination box last line is firmware update just follow the prompts like its been said BYS3 was the latest I could find Link to comment Share on other sites More sharing options...
Jswerve Posted November 7, 2007 Author Share Posted November 7, 2007 I just crossflashed to 1635S CSOT...I'll post back with results. Link to comment Share on other sites More sharing options...
dontasciime Posted November 7, 2007 Share Posted November 7, 2007 There was a typo in my original post should have said 1633s not 1635s and I see you have flashed with 1653s CSOT which is a different drive again. 1635 firmware starts with Y [YS0Z] being latest 1633 firmware starts with B [bS0Y] being the latest and B was the original letter your Sony firmware started with 1653 firmware starts with C [CS0T] being latest 1633 and 1653 are close together but you should flash to 1633 if you can . If your drive is even recognized anymore Link to comment Share on other sites More sharing options...
Jswerve Posted November 7, 2007 Author Share Posted November 7, 2007 There was a typo in my original post should have said 1633s not 1635s and I see you have flashed with 1653s CSOT which is a different drive again. 1635 firmware starts with Y [YS0Z] being latest 1633 firmware starts with B [bS0Y] being the latest and B was the original letter your Sony firmware started with 1653 firmware starts with C [CS0T] being latest 1633 and 1653 are close together but you should flash to 1633 if you can . If your drive is even recognized anymore The drive works fine. So you are telling me to flash with 1633s BSOY correct? Link to comment Share on other sites More sharing options...
Jswerve Posted November 7, 2007 Author Share Posted November 7, 2007 Downloaded 1633s BSOY but it says it cannot update my drive because I crossflashed it to 1653s. Anyone know how to counter this? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted November 8, 2007 Share Posted November 8, 2007 crossflash to a 1633, then you can run the real 1633 firmware updates direct from liteon. The cdfreaks forum will have this covered, take a stroll over there. Link to comment Share on other sites More sharing options...
dontasciime Posted November 8, 2007 Share Posted November 8, 2007 if you managed to crossflash to 1653 use the same procedure but use 1633 firmware instead of 1653 Link to comment Share on other sites More sharing options...
Jswerve Posted November 8, 2007 Author Share Posted November 8, 2007 if you managed to crossflash to 1653 use the same procedure but use 1633 firmware instead of 1653 I got it... Link to comment Share on other sites More sharing options...
Recommended Posts