1. Re: pcspeak.zip...
At 08:18 AM 10/14/97 +0900, Lee woo seob wrote:
>Thanks Craig Gilvert,
You are welcome :)
>"Sloppy Fix" worked. i also tried commenting tick_rate(500) statement,
>but it made no difference... i really don't understand why this kind of
>problem occurs, and what makes me more confusing is that, the problem only
>occurs in my old 486, but does *not* occurs in my 586! (i have two
computers).
>Hmmm....
>
>from Lee woo seob...
>
>
Hmmmm indeed. After going back and looking at all the include files, I
only have one other possible culprit to suggest. The test.ex file calls
the routine get_cursor() (from screen.e), which makes an dos interrupt call
to get the current text cursor shape. Perhaps I did not make the call
quite correctly, or something of that nature. Or, perhaps the 486 you
referred to just doesn't like that dos call :).
Seems kind of unlikely to me, but *something* weird is happening there,
and get_cursor() and tick_rate(500) are the only two statements in the
whole program that are not perfectly standard, normal Euphoria.
Oops! Just remembered something. When Euphoria crashes with the tick
rate high, it is left set high. I know you did not mention a crash, and
Euphoria is supposed to reset the tick rate when it exits normally, but
suppose that setting the tick rate to 500 scrambled the silicon brains just
enough that Euphoria could not set the tick rate back to normal after
exiting? Then the problem would still be there even though you commented
out the tick_rate() line. Have you tried commenting it out, *rebooting*,
then running the program?
-----------------------------------
Craig Gilbert
cgilbert at cennet.mc.peachnet.edu
"Positing infinity, the rest is easy."
-- Roger Zelazny, in 'Creatures of Light and Darkness'
-----------------------------------
