home *** CD-ROM | disk | FTP | other *** search
- I am pleased to announce the availability of this beta version of UW/WIN.
-
- The main improvement of this version (1.04) over 1.03 is both vt100 terminal
- emulation and file downloads. X/Y/Zmodem protocols are supported. Uploads are
- not ready yet, but I feel that significant enhancements exist over 1.03 to
- be able to release it while uploads are being developed. Also included is a new
- feature to log all screen output to a file. You can have any or all UW windows
- logging at the same time.
-
- This small document outlines the enhancements, pending updates to the
- actual documentation.
-
- 1.) vt100 emulation is enabled using the "Emulation" menu item to bring up
- the dialog box. vt52, adm31, and vt100 are selectable. The documentation
- has a list of capabilities actually supported.
-
- 2.) Session logging is enabled through the "File" menu. If not currently
- enabled (it is enabled if a check mark appears next to it in the menu),
- then a dialog box is brought up for you to select the file to log to.
- The default extension is .ulg. The actual logging is accomplished in
- conjunction with a separate module, included in this package, uwlog.exe.
- UW/WIN spawns this program, and opens a dialog with it for passing
- data between them. uwlog.exe does the actual file I/O for UW/WIN. This
- file must reside in your path, preferrably in the same directory as the
- other UW/WIN files.
-
- Once a file is selected, all output to that windows is also recorded in
- the file. To turn off logging, and close the file, select "Log" from the
- menu again.
-
- 3.) File download support is also accomplished via a separate module, rz.exe.
- This file can handle X, Y, and Zmodem protocols. As with uwlog.exe, it needs
- to reside in your path.
-
- To utilize transfers from UW/WIN, you would first start the appropriate
- send utility from your UNIX system. A good choice is the rzsz package,
- available freely from many UNIX archive sites. For X and Y modem, after
- issuing the proper UNIX command to send the file, you will select
- "UW | Download | [XY]modem". For Zmodem, the init string is recognized
- automatically and the process is started for you. There is a Zmodem
- item on the "UW | Download" menu anyway.
-
- For Y and Zmodem, you get a dialog box which will serve as the basis for
- displaying the transfer progress. Initially, the filename field is filled
- in with the data sent by the sender. Since UNIX filenames may have more
- characters and different formats as DOS filenames, they are shortened/
- simplified by a basic algorithm that strips out characters outside of
- A-Z, 0-9, _, and truncates characters from the name portion to 8
- characters, and 3 for the extension. For example, ".cshrc" would become
- cshrc, "f.cshrc" would become "f.csh", etc.
-
- The size of the file is also displayed. You may use the directory
- navigation box to change the directory it is going in to. At this point,
- to start the transfer, press the "Start" button. You may cancel while
- downloading using the cancel button. Some sz programs don't look for
- the cancel string too often, so be patient while it waits for an
- acknowledge to the cancel. When you get the "Start" button back (it
- will change to "OK!", or "ERROR!", or "Skipped!" depending on the
- outcome), pressing it, or cancel, will close the dialog. There is
- also a check box, "Multiple Query". This turns on or off the wait
- between files if more than one file is sent. This is not currently
- functional.
-
- For Xmodem, the dialog box is a little different. The sender does
- not send the filename, or its size, so you must use the file navigation
- to select a file to download into. Because the total size is unknown,
- there also is no status for %complete.
-
- You may download from the main protocol 0 window, or any window using the
- UW protocol 1. Note that because of limitations in the UW server, response
- typically isn't great for other windows while a download is in progress.
-
- I, and others, have noticed a problem under Windows 3.1 where the
- comm will lose characters if the mouse is moved while receiving
- characters over the comm port. We believe this to be a windows
- problem because other comm packages exhibit the same behavior.
- This can cause excessive errors during downloads. This seems to
- be isolated to certain video drivers. Be sure to get the latest video
- drivers for your card.
-
- If you find problems, please report them to me. If at all possible, try
- and include as much info as possible about your environment.
-