This is Help-Broken-NeXTcube... in view mode; [Up]
Date: Sun 25-Nov-1991 20:07:08 From: shanega@athena.mit.edu (Shane G. Artis) Subject: Help! Broken NeXTcube... Hi! Sorry if this is extremely badly fomatted, but I'm posting from my broken NeXTcube which is running in standalone mode. Can anyone help me fix it? I have a NeXTcube with 12 Meg of memory, OS 2.1, 68040, a 100 Meg hard drive (boot device) and an OD for backups, etc. Here's what happened: I viewed many images with ImageView 0.9, and eventually my small boot drive ran out of space for the swapfile. This has happened to me before. I generally have to reboot, and that is what I did. This time, however, instead of logging me in (I have a single-user machine - not networked) it stopped at the image that says : 'Starting System Services'. I used command-~ to restart, and this time I went to the ROM monitor and booted while watching the system messages. The last message printed before the machine seized up was: This was repeated every 30 seconds or so until I rebooted. This time, I rebooted with an OD I keep for backups, and went straight for multi-user mode. This didn't work either, even though the disk was never in the machine during the original crash! It went farther in the boot process, but when it generally logs me into me user account I got only a blank screen and the mouse in the upper-left corner, which would periodically disappear and reappear as the windowserver continued to try to log me in. How could the backup OD have gotten corrupted? I used it fine just yesterday... Anyway, I've tried both boot processes repeatedly with identical results each time. Does ANYONE have any clue what is going on? In general, I am very familiar with my sytem, but I've never learned anything about the ports or the WindowServer at a low level. Help! I've crashed and I can't get up! Thanks, Shane
Date: Sun 25-Nov-1991 23:29:51 From: tom@csustan.csustan.edu Subject: Re: Help! Broken NeXTcube... In article <1991Nov25.200708.11868@athena.mit.edu> shanega@athena.mit.edu (Shane G. Artis) writes: > . . . The last >message printed before the machine seized up was: > >syslog: loginwindow: could not find WindowServer port! For what it's worth, I had similar problems recently. I finally discovered that the file /usr/shlib/libNeXT_s.C.shlib was corrupt. Replacing that file fixed the problem. You might also check other files in /usr/shlib. For reference, here is the result of `sum /usr/shlib/*' : 28128 1448 /usr/shlib/libNeXT_s.C.shlib 43604 128 /usr/shlib/libdsp_s.A.shlib 12280 793 /usr/shlib/libmusic_s.A.shlib 59558 72 /usr/shlib/libni_s.A.shlib 61259 658 /usr/shlib/libsys_s.B.shlib 12933 125 /usr/shlib/libvideo_s.A.shlib In my case, I was able to boot from an optical and copy the file from there, so this may not help in your case :-( >Help! I've crashed and I can't get up! >Thanks, >Shane Tom Carter tom@csustan.csustan.edu
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.