Jump to content

aarste

Members
  • Posts

    10
  • Joined

  • Last visited

aarste's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Thanks ianymaty and Cynthia, the results look good assuming low jitter % is a good thing I use 16x Verbatim MCC-004-00 so it should give equally good results from your graph benchmark at http://forum.imgburn.com/index.php?showtopic=10843&st=20&p=107615entry107615 too. I will flash to 1.3 as it came as 1.2 and give it a go tomorrow in ImgBurn. I assume I should choose MAX, or go with 24x for a test run? I normally use AWS with MCC-004-00 media ID limited to 12x to be on the safe side, but probably not necessary anymore.
  2. Just wondering what are others opinions on this matter. The highest speed media on svp.co.uk is only 16x, and I recently got a new Sony Optiarc DVD±RW AD-7241S as part of my new custom build, which can write at 24x on both -/+ DVD formats. Would you burn at 24x to a 16x disc? Or is the risk of coasters still present?
  3. I tried to burn a 4.37 GB MKV file to a DVD for storage (not for playback on a media device or such) and ImgBurn said I would not be able to fit this unless I did one of the 2 options, which I believe was to change the filesystem to UDF only, or the 2nd option - change the ISO9660 restriction to allow files to exceed the size limit. I went with the 2nd option and found that the md5 of the burned mkv file matched the one on my hard disk (which is all good). But the question is, can I expect any disadvantages from the change I made to fit this file onto DVD? Or is it just a "safety net" put in place into ImgBurn to prevent overburning or something like that? Windows 7 asked me upon inserting the disc if I wanted to treat this disc as an UDF drive or something similar which I cancelled out of, but can't seem to reproduce this prompt window again for some reason. File size of the MKV file is: 4.37 GB (4,694,314,392 bytes) Thanks
  4. Oh that's very strange, the installer must have started ImgBurn as Admin thinking it was loaded as normal user. Second attempt was to run it as Admin after reading around which didn't work, but now I know both instances were running as Admin. I can drag and drop fine now on 3rd opening of the application normally from the start menu, thanks
  5. Hello, I've clean installed Windows 7 today and was previously on XP. I've installed the latest ImgBurn and found that I can't drag and drop selected folders from Windows Explorer to the Build window in ImgBurn anymore. Is there a setting I'm missing to enable this? Thanks
  6. Sorry for resurrecting an old topic, but my LiteOn drive finally failed, as it started to read almost every DVD I had in the collection as a DVD-RW disc and being unreadable in Windows Explorer. I suspect it must have come from a bad batch as it was up to date with firmware. Prior to that failure I had to burn DVDs slightly differently, making an ISO image of the files I wanted to burn, then burn the ISO, and if the burnt disc became unreadable I cycled the tray a few times until it could be read then did a verification against the ISO image on my Hard disk, which passed all the time. But anyway, ordered a Pioneer DVR-216DBK last week and started doing some burning on that now, fingers crossed as the issue hasn't come up yet
  7. Seems ok now, burned another disc at 12x instead (Verbatim DVD+R MCC 16x) and from files on the local hard disk rather than from a network drive. 16x was probably too fast as its more than 14mb/sec on a 10/100 network, the 40mb buffer did drop a lot but didn't show any errors otherwise when I did network burn. But whatever different choice I did to burn at 12x or do a local burn made ImgBurn read it as a "I 14:50:55 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x)" for verification after cycle. ImgBurn.log
  8. here we go, did attach last time but probably got lost since the post had to be moderated
  9. I believe this has started happening since 2.4.0.0, although I'm still new to ImgBurn and only did 2 burns on the previous version which went fine. What happened is I burned an ISO and when data verification started it just threw out read errors until I cancelled it. It wasn't until I closed and restarted ImgBurn and cycled the tray again and retrying image verification comparing to the ISO on the hard drive it passed fine. Same thing happened again when I used Build mode and made a data disc of xvid movies, verification failed until I restarted ImgBurn or cycled the tray myself. I couldn't run a verification for file comparision so I just used the standard verification to check for bad sectors, which passed fine. The log of this burn is attached to the post, can't find the log of my ISO burn though. To summarise, ImgBurn wants to be restarted (or the tray cycled a 2nd time) before it can actually do data verification of my burned disc otherwise it will spit out data errors from sectors 1 to 30 (at which point I decided to cancel). Ignore the Discovery errors, that was just me thinking it was a verification check ImgBurn.log
×
×
  • Create New...

Important Information

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