Dear folks,
Yes, as Garry points out here, hardware issues are also possible
culprits. (Less likely than poorly-compiled or corrupt software, in
my experience, but YMMV.)
Anthony J. Albert
On 20 Feb 2001, at 23:19, Garry wrote:
> Yes, it is possible for hardware to do this.
> Remember, if an instruction value is bad when the CPU
> "sees" it, it doesn't matter how it got that way.
>
> A bad memory chip, damaged CPU, dirty connection
> with motherboard, etc. can all cause things like this.
>
> I had to replace my old Cyrix 686 (pentium-class CPU)
> last year because it overheated over a prolonged period
> of time (bad cooling fan). The symptoms were frequent
> illegal instructions, protection faults, and so on.
>
> I replaced the CPU and fan, reinstalled the operating system
> and -- poof! -- no more problem. (It's still a slow, 166 mhz
> machine, but at least it doesn't blow up any more.)
>
> ~~Garry
> [EMAIL PROTECTED]
>
> ----- Original Message -----
> "Constant Brouerius van Nidek" <[EMAIL PROTECTED]> wrote:
>
>
> > Dear Garry
> > Understood (more or less ;-)) your expose.
> > I am already working on this computer since months because it will
> > not work properly. Is this opcode error caused by software only or
> > could it also be caused by a hardware glitch?
>
==============================================================
Anthony J. Albert [EMAIL PROTECTED]
Systems and Software Support Specialist Postmaster
Computer Services - University of Maine, Presque Isle
"We took risks. We knew we took them. Things have come out against
us. We have no cause for complaint." - Explorer Robert Scott, found in
his diary after his party froze to death in Antarctica.
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
