SCO

I think they will pull the plug before I get a chance to go into that level and send it back to the vendor. Who I think does not even have a legacy department for these toolsets anymore.

This means they would just send us a new controller at a expense that I could most likely buy a sport car.

So going backwards, can we think of any reason why it would bomb out after creating the kernel. I cannot find a single reason in my research, everything I have found shows some form of error code. This has no error code displayed.

Alexander

Is the file system floppy disk write protected? Or possibly is the diskette drive dirty enough that it thinks all diskettes are write protected?

The controller is from a clean room so it is actually cleaner than new in box.

I swapped the SCSI controller card with a identical one, still same situation.

they are pulling the plug on my to send this out today, so ill ship it out most likely Monday morning.

If you can think of any other things to try let me know between now and then. Otherwise I want to thank all of you for helping on this especially jgt.

I think I would try making a new boot and root set on one of the other 3 machines, verify operation on it, then try it on the machine that is failing. That would eliminate bad boot and root, just in case the supplier duplicated them from a bad original.

More likely, in my experience, that the CD is bad by a factor of at least 20 to 1. Can you swap a CD across.

To answer the previous question, keyboard is generic and shows up as it is booting up.

Assume that the SCSI bios reports all devices correctly on BIOS attachment.

So after pulling the replacement controller out of stores it was DOA. vendor would not honor warranty So I was allowed to do more work, also I found a bevy of old PC parts I could use to start isolating the problem.

After swapping everything out then returning all to normal. I decided to build a frankenstien out of the spare parts, and attempt to restore the HD which had been formatted to try to see if I could get some better error codes.
moved original D into frankenstien then restored original image back onto it.
after having to make a minor mkdev graphics change. the system booted right up with no problems, until it tried to find boards required to run the system software.

moved HD back into original controller booted up then gave the following code
Open event driver failed.
Fatal server error:
Check mouse configuration.
turns out PS2 mouse had enough uph to limp in windows but failed in SCO unix.

The lock up occurs when the PS2 mouse fails.

ordering new P2 motherboard. just wanted to update on the root cause of all this and close this thread out.
thanks again for all your help.

Alexander

If your application does not use Xwindows, you could also permanently disconnect the mouse and

Code:

#/etc/scologin disable

Then Xwindows will not ever start, nor will the system look for a mouse.