morgan@comcon.UUCP (comcon) (03/14/90)
I don't know if anyone out there has worked with Cromix before, but I
think my problem may be hardware related. Here's the scenario.....
I installed a 1/4 tape back-up is our system the other day, we are
running a 68010 1 meg. Psuedo-Unix machine. Prior to installation the system
was working fine, after I got the drive installed and rebooted the system
and ran a few checks on the system. One of those checks was a "Version" command.
When ran with a filename this does a CRC check, confirms the file is good and
displays a version header. If ran with no arguments it does a consitency check
on the kernal. I have no docs on exactly what it checks, but one thing it does
do is a CRC check on the read-only part of the kernal. I got a error back
saying "system image corrupted". Now, I ran into that before when using the
debugger. If you abort instead of exiting properly you will get this. Seems
the debugger sets the trace and trap vectors to its own routines and upon
exit restores those to the proper addresses. So, the first thing I did was
check the vectors. They are good. To make this a little shorted, I ran
a few checks, back-tracked on what I did and the only mistake I made was
to forget to remove the terminating resistor on the tape drive. (the 2 page
doc I had on the drive said it was at UR5 on the PCB which didn't exist, but I found it).
I pulled the drive back out and removed the resistor, rebooted the system
and suprise, no more errors. The I proceeded to check out the tape drive to
see if it functioned okay, which it did. Then just on a whim I checked the
Version again. Same error. As I said the only other time I had this error
was when the vectors were messed up. They are fine now. I don't know if
anyone out there has ever worked with Cromix, but if you have and have any
ideas could you drop a me a line. I'm lost. The only other thing I can think
of is possibly some bad RAM. the RAM where the kernal is loaded into could
be bad and I'm losing a chunk or so. I'm not sure where and when the CRC is
calculated for the kernal, I assume it's checked prior to loading the copy
off the boot disk and then they compare that with a calculated CRC of the
kernal in RAM. Any ideas????
Morgan
--
Morgan M. Morgan BITNET: TSMJM@ALASKA.BITNET UUCP: uunet!comcon!morgan
CIS: 76164,3477
"Remember....it don't mean shit to a tree!"