Jump to content


Beta Team Members
  • Posts

  • Joined

  • Last visited

1 Follower

About dbminter

  • Birthday 01/25/1974

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender

Recent Profile Visitors

19,173 profile views

dbminter's Achievements


ISF God (5/5)

  1. Generally, no. When discs can't be read, that's it. Optical is a generally all or nothing situation. What you might have better luck with is not a utility to recover the data but a different drive to try reading the discs in with. Try someone else's drive and see if the discs still behave the same way. If they don't AND they have a different make and model of the drive you have, you know the discs are shot.
  2. Depends on what you're trying to do. If you're just burning some MP4 files on a Blu-Ray for playing back on a PC or a BD player that plays container files like MP4, choose UDF. If you're trying to get MP4's to play like a DVD or a Blu-Ray Video disc, be aware that some BD players simply won't play them that way, particularly if you're trying to make a DVD. You need a video converter application to make a DVD/Blu-Ray Video disc. If you've got the proper VIDEO_TS or BD folders, just drag and drop those into a Build job and ImgBurn will make the necessary file system and other settings adjustments.
  3. I was more concerned about batch processing. There could probably be switches or default behavior where ImgBurn might close itself.
  4. It is possible to run 2 instances at once, but it sounds like you're burning a queue of discs or you're using batch processing. I've never done either of those before so I don't know what the behavior of the software would be in those instances.
  5. It would be highly unlikely if you received an entire cake stack from the factory that has been partially written to. So, the most likely culprit at this point is your drive. I would, at this point, invest in trying a new drive. A USB one would be easiest to set up, but most USB drives are slim models, which tend to be trash. I'd be sure to get a different make and manufacturer than the drive you currently have. One other thing I'd try, though I doubt it would help. But, it would be easier and cheaper than the above solution if it works. In ImgBurn, open Tools --> Settings --> I/O --> Page 1. Under Interface, there are a series of options you can check. Try changing these and press OK. Once the Log window refreshes to show you have the new I/O setting enabled, see if these discs still list as not empty. Try each I/O setting if one doesn't work.
  6. I forget precisely how to fix this, but I think it's somewhat along these lines. First, insert a blank DVD. I'd take a disc from the very bottom of the package, which has the highest likelihood of really being blank. Then, open the disc in File/Windows Explorer. There should be something on the screen about files waiting to be written to the disc and the option to open the folder where they're stored. When you open this folder, delete everything in it. Particularly desktop.ini or any .ini files. I think this will return to File/Windows Explorer that the disc should be treated as a blank disc. I also found these instructions. I've never done them so I can't vouch for their effectiveness: Open Run by pressing the Windows key + R simultaneously. Type shell:cd burning, and then press Enter to open the Temporary Burn Folder. Delete all the files in the Temporary Burn Folder folder. Restart the PC.
  7. Unless some files were added for writing to the disc in File Explorer and were never written to. Windows allows you to write files to a recordable DVD even after you've added some to them. If those files never were written, they're "queued" for future writing. This might explain why every time you insert a new blank DVD-R it's showing files are to be written to them.
  8. Well, it appears SOME data was written to it. In the first screenshot, just under 0.2 GB are on it.
  9. Okay, that means your discs aren't blank or your drive thinks they're not blank. Most likely the latter. Try opening one of these discs in File/Windows Explorer. See if there are any contents on these discs already. In which case, I'd just invest in a 2nd USB burner drive and connect that. Then, try again. Preferably, don't use the same model drive. Although the metadata shows 154 MB is apparently on this DVD+R you inserted.
  10. What happens when you try Read mode on one of these blank discs you put in your drive? What does ImgBurn say about the disc?
  11. "Burning files" can mean one of two things. Either you're burning an image file or you're writing files to a disc directly.
  12. What's more worrying is the screenshot is showing Unknown for key elements like Sectors, Size, and Time. An image file needs that data or it can't be burnt to a disc. Are you sure you actually opened an image file for burning to CD-R?
  13. What do you mean by "trimmed at 48579680?" Is the maximum file size 48,579,680 bytes? EDIT: Never mind. I see what you mean now. The number of data sectors reported in the .IBG file. I've never used those .IBG files, so I never would have noticed.
  14. Well, theoretically, there would be no loss in quality because PS1 games are data. However, some, I think, are kind of like mixed mode discs, with the audio tracks, music, etc. as Audio CD tracks on the disc. So, I'm not entirely sure. "Quality" for PS1 game discs, I would think, would be more measured in the quality of the CD-R's you're using to write the PS1 images to.
  15. While I have never seen that behavior you encountered with reading PS1 games, there are certain PS1 discs that can't be read by ImgBurn. It's a combination of the type of disc itself, the hardware being used, and using ImgBurn. I've never figured out what the correlation is. For instance, I know ImgBurn cannot read Mega Man 8. Both myself and others have had the same problem. The only solution I came up with for these discs is to read them with Alcohol. There used to be a free version for Alcohol, but I don't know if there is anymore.
  • Create New...

Important Information

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