Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. With buffering etc the physical layerbreak on the disc shouldn't be a problem when playing avi files.
  2. You have to run it with those switches every time if you want it to use them.
  3. This entire thread is a bit
  4. Post a log of you burning (with Verify enabled) a disc you then wish to play on the PS2. Does your PS2 actually display a message when you insert one of the burnt discs?
  5. Ok, I'll look into it in a couple of days when I return from my holiday
  6. ImgBurn would burn such a file 'as-is', so any problem with playback comes from your player. For help with other software, please visit their own forums.
  7. Extract the files from that image and build it again with ImgBurn via Build mode.
  8. I've run all the images / udf versions ImgBurn can create through that tool before and they're fine. It doesn't change the FSD File Set Identifier text because it's not a 'volume identifier' - the name kinda gives that away.
  9. Sorry, I have no interest in supporting that technology.
  10. Does it actually burn + verify ok? Post the full log please.
  11. Are you using 2.4.2.0?
  12. This is nothing to do with UDF or windows, it'll be because your drive has made a duff burn on the disc and now the drive can't read it back.
  13. You have to tell it not to use runtimes or dynamic links.
  14. yup, c++ builder and my two hands.
  15. Don't enable debug mode until you're at the point (well, just before) where you know it's going to freeze. Keep an eye on the status bar in the main program too and tell us what it says when it gets stuck.
  16. If ImgBurn finds the LB position in Write mode then you can just burn it without any messing around, it'll be fine.
  17. If you can't see the file in the browse window then you've probably got the file extension set to something ImgBurn doesn't support. Try changing the 'file types' dropdown box to show all files (*.*) If that doesn't work, drag and drop the iso file onto the 'Source' groupbox when you're in write mode.
  18. It probably means you've got a picky (old) drive.
  19. 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.
  20. 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.
  21. Have you tried chkdsk with a full bad sector scan/recovery enabled? (so it scans the entire disk surface)
  22. Sorry, I'm away at the moment (until the 19th) and can't do anything on ImgBurn.
  23. 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.
  24. 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.
  25. 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.
×
×
  • Create New...

Important Information

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