ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / OS2 / OS2YOU20.ZIP / OS2YOU.DOC < prev next >

Wrap

Text File | 1991-05-05 | 48.4 KB | 1,024 lines

OS2YOU 2.0 (read OS/2 to you) 1991-04-09 (c) 1990 Mikael Wahlgren ========================================================================== Introduction ============ Os2You is a communication software to allow remote operation of any OS/2 full screen text session and the DOS compatibility box, over an asynchronous line (by cable or modem), a pipe or a remote pipe (over a LAN). The program can be used with many different terminals and allows high speed file transfers between host and remote. The program may be used in two different ways. You can run the program as it is stand alone, but it is also possible to call the program from your own program, allowing your own programs to offer remote operation. The program can directly replace the program MaxPipe (from Peter Fitzsimmons), and will be compatible with more programs than MaxPipe. The program is only tested with OS/2 1.3 SE, but should work OK with OS/2 1.2 and OS/2 2.0. If you have got the distribution files packed in a ZIP-file, you should unpack them first. Files included in this package: OS2YOU.EXE The remote software OS2YOU.DOC This documentation SPECS.DOC Specification for the pipe protocol ORDER.DOC Printable Order/Invoice form LANTERM.EXE Terminal program using DOS on a LAN or modem. LANTERM2.EXE Terminal program using OS/2 on a LAN or modem. LANBRIDG.EXE LAN Bridge, to access OS/2 Requesters remote over LAN DOS2YOU.EXE Program to access DOS compatibility box DOSREDIR.EXE DOS-program required to use DOS compatibility box remote ????????.PRM Terminal description files for different terminals SZ.CMD Command file to initiate Zmodem file transfer from host to remote using M2Zmodem (not included). RZ.CMD Command file to initiate Zmodem file transfer from remote to host using M2Zmodem (not included). If you don't think this is the most current version of Os2You, you could send a formatted diskette and four International Post reply coupons (Coupon-Réponse International, Union Postale Universelle) to my address mentioned last in this documentation. Stand alone installation ======================== You should copy all the distributed files to a subdirectory on your hard disk. The directory should be specified in your PATH and DPATH environment variables. Assuming you have copied the files to subdirectory called "C:\Remote" this is done by the command: SET PATH=%PATH%C:\Remote; SET DPATH=%DPATH%C:\Remote; To configure the program in stand alone mode, you run the program OS2YOU from an OS/2 Command Prompt, without any parameters. You will get a configuration menu with different options. When you have configured the modem, you can either enter host mode operation or exit the program. Note that you should always use a Full Screen text session for the programs. The asynchrous support device driver COM0x.SYS driver should also be loaded in your CONFIG.SYS file. To start the program with an existing configuration file, you start the program by typing "Os2You -c <cfg-file>" at the OS/2 Command Prompt (you replace <cfg-file> with the configuration filename you want to use). For more command line start options see separate section below or enter "Os2You -?" at the prompt. The program will now put the modem into auto answer mode (if your modem is supported by the program), and wait for an incomming call, and answer it. When the connection is established, the caller will be asked for an ID and password and validate them with your configuration file. If you have specified a callback number for the caller, the connection will be closed, and the Os2You program will call the phone number in the userlist entry (note that you should only include the phone number in the user list entry and not the Hayes command prefix "ATD", but if you want, it is possible to include any dialling command in the entry). The caller will be asked for the password once again, and will then be spawned to an OS/2 full screen text session. If you have OS/2 1.2 or later, it is recommended to put the line "AUTOFAIL=YES" in your CONFIG.SYS file. This will cause the operating system NOT to generate pop-up error messages, which would cause the Os2You- program to hang (or actually be suspended while waiting for a keystroke from the "real" keyboard). With the default priority (priority set to 14), the screen update thread has exactly the same priority as the executed program. This results in a regular screen updates in most situations. Sometimes however a higher value may result in smother operation. If you find that the screen update performance is not at all what you expected, you may try to change this value. Note that sometimes, a higher priority means that the thread will steal too much CPU, resulting in much worse performance. Using Os2You with pipes or remote pipes with a LAN ================================================== It is possible to use Os2You in a LAN, in two different ways. You can install Os2You on a OS/2 network SERVER, and access it remote from any workstation in the LAN. You can also install Os2You on a network REQUESTER, and access the requester from any workstation in the LAN, but this will require that the LanBridge program is installed on an network server. If you want to use Os2You in a LAN on a SERVER, you should configure Os2You for stand alone operation (se above), but replace the communication device with a remote pipe name like "\Pipe\Os2You1". If you want to use Os2You in a LAN on a REQUESTER, you should configure Os2You for stand alone operation (se above), but replace the communication device with a remote pipe name like "\\Servername\Pipe\Os2You1". You will also have to install LanBridge (LANBRIDG.EXE) on the LAN SERVER specified in the pipe name. You install LanBridge like: LanBridg \Pipe\Os2You1 \Pipe\LanTerm1 Regardless of how you have installed Os2You, you have to use the LanTerm or LanTerm/2 programs to access Os2You over a LAN. The program LanTerm is used on workstations running DOS and LanTerm/2 is used on workstations running DOS. The programs are started with just one parameter specifying which pipe to use for communication. Suppose you configured the system with the pipe name mentioned above. In this case you start LanTerm or LanTerm/2 by typing: LanTerm \\Servername\Pipe\Os2You1 LanTerm2 \\Servername\Pipe\Os2You1 at the command line prompt. The LanTerm and LanTerm/2 programs are automaticly terminated when you exit the remote session. If you terminate LanTerm or LanTerm2 abnormally (like pressing Ctrl-Break), the host session will be closed at once, and Os2You will wait for the next "caller" and LanTerm or LanTerm/2 will be terminated. If no parameter is specified when starting the LanTerm or LanTerm/2 program, it will look for an Os2You.CFG file and try to configure itself using the information specified in the file (using the Install.EXE program). LanTerm/2 (but not LanTerm) may be used for asynchronous communication devices as well as pipes. With LanTerm and LanTerm/2 most keys that is possible to emulate with Os2You, are mapped to their correct keys, except <Esc> that you have to press twice, for compatibility reasons. All Esc-sequences used over the asynchronous line will work with LanTerm and LanTerm/2 too. It is possible to start multiple sessions with Os2You using the same Pipe- name. Each running copy of Os2You will be ready to receive a connect request from a remote user, and the user will be connected to the first free instance of Os2You. It isn't even necessary that the Os2You program is started from the same machine in a LAN. You may start Os2You with the same pipe name from any LAN station, and a connect request will be directed to the first free instance. Note, that early versions of OS/2 LAN Server did not work properly with remote named pipes, especially not from DOS Requestors. This software is tested with OS/2 Lan Server 1.2 CSD 4093, and worked on this configuration both from OS/2 requestors and DOS requesters. But when tested with CSD 4063 the program did not work with DOS Requesters, but was OK with OS/2 Requesters. This is a chart of how Os2You and LanTerm is configured to work together: ╔═════════════════════════╗ ╔═════════════════════════════════╗ ║ OS/2 Async. host ║ ║ DOS Remote (terminal) ║ ╟─────────────────────────╫───modems────╫─────────────────────────────────╢ ║ Os2You <- <comport> ... ║ │ ║ LanTerm <comport> <baudrate> ║ ╚═════════════════════════╝ │ ╚═════════════════════════════════╝ │ ╔═════════════════════════════════╗ │ ║ OS/2 Remote (terminal) ║ └──────╫─────────────────────────────────╢ ║ LanTerm2 <comport> <baudrate> ║ ╚═════════════════════════════════╝ ╔═════════════════════════╗ ╔═════════════════════════════════╗ ║ LAN Server (host) ║ ║ DOS Requester (terminal) ║ ╟─────────────────────────╫─────LAN─────╫─────────────────────────────────╢ ║ Os2You <- \Pipe\Os2You1 ║ │ ║ LanTerm \\Srvname\Pipe\Os2You1 ║ ╚═════════════════════════╝ │ ╚═════════════════════════════════╝ │ ╔═════════════════════════════════╗ │ ║ OS/2 Requester (terminal) ║ └──────╫─────────────────────────────────╢ ║ LanTerm2 \\Srvname\Pipe\Os2You1 ║ ╚═════════════════════════════════╝ ╔══════════════════════════════════╗ ║ OS/2 Requester (host) ║ ╟──────────────────────────────────╢ ║ Os2You <- \\Srvname\Pipe\Os2You1 ║ ╚══════════════╤═══════════════════╝ │ │ ╔══════════════╧═══════════════╗ ╔═════════════════════════════════╗ ║ LAN Server (bridge) ║ ║ DOS Requester (terminal) ║ ╟──────────────────────────────╫───LAN──╫─────────────────────────────────╢ ║ LanBridg ║ │ ║ LanTerm \\Srvname\Pipe\Lanterm1 ║ ║ \Pipe\Os2You1 \Pipe\LanTerm1 ║ │ ╚═════════════════════════════════╝ ╚══════════════════════════════╝ │ ╔═════════════════════════════════╗ │ ║ OS/2 Requester (terminal) ║ └───╫─────────────────────────────────╢ ║ LanTerm2 \\Srvname\Pipe\LanTerm1║ ╚═════════════════════════════════╝ Terminal emulation ================== The included files should be run in an OS/2 full screen text session, and will allow you to connect to it by modem or cable. In addition to this program, you will need a terminal emulation program, that is capable of emulating one of the included terminal emulation modes available with Os2You. It doesn't matter which operating system your terminal emulator is running. If you use OS/2 or DOS you may use the LanTerm2 (for OS/2) or LanTerm (for DOS) programs for both terminal emulation over a network using named pipes, or as an asynchronous terminal program. It will remap the keys to their corresponding Esc-sequences, and is also compatible with the Os2You binary mode (when running over a Pipe), which sometimes are faster than the terminal emulation mode, when used on fast connections. If you want to run LanTerm2 or LanTerm on a asynchronous connection, you should start LanTerm2 with the following syntax: LanTerm2 <COM-device> [baudrate] LanTerm <COM-device> [baudrate] The device name MUST begin with "COM" (like COM1). If no baudrate is specified the program uses the default baudrate. When used in this mode, the programs always sets the COM-device to 8 databits, 1 stop- bits and no parity. The LanTerm program for DOS, requires that ANSI.SYS is loaded in your CONFIG.SYS file. The DOS-mode program will only work with COM1 and COM2 serial ports. The programs are terminated by pressing Ctrl-Break. The following terminals are supported by Os2You currently (ANSI is default if none selected): Terminal Description file =============================== ================================= ANSI/VT100/VT102 ANSI.PRM (same as default) Hazeltine 1500 HAZEL.PRM (not tested) IBM 3101 IBM3101.PRM Tandberg TDV 2116 TANDBERG.PRM Televideo 910-955/ADM 5/Wyse 50 TELEVID.PRM VT52/Heath/Zenith/ADDS VP VT52.PRM If you want to select another terminal emulation than the default ANSI terminal, you should add "-t <term-file>" as a command line start option. Note that the description files only alter the screen output, and does not care about different keystroke combinations used by different terminals, except the ANSI escape keysequences. Also note that some terminals will work better if you run Os2You in a screen with only 24 lines (MODE CO80,24) instead of the more common 25 lines. If your terminal is not supported with a terminal description file, you may define your own terminal, by starting OS2YOU without any parameters, and select "Terminal definitions" in the configuration menu displayed. See section 'Defining your own terminal' below. The program automaticly detects how many columns and lines the OS/2 session contains, but you have to configure your terminal program for a screen size with at least the same amount of columns/lines (it doesn't matter if the terminal program uses more columns/lines than the OS/2 session). It is possible to alter the screen size with the MODE-command, while connected to Os2You, as long as the screen will fit on the remote screen. To "emulate" different keystrokes, Esc sequences are used. The following Esc sequences are valid (note that upper/lower case letters are significant): Ch. Result Ch. Result Ch. Result Ch. Result Ch. Result (?????) === ====== === ====== === ====== === ====== === ================== A Alt-A N Alt-N Esc Escape 1 F1 ! Shift/Ctrl/Alt-F1 B Alt-B O Alt-O t BackTab 2 F2 @ Shift/Ctrl/Alt-F2 C Alt-C P Alt-P 3 F3 # Shift/Ctrl/Alt-F3 D Alt-D Q Alt-Q w Arr up 4 F4 $ Shift/Ctrl/Alt-F4 E Alt-E R Alt-R < Arr left 5 F5 % Shift/Ctrl/Alt-F5 F Alt-F S Alt-S > Arr right 6 F6 ^ Shift/Ctrl/Alt-F6 G Alt-G T Alt-T z Arr down 7 F7 & Shift/Ctrl/Alt-F7 H Alt-H U Alt-U 8 F8 * Shift/Ctrl/Alt-F8 I Alt-I V Alt-V c Ctrl-Break 9 F9 ( Shift/Ctrl/Alt-F9 J Alt-J W Alt-W 0 F10 ) Shift/Ctrl/Alt-F10 K Alt-K X Alt-X - F11 _ Shift/Ctrl/Alt-F11 L Alt-L Y Alt-Y = F12 + Shift/Ctrl/Alt-F12 M Alt-M Z Alt-Z s Set F-key to Shift i Insert h Home u PageUp l Set F-key to Ctrl d Delete e End n PageDown a Set F-key to Alt ============================================================================= Tab Task list b Toggle binary mode Break Force Os2You to exit p Toggle physical screen Space Force Os2You to update screen ? Status information The above screen is showed if you press Esc without any character following within approx. one second. You may select any keystroke from the menu, and the menu exits, ans Os2You sends the selected keystroke to your application. If Esc is pressed and directly followed by another character, the selected keystroke is sent directly to your application, without showing the help screen. ANSI escape sequences for cursor movements are mapped to their corresponding arrow key. All characters, except Esc, are translated directly to the corresponding keystroke. ASCII 01H is translated to Ctrl-A, ASCII 02H to Ctrl-B and so on. To emulate Shift, Ctrl and Alt function keys, you have to first select which mode you want by pressing Esc-s, Esc-l resp. Esc-a first followed by the appropriate function key Esc-code. In the upper right corner of the help menu the current state of the function keys is written. The above table means that you should press Esc FIRST and THEN a character. "Esc-i" means that you should press "Esc" first and then followed by "i". Note that you have to press "Esc" twice, if you want to emulate a "Esc" keystroke. Task list ========= By pressing Esc-tab (first <Esc> and then <Tab> 1bH, 09H) you will get a list of programs currently running. It might look like this: Os2You Task List ================ A Switch to B OS/2 window C OS/2 window D Group - Applications E Group - Bookshelf F Group - Utilities G Group - Toolkit Editors H Group - Compilers I Group - Communication J M2ZMODEM.EXE K Os2You.EXE L TS.EXE M Group - Main N PM Diary O Desktop Manager > Next entries Z Return to original session The task list displayes all running programs. If the list is too long for the screen, you may scroll up and down with the '<' and '>' keys. You enter the character displayed before the program you want to switch to. If you want to return to the original session (the one you started from) you should select 'Z'. You can only switch to programs running in an OS/2 full screen text session. If you try to switch to another session, you will get an error message. If you run another session than your original one, some limitations will exist. The screen size is assumed to 80 columns and 25 rows, and is not adjusted to the real size of the running session The cursor position will not be updated while running another session than your original session. On some VERY unusual conditions the program won't be able to figure out if the program is running in monochrome or color mode. Note that the session you select is switched to the foreground at the host machine, and will interrupt any user running another session at the machine from the keyboard. It will also interrupt any other user running the same host through Os2You running other session than their original session. The session you selected should NOT be switched to the background, while you are connected to it, as you will lose all output from the connected session, while running in the background. The task switcher requires OS/2 1.2 or compatible to work. File transfer ============= If you have M2Zmodem version 2.09 or later (another program from the same source), you may use it to up/download between the host and remote. This solution also allows auto Zmodem uploads. I suggest that you copy the M2Zmodem.EXE and M2Zmodem.MSG-files into the same directory you used for Os2You. Then you should include this directory in your PATH and DPATH. It is now possible to receive files from host to remote (download) by just typing "Sz <files>" at the command prompt (any wildcards allowed). If you run LanTerm/2 or LanTerm as terminal program at the remote (or any other terminal program with Zmodem autodownload), the file transfer will be automaticly started at the terminal side too, if not, you have to request download in your terminal program. If you use LanTerm (for DOS), you should get DSZ file transfer program (shareware from Omen Technology). If you use LanTerm/2 (for OS/2), you should get M2Zmodem file transfer program (shareware from the same place you got Os2You). Both programs should be installed in the same directory as LanTerm(/2), or in a directory specified in your path. To send files from remote to host (upload) just type "Rz" at the command prompt. When you request upload in your terminal program, you should enter which files to send. If you have called your receive batch file "Rz.Cmd" you don't even have to start the batch file before starting your send procedure, because the Rz command is executed automaticly by the Zmodem initializing procedure, if you are at the command line when you start the send procedure (auto Zmodem download). The described configuration uses the fast and reliable Zmodem protocol for file transfers. If you want to use another, like Xmodem, Xmodem-1K, Ymodem or Ymodem-G, you could just alter the CMD-files to change your protocol. The parameters for M2Zmodem are described further in the M2Zmodem.DOC file, or written to screen, if you just enter M2ZModem at the command prompt. If you don't know how to get M2Zmodem, you could send a formatted diskette and four International Post reply coupons (Coupon-Réponse International, Union Postale Universelle) to my address mentioned last in this documentation. DOS-compatibility box ===================== When you run the OS/2 session remote, you may enter the command "Dos2You" at the command line, and you will get access to the DOS-box (if available). Note that any user running at the physical screen will be interruptet when the DOS-box is entered. The cursor position won't be set correctly when running the DOS session. Dos2You requires OS/2 version 1.2 or later, and the DOS.SYS driver must be loaded. Note that your AUTOEXEC.BAT file should NOT contain any statements that would require any keyboard input, as the Dos2You program gets control of the DOS-box AFTER the AUTOEXEC.BAT file is executed, which means that any user input in the AUTOEXEC.BAT is taken from the "real" keyboard. To enable Dos2You, you should copy the DOSREDIR.EXE file to a directory in your DOS-path, or load the DOSREDIR-program in your AUTOEXEC.BAT file. The DOSREDIR-program is a resident program that will communicate with the Os2You-program, allowing Os2You to control the DOS session. The DOSREDIR program requires that a printer port is installed in the system, and will demand IOPL (put the line "IOPL=YES" in your CONFIG.SYS file). The DOSREDIR program MAY conflict with the printer stream, but should not cause any other serious conflicts in your system. The keyboard won't accept extended keycodes (like function keys). When returning from the DOS-box you have to press Esc-P to reset Os2You to not use the physical screen area. No extended keys like function keys will work in the DOS-box. Defining your own terminal ========================== If your terminal is not supported by a terminal definition file, you may create your own by starting OS2YOU without any parameters and select "Terminal definitions" in the configuration menu displayed. The program will ask for a file name for the terminal definition file. Enter the the terminal definition file you want to create or alter. The program will show a menu with different terminal setting. When not otherwise stated you should enter the hexadecimal values separated by spaces (max 20 values) corresponding to the ASCII-code for the characters to be sent. Note that ALL values should be give in HEX-form (spaces will be replaced by under- score characters). The program asks for the following: 1. Initializing string. String to initialize the terminal to selected mode. In most cases should this string be left blank. 2. Cursor position; command. String to begin a cursor position command. 3. Cursor position; separator. String to separate row and column parameters in cursor position command. 4. Cursor position; end. String to end cursor position command. 5. Cursor position; column first. Select 'Yes' if the column should be sent as the first parameter, otherwise enter 'No', and the row will be sent first. 6. Cursor position; column offset. Value with which the column is added with, before the cursor position command is sent. The left most column is treated as column 0. 7. Cursor position; row offset. Value with which the row is added with, before the cursor position command is sent. The top row is treated as row 0. 8. Cursor position; binary address. Select 'Yes' if the row and column parameters should be sent as binary values, using one byte each. 9. Cursor position; maximum parameter length. Enter the length the row and column parameters may be assigned at most. This value should be set to 1 if binary address is selected. 10.Cursor position; zero pad Col and Row parameters. Select 'Yes' if the row and column parameters should be padded with leading zeros up to the length indicated by the above parameter. 11.Scroll screen up; init string. String sent to initiate a scroll operation. 12.Scroll screen up; each row. String sent following the init string to scroll the screen up one row each time. It doesn't matter if the cursor is moved during this command, as the cursor position will be restored automaticly by the program. If no special scroll command is available with your terminal, you should enter a string that places the cursor at the bottom row, and advance one row. 13.Clear to end of line. String sent to clear the remaining (or all) of the line the cursor is positioned at. The line should ONLY be cleared, NOT deleted. Currently it doesn't matter if the whole line is cleared, or only the end of it. 14.Clear screen. String sent to clear the entire screen, and position the cursor at the home (upper left) position. 15.Use ANSI colors. Set to YES if you want Os2You to send color attributes with ANSI escape sequences. If set to NO, no color information will be transfered. 16.Strip control characters. Set to YES if you want Os2You to replace all visible control characters (between 0 and 31) on the host screen with space characters instead. This is usable if you use a terminal that won't display control characters, but treat them as control information. 17.Strip high order characters. Set to YES if you want Os2You to replace all high order characters (between 127 and 255) on the host screen with space characters instead. This is usable if you use a terminal that does not support the PC character set, or if you use 7 databit connections. Some terminals require a short "breath" after some commands like clearing the screen and positioning the cursor. This may be accomplished by entering trailing zeros after the command strings. Os2You will send these null characters, but your terminal will in most cases ignore these characters and get their pause. Command line options ==================== If you want to start the program from the OS/2 Command prompt without the phone answering capabilities, or want to call the program from your own application, the program is started with some parameters. The program may use a "hot" file handle (already opened). It is the callers responsibility to set the communication port as wanted, and Os2You will use the current settings when called. When the program exits, it restores the communication port to it's previous state. If a program was successfully spawned the program will exit with Exit-code set to zero. If the program failed by any reason, the Exit-code will be set to a non zero value. The parameters may be entered at the command line or/and set in the environment variable "OS2YOU". If both the environment variable and a command line is entered, the environment variable will be parsed first and the command line after that, making command line parameters override any settings in the environment variable. The environment variable is set by the "SET OS2YOU=xxx xxxx xxxx xxx" command. The following parameters are available (note that they should be lower case). -c <fname> Use the configuration file <fname>. This option is only valid if you use the HOST-mode or callback processing. Default is "OS2YOU.CFG". -d Do NOT detect carrier loss. Normally the program monitors the carrier and close the remote session if carrier is lost. By adding this parameter you override this beaviour. -e <fname> Execute program <fname> for the remote session (typically CMD.EXE). This parameter is the last one read by Os2You. All following parameters are sent to the called program. Default is "CMD.EXE". -f <decint> Delay between screenupdates with <decint> milliseconds. Default is 100 mSecs (0.1 seconds). -i <decint> Exit if keyboard inactive in <decint> seconds. If set to zero no inactivity timeout is used. Note that only the keyboard activity is monitored, and that the inactivity counter is active even if the screen alters. Default is zero (no inactivity counter). -l <dname> Use device <dname> for communication. If <dname> is replaced by a percent sign and a decimal value (for example "%5"), the program will use the device handle (5 in the example) for communication. The program may also use pipes handles for communication. This parameter has no default value, and if the parameter is omitted, the program will start up in HOST mode. -n <uname> Use parameters for user <uname> in the configuration file, including callback processing to <uname>. This parameter is only valid if you do NOT start the program in HOST mode. If you want to include spaces in the <uname> you should replace the space by an underscore "_", or surround the parameter with double quotes. Default is to not use any entries in the configuration file. -p Use physical screen area for remote. If this parameter is specified the program will use the physical screen area for remote, and NOT the screen area owned by the session. If this parameter is specified you can't use the "-s" parameter. Default is to use the session screen area. -prty <decint> Screen update priority <decint> 0-39. This parameter sets the priority for the remote screen update thread. Zero is the lowest priority and 39 the highest. Priority 0-9 executes with IDLE priority, 10-19 has REGULAR priority, 20-29 HIGH priority and 30-39 TIME CRITICAL priority. If priority is set to 14 the screen update thread has the exact same priority as the executed program. Default is 14 giving the update thread exactly the same priority as the executing program. Setting the priority to a higher value (15) may result in smother operation. -s Disable the built in task switcher and physical screen. If you don't want the remote user to be able to switch between running tasks, you should disable this feature. If this parameter is specified you can't use the "-p" parameter. Default is to enable the task switcher. -t <fname> Use terminal definition file <fname>. The file extension ".PRM" is added if no extension is included. This parameter has no default value, instead the program has a built in table for ANSI terminal emulation. Examples: Os2You -l COM1 -f 1000 -i 300 -e CMD.EXE /K DIR This command will tell Os2You to use COM1 and update the screen each 1000 millisecond. If no remote keystroke is received within 300 seconds the program will be forced to exit. CMD.EXE is loaded for remote operation with the parameters "/K DIR" (which will tell CMD.EXE to display a directory list). Os2You -l %4 -f 100 -i 0 -d -e CMD.EXE This command will tell Os2You to use device handle 4 (decimal value) and update the screen each 100 millisecond. If carrier i lost the program will be terminated. but no inactivity timer is set. Os2You -l %4 -f 100 -i 0 -d -n Mikael_Wahlgren This command is similar to the previous example, except that the program will spawn the program and use the parameters indicated by the username "Mikael Wahlgren" in the configuration file. By using the "-n" option it is possible to spawn different session depending on username. To be compatible with MaxPipe (TM of Peter Fitzsimmons) an alternate calling syntax is automaticly invoked, if the first parameter does not begin with a minus sign "-". In this case, the syntax will be like: Os2You <device> <programname> <parm1> ... <parmN> <device> Tells which communication device to use. It is possible to pass a "hot" device handle by replace the device name with a number corresponding to a the device handle decimal coded (like %4). The device name may be replaced by a pipe name, but special care should be taken, when using this possibility. The best choice when using pipes is to use the stand alone interface. <programname> Tells which program to load for remote operation. (Typically CMD.EXE). <parm1> ... <parmN> The remaining parameters are optional and are passed as parameters to <programname>. All other values are set to their default when using this syntax. To select which communication parameters to use, you should use the MODE- program, included with the operating system. See more in the documentation for the operating system to see how to configure your communication line. All communication parameters set with MODE, will be used with Os2You. Example: MODE COM1:2400,N,8,1,OCTS=ON,DTR=ON,RTS=HS,BUFFER=ON This command will tell Os2You to use baud rate 2400, no parity, 8 data bits, 1 stop bit, hardware handshaking CTS/RTS and use the extended hardware buffering capabilities. Multi user configuration ======================== By using Os2You you may actually use OS/2 in a multi user like manner. Note that Os2You lacks any sort of security control for file managing, which a "normal" multi user operating system includes. Commonly asked questions and problems ===================================== Q1. What terminal program should I use to communicate with Os2You and which terminal emulation mode? A1. Use ANSI-BBS for your terminal program if it is available and the built in or ANSI.PRM terminal mode in Os2You. If you run OS/2 on the remote, you may use the LanTerm2 program, by configuring it with Os2You configuration menu, and start LanTerm2 without any parameters. Or you could start LanTerm2 with the COM- port and baudrate as parameters, like "LanTerm2 COM1 2400". This program in combination with the built in emulation in Os2You, is the most comfortable configuration, as the keyboard will work as you are used to. Q2. When started in HOST-mode and modem, Os2You loops around, asking for <Enter> and eventually logon parameters, even if no user are calling. A2. Os2You relies entirely on the DCD (Data Carrier Detect) signal on the RS232-interface to reflect the real carrier state. DCD is a that tells the computer that the modem is connected to another modem. You have to verify that the signal on the RS232 interface is connected to the signal at the modems interface, and that the modem is configured to reflect the real carrier state. Q3. When logging on to Os2You HOST mode, I first get a lot of garbage characters, before I get the "Press Enter" message. A3. This is normal, if you have configured Os2You for multiple baud rates. Os2You tries to find the correct baud rate for you. Q4. When the loggin on to Os2You HOST mode, the modems RD (Receive Data) signal is blinking all the time, even when nothing appears on the screen. A4. This is normal. Os2You continously sends characters to the remote when logging on, of technical reasons. Q5. The screen doesn't scroll correctly. A5. Scrolling has proved to be the hardest part to implement. This has to do with the fact that the Os2You program has no way to find out how many lines your terminal program on the remote has. The built in ANSI driver in Os2You positions the cursor at line 999 and sends a LF. This works with the standard OS/2 ANSI driver, and some terminal programs, as a line number greater than the maximum line, will result in a position at the last line. Other terminal programs just ignores cursor positions that is outside the screen size. This is why there is a separate ANSI terminal definition file available. By using this file Os2You will position the cursor at line 25 and send a LF, which works if your screen size is just 25 lines. If neither the built in ANSI terminal nor the delivered ANSI definition file works, you should modify ANSI.PRM (or the terminal definition file that is appropriate for your terminal), and alter the scroll sequence. Q6. Background colors are not displayed correctly at the remote screen, using ANSI colors. A6. When Os2You sends a ClrEol (Clear to end of line) sequence, it assumes that the line is cleared with the attribute currently in use. This is how it works in the ANSI driver for OS/2. Some terminal emulators though, fill the cleared line with the standard attribute in opposite to the currently used attribute. Q7. When running some programs, I don't get any output from it. A7. Os2You is not compatible with programs running in Presentation Manager. Some programs running in OS/2 full screen text sessions require the physical screen buffer. Those programs won't be 100% compatible with Os2You, but you might to be able to run the program if you use the task switcher and switch to the offending program, as programs selected by the task switcher will run in the foreground and have the physical screen adressable. Q8. When running some programs, I get output from the program, but the keyboard doesn't seem to work. A8. The programs keyboard handling is not compatible with Os2You. Please report the problem to me, and if possible, send a copy of the offending program. RELEASE NOTES ============= Only bugs and improvements not described elsewhere are documented in this section. 1.0: First release. 1.1: The program could terminate with a GP error when run on a PS/2 system. The port-parameters was not correctly restored. This is now corrected. 1.2: Improvements 1.3: Improvements 1.4: Improvements 1.5: Bug, that made the program incompatible with some programs (especially programs polling the keyboard) is fixed. 1.6 Improvements 1.7 Some scancodes adjusted to make the CTRL-key, Enter-key and some other special keys more compatible with some programs. The command line syntax is altered. Note that it is NOT compatible with previous syntax. This had to be done, as the previous syntax was unclear, and not flexible enough. LAN/Pipe operation fixed. 1.8 LAN/Pipe operation fixed again. Previous LanTerm2 didn't work due to a serious compiler bug. The configuration file is opened in "Deny Write" mode for security reasons. This makes it impossible to modify the configuration file during an session. 1.9 The "Allow Task Switch" option in the login table is now used to disable the task switch and the Break-functions. If the "-s" option is used or "Allow Task Switch" option is set to NO in the user profile, the user won't be able to use the Esc-c, Esc-Break sequences (to end the session abnormally). Now Break scancodes are also sent. Lanterm.EXE (LAN-operation for DOS workstations) are now included again. I hope it works OK, but I haven't been able to test this, as I don't have access to any network with DOS workstations able to run named pipes. Better shutdown operation, when a program gets stuck, or user lost carrier. REXX-sessions are shutdown correctly. Terminal configurable in user table. The configuration file is optionally (configurable) opened in "Deny Read/Write" mode, to prevent an user to look at the configuration file. If the program is not configured to lock the file, it will be possible to read, write and change the configuration file. 1.91 Fix to get the program work with LAN Server 1.2 CSD 4093 and DOS Requesters. Also tested successfully using Novell server and remote named pipes. LanBridge added, to run OS/2 LAN Requesters remote over LAN. If program can't be killed, when exiting the session, Os2You will go back to login screen. Next user will probably get confused, because the previous program is still alive. "-s" (disable task list) is default when using MaxPipe parameter syntax. LanTerm and LanTerm2 programs are altered, to change the behaviour of the Esc-key. If the Esc-key in LanTerm(/2) is pressed the program will send double Esc-codes making Os2You send one Esc-sequence to the application. If you press Shift-Esc in the LanTerm(/2) program will send just one Esc-code, making Os2You to wait for an Esc-sequence (or displaying the help screen). 2.0 Color attributes are now transfered to the remote screen, by using ANSI color escape sequences. It is default to use ANSI colors when no terminal definition file or an old definition is loaded. To upgrade your old terminal definition files, select terminal definition from the Os2You menu, and modify the ANSI color entry. Your other definitions will be intact. The screen update handling is altogether rewritten. In some respects it is faster, but in some situations it might also be slower than before. The terminal does not need to wrap at end of lines anymore. The program now supports different screen widthes and heights. The program assumes that you are running the application in color mode (two bytes per character cell). If this is not the case, the program will transfer false attributes (converting underline/highlights to colors). The "-n" option now allows Os2You to directly spawn different sessions depending on the username. The callback, shell, terminal and switch parameters are used from the login table. The COM-buffers are flushed by reading all available characters, in addition to a DosDevIOCtl call, as the DosDevIOCtl call didn't seem to work in some networking environments. The option to strip control characters (0-31) and high order characters (127-255) are added in the terminal definition file. The default, if no terminal definition file or an old definition is used, is to strip control characters but leave high order characters. LanTerm/2 (for OS/2) and LanTerm (for DOS) are modified to accept COM-ports from the command line. Both program can be started with the syntax "LanTerm <COM-port> <baudrate>". The COM-port must have a name beginning with "COM", and for the DOS-version only COM1 and COM2 are valid. LanTerm (for DOS) requires that ANSI.SYS is loaded in your CONFIG.SYS file. Both programs take advantage of the FIFO buffered 16550 UART if available. LanTerm/2 and LanTerm now have Zmodem AUTO download/upload capability. To transfer files between host and remote, just issue a file transfer command on the host (use the Rz or Sz command files and M2Zmodem), and the file transfer program will start on both host and remote. If you upload from remote to host, you will asked for a filename/pattern. LanTerm/2 uses M2Zmodem, and LanTerm uses DSZ as file transfer programs, and these programs much be available in the current directory or in a path. Planned enhancements ==================== The following is a list a enhancements planned in a future release. It isn't sure that the next release of the program will include these enhancements though. Any adjustments necessary for Os2You to work with OS/2 2.0 will be made, when OS/2 has been released. 1. A special terminal program with enhanced terminal features for DOS and OS/2. This will fasten operation, and ease operation, as it you wouldn't have to remember Esc-sequences to emulate different keys. Only to registered users. 2. The DOS-box will be improved when OS/2 2.0 is out. No further effort to improve the DOS-box before that will be made, as the method probably will have to be changed anyhow. Copyright notes =============== OS/2 is a trademark of IBM Corporation. PS/2 is a registered trademark of IBM Corporation. IBM is a registered trademark of International Business Machines Corporation. DSZ is a trademark of Omen Technology Incorporated. 386/SX might be a trademark of Intel Corporation. Novell is a trademark of Novell Inc. Important license information ============================= It is illegal (or at least unethical) to patch the program in any way. Any reverse engineering (disassembling or monitoring) is not an approved use of the application. If you register the software with at least 300 SEK (about $50), you will get a license file and a copy of the most recent version of the program. In this case, you will also get rid of the registration screen during logon. In the future this registration file may enable features in the program not available in unregistered configurations, but currently all functionality is available in unregistered copies. Note, that the registration file you get is valid for any future release of this program, and that you will be treated as registered to any future release. If you use the program on a regular basis, or in commercial use, you must register with minimum the above mentioned sum for each machine running the Os2You program. The LanTerm, LanTerm2 and LanBridg programs don't need any further registration, and may be used in unlimited instances, but an extra registration per each 20th instance of LanTerm or LanTerm2 is appriciated. For use in the Scandinavian countries (Sweden, Norway and Denmark), I have the right to refuse registration of a user and prohibit commercial use of the program, if I wish. This will be the case, if the use of the program conflicts with commercial interests related to me. The sourcecode (in Modula-2 and C) of the program is available, on special terms. Please contact me if this is of interest. You are encouraged to spread this program (without registration file) to anyone that might be interested. If you want to register, send swedish banknotes, bank cheque or let bank transfer money to my account by SWIFT (note that you should send all money in swedish currency). ╔═══════════════════════════════╦═══════════════════════════════════════╗ ║ My bank account is: ║ My address is: ║ ╠═══════════════════════════════╬═══════════════════════════════════════╣ ║ Account no: 414 46 44-4 ║ Mikael Wahlgren ║ ║ PostGirot Sweden Inter. ║ Kransen 4E ║ ║ S-105 06 STOCKHOLM ║ S-416 72 GOTHENBURG ║ ║ Sweden ║ Sweden ║ ║ ║ ║ ║ SWIFT: PGSI SE SS ║ Fidonet: Mikael Wahlgren 2:203/302.5 ║ ║ Telex: 10185 pgint S ║ Internet: d9mikael@dtek.chalmers.se ║ ╚═══════════════════════════════╩═══════════════════════════════════════╝