Started by itomato, November 04, 2006, 08:47:55 PM
mkisofs -r -b 4.2_YOUR_SPECIFIC.floppyimage -c boot.catalog -o cdname.iso .
cdrecord -v speed=2 dev=/your/cdr cdname.iso
Quote from: "itomato"I just made El Torrito bootable CDs for installing OPENSTEP 4.2..
Quote from: "itomato"In case anyone is curious how I made these:* Create a temp directory. In this case, it was OS42.* Move your .floppyimage files into the directory.* Run 'mkisofs' like so:Code Select Expandmkisofs -r -b 4.2_YOUR_SPECIFIC.floppyimage -c boot.catalog -o cdname.iso .* Run 'cdrecord' like so:Code Select Expandcdrecord -v speed=2 dev=/your/cdr cdname.isoThis should work equally well for NeXTSTEP 3.3 or Rhapsody.NOTE: I haven't successfully installed with this method, but I think it's because I burned my OS42 CD incorrectly.. For some reason the label did not get written, and the size is over 500MB.
Quote from: "itomato"REVISED: I made use of 'bchunk' to create ISOs from my .bin image backups, and this handy cuesheet:Code Select ExpandFILE "OS42_User.bin" BINARYTRACK 01 MODE1/2352INDEX 01 00:00:00The ISO burned correctly - 488MB, "OPENSTEP_42" disk label..It's installing happily onto my Dell Lattitude CP Notebook
FILE "OS42_User.bin" BINARYTRACK 01 MODE1/2352INDEX 01 00:00:00
Quote from: "neozeed"Outside of a ROM upgrade I don't think it'll work (booting a cd on black). However if you dig around someone DD'd a CD onto a hard disk, then booted from that hard disk...That may be an easier path to go down...As an alternative, I wonder how hard it is to netboot a NeXT? Let alone if you can install via a Network install...
Quote from: "neozeed"Wow now that is weird. I was under the impression that OS & NS used the same filesystem for the CD's and thusly should be readable by eachother...Can you install your OS cd on a PC? (vpc/parallels/Q/Qemu etc etc?)Perhaps it's damaged....
Quote from: "itomato"* When selecting drivers for ATA/IDE, choose the "Primary/Seconday EIDE", the singular "EIDE", or SCSI if you're using SCSI.. If you choose the Intel PIIX driver at this point, even if it is recognized, you will have to load the driver from diskette after the initial installation. This might not be a problem on a desktop machine with a floppy as well as CDROM, but when installing on a laptop, it can be problematic.
Quote from: "kb7sqi"nextchef, I'm having the exact problem this moment w/ a Dell Latitude C610. So, I'm going to take my hard drive & throw it in an older laptop which still has a floppy drive. Then I'll finish the install from there. After that, I'm going to throw the hard drive back in the newer laptop.
Quote from: "nextchef"Quote from: "kb7sqi"nextchef, I'm having the exact problem this moment w/ a Dell Latitude C610. So, I'm going to take my hard drive & throw it in an older laptop which still has a floppy drive. Then I'll finish the install from there. After that, I'm going to throw the hard drive back in the newer laptop.Good idea, as I can throw it in my gateway laptop which has a working floppy. My hope was to upgrade to the dell since it has a larger screen and more memory than my current gateway OPENSTEP laptop. Come to think of it, I might be able to just ghost that drive over this one in the Dell and not have to re-install. The video drivers are different, so I would probably have to interrupt the boot and do a 'config=Default' so it loads the generic drivers.Thanks for the good idea.