It is clear what is damaged in your computer.
Your 8253 timer contains 3 16-bit timers counters and is attached to system
bus. Output from timer 0 is attached to interrupt level 0 and is used to
generate an interrupt each 54.925 ms. Thanks to this timer system's time of
day clock works and I/O routine too.
Output from channel 1 is used to generate DMA request on DMA channel 0, this
is used to refresh DRAM.
Since your timer is not working properly you got also parity error due
missing refresh cycles.
You computer starts but after it got hot it hangs, this MAY be a bad
elettrical contact: remove and re-insert you 8253 chip. At least you must
replace it.
------------
If you find this info useful please give me a click: http://www.khet.net/gmc
> On 2000-10-15 [EMAIL PROTECTED] <Sam> said:
>
> >Error 102 = Timer Failure.
> >Info is from "Pocket PC Reference" by Thomas J. Glover and Millie M.
> >Young, 5th Edition, and is found in the section dealing with IBM
> >XT/AT class error codes. See page 62.
>
> The only reference I have to a "timer" of some kind is in the
> glossary of a repair book I have called *Assembling and
> Troubleshooting Microcomputers (James Perozzo; Delmar Publishers,
> Inc.), where it says:
>
> "Timer chips - Integrated circuits used to provide digital waveforms
> or to provide timing functions through their counting ability."
>
> There is no other information (not easy to locate, anyway) about
> troubleshooting a problem with "timer failure". As a matter of fact,
> this book provides the IBM diagnostic disk's error codes, but for some
> reason 102 is not listed (101 and 103, but not 102).
>
> >Another error you mentioned in one of your posts on this subject is
> >"Parity Check 1 6000". I could not find this error listed.
> >Perhaps, and this is just my guess, the 6000 is a hex address.
>
> That's "Parity Check 1; 60000 (s)". I think I found the reason for
> that problem (which was on the IBM AT), but now I'm focusing more on
> the PC/XT problem.
>
> P.S. -- Just a moment ago, the PC/XT stalled again, but this time a
> message from PC DOS appeared at the bottom of the screen after a short
> beep:
>
> "Internal stack overflow
> System halted"
>
> Could this be what's halting the system... and I finally got a message
> explaining the problem from DOS? I quickly investigated the nature of
> stack overflow problems, and they exhibit the same symptoms we've been
> attributing to "chip creep", etc.. So I've added stacks=12,128 to my
> config.sys file (PC DOS 3.3 on the XT) and will report whether or not
> that helps with the stability of this system.
>
> Jerry >>>> USR Courier HST--V.32 | IBM PC/XT & PC Color Display <<<<
> >>>>> PC DOS 3.3 & WordStar 3.30p | 20 MB HDD & 360K FDD <<<<<
>
> Net-Tamer V 1.11.2X - Registered
>
> To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
> unsubscribe SURVPC in the body of the message.
> Also, trim this footer from any quoted replies.
> More info can be found at;
> http://www.softcon.com/archives/SURVPC.html
>
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
