-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
Looks like you're getting corruption on the entire bus. Change your cable (make sure you replace it with a decent 80 wire one). Put the drive on 'MASTER' and attach it to the end of the cable (the other end being attached to the motherboard of course!). Check your bios setting to make sure UDMA is enabled properly and finally, follow the DMA post in the FAQ.
-
Optical drives are never really 100% when hooked up to 3rd party controllers. Some do work much better than other though and some don't work at all. You've probably got a jmicron controller on your board, that's what most motherboard manufacturers use. What you need to do now is look in 'Device Manager' and find out exactly which chipset / model it is. If you open up the 'SCSI and RAID controllers' branch, you should see it listed in there. (If it's not in that one, look under 'IDE ATA/ATAPI controllers') Tell us what you see (or provide another screenshot of device manager with those branches expanded) and one of us will hunt out the latest drivers for you. They might just fix the issue if you're lucky! That is of course assuming it's *something* to do with that in the first place. It could just be a bad drive/media/write speed combo. I've no real experience of the 8x Verb DL discs, I always buy the 2.4x ones and they burn ok in my Pioneer 112.
-
Have you tried burning at any of the faster speeds the drive supports? The 965 chipset doesn't support the legacy IDE ports/connectors now so you're running the drive on a 3rd party controller. It might be an idea to visit the website of whoever makes it and look for some updated drivers.
-
No. Don't think of the layers as individual data containers or 2 different discs stamped together, they're not. To the software, it's all one big disc really. There's nothing to say a file won't cross (span) the physical layer break - i.e have some of it's data on the first layer and the rest on the 2nd. When you address the sectors of the disc, they just go up in sequence from the start of layer 1 to the end of layer 2. i.e. Start of disc (LBA): (start layer 1) 0, 1, 2, 3.... 14, 15.... (switch to layer 2).... 16, 17, 18... 29, 30, 31 (End of disc). All in all, the disc goes from LBA 0 to LBA 31, with the phyiscal layer break position somewhere inbetween.
-
its pocible burn multiple DVD's at the same time ?
LIGHTNING UK! replied to animepowa's topic in ImgBurn Support
If the hdd can keep up with the random access reading, yes. As you say, just open 2 instances of ImgBurn. -
You're trying to do something that simply isn't possible! If you have an ISO file and only want *some* of it's content, it's down to you to remove it. ImgBurn simply burns exactly what it's given. Mount the ISO in DAEMON Tools or something and then just drag over the folders you want on the disc into the 'source' window. I suggest you put the options on the 'Media' tab back to their default values.
-
Your drive simply isn't burning the discs properly. Maybe it's time to ditch that old one and invest in something up-to-date?
-
It's not infinite. There's a little fall back mechanism where if one variation of the command fails, another one is attempted. In the generic I/O error boxes, there's no way to differentiate between you telling it not to retry the same command (i.e. 'cancel'), or to totally give up. Depending on exactly which command you 'cancel', there should only be a few extra (slightly different) attempts at that specific function (be it closing the track, closing the session, closing the disc etc). Just don't have any failures and it won't be an issue! It's certainly not one for me.
-
The 'Media' tab has nothing to do with anything.
-
You're getting EXACTLY the same error? Have you not tried the 1.21 firmware yet?
-
ASPI is old now and ImgBurn doesn't use it, it uses SPTI instead (which is built into Windows). If you build an image rather than doing it on the fly (and then burn it), check and see if a manual verify returns errors in the exact same place - repeat the verify a few times, maybe even in different drives if you have access to any. Check and see if you're always getting errors in the same sector etc on multiple burns. Look for patterns basically!
-
Did I choose the correct DL layer break?
LIGHTNING UK! replied to DjKilla's topic in ImgBurn Support
If you look at the LBA column, you'll see that 4 and 5 are essentially the same thing, just different representations of it. What you need to remember (or learn!) is that the order of files goes... IFO -> VOBs -> BUP, (next VTS set) IFO -> VOBs -> BUP, (next VTS set)...... So by putting the IFO at the start of the 2nd layer, it's exactly as Blutach says - 'having the whole of VTS3 (and higher VTSs) on a single layer' - whereby 'single layer' is of course the 2nd one. -
If the flag is set to show the burn failed, it'll now prompt before performing sync cache and the finalise disc commands (subject to further testing). I'm not so sure it's a good idea because drives can get confused if a write operation doesn't finish off properly and you just end up with loads of 'command sequence error' errors.
-
DMA is covered in the FAQ.
-
You cannot use ImgBurn for that, license an SDK off one of the big players.
-
Did I choose the correct DL layer break?
LIGHTNING UK! replied to DjKilla's topic in ImgBurn Support
I'd be inclined to go for the 3rd one down, but it's really not a big deal. -
I'm not so sure that's true. If it errors out, you can abort it. This is a program suggestion more than a bug. I'll move it for you.
-
A few questions about device buffer and burning issues
LIGHTNING UK! replied to Nekki's topic in ImgBurn Support
Unless you have DMA issues, there's nothing to fix. -
The program that submits the write commands shouldn't make a difference. The only thing it can be if 'FreeEasyBurner' REALLY does always work 100% of the time and ImgBurn always fails is that it's using the Packet/Incremental write type rather than DAO, which ImgBurn defaults to. Either way, it's still a drive issue. Both write types should work, or both should fail. Just try changing the 'Write Type' setting to Packet / Incremental in ImgBurn's settings. Of course the media is the root cause of your problems and as everyone has already said, you should ditch it and start using some good stuff. Don't ever go by the brand name, it doesn't mean anything.
-
Just because the Verbatim disc works doesn't mean you should forget about the firmware update. The drive being up-to-date firmware wise is a very important part of the burning process.
-
You didn't need I/O debug mode on, it's only useful when I actually ask for it. That aside, you can see the error there... 'Das Zeitlimit f
-
If the original isn't mode 2, I don't see why you'd ever need to convert it. If it IS mode 2, just read another image from your original. One of the ISO editing utils might be able to convert it. I could tell you how to do it manually but you'd be there all year editing every sector!
-
It doesn't appear to be reporting the disc info properly. Notice it says 'Status: Complete' rather than 'Status: Empty'. Try looking for a firmware update for the drive.
-
Put ImgBurn back on the SPTI interface. When you've done that and have burnt another disc (or at least tried to), post the FULL log (from that burning session).
-
The only thing that can cause power calibration errors is the drive/media combo. As you're already using the best media available, it's pretty much got to be the drive.