Last Try to Resurrect Sick UNIXpc
Dave Mundhenk
doc at nucleus.UUCP
Mon Sep 18 04:09:09 AEST 1989
Well, I'm posting again regarding weird goings-on in my 7300.
I may be wearing out my welcome here, but the way things are
going I probably won't be a UNIXpc owner much longer, at least
the owner of a "working, intact" UNIXpc.
The machine is a P3..P5 512K motherboard. I have a 512K RAM
expansion card in it. The motherboard has a daughterboard over
the area where the battery is - others I've seen don't have
this and I don't know the significance of it. I pulled the dead
original battery and wired up a battery holder outside the case.
Motherboard appears to have extensive field mods (know what
'vermicelli' is?). ;-)
I run the hard disk off an external 150 Watt power supply.
Disk is currently a CDC 94155-85. (Brand New). Had foundation
set installed and running briefly when the root directory appeared
to be trashed - /tmp was a very large FILE with 000 permissions, etc.
Now trying to re-install the foundation set from either of 2 known
good sets (3.5 and 3.51). Got some floppy-related errors so I've
tried everything with another known good floppy drive also.
Here are some of the errors encountered:
In diagnostics,
Test: Floppy disk Test
Subtest: Random seeks with read sector
Pass: 2
Error: FLOPPY: Error on Check - Read: Response = 8,
start Block = 1.
Test: Hard Disk Test (Drive 0)
Subtest: Read all the disk
Pass: 1
Error: WINCHESTER: Error on Check - Read: Response = 40,
start Block = 31063.
Test: Expansion memory test
Subtest: Data bus test (Walking 1's)
Pass: 1
Error: Memory error at Address 0: Wrote 80; Read back 0.
^
|
This repeated for 2,4,6,8,A,C,E,10,12,14,16, etc. before
I aborted and moved on...
Here's what happens when I read in the Foundation Set:
Floppy boot boots OK (sometimes must power on & off several times
first). Prompts for Floppy File System Disk. Floppy FS disk reads,
prompts "...want to continue? [Yes,No]" and I answer "y". It says
"making file system on hard disk". OK. Then "copying loader onto
hard disk". OK. Then "Copying System V files to hard disk" or
something like that. After about 10 seconds, I get the message:
#FDERR ST:40 TR:3 SR:1 DR:0 DMACNT:FF00 DCRREG:F7 MCRREG:CF00
#FDERR ST:40 TR:3 SR:1 DR:0 DMACNT:FF00 DCRREG:F7 MCRREG:CF00
#FDERR ST:40 TR:3 SR:1 DR:0 DMACNT:FF00 DCRREG:F7 MCRREG:CF00
^
panic: dup mem alloc |
|
Please record the panic message. |
Press hardware reset to reboot. |
|
[This came out as "CD00" several times also...]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I think this may be my final plea for help. I can't afford to
put much money into this machine, and if it needs work on the
motherboard I will probably have to sell the 70MB disk and use
something smaller and slower |-(
I got a variety of sugg{Ystions in response to previous postings.
Most were "bad floppy drive", "bad WD1010", "RF interference".
Augustine Cano mentioned that it might be the DMA chip, so it
be worth a try to replace that [them?]. Did I mention that I also
put in a new WD2010? Just out of curiousity I may put the WD1010
back in. What the hell. I'll try feeding it toast and coffee if
it will help.
If it is really sick I will part it out and stick with IBM
compatibles and 3B's (or whatever else is handy that WORKS!).
BTW, I have a DOS-73 board that I was hoping to install in this
machine if I got it working. If this is curtains, anyone want to
make me an offer on that or any other parts?
-sigh-
I like this machine, please help me resurrect it!
Dave Mundhenk =-=-=-=-=-=-= 201-580-4943
Please reply to: ...!att!lc15a!doc
--
Dave Mundhenk =-=-=-=-=-=-= 201-580-4943
Please reply to: ...!att!lc15a!doc
More information about the Unix-pc.general
mailing list