🚀 go-pugleaf

In article <1992Sep28.050130.23485@athena.mit.edu> shanega@athena.mit.edu  
(Shane G. Artis) writes:
> 
> Hi, I have a pair of questions for sysadmin types.  Any hints or
> clues would be very helpful.
> 
> First, I'm trying to install 3.0 on my station from handmade floppies
> created using tar and split from a 3.0 optical disk mounted on another
> machine (I am fully licensed for 3.0, but I didn't buy the CDROM drive
> and there's no word on when 3.0 will be available in floppy format).
> I know my NeXT well enough to do a good job getting all the important
> files needed to boot the machine and run NeXTSTEP - at least I thought
> so.  I tar-ed the new machs, the libs, the shlibs, the usr and bin
> directories and created new device drivers using MAKEDEV (while booted
> from a floppy) into the appropriate locations, wrote a new boot block
> to the hard disk so it would boot the new mach, and then rebooted.
> The machine came up in singleuser mode just fine, but when I tried to
> start up the windowserver (by exiting singleuser mode) I got a mouse
> cursor and nothing else.  The mouse cursor went away and then returned
> periodically, along with a bit of disk action, but no windowserver.
> Rebooting back up into NeXTSTEP 2.1 and looking at the private/adm
> messages file gave me one clue.  The final line in the file before the
> most recent booting messages was:
> 
> loginwindow: Cannot find windowserver port!
> 
> What does this mean I'm missing or doing wrong?  I think everything is
> all there, but maybe I missed a file somewhere.  I'm pretty sure my
> permissions are all set correctly and so on.
> 
> 
> The second (and simpler) question I have is: Has anyone connected a
> Sun brand CD-ROM drive to their NeXT and successfully used it to
> install 3.0?  Are the drives compatible and the CD formats compatible?
> 
> Thanks for any help!
> 
> Shane

Well, I had the same problem even WITH the CD-ROM.  It turns out (after
some panicked and adreneline-filled moments) that one of the files
installed by the 3.0-prep floppy didn't install correctly.  Here's how
I managed to resolve it:

- Boot single-user from semi-corrupted hard disk (if this doesn't work,
  boot single-user from anything and mount the hard disk).

- Mount the 3.0-prep floppy (I forgot its official name, but it has the
  kernel and a few other files that it installs).

- Go into the installation package, copy the stuff into /tmp, and
  uncompress (and untar, if necessary...again I forgot the exact
  details, and the floppy isn't handy).  Compare using diff or cmp
  the files with their "installed-and-corrupted" counterparts.  The
  one that I found to be faulty was /usr/lib/NextStep/WindowServer.
  There is also /usr/lib/NextStep/PS.VM.

- Copy the new file(s) in /tmp over the corrupted one(s).  Reboot.

- Cross fingers, burn incense, etc.

Hope this works for you...I can't think of a reason that this could
have occurred, but I guess we're just lucky :-).

Good luck,

-Mike

--
Mike Panzitta
Doberman Systems
doberman!mike@uunet.uu.net (NeXTMail)

In article <1992Sep28.064542.12171@doberman.uucp> doberman!mike@esunix.sim.es.com writes:
>In article <1992Sep28.050130.23485@athena.mit.edu> shanega@athena.mit.edu  
>(Shane G. Artis) writes:
>> 
>> Hi, I have a pair of questions for sysadmin types.  Any hints or
>> clues would be very helpful.
>> 
>> First, I'm trying to install 3.0 on my station from handmade floppies
>> created using tar and split from a 3.0 optical disk mounted on another
>> machine (I am fully licensed for 3.0, but I didn't buy the CDROM drive
>> and there's no word on when 3.0 will be available in floppy format).
>> I know my NeXT well enough to do a good job getting all the important
>> files needed to boot the machine and run NeXTSTEP - at least I thought
>> so.  I tar-ed the new machs, the libs, the shlibs, the usr and bin
>> directories and created new device drivers using MAKEDEV (while booted
>> from a floppy) into the appropriate locations, wrote a new boot block
>> to the hard disk so it would boot the new mach, and then rebooted.
>> The machine came up in singleuser mode just fine, but when I tried to
>> start up the windowserver (by exiting singleuser mode) I got a mouse
>> cursor and nothing else.  The mouse cursor went away and then returned
>> periodically, along with a bit of disk action, but no windowserver.
>> Rebooting back up into NeXTSTEP 2.1 and looking at the private/adm
>> messages file gave me one clue.  The final line in the file before the
>> most recent booting messages was:
>> 
>> loginwindow: Cannot find windowserver port!
>> 
>> What does this mean I'm missing or doing wrong?  I think everything is
>> all there, but maybe I missed a file somewhere.  I'm pretty sure my
>> permissions are all set correctly and so on.
>> 
>> 
>> The second (and simpler) question I have is: Has anyone connected a
>> Sun brand CD-ROM drive to their NeXT and successfully used it to
>> install 3.0?  Are the drives compatible and the CD formats compatible?
>> 
>> Thanks for any help!
>> 
>> Shane
>
>Well, I had the same problem even WITH the CD-ROM.  It turns out (after
>some panicked and adreneline-filled moments) that one of the files
>installed by the 3.0-prep floppy didn't install correctly.  Here's how
>I managed to resolve it:
>
>- Boot single-user from semi-corrupted hard disk (if this doesn't work,
>  boot single-user from anything and mount the hard disk).
>
>- Mount the 3.0-prep floppy (I forgot its official name, but it has the
>  kernel and a few other files that it installs).
>
>- Go into the installation package, copy the stuff into /tmp, and
>  uncompress (and untar, if necessary...again I forgot the exact
>  details, and the floppy isn't handy).  Compare using diff or cmp
>  the files with their "installed-and-corrupted" counterparts.  The
>  one that I found to be faulty was /usr/lib/NextStep/WindowServer.
>  There is also /usr/lib/NextStep/PS.VM.
>
>- Copy the new file(s) in /tmp over the corrupted one(s).  Reboot.
>
>- Cross fingers, burn incense, etc.
>
>Hope this works for you...I can't think of a reason that this could
>have occurred, but I guess we're just lucky :-).
>
>Good luck,
>
>-Mike
>
>--
>Mike Panzitta
>Doberman Systems
>doberman!mike@uunet.uu.net (NeXTMail)


-- 
                                         _/                              _/
Andrew Duchowski      _/_/  _/_/_/   _/_/_/ _/_/_/ _/_/_/  _/    _/  _/_/_/
Texas A&M University   _/_/  _/  _/ _/   _/  _/   _/_/_/_/ _/ _/ _/ _/   _/
andrewd@cs.tamu.edu  _/  _/  _/  _/ _/   _/  _/   _/       _/ _/ _/ _/   _/

In article <1992Sep28.050130.23485@athena.mit.edu>  
shanega@athena.mit.edu (Shane G. Artis) writes:
> The second (and simpler) question I have is: Has anyone connected a
> Sun brand CD-ROM drive to their NeXT and successfully used it to
> install 3.0?  Are the drives compatible and the CD formats compatible?

Yes. The Sun 595-1929-04 is nearly identical to the NeXT drive. The  
audio on the NeXT drive is better, the color matches better, and the  
enclosure shape is cuter, but other than that they seem interchangable.

To be totally honest, I only used the Sun drive to install 3.0 PR-1; my  
NeXT drive arrived right after that and I had no reason to hook the NeXT  
drive to a Sun.

--Denis Lynch
ESL Inc.

In article <1992Sep28.050130.23485@athena.mit.edu> shanega@athena.mit.edu (Shane G. Artis) writes:
>
>Hi, I have a pair of questions for sysadmin types.  Any hints or
>clues would be very helpful.
>
>First, I'm trying to install 3.0 on my station from handmade floppies
>created using tar and split from a 3.0 optical disk mounted on another
>machine (I am fully licensed for 3.0, but I didn't buy the CDROM drive
>and there's no word on when 3.0 will be available in floppy format).
>I know my NeXT well enough to do a good job getting all the important
>files needed to boot the machine and run NeXTSTEP - at least I thought
>so.  I tar-ed the new machs, the libs, the shlibs, the usr and bin
>directories and created new device drivers using MAKEDEV (while booted
>from a floppy) into the appropriate locations, wrote a new boot block
>to the hard disk so it would boot the new mach, and then rebooted.
>The machine came up in singleuser mode just fine, but when I tried to
>start up the windowserver (by exiting singleuser mode) I got a mouse
>cursor and nothing else.  The mouse cursor went away and then returned
>periodically, along with a bit of disk action, but no windowserver.
>Rebooting back up into NeXTSTEP 2.1 and looking at the private/adm
>messages file gave me one clue.  The final line in the file before the
>most recent booting messages was:
>
>loginwindow: Cannot find windowserver port!
>
>What does this mean I'm missing or doing wrong?  I think everything is
>all there, but maybe I missed a file somewhere.  I'm pretty sure my
>permissions are all set correctly and so on.
>
>
>The second (and simpler) question I have is: Has anyone connected a
>Sun brand CD-ROM drive to their NeXT and successfully used it to
>install 3.0?  Are the drives compatible and the CD formats compatible?
>
>Thanks for any help!
>
>Shane

2./	I have not used a SUN brand CD-ROM, but I have used an Apple
CD-ROM.  In fact I have used an Apple CD-ROM to upgrade my Cube to 3.0
My advice is...plug the sun CD-ROM into your SCSI chain and try it.  You
should be able to tell if it's working from the bootup diagnostics.
PLEASE email with what you find out.

PS.  Make sure you have run the 3.0Prep program...this should allow you
to read the following formats [I assume that SUN CD-ROMs adhere to ISO
9660 standards]  ISO 9660, Rock Ridge, Mac HFS, NeXT Proprietary.
Please note that it was [and is] not necessary for me to upgrade a 2.0
machine inorder to read an ISO 9660 CD using an Apple Drive.

PPS. Please let me know by E-Mail if this works...

David
NeXT Campus Consultant
next@yorku.ca

In article <1992Sep30.025538.28651@newshub.ariel.yorku.ca> cs911409@ariel.yorku.ca (RICHARD DAVID ASPINALL) writes:
>
>2./	I have not used a SUN brand CD-ROM ...
>

A Sun CDROM worked for me just fine.

-Chris