Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. If you email one of the problem files to 'support' (check the programs about box), I'll take a look at it. What OS are you running?
  2. Did you use Verbatim MKM-003-00 discs? They're what 'everyone' tells you to use, so that's what you should be using. Your drive errored out when trying to burn to the 'CMC MAG-D03-64' ones you've got there... it doesn't like them.
  3. If you use 'advanced' input mode and add that file to the disc layout, what does it list in the size column? Perhaps you could take a screenshot of the disc layout editor window so I can see?
  4. ok and what's the size of the file according to the OS?
  5. All that's happening is the program is unable to read X bytes from a file that's supposed to be X bytes in size... it's as if the file is shrinking between when the OS reports its size and when ImgBurn then tries to read it. The debug info will tell me a bit more about what's going on. I wonder if the problem is coming from Windows 8.1 trying to read that HFS partition or if it's something to do with bootcamp. I've never tried either so I can't comment!
  6. So are you saying that if you repeat that very same build operation (i.e. just click the start/build button again), you won't always get the error on the same file? Press the F8 key before you try again (to enable I/O debug mode) and then post a new log once it has errored out please.
  7. Go into write mode and go through each of your drives (in the 'destination' selection box), right clicking on said box and selecting 'Family Tree'. Close the prompts that come up and just copy + paste everything from the Log window. Make sure you highlight which drives have the problem. I can only assume they're connected differently somehow (a different controller maybe) or have PIO/DMA issues. Try unplugging the slow drives and switch them with one that's working full speed. Are they then ok? If so, that at least rules out the drive itself and then it's just down to your hardware/software configuration.
  8. Put your drive's advanced settings back to default. I.e. Force ht off, online ht off and overspeed off, smart burn on.
  9. I believe this is the issue here (and I've seen it before, see links below)... http://forum.imgburn.com/index.php?/topic/19660-2560-abnormal-program-termination/?hl=%2Bpotentialmappeddrive&do=findComment&comment=139298 http://forum.imgburn.com/index.php?/topic/17352-please-i-need-help/?hl=%2Bpotentialmappeddrive&do=findComment&comment=129311 00891148 +024 ImgBurn.exe MPShellUtilities PotentialMappedDrive 0089cef5 +03d ImgBurn.exe MPShellUtilities TNamespace.GetValid 009c5326 +012 ImgBurn.exe Virtualexplorertree TCustomVirtualExplorerTree.ValidRootNamespaceIt's not ImgBurn itself that's crashing, it's the explorer style component used on the 'Disc Layout Editor' window. I have no idea why it's crashing though, I can only assume (based on the function names) it's something to do with the drives (mapped?) on the machine.
  10. Every app has (can have) a different offer screen. I have no idea what they look like, nor which one you'll see. Should you ever get offered Google Chrome when installing ImgBurn, that offer screen may well look the same as the one you're seeing in mIRC.
  11. Do what 'everyone' tells you. 'Everyone' gives that same bit of advice for a reason! Your drive will still error out at 97% though as it simply can't burn those oversized images.
  12. If the 'sort files by source list order' option in the settings (build tab) doesn't do it, you can't.
  13. Update the firmware on the drive. http://www.firmwarehq.com/LG/GSA-4167B/files.html Clean the drive with a cleaning disc. Buy better discs.
  14. All drives support a generic command set these days and that's what ImgBurn uses. As such, all new drives are supported automatically.
  15. Yes, it's just what the drive is returning. Set it to burn at 2x and see what the average/max write speeds really are.
  16. It slows the burn down a lot (I think it just always burns at 4x or 8x etc) and the drive comes with it disabled by default. By all means play around with it but I expect you'll disable it again.
  17. Yeah, in the advanced settings.
  18. http://www.pioneerelectronics.com/PUSA/Press-Room/Professional-Products/New+Pioneer+DVD%7CCD+Computer+Writers+Loaded+with+Performance+Features+for+Exceptional+User+Experience The first paragraph may cover it.
  19. That's in the 'file' menu - assuming you haven't closed the program. You can navigate to the graph folder via the help menu.
  20. I can't say that I'm familiar with snap.do so I've no idea what would need to be removed. You have a few options.... Google 'snap.do removal' and see what comes up. Contact opencandy and see what they say on the matter. If you aren't happy the removal process fits with their t&c's, they should be told about it. Contact whoever makes snap.do and ask them how to remove it.
  21. It's a simple graph of progress against speed. If the drive doesn't burn at a single steady speed, it'll either ramp the speed up slowly as the drive burns from the inner ring to the outer ring or it'll step the speed up in stages. i.e. burn up to 1gb at 4x, then switch to 6x for 1gb to 3gb and then 8x for 3gb to the end of the disc (or layer).
  22. It comes alone if you opt out of whatever OpenCandy happens to offer you. It can vary each time you run the setup program. Anyway... You'd have to direct this question to OpenCandy... I am not OpenCandy. Simple to me would be the traditional method via 'Programs and features' in Control Panel.
  23. If it's not within a VOB file, but on a file, it just means that file will be the first thing on the 2nd layer. The VOB files sit between the IFO and BUP files, so it means there will be no transition point within them.
  24. Look at the write speed graph. I'm sure the changes you're seeing will make more sense.
  25. Put one of the Verbatim discs in the drive, switch to 'Write' mode and then bring up the automatic write speed configuration screen. It'll auto-populate the Disc ID field. Failing that, you'd probably set the speed within DVDFab itself and it'll then pass it to ImgBurn.
×
×
  • Create New...

Important Information

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