I was thinking the [SysRq] would be part of the kernel in the form of a
key-action pair.  The table would be loaded at boot time and would by-pass
running programs checking keyed input directly.  That is what the LINUX
[SysRq] key sequence does.  LINUX uses it for example to kill hung
processes.
It would also be possible to alter and manage the [SysRq] at the command
prompt with some simple program.  Routines to carry out requested actions
are another issue.  Something like simple sending end-of-print-job would be
a BIOS like routine that hooks the printer output.

Cheers.


On Thu, Oct 9, 2008 at 12:40 PM, Alain M. <[EMAIL PROTECTED]> wrote:

> That is a good idea, it is much simpler than reading the screen...
>
> Now all you need to do is a TSR with file access, it probably can be done
> inside int28
>
> ALain
>
> john s wolter escreveu:
>
>> I was thinking it would be useful to have an escape key sequence of some
>> kind.  LINUX consoles have a [system-request] key feature that is a kernel
>> option as I remember.
>> Taking this thought further, a general facility defined in an ini-file
>> that has escape-sequences matched to actions.  A key sequence would do some
>> action like sending an [end-of-print-job] escape sequence to a selected
>> output.  It could also be something to get control back to the DOS prompt.
>>  I'm sure there are other ideas in this form.
>>
>> Just a thought.
>>
>> Cheers.
>>
>> On Thu, Oct 9, 2008 at 9:55 AM, Alain M. <[EMAIL PROTECTED] <mailto:
>> [EMAIL PROTECTED]>> wrote:
>>
>>    There could be an alternative: make a TSR that reads the screen and
>>    detects some special "finished" text in this screen, then opens and
>>    closes the "LPT1" file...
>>
>>    Its a bit complicated, but I have seen/done worse ...
>>
>>
>>    Alain
>>
>>    john s wolter escreveu:
>>
>>        Alain,
>>
>>
>>        That's fascinating.  I'll have to test that.  As far as the DOS
>>        program I'm forced to use, updating it would require a large
>>        investment.  There is no prospect to generate enough cash to pay
>>        for the update.          Somewhere I have some disassembly of DOS
>> which may reveal why.
>>         Where did I put that?
>>
>>        On Wed, Oct 8, 2008 at 10:44 AM, Alain M. <[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]
>>
>>        <mailto:[EMAIL PROTECTED]>>> wrote:
>>
>>           That is one case where millions of ignorant are just plain
>> wrong.
>>
>>           I found a fix for that many many years ago in a Novell manual
>>        and it
>>           works on everything except Dosemu:
>>
>>           Don't write to LPT1:, instead open a file named "LPT1" and
>>        write to
>>           it normaly. You will see that when you *close de file* the
>>        spool is
>>           flushed.
>>
>>           This is no trick, it was well documented at the time, and it is
>>           implemented for basic compatibiliy.
>>
>>           Alain
>>
>>           john s wolter escreveu:
>>
>>               I found not only myself but millions, according to Google,
>> of
>>               others have experienced printing delays when printing from
>>               inside a virtual DOS session.   FreeDOS's parts [ in | on |
>>                inside] XP is not immune to XP's behaviors.  I came across
>> a
>>               fix at Tom's Hardware.  The delays were 17 seconds and 3 to
>> 5
>>               once the changes were made.          I wanted to print to
>>        a TCP/IP networked & USB HP laser printer
>>               from a old DOS program that outputs to LPT1.   No program
>>        source
>>               is available of course and Windows XP does not capture LPTx
>>               output as did Win98.  I've found the NET command still
>>        works in
>>               the DOS box and  LPTx printing can be redirected to any
>>        shared
>>               printer.          NET USE LPT1
>>        \\sharingcomputer\theprinter  at the command prompt.
>>
>>               This includes using \\12.0.0.1 <http://12.0.0.1>
>>        <http://12.0.0.1>
>>               <http://12.0.0.1>\printer localhost loopback.  This
>>        worked but
>>               the printing would not start for 15 seconds.   You can also
>>               install the "Microsoft Loopback Adapter" software  for
>>               standalone computer, turn on networking, share a printer,
>> and
>>               then connect it to an LPTx port.
>>
>>
>>               Specifically here's the fix,...
>>
>>               http://www.tomshardware.com/forum/21658-45-printer-delay
>>
>>               Here it is...
>>               1) in REGEDIT ( START->RUN-> REGEDIT ) click :
>>               Hkey_local_machine then click : System then click :
>>               CurrentControlSet then click : Control somewhere at the
>>        bottom
>>               of the control list Click: WOW
>>               in LPT_timeout property change it to 2 (seconds)
>>               2) Go to SYSTEM.INI file in [386enh] section search
>>        [Network] if
>>               it does not exist enter the following :
>>               [Network] PrintBufTime=10 [IFSMGR] PrintBufTime=10
>>               this will reset the wait to 10 seconds
>>               Hope this is of some use.
>>
>>               --        John S. Wolter President
>>               Wolter Works
>>               Mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>
>>               <mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>>
>>               <mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>
>>               <mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>>>
>>
>>               Desk 1-734-665-1263
>>               Cell: 1-734-904-8433
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> -------------------------------------------------------------------------
>>               This SF.Net email is sponsored by the Moblin Your Move
>>               Developer's challenge
>>               Build the coolest Linux based applications with Moblin
>>        SDK & win
>>               great prizes
>>               Grand prize is a trip for two to an Open Source event
>>        anywhere
>>               in the world
>>
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>        <http://moblin-contest.org/redirect.php?banner_id=100&url=/>
>>                     <
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>        <http://moblin-contest.org/redirect.php?banner_id=100&url=/>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>               _______________________________________________
>>               Freedos-user mailing list
>>               Freedos-user@lists.sourceforge.net
>>        <mailto:Freedos-user@lists.sourceforge.net>
>>               <mailto:Freedos-user@lists.sourceforge.net
>>        <mailto:Freedos-user@lists.sourceforge.net>>
>>
>>               https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>>
>>
>>
>>        --        John S. Wolter President
>>        Wolter Works
>>        Mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>
>>        <mailto:[EMAIL PROTECTED]
>>        <mailto:[EMAIL PROTECTED]>>
>>        Desk 1-734-665-1263
>>        Cell: 1-734-904-8433
>>
>>
>>
>>
>> --
>> John S. Wolter President
>> Wolter Works
>> Mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>> Desk 1-734-665-1263
>> Cell: 1-734-904-8433
>>
>


-- 
John S. Wolter President
Wolter Works
Mailto:[EMAIL PROTECTED]
Desk 1-734-665-1263
Cell: 1-734-904-8433
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to