•  Back 
  •  Main 
  •  Index 
  •  Tree View 
  •  Cross references 
  •  Help page 
  •  Show info about hypertext 
  •  View a new file 
Topic       : TosWin2
Author      : Christian Felsch
Version     : 2.7
Subject     : Documentation/miscellaneous
Nodes       : 31
Index Size  : 838
HCP-Version : 3
Compiled on : Atari
@charset    : atarist
@lang       : en
@default    : 
@help       : 
@options    : -s -t4 +z
@width      : 75
View Ref-FileCommunication between tw-call and TosWin2

The communication between tw-call and TosWin2 is done via several
messages. Shared memory is used for data exchange, so there are no
problems with memory protection.

The following messages are exchanged:

   TWSTART (0x0CF1), tw-call -> TosWin2
      tw-call asks TosWin2 if it is ready to receive data.

   TWOK (0x0CF2), TosWin2 -> tw-call
      Answer from TosWin2 to TWSTART.

   TWWRITE (0x0CF3), tw-call -> TosWin2
      tw-call has stored the data in the SharedMem. The block is
      available under the name u:\shm\tw-call.xxx, where xxx stands
      for tw-call's GEM-ID. The block has the following structure:

         char  name[256]   Program name with path.
         char  pfad[256]   Current directory.
         char  arg[4096]   The arguments, separated by "\n".
         char  env[4096]   The environment as a copy from the
                           tw-call basepage.

   TWREAD (0x0CF4) TosWin2 -> tw-Call
      TosWin2 has read the data.

   TWERR (0x0CF5) TosWin2 -> tw-call
      An error occurred while reading.

In addition to the program data transfer messages, the following is also
sent:

   TWTOP (0x0CF6) tw-call -> TosWin2
      A TOS program menu entry has been clicked and TosWin2 should top
      the corresponding window.

   TWSHELL (0x0CF7) tw-call -> TosWin2
      If tw-call is started with the "-l" option, it sends this message
      to TosWin2, so that TosWin2 starts a new shell.