-
Posts
30,523 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
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.
-
Update your drives firmware to 2.1B and buy some decent Verbatim DVD+R DL media. The other brands are useless. http://forum.rpc1.org/dl_firmware.php?download_id=1904 If that doesn't work, buy a new drive.
-
Indeed, a write error means exactly what it says. The drive had a problem when trying to write to the disc. Change the media or change the drive. Simple as that I'm afraid.
-
Something is misbehaving and it's impossible to know what from the info you've provided. I'd need a complete log with I/O debug mode enabled before you click the 'Write' button. (press F8 to enable it). Enable it, start the burn, disable it. SAVE the log to a file and upload the file.
-
Dirty lens on the drive? Try a cleaning disc or something.
-
ok well you can't convert to that format with ImgBurn. Actually, you can't convert to anything with ImgBurn, only FROM something (when burning on the fly etc).
-
ImgBurn stop burns without any error whilw using IEEE1394
LIGHTNING UK! replied to OOO's topic in ImgBurn Support
What bit is it stopping on? Writing the leadin or when writing the actual image? (look in the log window) It wouldn't hurt if you actually copied the log to your next post so we can see what's up. The program only ever submits commands and waits for a response. If it doesn't get one, there's nothing I can do about it, it's just some glitch with the I/O interface. -
ImgBurn is just a standalone exe. If it's not running, the machine wouldn't even know it exists. There are no DLL files or drivers for it. As such, you need to look elsewhere for the cause of your problems.
-
Look on an xbox related site, this forum is for ImgBurn.
-
With that specific error, yes.
-
Mode 2 only applies to CD discs.... so I guess it's a CDROM version yeah?
-
If it's not a movie DVD, there's no IFO file to get the layerbreak info from. The physical layerbreak position of the DL media will be showing in the info panel on the right when you have the disc in the drive. Just scroll down to the bottom of the text.
-
Try the 1.21 firmware update. After that, yeah, consider them to be coasters
-
Unable to find any cells for a layer break
LIGHTNING UK! replied to Anchor1's topic in ImgBurn Support
Yeah, cells or chapters. You just really need them around the midway point - i.e. between 3 and 4GB if the image is 6.7GB -
You can't burn multiple iso images to one disc, no. An ISO is an ENTIRE disc image - even if it's actually a lot smaller than the destination media. If you want the contents of images on the same disc, extract them all somewhere and recreate the disc.
-
Unable to find any cells for a layer break
LIGHTNING UK! replied to Anchor1's topic in ImgBurn Support
You need to insert some chapters / cells so that you can split it nicely. If there aren't any in the regions that 'should' work as a layer break position, there's no way to make a proper layer break. Using other tools wouldn't get around that, they'd just be ignoring the specs if they worked. I too could just burn it and forget about correct alignment, but I decided not to. -
vade, Please don't hijack threads. Normally I'd now tell you to go make your own, but as it's pretty clear you're trying to read a protected disc, I won't bother. ImgBurn will not read protected discs and there's to be no discussion of such things on this forum, capisce?!
-
If you say you've tried 2 machines, can I assume that those machines (when running a real copy of XP etc) work fine? When under wine, what happens if you run a standalone verify? Does it always find errors in the same sectors / byte locations?
-
It would really help to see a log of you burning something. The program doesn't ever really 'hang', it just waits for your drive to finish processing certain commands and may appear to have hung. When the drive responds (be it with success OR failure), the program will continue. If the drive stops responding - or it's state never changes (as can happen when doing 'sync cache', 'closing track / session / disc'), it's normally a sign that the drive doesn't like the discs you're using. If you're not doing so already, use Verbatim or Taiyo Yuden media. They're by far the best.
-
New drive or new media... take your pick! They just aren't getting along very well at the moment, hence the error.
-
You can't burn complex images (which VCD's are) with Imgburn. Single session / track only - and that's especially true if it's an nrg file because I don't have the nrg file format specs.
-
I'm afraid not, no. I don't know how to make use of additional CLI switches to get info into my script. If you're doing this for a company, why not just stick the exe (plus other files) in a network location? Then you only need to update it in one place. You could also make a simple MSI for it and push it out that way.
-
It's '/S', not '/s' (case sensitive - lol, don't ask me why, I didn't make NSIS!).
-
ImgBurn is just an image / file burning tool. It won't make anything special for you, everything is burnt as-is.