Jump to content

FlyingHorse

Members
  • Posts

    8
  • Joined

  • Last visited

About FlyingHorse

  • Birthday 12/11/1965

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Home

FlyingHorse's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. I take it that the MCC-003 are the -R media? I suppose that is what I'll have to do. The only thing that bugs me is that ALL other ISO images burn without any problems except for this one particular file. I just don't get it. #39;(
  2. My point exactly. If the data in the ISO is bad to begin with then wouldn't the burn that results would be bad as well? From my first post I tried 3 different batches of Verbatim +R and also tried at different speeds.
  3. Okay, I just downloaded a copy of SuSE 10.3 which is a 4.0GB image and it burned without a single problem. Could something be wrong with the ISO file from MS? Is there some way to check for errors? I am really at a loss now. Please any suggestions would be appreciated.
  4. I'll check out the link. I am running an EVGA Nvidia based 680i SLI motherboard & chipset. Thanks.
  5. Mine has been problem free for months... until today. I tried that as well and same error happens. Might be cheaper for me to purchase a different unit than to toss all these +R media
  6. That just brought up an I/O error box:
  7. This is a typical log file for the failure that I get: I 17:34:26 ImgBurn Version 2.4.0.0 started!I 17:34:26 Microsoft Windows Vista Ultimate Edition (6.0, Build 6001 : Service Pack 1) I 17:34:26 Total Physical Memory: 4,191,884 KB - Available: 2,304,740 KB I 17:34:26 Initialising SPTI... I 17:34:26 Searching for SCSI / ATAPI devices... I 17:34:26 Found 2 DVD-ROMs and 1 DVD
  8. Thank you Lightning UK for all your efforts with ImgBurn. I have replaced all my other burning apps with this single one and couldn't be more pleased. Keep up the great job and check your PayPal account!
×
×
  • Create New...

Important Information

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