Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. The only way to do this nicely would be to remember the current screen resolution and to then reposition / ignore the x&y co-ordinates in the settings they're different to the last time it was run. If you tell the program not to update the settings you could just remove the position settings and then it would always auto centre.
  2. Are you sure your source VIDEO_TS folder had all the right files in it and that the DVD Video structure was valid? i.e. It would need a bunch of IFO/BUP/VOB files in it. ImgBurn is not a conversion tool so it'll only work if the files are in the correct format for your player.
  3. Have you tried chkdsk with a full bad sector scan/recovery enabled? (so it scans the entire disk surface)
  4. Sorry, I'm away at the moment (until the 19th) and can't do anything on ImgBurn.
  5. The buttons are using the standard 16x16 icons (they're taken directly from explorer.exe). If the buttons are too small for your users they can always go by the 'File' menu. Failing that, just use another program with a n00b friendly wizard interface that holds the user's hand throughout the whole process.
  6. It's only querying the drive with said drive letter (C: in this case) and getting its file system via a single API call, so if anything is confused then it'll be the OS.
  7. Most I/O is synchronous and you'll find that media player will attempt to access the drive when you put a disc in just as imgburn does. The two programs will both be waiting for the drive to respond to commands having inserted the disc and that'll be what's causing the hangup. It's certainly not anything to do with ImgBurn.
  8. It must be EXACTLY the same error in EXACTLY the same place.
  9. It's the auto retry upon the finalisation error that seems to be messing it up.
  10. Untick the 'automatic change booktype' (or something like that) in the settings on the Write tab.
  11. It shouldn't matter
  12. Sorry, it's just a Windows API function that I call with the specified size. It's failing and that's the reason Windows is reporting.
  13. On the Write tab in settings, untick the 'Finalise Disc - Auto Retry' option and the one to the right of it too (without a name/caption).
  14. What does that error say in english? The API call is failing, it's nothing to do with ImgBurn.
  15. You only need double layer discs if what you're burning requires a double layer disc! (that image doesn't) You're ok to buy DVD+R or DVD-R (i.e. both the available formats)
  16. The drive doesn't support the discs you're using. Get some 8x Verbatim / Taiyo Yuden ones. You could also check with whoever manufacturers your laptop to see if there are any firmware updates available for the drive.
  17. Try some better media. Some proper 'write once' (i.e. not rewritable) media maybe - by either Verbatim or Taiyo Yuden.
  18. Please post the log.
  19. sorry I should have said that you need Immediate I/O enabled (or rather not disabled!) when doing the F8 debug testing!
  20. You didn't burn anything going by those logs.
  21. Try doing one with 'Immediate I/O' disabled in the settings - you might get a different error code as the drive then won't return control to the program until it's finished finalising - rather than ImgBurn polling to check if it's done and detect any errors. What would be interesting actually is to capture the full error in the log. Next time you burn and it gets to the finalising bit (or just before it), press the F8 key to enable I/O debug mode. Then if you could copy+paste the chunk of the log (or save and upload), I'll take a look at it. ImgBurn *could* ignore these error at the end - which I bet most programs do - but that doesn't really solve anything. If there wasn't a problem, the drive shouldn't be reporting that there was.
  22. You might have more luck with DVD+R discs, at least they're supported up to 8x rather than just 4x. Really though you could just do with investing in a new drive.
  23. right click the drive in explorer -> properties -> tools. Tick both the checkboxes and click start.
  24. Ah, read mode... I thought we were talking about build mode. Yes the file name comes from the volume label and changing underscores to spaces has never been an option. You can still change the name to whatever you want though, it just means you have to do it manually and that'll take a minute of your time.
  25. If the program can't read from a file then you probably have an issue with your hard drive. Run check disc (chkdsk) on it and check event viewer for related errors.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.