1. Re: pcspeak.zip...
Crag Gilbert wrote:
> Sloppy Fix: Take out all the '\n' characters at the end of the puts()
>lines, then put locate() statements before each puts() to line up the menu
>lines correctly. Brutal and ugly, but it should work. Or extend the
>strings out with spaces to make them wrap to the next line naturally.
>
> There is one possibility. The pcspeak.e file has the statement
>tick_rate(500) in it, to get the necessary resolution for some of the sound
>effects. High tick rates can cause very strange errors on some machines,
>so you might try commenting that statement out to see if it works properly
>that way. Of course, if you do that, not all of the sound effects will
>work then.
>
Thanks Craig Gilvert,
"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...
