DB>> Procedure My_Break;Interrupt;
DB>> Begin
DB>> end;  {Does absolutely nil}

IS> Of course, you could always use it to set some global 
IS> variable, such as CtlBreakPressed := true, or such, which is 
IS> easy to test per some loop.

Yep, or make a big screen come up shouting "I'm not letting you out,
nah nah!!" or "The programmer has deemed you an inappropriate
person to use this function!" :)

DB>>  getint($1B, real_break); {Get pointer to the old 
DB>> interrupt} setint($1B, {at}My_Break);  {Set the interrupt to a
DB>>  procedure} Do_whatever_you_want_here;
DB>>  setint($1B,Real_Break) ; {Don't forget to reset it before 
DB>> you exit}

IS> Indeed!  This suggests maybe setting up an ExitProc for 
IS> safety, too.

Why not.. 

IS> PS: thanks for the VP demo.  Not half bad, eh?  I've only 
IS> played with the examples so far, but am quite impressed.  I 
IS> should check SpeedPascal too ..

It is pretty good isn't it. I don't like speed pascal as much but your
welcome to grab a copy anytime. If you run in 1024x768 the font in VP is a
bit small but if you use an INI editor and edit your USER.INI you can
change it. Go to the settings for "Virtual Pascal PM IDE" and
change the FontX and FontY. Makes it much easier to read. I'll have to look
for some delphi code to convert to OS/2.

Doug.

--- Msgedsq/2 3.10