scotto@crash.cts.com (Scott O'Connell) (08/10/90)
System #1
Compaq 386/20 w/8meg
DTC 6250 ESDI with 2 CDC 383's
Equinox MegaPort
Mountain Hardware 7150 Tape Drive
Excelan LAN Workplace
Mono Card/Monitor
SCO Xenix 2.3.2
System #2
DTK 386/25 w/8meg
[rest is same]
About 3 months ago I purchased the SCO Manager. I installed it on system #1
which had been in operation for several months in its current configuration.
Everything worked fine and we were quite pleased with the software. I then
upgraded to system #2. The kernel wouldn't load, instead it would reboot
the system. Just for the heck of it I tried to boot the system at 10 mHz
and was surprised to find that it not only booted but could then be run at
25 after the kernel loaded.
I called SCO and was told that it was because SCO MultiView Runtime needed
to be the first thing linked to the kernel. I then followed their advice
and reinstalled the link-kit, installed SCO Manager, and verified that the
system did indeed boot. I then proceeded to reinstall the other software,
checking after each, that linked to the kernel. Tape Drive and
MegaPort were fine. When I got to the Equinox driver I ran into the same
situation where the kernel wouldn't load. I called SCO and they basically
said that the LAN Workplace was not on the supported product list now that
they have thir own similar product. Knowing that I'd have problems with
this I just removed the Excelan product and have been running ever since.
Last night I tried to install the Para Systems UPS monitoring program on
this machine (it had already been installed on the Compaq). When I tried
to boot after the link I'm again back to the same problem. Again, if I
boot at 10 mHz, I'm okay from there on.
I haven't called SCO because I know this UPS software is going to be
targeted as the problem. That's two products that work on a 386/20 with
MultiView and two products that DON'T work on a 386/25 with MultiView.
Does anyone have any ideas? It must be timing related since it does this
only on the fast machine, but how do I get around it?
Thanks in advance
--
Scott O'Connell - N6ZEK UUCP: {nosc, hplabs!hp-sdd}!crash!ipars!scotto
ARPA: crash!ipars!scotto@nosc.mil
INET: scotto@ipars.cts.com