Jump to content

Meneldur

Members
  • Posts

    4
  • Joined

  • Last visited

Meneldur's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. I see none. Keeping the "irony" flag up, I ask you this. Check the following log: If you don't see an error, I'm missing something. I found the problem. It was in nForce drivers. When (properly) replaced, ImgBurn erased the disc with no glitches. I guess I did something incorrectly between rolling back the driver to MS and retesting ImgBurn.
  2. Well, Lightning. I don't know if you are talking to me when you say we have no idea of what's going on. If that's so, I do know what's going on inside my rig. I showed my case clearly. I inserted a CDRW, launched ImgBurn, tried to erase it. Error. Changed driver to Windows original (in XP this solved all my problems with nForce chipset and drivers), inserted CDRW, launched ImgBurn, tried to erase. Error. Closed ImgBurn, fired up Explorer, secondary-click over CDRW, Erase it. Worked. Launched ImgBurn, created compilation, burned to CDRW. Worked. I'll try rolling back to nForce drivers and using them to erase CDRW with Windows.
  3. Thanks for pointing me in the right direction. I have the log here.
  4. Hi, everybody. I've been using ImgBurn since mid-2008 in WinXP SP3 with excellent results. This app rocks. I installed Windows 7 Beta 7057 last week to satiate my nerd inside. All is functioning perfectly despite one or two minor glitches with certain apps. One of them is ImgBurn 2.4.2.0. Today I couldn't under any circumstance make ImgBurn quick erase a CDRW. I tried even rolling back the SATA channel driver to Microsoft original to no avail (nVidia nForce latest drivers were in place). But using Windows built-in recording functions worked flawlessly erasing the disc. I then used ImgBurn to burn a couple of files to the now blank CDRW and it worked perfectly. Strange. It couldn't finish erasing the disc but burned it with no problems. The log showed some trouble when trying to erase, though. The process always stalled at 8% and then an ImmediateIO problem was logged (sorry, I erased the log), stating "0/2 tries" or something like that. I'm using SPTI as I/O driver.
×
×
  • Create New...

Important Information

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