1. Control+C Bug info...

A still unsolved bug (as I recall) is the fact that ex.exe crashes when I
press control+pause or control+c and I know you are well aware of that.

Nevertheless, I came accros a file on my HD, called config.txt (in the
windows directory) which includes the following information:


--From windows\config.txt ----

BREAK
=====

This command sets or clears extended CTRL+C
checking. You can use this command at the
command prompt or in your CONFIG.SYS file.

You can press CTRL+C to stop a program or an
activity, such as file sorting. Typically, MS-DOS
checks for CTRL+C only while it reads from the
keyboard or writes to the screen or a printer. If
you set BREAK to ON, you extend CTRL+C checking to
other functions, such as disk read and write
operations.

Syntax

    BREAK [ON|OFF]

To display the current BREAK setting at the command
prompt, use the following syntax:

    BREAK

In your CONFIG.SYS file, use the following syntax:

    BREAK=ON|OFF

Parameter

ON|OFF
    Turns extended CTRL+C checking on or off.

----- end of qoute ----

Maybe this can lead to the answer ?

Ralf

new topic     » topic index » view message » categorize

2. Re: Control+C Bug info...

>A still unsolved bug (as I recall) is the fact that ex.exe crashes when I
>press control+pause or control+c and I know you are well aware of that.
>
>Nevertheless, I came accros a file on my HD, called config.txt (in the
>windows directory) which includes the following information:




>Typically, MS-DOS checks for CTRL+C only while it reads from the
>keyboard or writes to the screen or a printer.
BREAK OFF

>If you set BREAK to ON, you extend CTRL+C checking to
>other functions, such as disk read and write operations.

BREAK ON


>ON|OFF
>    Turns *EXTENDED* CTRL+C checking on or off.

>Maybe this can lead to the answer ?


Unfortunetly, no.
BREAK is Off by default, turning it on makes it more
dangerous as you can halt a program in the middle
of writing to a file. (Then you'd have to run ScanDisk)

Are you saying that:

include machine.e
allow_break(0)

Doesn't keep your program from crashing?

I have found that using keyread.e's get_keys(), CTRL+C
doesn't crash the machine. David Cuny also has a solution
in his TextGUI.

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu