...and that's where it sits. Primary boot path is set to scsi.4.0 and I have a 9.1Gb drive configured for ID4, the Alternate booth path is set to scsi.5.0, the Console path is graphics, and the Keyboard path is HIL. I am using a serial terminal since I have no HIL keyboard. Potential boot devices are as follows:

kshuff wrote:...and that's where it sits. Primary boot path is set to scsi.4.0 and I have a 9.1Gb drive configured for ID4, the Alternate booth path is set to scsi.5.0, the Console path is graphics, and the Keyboard path is HIL. I am using a serial terminal since I have no HIL keyboard.

I am pretty sure that NEXTSTEP won't use a serial terminal as a console.

kshuff wrote:...and that's where it sits. Primary boot path is set to scsi.4.0 and I have a 9.1Gb drive configured for ID4, the Alternate booth path is set to scsi.5.0, the Console path is graphics, and the Keyboard path is HIL. I am using a serial terminal since I have no HIL keyboard.

I am pretty sure that NEXTSTEP won't use a serial terminal as a console.

It should still install right? I get no activity after the message displayed above, no disk or cdrom activity.

I know NextSTEP was particular about a stick of ram in my SS20 that Sol7 wasn't but I don't think that's what's the problem here. Everything in Next is GUI though so I agree that you need to get a keyboard and mouse.

Yeah, in my experience (which includes 0 NeXT) the software needs to know that its outputting to serial. If the installer is pure gui (or loads from the gui) then chances are you wont get it to output to the serial.

zmttoxics wrote:Yeah, in my experience (which includes 0 NeXT) the software needs to know that its outputting to serial. If the installer is pure gui (or loads from the gui) then chances are you wont get it to output to the serial.

I've had it running on a King Gecko 712/100 with 192mb ram. It can spawn a getty on a serial console, but requires a frame buffer for the install. Also, you'll later need to do the two-step boot to get it to not try and log into a NIS domain.. afair it defaults to one and you finish the install and suddenly buggar! you can't log in

Frame buffer required to the best of my knowledge. Sorry for the bad news.

uridium wrote:I've had it running on a King Gecko 712/100 with 192mb ram. It can spawn a getty on a serial console, but requires a frame buffer for the install. Also, you'll later need to do the two-step boot to get it to not try and log into a NIS domain.. afair it defaults to one and you finish the install and suddenly buggar! you can't log in

Frame buffer required to the best of my knowledge. Sorry for the bad news.

I've got a video card in one of the systems so that's not a problem, and I managed to get a keyboard and mouse so, we'll give it another try.

Finally got around to installing NextStep last night. After trying to get the system to use the framebuffer instead of outputting to serial, it finally installed. But, I still have issues. Sometimes when I power it up, it still outputs to serial and I get this on the terminal:

which just sits there and does nothing. If I push the reset button a few times I can get it to come up using the framebuffer, I get the nice NEXTSTEP splash screen on the monitor which says starting nextstep, but that has been sitting there like that since last night, no messages on serial. ???

May have fixed it. Tracked down the service manual online and according to the diagnostic LED's I came up with an HPMC due to a bus error. Turns out the system I/O board was the culprit and replacing it with a spare board from another 735 did the trick, I'm no longer getting an HPMC. But, turns out the super block on the drive is trashed, so running fsck now, let you guys know how I make out.