dbminter

Actually, I just discovered that .CUE files are basically text files. I just needed to change a label field because of a typo. So, I'm guessing I can just edit the file in Notepad, change the text with the typo, and save it and everything should be okay?

Is there a way to edit .CUE files of Audio CD's created by ImgBurn? I tried Cuemaster, but it's really old plus it didn't work. Said Multiple FILE statements not allowed.

I was writing an image to a DVD+RW. It was new and hadn't been formatted yet, so the write first started by formatting the disc. While it was doing that, I turned on my LiteOn Lightscribe USB drive to write a label on a Lightscribe surface DVD-R. After the formatted completed, the write never started after the format due to some kind of Device not ready error. There was no entry in the log and I didn't write down the window of error dialog text, so I'm not sure what it was. I'm guessing this is most likely caused by the detection of new devices, right? I just started the write again and the SATA drive then wrote correctly to the disc.

This sort of goes hand in hand with my past post about the 99% erasing/formatting length of time. The Finalising of a disc starts at like 2% and then goes up in incremental values. Then, when it gets to 99%, it stays at 99% for quite some time on most drives I've seen. (My USB LiteOn seems to go really fast at 99% versus my SATA drives I've used in the past.) So, I was wondering what it's doing at 99% of Finalising that might take so long.

Looks like the drive does need to be replaced. Now, I'm getting the same error twice in a row on DVD+R DL's. It writes 8x Verbatims at 8x for layer 0, then speeds down to 4x and stays there for layer 1. Then, on Verify, it fails exactly at the layer transition. E 19:38:13 Failed to Read Sector 2049106 - Reason: Timeout on Logical Unit I'm making a 3rd write of this image to a 3rd Verbatim DVD+R DL from the same cake stack in my USB LiteOn. I'll know for sure if it burns and verifies successfully on that. Write's completes on the USB LiteOn. It's an older drive and I never really used it for writing DVD+R DL's before for DVD Video. At layer 1, it drops at one point from 8x to 6x then towards the end of the burn drops down to 4x. I've seen it drop down to 4x on layer 1 towards the end of some burns of DVD+R DL before, so it's not unexpected. Let's see how the verify goes. Well, Verify passed the layer transition. And, the Verify completed. So, I'm going to replace the drive.

Wait, if DVD+RW are already formatted, how come whenever I insert a new DVD+RW, it says it needs formatting? Or does it say erasing?

Actually, I've seen that on every drive I can remember that I've used to format a rewritable disc.

Whenever a disc needs to be formatted, the percentage complete jumps to 99% and stays there for the entire length of the format. What exactly is it that takes so long at 99% to complete a format?

So, there is, in fact, not a Write LeadIn for DVD+RW?

Is there a longer Writing LeadIn time between DVD-RW and DVD+RW? I seem to recall that when writing images to DVD-RW, there's a measurable period of time during the Write LeadIn phase. On DVD+RW, though, I think the Write LeadIn occurs almost instantaneously, if there even is a LeadIn on DVD+RW. Have I just imagined this or are there differences in the times in Write LeadIn on DVD-RW versus DVD+RW? Or is there not a Write LeadIn on DVD+RW? I'm no expert on the subject, but I'd have to think there must be some kind of Write LeadIn on both media. I'm not sure, though.

In a restructuring attempt to save the company, Sony is selling its PC division. I say good riddance! I've only had 2 good Sony experiences in the PC realm. I got a VAIO monitor in 1997 that lasted for about 6 years and I liked that monitor. I also got in on the ground floor of its DRU dual format DVD burners, the 500 A. I also had the 700 A which died after like 2 months, the beginning of Sony's decline in quality. I then had 2 other DRU drives before they exited that market. Sony then bought up Optiarc and the quality of the drives plummited. Then there was the BD-RE I had that died after 5 writes! Sony had some early quality experience with the Playstation, but has driven the quality of that brand into the ground. The PS 1 was fine. The PS 2 started out fine, but they gradually removed features and switched back to the PS 1 style top loading system. The tray system was adopted in the PS 2 exactly to fix the issues the top loading disc design caused. Sony then got cheap and replaced the tray system because the top loader was cheaper. Then came the PS 3, minus backwards compatibility and the infamous removal of features customers paid for. So, my love for Sony no longer exists. The PS 1 was my first real experience with Sony and it was a joy. The early years of the PS 2 were even better. Then, Sony just got to be a cheap ass and I don't feel sorry for their financial woes at all.

That article is almost 4 years old, though. It says that as devices and drivers mature, the speeds should improve. By now, that article's information is probably obsolete.

I will try to remember to do such things next time I encounter a read.

I don't think it's RipLock because I've had 2 different LiteOns on this channel that did the same thing. Plus, sometimes, DVD Video on a DVD-5 reads to an image file in like 5 minutes and sometimes 10. However, they were both LiteOns, so it could be a lock across the board on LiteOn. But, there doesn't appear to be RipLock on the USB LiteOn, then, so, that probably can't be the case. Plus, the application can make a difference, too. For instance, I no longer read DVD-9 DVD Video with ImgBurn. I use AnyDVD instead because AnyDVD tends to read them in at a faster rate. A DVD-9 takes about 30 minutes in ImgBurn on the SATA LiteOn. In AnyDVD on the same drive, it takes about 15. For instance, yesterday or the day before, I had an unprotected DVD-5 DVD Video disc that was pressed media. ImgBurn on the SATA LiteOn wanted to take 10 minutes to read it. I inserted it into the USB LiteOn and it read it in in 5 minutes.

Unfortunately, it's not consistent. I insert discs into the SATA drive and check the supported read speeds. Sometimes it's higher than other times. Usually, it's a difference of about twice the speed. And read time tests bear this out. The USB drive is about twice as fast. There's no real reason to it. Sometimes the SATA drive is twice as slow as the USB and sometimes it's not. Plus, the type of source seems to make a difference. For instance, a DVD Video, even when not protected, reads slower than a disc that is just data, even though, technically, a DVD Video disc is just data, too. It makes no real sense, actually.

I've noticed something lately in my Read speeds. I'm getting faster Read speeds on my USB 2.0 LiteOn versus the SATA LiteOn. I've had 2 different SATA LiteOns in the same bay on the same SATA channel and I still get faster Reads on the USB. I would think SATA is faster than USB 2.0, but according to my results, it's not. Am I wrong? It's been like this for about a year now.

I didn't know a Verify was just a Read operation. Good to know! This drive is an older drive. It's ID string returns it as a possible 2009 model. It came new with my Dell in 2011. I never used it. I removed it and replaced it with one I wanted instead. So, it sat in a cool room in my old PC case for 3 years before I opted it in. Only reason I'm using it and not replacing it with something newer is I'm cheap! Plus, I don't want to start trying replacement drive brands until I need to as I no longer trust LiteOn for new drives. If the option is checked, though, a Verify still compares against the image contents, right?

BTW, part deux, is USB 3 still slower than SATA? Is eSATA faster than USB 3?

Came across this a week or 2 ago. I had a burn where the Write completed and the Verify passed with no errors. I then right afterward tried Reading that disc to an image file but it failed to Read at the layer break. I wish I had thought about it at the time so I could post an appropriate log section for the actual error. I was just wondering how a disc that passes a burn and a verify can fail at a read. But, I think I remember something else, though, that paired it down to the drive I was using for the Read. I tried Reading the disc in the same drive that burned it and it read it just fine. I just reburned the disc again to test it and it Read file in the LiteOn I was trying to use as the reader before. Even though it's most likely down to the drive, I still find it rather odd that a disc can pass Write and Verify and then fail at a Read. I think it might have even been what convinced me to replace my old Lightscribe LiteOn. But, I don't know if had already replaced it or not before then.

So, I'm guessing DVD Video uses the 1988 standard since DVD Video was introduced around 1996, just before the 1999 standard could be introduced.

BTW, what happens when you have a mix of USB 2 and USB 3 devices connected at the same time to a USB 3 bridge? Does it affect the speed of the USB 3 device so it only reads/writes at USB 2 because of the connected USB 2 device.

I had an image created by Macrium Reflect of its recovery environment. I edited it with UltraISO to add some folders. When I loaded the image in ImgBurn to burn, I noticed I could edit the ISO9600 label field to have a : and spaces. I thought ISO9660 was no special characters like colons and no spaces, using underscores instead. I also noticed there are apparently 3 different options for ISO9660. The one selected was DOS. Is the ISO9660 for DVD Video images something else that doesn't allow these characters and is therefore different? My only real experience with ISO9660 label fields is for DVD Video and these Macrium Reflect images. I just never tried changing the ISO9660 field before for these Reflect images.

Burned a second Verbatim DVD+R DL in the same drive and it burned and verified fine. So, must have been just the one disc in the stack.

Never came across this error before: I 12:12:48 Finalising Disc... W 12:12:58 Potential 'WaitImmediateIO' Deferred Error - (14%, 0/3) - Session Fixation Error Writing Lead In W 12:12:58 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead In W 12:12:58 Retrying (1 of 3)... W 12:13:08 Potential 'WaitImmediateIO' Deferred Error - (10%, 0/3) - Session Fixation Error Writing Lead In W 12:13:08 Retry Failed - Reason: Session Fixation Error Writing Lead In W 12:13:08 Retrying (2 of 3)... W 12:13:11 Potential 'WaitImmediateIO' Deferred Error - (0%, 0/3) - Session Fixation Error Writing Lead In W 12:13:11 Retry Failed - Reason: Session Fixation Error Writing Lead In W 12:13:11 Retrying (3 of 3)... W 12:13:19 Potential 'WaitImmediateIO' Deferred Error - (7%, 0/3) - Session Fixation Error Writing Lead In W 12:13:19 Retry Failed - Reason: Session Fixation Error Writing Lead In Could it be something with the drive going bad? It's been over a year now and my LiteOns lasted about a year. This is an LG, though, so, I don't know how long I'll get with one of these. I'll try burning another DVD-9 and see if it's the drive, i.e. if I get this error again. Could be the one disc in the stack, but, I'm still using the Verbatims that worked on Monday.

LUK, this is a dumb question but how is ImgBurn pronounced? ImageBurn or I M G Burn?