Jump to content

Protee

Members
  • Posts

    3
  • Joined

  • Last visited

Protee's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Alright. Will look into getting an iHas 124b type then. Got the samsung for xmas from the wife, and don't think she knew about the particular drive specs on it. Any chance you could look at the logs from before the samsung was installed? I actually had a iHas524B installed and it worked for a good while, then just started giving me coasters. Granted, I do believe most of the discs were memorex, but was still weird. Most recent one is actually the second listed (07Nov2013).
  2. Reason I mentioned the second link about Kite, is that he actually uses the drive, and has successfully burnt discs because the payloadtool works with the drive even though not listed as "fully accepted" on the list of drives it works with. Apparently the list hasn't been updated in a while.
  3. Recently started errorring out like no ones business trying to make hard copies of my backups. I've turned somewhere around 15 discs into coasters. Initially just figured was my disc quality. and then after a good few verbatims (001's) ate it, obviously my drive must be the problem. Replaced the drive, and still getting errors on them. Not sure what the deal is. Gives me the error during it's verify stage as a read error. Hoped that it was just Imgburn being wrong, but ran the disc through abgx and it read everything fine until like 30% through the game crc where it errored out and told me that all good except the game data. Been told that I should be using 003's instead, but been using the guide here: TUT-How to correctly burn XGD3 games| Se7ensins Gaming Community And supposedly so long as it burns at 2.4 speed, should be fine. In addition, as you'll notice I'm using a samsung TSSTcorp CDDVDW SH-224DB SB00 drive. Wasn't sure about it's validity at first, but according to Kite here: I'm Confused| Se7ensins Gaming Community so long as when using burnermax imgburn recognizes it as 8.7x gb, should be good. And imgburn does infact recognize it as such. Being a non-liteon drive, don't have any of the special stuff such as forcing hypertuning. If you guys could tell me what I'm doing wrong, or just what's messed up would be very helpful. ImgBurn Log.txt
×
×
  • Create New...

Important Information

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