Ok, the scroll lock saga is now much closer, but still has the curious business about the Pause key pausing program execution. This just ain’t so. I gave an example that anybody could run to demonstrate this, and a loong explanation why this may appear to be happening, but that apparently wasnt enough evidence.
So, as more evidence, I opened up my big can of programming whup-butt, and wrote a bunch of programs, in various languages, to test this very thing. Below are the programs written in FORTRAN, Pascal, Perl, and C. All they do is loop forever, writing output.
Perl example:
$i = 0;
while( 1 ) { print "This is a test of interrupting output…$i
"; $i++ }
**** FORTRAN EXAMPLE
I = 0
10 WRITE( 6, 100 ) I
I = I + 1
GOTO 10
100 FORMAT( ‘This is FORTRAN LOOP test #’, I10 )
END
/* C Example */
#include <stdio.h>
int main( void )
{
int i; i = 0;
while( 1 ) { printf("This is a test… %9d
", i ); i++; }
}
{ Pascal Example }
program runs( input, output );
var i: integer;
begin
while( true ) do begin writeln(‘This is test #’, i:10 ); i := i + 1; end;
end.
I compiled the FORTRAN example with Lahey FORTRAN 95
I compiled the Perl example with ActiveState Perl 5.8
I compiled the Pascal example with Borland Pascal 6
I compiled the C example with Borland C 5.5
I ran them all the same way: runs.exe >OutFile.Txt
oops, except for the perl one: perl runs.pl >OutFile.Txt
After 10 seconds I pressed the Pause key.
In every case, (Gomer Pyle voice) Surprise, Surprise, Surprise!,
the program kept running, as indicated by the Windows task Manager, the disk light being almost full on, and a growing disk file appearing on the disk:
07-Oct-03 03:07:33 PM 0 OutFile.Txt
07-Oct-03 03:07:48 PM 45,438,768 OutFile.Txt
07-Oct-03 03:07:57 PM 86,303,806 OutFile.Txt
07-Oct-03 03:08:22 PM 245,665,261 OutFile.Txt
07-Oct-03 03:08:38 PM 315,097,096 OutFile.Txt
07-Oct-03 03:07:49 PM 374,349,508 OutFile.Txt
Now it’s quite possible that every program Ms. P has run lately has some built-in quirk whereby it polls the Pause key. That’s not completely out of the question. I’m just trying to show that this isnt a feature that’s built into the operating system, and it’s not a part of any common computer language behavior.
Oh, and I almost forgot, tere’s still the bit about: " Some DOS communication programs used the Break key as a shortcut to terminate a modem connection, but that was really a function of the program, not the operating system."
??? Huh ??? Do you have a source for this? Because all indications are that the break key only broke modem connecionts on the very old Teletypes, which inherited this from telegraph days.
I don’t recall a single comm program that did this, for several reasons.
#1:It would be silly to have the break key do anything other than send a “break”.
#2: The way you usually ended an on-line session was to send some “BYE” command to the mainframe that way it could properly log you off and IT would hang up the phone, this was much prefferred that you just breaking the connection abruptly, and perhaps leaving your connection open racking up connect time charges.
#3: Even if you did want your modem to hangup, 99% of the comm programs expected to be talking thru a “hayes command set” modem, where the one and only command for hanging up was “AT”, followed by “AT H”. Either you could issue these commands right from the keyboard, or there would be some “Hang up” command in the comm program that would do the same. But sending “break” was never a hang-up option on any comm program I’ve ever seen.
Regards,
grg88