Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Christopher Chiesa)
Newsgroups: comp.sys.atari.8bit
Subject: Re: 130 XE Service problem
Summary: Fried 130XE
Keywords: 130XE service problem
Message-ID: <3082@bsu-cs.UUCP>
Date: 17 May 88 07:05:23 GMT
References: <670@lakesys.UUCP>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 20

In article <670@lakesys.UUCP>, rich@lakesys.UUCP (Rich Dankert) writes:
> []
> 	I have a 130 XE machine, that will not allow one to do 
> 	anything except watch the RAM test in the self help 
> 	diag's text. It goes there right off. Once in a while one 
> 	can press RESET and get the machine to Basic, but after 
> 	hitting Return, major Lock-up.
>
>	[list of attempted fixes deleted] 

Have you considered/checked the possibility that you have a bad 6502?  I've
seen that happen, although usually the thing just doesn't run, period.  Could
be just something subtle in that the reset line is getting tweaked when you 
don't want it to, in combination with something being wrong in the part of the
CPU that automatically starts at such-and-such location in memory on powerup.

Just a thought...

-- 
UUCP: <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!cfchiesa 
cfchiesa@bsu-cs.UUCP