Installation - SCO Openeserver 5.0.4 on an old PS/2 model 90 - Help
Tony Pattison
(9590) with two SCSI hard disks and a SCSI CDROM all on a single internal
host adapter. This venerable PC has 40 mb of RAM and an XGA/2 video card.
I can get the diskette to boot, although I have to use a "defbootstr
Sdsk=hf(0,6,0) Srom(0,1,0)" to get it to correctly identify the devices.
I go through the setup procedure, put in the keyboard type and the license
number/code/data, and then reply Ok a few times, tell it that this is a
Fresh install, and after pressing OK, the blue screen says that it's
"Extracting Files " (I can see the CDROM being accessed). It then tells me
that it is "Checking System state and loading installation files. Please
wait ...". At this point it accesses the correct hard disk three or four
times, and then just sits there. I've left it for over two hours (just in
case). But nothing else happens.
Any suggestions?
thanks
Tony
Jeff Liebermann
<tony.p...@totalise.co.uk> wrote:
>I'm trying to get OpenServer 5.0.4 installed on an old IBM PS/2 model 90
>(9590) with two SCSI hard disks and a SCSI CDROM all on a single internal
>host adapter. This venerable PC has 40 mb of RAM and an XGA/2 video card.
Cool. Want another one? I have one sitting in my dead computer pile.
The box was so beautifully built, that I just couldn't see myself tossing
it. Unfortunately, it's only a 486DX25. I also have a pile of MCA
boards buried (somewhere).
>I can get the diskette to boot, although I have to use a "defbootstr
>Sdsk=hf(0,6,0) Srom(0,1,0)" to get it to correctly identify the devices.
I think you mean "hd" not "hf". Has someone juggled the disk drives?
The boot SCSI drive *MUST* be drive ID=0, not 6. Move some jumpers
around on the drive and use the reference disk to verify that it is
correct.
>I go through the setup procedure, put in the keyboard type and the license
>number/code/data, and then reply Ok a few times, tell it that this is a
>Fresh install, and after pressing OK, the blue screen says that it's
>"Extracting Files " (I can see the CDROM being accessed). It then tells me
>that it is "Checking System state and loading installation files. Please
>wait ...". At this point it accesses the correct hard disk three or four
>times, and then just sits there. I've left it for over two hours (just in
>case). But nothing else happens.
This might help:
http://www.sco.com/cgi-bin/ssl_reference?105741
but I still think you have to move the hd ID to zero, and possibly the
cdrom ID to 5 (SCO's favorite defaults). If it has a tape drive, set it
to ID=2.
Also see:
http://www.sco.com/cgi-bin/ssl_reference?101956
which lists supported IBM hardware. Unfortunately, it only goes to
3.2v5.0.0 so no clue if things have improved for the Model 90 in 5.0.4.
The Model 90 was obsolete long before OSR5 appeared.
Goto:
http://www.sco.com/ta
and use "MCA" or "Microchannel" as keywords and see what pops up.
--
Jeff Liebermann je...@comix.santa-cruz.ca.us
150 Felker St #D Santa Cruz CA 95060
831-421-6491 pager 831-429-1240 fax
http://www.cruzio.com/~jeffl/sco/ SCO stuff
Tom Parsons
| On Sat, 9 Dec 2000 09:58:10 -0000, "Tony Pattison"
| <tony.p...@totalise.co.uk> wrote:
|
| >I'm trying to get OpenServer 5.0.4 installed on an old IBM PS/2 model 90
| >(9590) with two SCSI hard disks and a SCSI CDROM all on a single internal
| >host adapter. This venerable PC has 40 mb of RAM and an XGA/2 video card.
|
| Cool. Want another one? I have one sitting in my dead computer pile.
| The box was so beautifully built, that I just couldn't see myself tossing
| it. Unfortunately, it's only a 486DX25. I also have a pile of MCA
| boards buried (somewhere).
|
| >I can get the diskette to boot, although I have to use a "defbootstr
| >Sdsk=hf(0,6,0) Srom(0,1,0)" to get it to correctly identify the devices.
|
| I think you mean "hd" not "hf". Has someone juggled the disk drives?
| The boot SCSI drive *MUST* be drive ID=0, not 6. Move some jumpers
| around on the drive and use the reference disk to verify that it is
| correct.
I see a hf driver listed for IBM Hardfile adapters and yes, it was quite
common for IBM to use ID6 for the controller.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Bill Vermillion
Jeff Liebermann <je...@comix.santa-cruz.ca.us> wrote:
>On Sat, 9 Dec 2000 09:58:10 -0000, "Tony Pattison"
><tony.p...@totalise.co.uk> wrote:
>>I'm trying to get OpenServer 5.0.4 installed on an old IBM PS/2
>>model 90 (9590) with two SCSI hard disks and a SCSI CDROM all on a
>>single internal host adapter. This venerable PC has 40 mb of RAM
>>and an XGA/2 video card.
>
>Cool. Want another one? I have one sitting in my dead computer
>pile. The box was so beautifully built, that I just couldn't see
>myself tossing it. Unfortunately, it's only a 486DX25. I also have
>a pile of MCA boards buried (somewhere).
>>I can get the diskette to boot, although I have to use a
>>"defbootstr Sdsk=hf(0,6,0) Srom(0,1,0)" to get it to correctly
>>identify the devices.
>
>I think you mean "hd" not "hf". Has someone juggled the disk
>drives? The boot SCSI drive *MUST* be drive ID=0, not 6. Move some
>jumpers around on the drive and use the reference disk to verify
>that it is correct.
Not neccesarily true Jeff. Chaging the boot string on installation
will cause the correct drive to boot. In a system where I could
turn off drive 0, I defined a bootstring to be 0,1,0, so that the
SCO would boot off drive 1.
IBM's SCSI controllers follow the SCSI standard which really should
have the boot drive be the next highest priority after the adapter
itself, which is 7. The PC world adapators/OS'es all used
drive 0 because that matches the original standards of the
brain-dead PC, and PC-XT model. If he's using an IBM SCSI adaptor
and he moved the drive IDs' he *MUST* [using your words] change the
setting in the IBM adaptor.
I installed man SCO systems on IBM 80's and 90's.
>This might help: http://www.sco.com/cgi-bin/ssl_reference?105741
>but I still think you have to move the hd ID to zero, and possibly
>the cdrom ID to 5 (SCO's favorite defaults). If it has a tape
>drive, set it to ID=2.
Those are just the boot defaults. Using the bootstring you can
cause SCO to boot from any drive you wish. What will get you
is that if you don't set the bootstring, and the first HD the
controller finds is on ID1 [for example] after you install
the system won't boot because the default system expects to
load from drive 0. Ask me how I know :-)
--
Bill Vermillion - bv @ wjv . com
Jeff Liebermann
>Not neccesarily true Jeff. Chaging the boot string on installation
>will cause the correct drive to boot. In a system where I could
>turn off drive 0, I defined a bootstring to be 0,1,0, so that the
>SCO would boot off drive 1.
Argh. You're correct. According to the hints in:
http://www.sco.com/cgi-bin/ssl_reference?105037
OSR5 can boot from ID=6.
>I installed man SCO systems on IBM 80's and 90's.
I've only done one model 90 and I had to change the boot drive ID for
some long forgotten reason.
So, now we're still back to why it hangs when it tried to copy files
scribble to the hard disk. Terminators? Terminator power? Flakey
connectors? Dead drive? Something else on the SCSI bus? Dunno.
Bill Vermillion
Jeff Liebermann <je...@comix.santa-cruz.ca.us> wrote:
>On Sat, 9 Dec 2000 20:18:46 GMT, bi...@wjv.com (Bill Vermillion) wrote:
>>Not neccesarily true Jeff. Chaging the boot string on installation
>>will cause the correct drive to boot. In a system where I could
>>turn off drive 0, I defined a bootstring to be 0,1,0, so that the
>>SCO would boot off drive 1.
>Argh. You're correct. According to the hints in:
> http://www.sco.com/cgi-bin/ssl_reference?105037
>OSR5 can boot from ID=6.
>>I installed man SCO systems on IBM 80's and 90's.
>I've only done one model 90 and I had to change the boot drive ID for
>some long forgotten reason.
>So, now we're still back to why it hangs when it tried to copy files
>scribble to the hard disk. Terminators? Terminator power? Flakey
>connectors? Dead drive? Something else on the SCSI bus? Dunno.
Well he does have 2 SCSI HD's and the CDROM. He has the CD at
ID1. I'd suggest disconnecting the second HD to start with.
If had not specfied he used the bootstring I would have
suspected. Without the bootstring you can install it - but it will
never boot after install. At least that was how I learned about
this.
It could also be terminators as you point out. It's an older
machine and the power supply could be getting a bit tired - eg
lower that expected voltages.
I've done the trick of pulling off everyting except the needed SCSI
devices and had that work sometimes.
He probalby might need to go into the setup and turn off all
uneccesary things. I don't recall what you can turn off on
the PS2's. But ISTR that on booting the IBM setup disk you can
press Control A [I think] and get a much more complete menu.
Tony Pattison
thanks to all of you guys for your help.
I tried removing the second hard disk from the SCSI cable (leaving just the
adapter card, the hard disk I want to put Unix on and the CDROM that I have
the SCO Unix CD in). Still no joy.
I did find that if, when presented with the blue stuck screen, I press Alt
F3, I get a unix text prompt (Prompt = <Installation> ). From here I've been
able to use FDISK and DIVVY on the hard disk, oh and I've been able to mount
the hard disk as well (mount /dev/hd00 /mnt). When I mount the hard disk, I
can hear a few head 'ticks'.
So, I'm not convinced that the problem lies with the SCSI.
Is there any 'defbootstr' parameters that you can think of that might help
(at the moment I've tried "defbootstr Sdsk=hf(0,6,0) Srom=hf(0,1,0)
disable=Stp hd=Sdsk" . I found that if I din't disable the tape, I was told
that I had a tape on the SCSI).
Any ideas?
again thanks for your help so far
Tony
Bill Vermillion wrote in message ...