Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Yes, if you use 'Read' mode. By the look of it, you've been using 'Build' mode.
  2. Maybe, you'd have to try it and see for yourself. Use Discovery mode.
  3. Again, it's an ongoing thing. I started when I was in college and studying 'Computer Science' (age 16-18). I'm now 33.
  4. Well then you've built a new image rather than reading (sector by sector) what was already on the disc.
  5. It's an ongoing project that carried on with code from DVD Decrypter... so it's been going for years now (since 2000/2001 or something). It's written in Borland C++ Builder.
  6. No it doesn't.
  7. Sorry, I don't have a list. Without modified firmware (to extend the size of each layer), I very much doubt any drive will overburn anything other than single layer discs.
  8. Using the 'Copy To Clipboard' button and pasting would have been better/easier So did you try the 'Fix It' ? What about if you uninstall the IDE/ATA Controller entry from within Device Manager and reboot? (As per the DMA post in the FAQ) If there are no drivers installed messing things up, it must be a permissions thing on the drive objects within the registry.
  9. What's in your filter driver list? Use the feature in the Tools menu to provide that info please. There's a Microsoft 'Fix It' for cd/dvd driveĀ® problems, maybe that'll fix it? http://support.microsoft.com/mats/cd_dvd_drive_problems/en-us
  10. This isn't a suggestion, post in the right place next time please. That's covered under the 'Interfering Programs' warning in the settings.
  11. Maybe the machine is just too taxed by what ImgBurn is writing to the drive and it can't then handle the OS trying to access it at the same time. That would be especially true for external drives - usb etc. I can assure you there's no 'bug' here.
  12. ImgBurn does nothing with the destination drive beyond make a file on it and use it. On top of that, I can't say that I've ever had a problem accessing the drive I'm saving a file to.
  13. Does that answer your question?
  14. http://forum.imgburn.com/index.php?showtopic=2131
  15. You need licenses to use encryption and it's pointless as they've all been broken anyway.
  16. At any shop/website that sells computer bits. You just need to buy a new DVD burner. As yours is old and IDE, I'll assume your machine is quite old too and that you'd need to find another IDE one (rather than SATA) - that makes things a little harder because they don't really still make IDE drives (you won't be able to get the latest and greatest).
  17. oh ok, yeah that's nothing to do with me.
  18. Mode 1/2048. You could try picking the other one but the program will tell you that you've messed up.
  19. ImgBurn just burns as-is, so if you have problems with playback, your source files are to blame (or the playback device).
  20. The initial spec of ISO9660 only allowed for file names in the old 8.3 format (XXXXXXXX.YYY) and you could only use 'A' to 'Z', '0' to '9' and '_' characters in the names. There is no real support for large files either so you're limited to stuff under 4GB in size. UDF has no such limitations and add supports for Unicode characters etc. UDF isn't new though, it has been around for ages now and is used on all DVD / BD Video discs. I don't really understand why 7zip chose to extract from the ISO9660 file system rather than the superior UDF one, you'd have to take that up with its author. EDIT: I just installed the 9.20 version of 7zip and it extracts my Windows 7 images ok. Weird.
  21. Your drive can't burnt DVDs at all, it can only read them. It's what's known as a 'combo' drive. If you want to burn DVDs you'll have to invest in a new drive.
  22. Sync cache is what always happens at the end of a burn. It's where the drive is told to finish performing everything it has been told to do up until that point - because don't forget, drives have an internal buffer. So even though the program may have (successfully) sent all the data to the drive for writing, the drive won't actually have tried to write it to the disc until it has finished writing everything in its internal buffer (cache). The sync cache command signals the end of the burn so anything else the drive needs to do to the disc in order to make it work properly later on is also done at that point. Your drive reported a 'Write Error' whilst trying to perform those functions.
  23. You can create new topics in forum apart from the top 5 under the 'General' heading. ImgBurn doesn't 'create' a UDF image, it just reads exactly what's on the disc, sector by sector. From what I can see (the pics aren't showing up), there's no issue with ImgBurn here. Whatever you're using to extract the files from the ISO file (7zip) is just extracting from the wrong file system. The newer OS discs don't use the ISO9660 file system, they use the UDF one. So if your extraction program only extracts what's listed in the ISO9660 file system, all you're going to get is a file saying you need to use an OS that can read UDF. Use a program that extracts from the UDF file system and you'll be fine. Of course it's pointless extracting anything from the ISO when you have the original disc and could just copy+paste the files in Explorer! You could even mount the ISO in a virtual drive program (Something like Virtual CloneDrive) and copy+paste the files that way. The OS would have no problem picking up the UDF file system rather than the rubbish old ISO9660 one. Is your version of 7zip up to date? Maybe they've fixed this problem in a newer (beta?) release?
  24. Sorry, I don't follow you. It hasn't finished zeroing the sectors, that's what's failing to complete successfully.
  25. That's 2 questions, but who's counting?! 1. There's only one. The 'Calculate Optimal' / 'User Specified' one. 2. Yes of course it's after the burn... but it's before you then attempt to actually use the disc and it checks the entire thing, not just bits that may or may not get read in the first 5 mins of trying to use it. A seemingly successful burn can still be totally unreadable - drives are funny like that. Verify checks that the drive can read back what it just wrote. Sure, even if the burner can't read the disc that it just burnt, that doesn't mean another drive won't be able to... but it doesn't exactly fill you with confidence does it?!
×
×
  • Create New...

Important Information

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