[comp.sys.atari.st] Help! Hot memory?

Bill_Moore@mindlink.UUCP (Bill Moore) (03/12/91)

I have an older ST (purchased in 1986) with an easieST memory expansion board
installed with 2mb of memory.  Recently it has begun to lock up with narrow
vertical lines on the screen and eleven bombs. This happens when the machine
has been on for at least 1 1/2 hrs.  If I am able to reboot I have only 1/2 mb
of memory available.  I had the connections to the expansion board soldered,
and that has improved the problem -- it happens less often and the machine can
be on longer -- but it still happens.  Any ideas??  Suggestions??  Did this
ever happen to anybody else out there?  Thanks in advance -- a lot!!

hojo@cbnewsb.cb.att.com (HC Johnson) (03/15/91)

In article <5116@mindlink.UUCP>, Bill_Moore@mindlink.UUCP (Bill Moore) writes:
> I have an older ST (purchased in 1986) with an easieST memory expansion board
> installed with 2mb of memory.  Recently it has begun to lock up with narrow
> vertical lines on the screen and eleven bombs. This happens when the machine
> has been on for at least 1 1/2 hrs.  If I am able to reboot I have only 1/2 mb
> of memory available.  I had the connections to the expansion board soldered,
> and that has improved the problem -- it happens less often and the machine can
> be on longer -- but it still happens.  Any ideas??  Suggestions??  Did this
> ever happen to anybody else out there?  Thanks in advance -- a lot!!

You probably have 1 or more bad bits in the addon memory.
Remember, 1 bit is in each of the 16 chips.

When the bit goes bad, so goes the programs running in that memory; and you
lock up.  On reboot, TOS does a memory existence test to size the machine.
Your memory does not read back what TOS wrote, so the memory is truncated
at .5Meg.

This happened to me.  I wrote a simple C program to write/read back memory
starting at 0x8000 and soon found a bit being dropped. (write 0xffff to see
if a bit comes back 0, then write 0x0000 to see if a bit comes back 1).
In my case 1 bit was usually a 1. (it was floating).  I replaced the
corresponding  chip and all was well.

Howard Johnson
ATT BELL LABS
att!lzsc!hcj
hcj@lzsc.att.com

S_EDELMANN@iravcl.ira.uka.de (|S| Hans Chr. Ede) (03/15/91)

In <5116@mindlink.UUCP> Bill_Moore@mindlink.UUCP writes:

> I have an older ST (purchased in 1986) with an easieST memory expansion board
> installed with 2mb of memory.  Recently it has begun to lock up with narrow
> vertical lines on the screen and eleven bombs. This happens when the machine

I think it's just a contact problem. I wrote a program to find such errors
and i've included it in this message.
Just start the program, choose your configuration and wait until an error
occurs. Then you can see which ram chip is the problem (each bit
corresponds to a ram chip).
Remove that chip and start the program again. If the same bit is defective,
you have the right one.
Then you can try exchangching it with another chip on the board. If the
error is in the same bit, then it's a contact problem, and you should 
solder each contact of that socket again.
If the error is now in the other bit, then the ram chip is defective and
you should exchange it with a new one.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I   Hans Christian Edelmann  (at University of Karlsruhe, Germany)  I
I   E-Mail :  s_edelmann@iravcl.ira.uka.de or uk9d@dkauni2.bitnet   I
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

table
 !"#$%&'()*+,-./0123456789:;<=>?
@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
begin 644 ramtest.lzh
M(<4M;&@Q+=X#   &"0  D %O%B  "U)!351%4U0N4%)'YQ?V:;&8>4<L$V ,z
M;@NZ@-CVCE\BW*]KF^@;N+>S+VMIX*[K<SYY:?0LPHT%XKM803JJ4;&>!$=[y
M\<]/3L>+[LP.0HSD#!71!0;RC(7)-UP(5ZWB5C[<56[9=%G3:?K().]+#;-\x
MF1?I.?07GD$Z+&+YM]@+#2/DX3\P/@540N&&WW )/HA?LM /49JW"A+F<^'7w
MII>(JO)_>.S]K*)V==G)E("S1U:48D\ZJ\_&(7_0QRI'F8KY 'BBY8(T5(,0v
M %)'Q!_?VS#>A/"-+-QMX@'*H\$8A7/QFD=7&*-TS=Y[/!_#.$%.$#@;OF?5u
ML/F[]F0WIG+K',PX([!.T7Y)@/T_?=WL *?%\8)YQ&,8FGEXNYMS"GN2&EW.t
M'1Z_ R#N9U$JUO4B.OI@U\O7'ID:Z/7>SIOK O[T$ 6_D@M?K"X+#9 N+B"Ts
M2L4IWN0%@$(+4ZR!\J6)MGW+I@E[\F9+B*=FBE8A]PW^AG*&KNZ=60D:A8/;r
M%$;?>\%7Q:J17HSR4W"(1[@)[[5O.Z0Z:4ATQ;3IO7'3%O.G3J=-E1TJK.G0q
MPZ66G2HXZ4LSJ4?KQ$S.T$S+T$SS,4SS%$S@*IFLU3/'JF>-5,U>$S5:NF>=p
M;RH)?N@'#*XQZ<67KKD^S;>TU&Y+-C=\F["WK2:+8R^'T,C(04HVH/1E&B)1o
ML-9P-Q9P)TG L"<#,)P,\W CFX% W JFX%>U5&EX5"GFFQZ[FUB#E6VVG.NMn
M,XRT08K^<U ^,?KU"&P=QO*CM#R_L$$KEC68T0^O:RB<H_DJ4[IOLLWVGJ'0m
M*'0HAI\D>MZYP:M:@G60#KU,!Y0??>4_.2R7_ UAR:6B=34\_R!@!UXV\J;/l
M/IS-92LJ"*2QAEZSWV-&X??#>?-1A@(>)2MCL99FWAY@,LQA2E\_Y"1(P4I]k
M$(23F/FQ".D934;'L'*5N&Q8XT,H$W58][(9=1,5 UR=#4I216,(.V^^\RZ8j
MT!!\T0L ^OXUG.ZBA)H=X[GY12;;."%_?X?\\,3O3\ZWAWSE&42I(CX4D+QSi
MLW?7R&6T3:3=C9Z=APQ*U9"*?U/>]V;'?3ANF^L-.^<P[09O7!VBK4R].Y/3h
M$1:&[-U8Z^>5M90"X]"MYX;6^Z\G$J>"DQ)REL*4WEE-M:Q!?=A&K^UR (,-g
M ':R@"!?\ 5S*K 9Y_>?]W\YHK)S8^Z:H"[H/RBFX&#8:'!.!,/4$R:P.[)8f
MU">XV!C7_([2(B%VM$CR%,F4>$HR=16AIN,2WV_9@H8$RS-7&9J[34T_B7REe
DM7PJ\_G*MOD&M@.>Z@Z4WC&C[B;^'F,QUX_3%2=[7^GZ^0  d
 c
end

Roger.Sheppard@bbs.actrix.gen.nz (03/15/91)

Distribution:world 

In article <5116@mindlink.UUCP> Bill_Moore@mindlink.UUCP (Bill Moore) writes:
> I have an older ST (purchased in 1986) with an easieST memory expansion board
> installed with 2mb of memory.  Recently it has begun to lock up with narrow
> vertical lines on the screen and eleven bombs. This happens when the machine
> has been on for at least 1 1/2 hrs.  If I am able to reboot I have only 1/2 mb
> of memory available.  I had the connections to the expansion board soldered,
> and that has improved the problem -- it happens less often and the machine can
> be on longer -- but it still happens.  Any ideas??  Suggestions??  Did this
> ever happen to anybody else out there?  Thanks in advance -- a lot!!

Try reseating the MMU, as they do get dirty contacts, also Note, that
Atari now fit Clamps to hold the sides of the Sockets in..
its wise to do the same to the Glue...
-- 
Roger W. Sheppard   85 Donovan Rd, Kapiti New Zealand...