GEMDOS console functions and termination upon ctrl c

[Count]

As you may know, the GEMDOS console functions like Cconout, Cconin etc. lead to program termination when ctrl c is pressed. Same with mintlib's standard io functions, which use Fwrite and Fread.

Is there any way to disable this behaviour (plain TOS)?

[charles]

rewrite over it in memory?
or avoid using it.

[joska]

Not tested by me, but I believe you can use Crawin()/Crawio() for character input/output.

[wongck]

Not tested, may be Bconin/Bconout is low level enough?

[joska]

As a general rule you should not use BIOS functions when writing a GEMDOS program.

[wongck]

Ah, learn something new everyday. Thanks for the rule.

[Count]

As a general rule you should not use BIOS functions when writing a GEMDOS program.

That was my intention to ask this question. But if there is no chance to disable that by setting a bit in a system variable or something like that, I will switch over to BIOS functions. The RAWCON device is no option since I need the VT52 sequences.

[shoggoth]

If you’re writing C code, just catch the appropriera signal iirc.

[Spectone]

When a ctrl-c is received gemdos calls Pterm() but before it terminates the process it call the etv_term vector to give the process a chance to clean up. Setexc() can set the etv_term vector.

Where does Pterm() lead to? Probably the previous Pexec(). You can call Pexec() youself and when you get that Pterm() execution will return to just after the Pexec() you called.