Tx I'll give it a try tonight and report back my findings.. > > > When you "try to add or change any of the packages on the CD", are > you > > > burning a new CD, or using lrpkg.cfg and pkgpath.cfg on a floppy? > What > > > exactly are you changing? Does the initial ISO image load all > packages > > > properly if you don't modify anything? > > > > Yes, each time I am burning a new CD > > Yes, am using lrpkg.cfg and pkgpath.cfg on the floppy > > > > I works fine if I use your original CD with no changes. The porblem > starts if > > I add a LRP to the CD (re-burn a new CD). Doesn't seem to matter if > it is > > listed in lrpkg.cfg or not. > > <snip> > > > Hardware is a Dell PI 133, but has tried it on PII and same problem > occurs > > (errors generated may be different), but the end result is that it > appears as > > though it can't read the CD. > > > > I am using NERO to burn a CDRW. I am beginning to wonder if perhaps > the NERO > > software is doing/not doing something...... > > It sure sounds like you're not getting a good CD-Image. I found it > impossible to create bootable CD's with Adaptec/Roxio EZ-CD Creator (it > doesn't think a syslinux'd disk is bootable...apparently it only likes > MSDOS boot disks), and I found Nero cumbersome to use for bootable CD's > (and I couldn't get NERO to output a plain ISO image, so I had to burn > the disk, then read it on a linux system to make an ISO). If at all > possible, you should use the mkisofs command listed in the README file > on a linux system to create new CD images...if this is not possible, > maybe some folks on the NERO list can help you get your settings right. > > The mkisofs command I use is: > mkisofs -b bootdisk.bin -r -J -f -o <outputfile> -V <volume name> > <path>/CD-Contents/ > > The switches are: > -f follow symbolic links...this probably isn't imporant in NERO > (windows doesn't even *HAVE* symbolic links!), and simply allows me to > symlink the modules directory to avoid having a copy in each CD > directory taking up space on my HDD > > -r Add Rock Ridge extensions, with uid & gid = 0 > > -J Generate Joliet directory records > > -b bootdisk.bin Use bootdisk.bin as the El Torito boot image (aka > floppy emulation) > > -V specify the volume ID > > -o specify the output file name > > If you can successfully get Nero to emulate the behavior of mkisofs with > these switches, you should have a working disk image. > > *WARNING* While I have in the past used Nero to make bootable images, I > don't think I've tried to do this since putting the un-compressed > modules directory directly on the CD...I'm not sure Nero can make a CD > that will work with the current setup of loading modules directly from > the CD (various potential problems with long-filenames, permissions, > etc. when compared to simply loading a bunch of 8.3 named LRP files at > boot-time). I suggest using CD-RW's, and talking to some folks more > familiar with Nero if you can't use mkisofs. > > Charles Steinkuehler > http://lrp.steinkuehler.net > http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) >
------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
