Jump to content

jds

Members
  • Posts

    10
  • Joined

  • Last visited

Profile Information

  • Location
    Sydney

jds's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Thanks Lightning for such a great tool and for your great support! Sorry to dig up such an old post, but I was seeking answers to a couple of the same questions, so glad that after some careful reading (including the URL you linked), things slowly became clearer for me. Thank you! Just a suggestion, which you are free to ignore, would be to make the following minor text changes under the Bootable Disc tab : Patch Boot Information Table -> Patch Boot Information Table (isolinux) Extract Boot Image -> Extract a Boot Image This would make it a little more obvious what these two items are, and whether they're relevant. So in my case, it would then be clear that I didn't need the Patch Boot Information Table option, and that the Extract Boot Image selection wasn't asking for some kind of image file, but was a little tool to create such a file (presumably to use in the Boot Image selection above). Joe.
  2. Managed to find the missing link by sleuthing the Internet Archive : ftp://ftp6.nero.com/NeroASPIen.exe Joe.
  3. Another update : I've just had another opportunity/need to burn a CD-ROM (this time it's a CD-RW, in case it matters, which I don't think it does) ... However, since last time, I've disabled the horrid "Auto insert notification" setting and installed the "Unofficial Windows 98/98 SP1/98 SE CD/DISK/SCSI/SMART/VOL I/O Subsystem CDFS.VXD 4.90.3002 (patched for > 2 GB DVD size), CDTSD.VXD 4.90.3001, CDVSD.VXD 4.90.3004, DISKTSD.VXD 4.90.3001, DISKVSD.VXD 4.90.3002, SCSI1HLP.VXD 4.90.3001, SMARTVSD.VXD 4.90.3001 + VOLTRACK.VXD 4.90.3001 Drivers Fix v2" from http://www.mdgx.com/web.htm#98SE The installation package for this fix is a file called 'IOSYS98.EXE' (170 KB, English). A copy is also available from here : http://www.htasoft.com/w98se_post_usp4/ Now the problem's gone (without the horrid "Auto insert notification" work-around)! Joe.
  4. Also, try rebooting your machine (without the disk inserted) and see if it looks OK. It might be the same issue I reported here : http://forum.imgburn.com/index.php?showtopic=17692 Joe.
  5. Update : Well, I've now had the opportunity to burn another CD-ROM, this time with "Auto insert notification" enabled. Everything proceeded as before, ImgBurn burnt the disk, opened and closed the drive, then successfully verified it. After exiting ImgBurn, Windows Explorer showed the disk as blank, with 648MB capacity (it's actually a 700MB disk). However, after opening and closing the drive again, the disk appeared correctly in Windows Explorer (and tried to "autorun", of course). So, whatever the problem may be, the "Auto insert notification" process does put things right. Joe.
  6. Actually, I don't (I find this "feature" annoying/dangerous). Unfortunately, ejecting, refreshing, etc., didn't make a difference. However, next time, I'll try enabling the autorun/play/insert feature, and see if this makes a difference. Thanks for your help and suggestions! Regards, Joe.
  7. Hi, I updated ImgBurn to version 2.5.5.0 a few months ago, and now I've used it twice (to burn Knoppix and Ubuntu images, respectively) using 700M CD-R media (those images are big!), yet the same problem exists. The burning and verification works fine, yet unless I reboot, the CD-R appears blank, reporting 648M capacity with 648M free under Windoze (which is actually less capacity than originally reported when it really was blank). Also, no other CD-ROM is readable without a reboot. Thinking perhaps this was a drive firmware issue, I upgraded the firmware from version 4S04 to 4S09 before burning the second disk (with rebooting along the way, just in case). This made no difference with this problem. Any idea what is the cause? It's as if ImgBurn is leaving the CD-ROM drive in some funny state after burning, but that's just a wild guess ... Joe.
  8. Fair enough. Since I'd not had any issues with ImgBurn before, I'd had no reason to look for updates. Do you think the above problem is something that has been addressed in more recent versions (bearing in mind that I've not encountered this problem before using 2.4.1.0, so it may not be reproducible)? Joe.
  9. Update : Well, I decided to try rebooting to DOS mode and checking the CD-R from there. It was OK, the directory listing showed "8.3" filenames as is the norm. Then I tried Henrik Haftmann's DOSLFN driver & tools, these were also OK, except that the MKLINK helper application reported "ISO and Joliet trees have DIFFERENT order!". Now although this driver (with helper application) did show the LFN filenames correctly, the exclamation mark given by MKLINK seems to imply that ISO and Joliet trees being a different order is something incorrect, that presumably was done by ImgBurn. Next I restarted W98SE and lo and behold, there was the disk contents in all their glory! So ... 1) Why did the disk appear blank immediately after burning and following several removals and insertions? Why was it OK after rebooting? 2) Is this "ISO and Joliet trees have DIFFERENT order!" issue something that should be fixed in ImgBurn (assuming this is responsible)? 3) Is Tools/Drive/Close/Disc the equivalent of "finalize disk"? Is there a "finalize disk" option per se in ImgBurn for burning CD media? What are the other two Tools/Drive/Close menu options for? Joe. PS. Forgot to mention ... ImgBurn rocks! I long ago deleted the bloated Nero software that came with my CD burner drive, thanks to this vastly superior alternative!
  10. Hi, I infrequently burn disks, and don't know what's changed since the last time, but I've just attempted to burn a CD-R from a directory (software for my wife's camera, from original CD-ROM but with added updates) and everything appeared OK. However, the CD-R appears blank in Windows explorer (W98SE), yet it isn't because I can make an ISO image from it and the content is there. I searched the web for answers and one suggestion was that the CD-R wasn't finalized, so I tried the Tools/Drive/Close/Disc option (another search of the web had said this was a way to finalize a disk) but the outcome was the same as for : http://forum.imgburn.com/index.php?showtopic=17443 Here is the log for the original burn : Here is a log of reading the CD-R to an ISO image file : Note that I chose the ISO9660 + Joliet options, since AFAIK, at least ISO-9660 should work with W98SE (I'm pretty sure Joliet is also OK). Any ideas? Is the CD-R really finalized? Is this operation as per "Close Disc" or instead, "Close Session" or "Close Track" in ImgBurn? (BTW, the disks say "2x - 52x" and I chose "5x" for the write speed.) Joe.
×
×
  • Create New...

Important Information

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