Thanks to the folks who responed about my question regarding
re-installing the NeXT boot program. Everything's fine again.
BTW, I didn't bother to make the NeXT parition active to get it to boot
NeXTstep. What I did was use the NeXT 3.2 install floppy, boot from that
and then enter the boot command sd()mach_kernel.
This left the DOS partition active and then under NeXTstep I did
the 'disk -d /dev/rsd0a' and everything was fine.
This cut out the steps of changing the active partition back and forth
(NeXT Mail Welcome)
Quote:: Brown) writes:
: > I know I've read this topic on this group before but I don't have any
: > the associated messages so I'm hoping the involved parties can easily
: > their answers.
: > I had installed NeXTstep 3.2 on a series of Dell computers along with
: > partitions and all of the associated messy-dos software.
: > Everything was fine until some kind person upgraded a few of the
: machines to
: > DOS 6.2 and now, you guessed it, they don't offer the option of
: > NeXTstep anymore. I'm pretty sure the drives weren't repartitioned so
: > if I can somehow re-install the NeXT boot program I think I'll be
: > Does anyone have the solution?
: > Thanks.
: > --Jason Brown
: > Senior Software Engineer
: > (NeXT Mail Welcome)
: Using "fdisk" under DOS make the NEXTSTEP partition the active
: partition. Reboot the machine to bring it up in NEXTSTEP and type:
: "disk -b /dev/rsd0a" for a SCSI disk
: or "disk -b /dev/rhd0a" for an IDE disk
: You must be logged in as root to do this.