reesboi89

Truth be told my friend, I think the reason the 2.4x didnt work first time is because I didnt manually change the booktype which I usually do and some other settings were not as they should have been. I'm very happy with the burns at 4x, they are flawless. I just wanted to see for myself if 2.4x had any kind of edge over 4x so that my mind would have definitive proof. My test involved burning the same game at both speeds to see if there was increased stability or changes in the composition. I have done that, and can safely tell everyone....there isn't. Atleast not noticeable while playing. Ofcourse one speed could produce a higher quality percentage than the other, but in the areas that really matter (playability, graphics etc.) they were both exactly the same. So there you go people, burning at 2.4x rather than 4x isn't really necessary, it's all basically dependant on your media/drive capabilites. Next week on Mythbusters........

OK, got some updates. First of all, I tried to get the burn quality program that was suggested, but it said that it was not compatable with my drive so that was out. So taking a pot shot, i tried burning at 2.4x one more, to test Lightning's thory that it was infact a fluke. It both burned and verified wihout a problem and booted in the console without fail, so I don't know whether it was a bad disc or maybe some of the settings i selected were ill-advised, but I guess on the whole it's a choice of either 4x burn and guaranteed success, or 2.4x burn and maybe some inconsistency. I will get back if I find out anything else on the matter.

YOU SO SMARRRRRRRRRT lol. I'll look into the Scan, but what you're saying makes perfect sense. If 2.4x was so superior, it would have effing worked right? I haven't had any problems making backups on 4x up to this point, but I'm the kinda guy who keeps trying to straighten the portrait to the perfect angle and all the while he doesnt notice his house burning down :)I'll update as soon as i get some results.

Actually no, I havent installed a disc onto the xbox, maybe I should try though. So there really is no difference between burning at 2.4x and 4x in terms of disc quality i.e framerate issues or graphical jaggies, and you think i should just leave it? Just to clarify like

So what do you mean by see the burn quality? It actually says how stable it is or something? And seeing as how it may have been a fluke, would you recommend round two? It's just, I've got this stupid idea in my head that even though 4x produces good burns, that burning at 2.4x would maybe make the graphics more stable if you get what I'm saying, is there really any substance to this notion?

Ha never knew that, good to find out though. Anyway, here is the log of the failed 2.4x burn. On a side note, I did try the same discs again on 4x and it did burn and verify without problems, but I didnt pay an extra 2 quid for the same results lol. So have a look for me mate. I 12:10:11 ImgBurn Version 2.5.5.0 started! I 12:10:11 Microsoft Windows Vista Home Basic Edition (6.0, Build 6002 : Service Pack 2) I 12:10:11 Total Physical Memory: 980,756 KB - Available: 364,416 KB I 12:10:11 Initialising SPTI... I 12:10:11 Searching for SCSI / ATAPI devices... I 12:10:11 -> Drive 1 - Info: TSSTcorp CDDVDW SN-S082H SB00 (D:) (ATA) I 12:10:11 -> Drive 2 - Info: Optiarc DVD RW AD-7260S 1.03 (E:) (USB) I 12:10:11 Found 2 DVD±RW/RAMs! I 12:12:32 Operation Started! I 12:12:32 Source File: C:\Users\Danielle\Desktop\mvl-dr2d.dvd I 12:12:32 Source File Sectors: 3,827,488 (MODE1/2048) I 12:12:32 Source File Size: 7,838,695,424 bytes I 12:12:32 Source File Volume Identifier: DVD_ROM I 12:12:32 Source File Volume Set Identifier: ec67c000MS UDFBridge I 12:12:32 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 12:12:32 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 12:12:32 Source File File System(s): ISO9660, UDF (1.50) I 12:12:32 Destination Device: [0:0:0] Optiarc DVD RW AD-7260S 1.03 (E:) (USB) I 12:12:32 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x) I 12:12:32 Destination Media Sectors: 4,173,824 I 12:12:32 Write Mode: DVD I 12:12:32 Write Type: DAO I 12:12:32 Write Speed: 2.4x I 12:12:32 Link Size: Auto I 12:12:32 Lock Volume: Yes I 12:12:32 Test Mode: No I 12:12:32 OPC: No I 12:12:32 BURN-Proof: Enabled I 12:12:32 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) I 12:12:32 Book Type Setting: DVD-ROM I 12:12:32 User Specified L0 Data Zone Capacity: 1,913,760 I 12:12:39 Set L0 Data Zone Capacity Succeeded! I 12:12:40 Filling Buffer... (20 MB) I 12:12:41 Writing LeadIn... I 12:12:45 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 12:12:45 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 12:12:45 Writing Layer 0... (LBA: 0 - 1913759) I 12:32:46 Writing Layer 1... (LBA: 1913760 - 3827487) I 12:53:13 Synchronising Cache... I 12:53:14 Closing Track... I 12:53:27 Finalising Disc... I 12:54:54 Exporting Graph Data... I 12:54:54 Graph Data File: C:\Users\Danielle\AppData\Roaming\ImgBurn\Graph Data Files\Optiarc_DVD_RW_AD-7260S_1.03_12-MAY-2011_12-12_MKM-001-00_2.4x.ibg I 12:54:54 Export Successfully Completed! I 12:54:54 Operation Successfully Completed! - Duration: 00:42:21 I 12:54:54 Average Write Rate: 3,154 KB/s (2.3x) - Maximum Write Rate: 3,563 KB/s (2.6x) I 12:54:54 Cycling Tray before Verify... W 12:55:01 Waiting for device to become ready... I 12:55:12 Device Ready! I 12:55:14 Operation Started! I 12:55:14 Source Device: [0:0:0] Optiarc DVD RW AD-7260S 1.03 (E:) (USB) I 12:55:14 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x) I 12:55:14 Image File: C:\Users\Danielle\Desktop\mvl-dr2d.dvd I 12:55:14 Image File Sectors: 3,827,488 (MODE1/2048) I 12:55:14 Image File Size: 7,838,695,424 bytes I 12:55:14 Image File Volume Identifier: DVD_ROM I 12:55:14 Image File Volume Set Identifier: ec67c000MS UDFBridge I 12:55:14 Image File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 12:55:14 Image File Implementation Identifier: Microsoft CDIMAGE UDF I 12:55:14 Image File File System(s): ISO9660, UDF (1.50) I 12:55:14 Read Speed (Data/Audio): MAX / MAX I 12:55:14 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 12:55:14 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 12:55:14 Verifying Layer 0... (LBA: 0 - 1913759) I 13:01:01 Verifying Layer 1... (LBA: 1913760 - 3827487) W 13:01:08 Failed to Read Sector 1913792 - Reason: No Seek Complete W 13:04:41 Retrying (1)... W 13:04:43 Retry Failed - Reason: No Seek Complete W 13:05:08 Retrying (2)... W 13:05:11 Retry Failed - Reason: No Seek Complete W 13:05:15 Failed to Read Sector 1913792 - Reason: No Seek Complete W 13:05:18 Failed to Read Sector 1913793 - Reason: No Seek Complete W 13:05:21 Failed to Read Sector 1913793 - Reason: No Seek Complete W 13:05:23 Failed to Read Sector 1913794 - Reason: Unrecovered Read Error W 13:05:27 Failed to Read Sector 1913794 - Reason: Unrecovered Read Error W 13:05:29 Failed to Read Sector 1913795 - Reason: No Seek Complete E 13:05:32 Failed to Read Sector 1913795 - Reason: No Seek Complete E 13:05:32 Failed to Verify Sectors! I 13:05:36 Exporting Graph Data... I 13:05:36 Graph Data File: C:\Users\Danielle\AppData\Roaming\ImgBurn\Graph Data Files\Optiarc_DVD_RW_AD-7260S_1.03_12-MAY-2011_12-12_MKM-001-00_2.4x.ibg I 13:05:36 Export Successfully Completed! E 13:05:36 Operation Failed! - Duration: 00:10:18 I 13:05:36 Average Verify Rate: 6,193 KB/s (4.5x) - Maximum Verify Rate: 15,898 KB/s (11.5x) I 13:05:39 Close Request Acknowledged I 13:05:39 Closing Down... I 13:05:39 Shutting down SPTI... I 13:05:39 ImgBurn closed!

Ok, just burned the new discs I bought at 2.4x. The burn went without a hitch, but horror of horrors, I got a no seek complete error during the verifying stage at around 50%. I don't have the log but it was something to do with I/O error and had a bunch of numbers on it...any sugestions?

Thanks a lot, I won't bother with the flashing then. I'll update once I have experimented. All of this will probably come in useful to some poor bastard who is having trouble will this whole process, so we have kinda wrote a detailed HOW TO guide with this entire thread, can't hurt.

Hey thanks man Yeah, spot on, I can't actually try for myself yet as they have yet to show up, so asking the pros is the next best. So in theory, can I expect to be able to burn at 2.4x with my new discs, or will I get ignored again by the Optiarc? And, is there any risks to using the program you suggested e.g hardware failure and the likes? Thanks again for your patience good man.

Ok got ya. I checked what you said and it said the media supported 4x 6x and 8x. But like I said, I have bought some 2.4x maximum burn speed Verbatims and was wondering whether the Optiarc supported 2.4x burning. Everywhere I've checked says it does but I wanted to double check. Is there any where to prevent the drive or IMGburn to not change my selected burn speed and to go with the one I stated?

Thanks for the support. I just have a quick question. Although I have had no problems burning, I have noticed that the speed is constantly set to 4x even when I select 2.4x. I believe this is because of the disc, as it says writable speeds are 4x 6x and 8x. I have purchased some verbatim 2.4x max write speed discs just to experiment. Will the optiarc burn these at 2.4x like I want, or is there something I need to do to make it respect this choice? Thanks

Right, I've been very busy lately, but I'm here as promised to let everyone know of my progress. I got the Optiarc 7260S and the caddy after a reasonably long wait (Easter holidays) and mounted it with no problems at all, aside from my huge hands not getting on with the tiny screws. Hooked it up to my laptop, and inserted the same media discs I had been using before. The booktype was automatically changed to DVD ROM which was handy, and after tinkering with all the necessary settings, I set about burning my first Xbox 360 backup. What followed was one of the most nerve racking half hours in recent memory, as my now pesimistic attitude was just waiting for some kind of bulls**t error to incite the inevitable red mist rage that would end with me assaulting someone with a Verbatim disc. But... FINALLY! It burned without problems, verified without a hitch, and when put into the console, finally released me of my scratched disc worries as it booted perfectly. I have now had hours of fun on this disc, FIFA 11 btw (awesome), and it has yet to display a single jaggy of any sort. I have burned 5 more backups since then and all have been perfect. I just wanted to thank all the people who aided me by replying to this topic, without whom I would still be crying rather loudly in a corner somewhere smashing a Pioneer 111d into my forehead. Particular thanks go to the bombshell that is Cynthia, who recommended the beautiful Sony Optiarc. I wish I had listened to you sooner lady, instead of going with what was supposedly the best drive around. So thanks a lot. One last note to anyone out there suffering with the stuff I did, pay no attention to urban myths about backup burning. Burning at speeds of 2.4x is unecessary, as I burned all mine at 4x with no problems at all. And also, don't run out and buy a Pioneer drive assuming because it worked for one person that it will for you, I made this mistake and could have saved myself a lot of grief. So do your homework first.

Cool, I don't think I will suffer from that as both the Opiarc 7260S and the caddy are pretty recent, plus this time theyare both NEW, not refurbished. I should have listened to ya in the first place and saved myself a lot of time/screaming/crying/more crying in the process by getting the Optiarc to start. I will keep you posted on my progress and updat you when the drive arrives on how it goes. Until then

So what exactly is the semaphore time out issue, and what is the percentage that it could happen with my chosen enclosure?

Fantastic news sweetheart, and thanks for the quick reply. Maybe they should call you Lightning instead . So you definately think this is the way to go and that I would get no issues? One other thing, would I need a SATA PCI card in addition to this or is it not required?