Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by geezer

  1. In ImgBurn, Try Tools...Filter Driver Load Order For a clue
  2. No problem. It wasn't THAT much work to get it back I did it the second time only to confirm that it really happened the first time. Keeping a lookout for the update...
  3. No, the default buffer size was used for all of them. Increasing the buffer is a good idea. If I decide to try the nvidia IDE driver again, I'll increase it and see what happens (I assume you mean the Read Buffer Size on the Build tab under Settings). When my three level folder structure disappeared along with the incomplete iso, I was a bit troubled as well! Thanks for the info.
  4. Somebody needed to ask. I guess I should have included more details. BTW, the single HD testing was reading/writing my data/storage drive (D:). The 2 HD testing was reading the D: drive and writing the ISO to my system drive (C:). The system drive also contains the swap file... Just for fun, I defragged both each run and repeated the native driver test. The highest fragmentation reported by Perfect Disc after each run was 14 fragments on the System drive and 4 on the D: drive. Beware of aborting an ISO generation with ImgBurn. When I let it delete the incomplete file (I let it do this on two different occasions) it deleted my entire folder structure up to the root level not just the .iso file.
  5. Hi LUK! The sources for all the ISO builds were the same. The drives were defragged at this point. My AV was also disabled during the builds. An ISO was generated on each drive using ImgBurn (1 HD then 2HD) and then deleted. Then repeated with Shrink. But, I did not defrag between each run or randomize the order of the ISO builds. So, not truly scientific... But interesting.
  6. Well, as an experiment, I rolled back the IDE drivers to native XP and built ISO's with the same sources. Quite a bit of difference with ImgBurn using a single drive for source/output. Also a significant difference with Shrink and 2 HD. Hmmm interesting. Maybe I'll just use the native XP drivers afterall!
  7. Try building the image without IFO/BUP 32K padding. Does this work OK?
  8. Thanks for the explaination LUK! I see your point. Since I took the plunge yesterday by installing the v6.86 MB drivers including the IDE driver (been running with the native driver and v6.70 for about 8 months), I'm a little paranoid about what it may "break". I made an image before the "upgrade", just in case...
  9. I only yesterday upgraded to 6.86 and installed the IDE driver this time. I had been running v6.70 without it (using the XP driver) but had some noticable "lag" during intensive disc I/O. The IDE driver seems to have cured the lag, but then again, it may be a bit slower. I didn't perform this test with the native XP drivers. How much difference did you find?
  10. It is an Abit NForce4 MB (AN8-SLI) with an AMD X2 4200 CPU 2 GB OCZ RAM 2 74GB Raptors Using the latest 6.86 drivers nForce drivers.
  11. Wow, I guess I should have been utilizing two different HD for building ISOs all along. I wonder why the Shrink ISO build is quite a bit faster (more throughput) than Imgburn using a single HD (left), but slower when using two different drives? I really like the improvements to ImgBurn. Great work LUK!
  12. Sorry, I just noticed that I never replied. Shamus this absolutely did work! If I eject the disc after the burn is complete but before I close the dialogue box of Imgburn, all is well. No need to refresh or reboot. Thanks again.
  13. After burning an image using ImgBurn (latest version) and ejecting the disc, my PC still thinks that the disc is in the drive. Double clicking the drive icon attempts to install windows media player. The only way to clear this is a reboot. See attachment for screenshot. I have autoplay/autorun disabled. WinXP SP2 Pro 2X BenQ DW1620 DVD-RW Any ideas?
  • Create New...

Important Information

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