1. Loosing control and doEvents
Thanks, Brian. Your comments are right on.
I experienced a machine hangup when I forced Euphoria to write out a
string without sequence markers, and then later read it back in as follows:
....
node_array = {}
for i=1 to 65535 do
node_array &= sprintf("%08d",i)
end for
node_array &= #1A
fn = open("nodes.dat", "w")
if fn=-1 then
puts(2,"Could not create or open file")
x = wait_key()
abort(x)
else
puts(fn, node_array)
close(fn)
end if
....
....
node_array = {}
node_array8 = {}
trace(1)
for i=1 to 65335 do
for j=1 to 8 do
node_array8 &= getc(fn)
end for
node_array = append(node_array, node_array8)
end for
The resulting file has the expected length (524281). The system first
reported it as having length zero for reasons that I do not understand.
I have forgotten what I did between that time and the time at which it
reported the length correctly.
Trace reveals that the first subsequence (8 characters) is read in with
no problem. The next getc() results in loss of control.
As has been pointed out, doEvents would not have been of any use in this
situation.
My own ability to investigate the problem further is hampered both by my
lack of knowledge, and by the fact that my computer has developed the
enraging habit of having the power switch become inactive so that it
must be unplugged. Then, on startup it freezes in the BIOS activation,
immediately after the NVidia graphics card is recognized.
It remains unusable for several hours, but responds "almost" properly
after a night of being off. I say almost because, on boot up the next
morning, the screen has a jumbled appearance and the computer must be
turned off and back on. At this point, the power switch works just fine.
The symptoms suggest:
temperature effect
capacitor discharge time
static electricity discharge
volatile memory effect
I suppose temperature is the most likely cause and replacement of the
computer is the most likely solution. Anyone ever seen a similar case?
I would appreciate comments on either the coding problem or the hardware
problem.
Allen
2. Re: Loosing control and doEvents
On Sat, 03 Jan 2004 17:34:23 -0600, Allen Robnett
<alrobnett at alumni.princeton.edu> wrote:
<snip>
>remains unusable for several hours, but responds "almost" properly
>after a night of being off.
<snip>
> capacitor discharge time
<snip>
>replacement of the
>computer is the most likely solution. Anyone ever seen a similar case?
>
>I would appreciate comments on either the coding problem or the hardware
>problem.
Four or Five years ago I was playing with installing Linux, & not
entirely unsurprisingly, it really did not like my WinModem. At the
time, it needed about four hours power off for the WinModem to be
usable when I rebooted to Windows. About two years later, that had
worn down to about ten minutes.
What I'm suggesting is it may be nothing whatsoever to do with a
hardware error, but a config error, I dunno, maybe it thinks your
on/off switch might be a sound card, so sends it some garbage (to see
if it really is a sound card), which knocks it for six. Whatever,
although I no longer use the WinModem, the rest of the PC is still
going fine. I wouldn't waste money on it, but a newer or indeed older
version of the OS might clear things up, you never know. Worth trying,
(imo), if you have that option.
Regards,
Pete
3. Re: Loosing control and doEvents
Sounds like some sort of BIOS corruption.
When your problem happends and you cannot turn the computer back on;
Before attempting the following you may want to check your current BIOS
setup, to besure
you know how it is setup, if you did not set it up origionaly yourself.
1) Unplug the computer,
2) Open (remove) the 'clear CMOS' jumper located on the mainboard for about
a minute or more to drain the CMOS battery
3) Then close (put back) the clear CMOS jumper,
4) Plug the computer back in and turn the computer on.
5) Open your BIOS setup and 'load defaults' and reset any custom
configurations, 'save and exit'.
See what happens, If computer boots normaly then there was CMOS curruption,
wich has now been fixed.
* You may want to check and clean ur CPU fan(s) while the lid is off.
If the above fixes your problem I have some suggestions on how to fix it.
----- Original Message -----
From: "Elliott Sales de Andrade" <quantum_analyst at hotmail.com>
To: <EUforum at topica.com>
Sent: Sunday, January 04, 2004 6:05 PM
Subject: RE: Loosing control and doEvents
>
>
> >From: Allen Robnett <alrobnett at alumni.princeton.edu>
> >Reply-To: EUforum at topica.com
> >To: EUforum at topica.com
> >Subject: Loosing control and doEvents
> >Date: Sat, 03 Jan 2004 17:34:23 -0600
> >
> >My own ability to investigate the problem further is hampered both by my
> >lack of knowledge, and by the fact that my computer has developed the
> >enraging habit of having the power switch become inactive so that it must
> >be unplugged. Then, on startup it freezes in the BIOS activation,
> >immediately after the NVidia graphics card is recognized.
> >
> >It remains unusable for several hours, but responds "almost" properly
after
> >a night of being off. I say almost because, on boot up the next morning,
> >the screen has a jumbled appearance and the computer must be turned off
and
> >back on. At this point, the power switch works just fine.
> >
> >The symptoms suggest:
> > temperature effect
> > capacitor discharge time
> > static electricity discharge
> > volatile memory effect
> >I suppose temperature is the most likely cause and replacement of the
> >computer is the most likely solution. Anyone ever seen a similar case?
> >
>
> These sound like symptoms of a faulty power supply.
>
> >I would appreciate comments on either the coding problem or the hardware
> >problem.
> >
> >Allen
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
> --
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.556 / Virus Database: 348 - Release Date: 26/12/03
>
---
--
