19. CHANGES Be sure to save your serial number/password (SNP) card and the putsnp program you received from Omen Technology to use with future versions of DSZ you may download! (Use GCOLORS to serialize GSZ.) Current GSZ and DSZ versions are maintained on EXEC-PC BBS, BIX, GEnie (IBM Roundtable), CompuServe (IBMCOM and CONSULT SIGs) as well as TeleGodzilla. DSZ is a popular program which has been the object of virus attacks. Pirated/hacked versions of DSZ have cost users and DSZ's developer thousands of dollars in lost time and other expenses, in addition to injuring of Omen Technology's reputation. Virus and Trojan code hidden in hacked/pirated copies of DSZ and programs claiming to "register DSZ" have caused loss of data. -rw-r--r-- 1 caf omen 52586 May 03 15:22 dsz.com -rwxr-xr-x 1 caf omen 60251 May 03 15:25 dsz.exe PKZIP -vt 32 bit CRC: 0B00125F 52586 dsz.com PKZIP -vt 32 bit CRC: BF552B2D 60251 dsz.exe -rw-r--r-- 1 caf omen 32864 Apr 26 08:44 gcolors.exe -rw-r--r-- 1 caf omen 70352 Apr 27 15:00 gsz.exe PKZIP -vt 32 bit CRC: C0990846 70352 gsz.exe PKZIP -vt 32 bit CRC: E83AEFB2 32864 gcolors.exe Your copy of DSZ should show the same CRC values. ZIP uses a 32 bit CRC compatible with the Professional-YAM and ZCOMM "crc" command. pkzip -vt dsz The following Pro-YAM/ZCOMM command gives the 32 bit CRC for DSZ.COM: EXAMPLE: >>>c: crc dsz.com If your copy shows a different CRC or file length, insist on a legitimate copy and report the source of the bogus/pirated copy to Omen Technology Inc. Omen Technology has received reports of serious problems caused by unauthorized patches to DSZ, and cannot assume liability for the performance of the resultant code. COM7 and COM8 are changed; see the "port" command above. A problem in the 1/17/89 and 2/2/89 DSZ versions corrupts files under unusual circumstances. Please delete all instances of the 1/17/89 and 2-02-89 version. There never was a "zmodem d" parameter in DSZ. Older versions of DSZ ignored attempts to set this nonexistient parameter with a message that Chapter 19 Pg 58 DSZ Reference Rev May-3-92 Typeset 5-3-92 humans ignored. DSZ now aborts when asked to set a nonexistient parameter. There is a "d" parameter that controls time/date stamping of files; Bulletin boards that need to disable time/date stamping of received files should simply use "pd0" not preceded by a "z". Good news for tired frog stompers! The ZMODEM rz/sz programs are available in native VMS flavors with wild cards, record format support, etc.. Pre compiled VAX/VMS files are contained in the RZSZ.TLB compressed text library, available in the TeleGodzilla upgrade/vms subdirectory, Compuserve VAXFORUM, GEnie, and other bulletin boards. The DSZ and GSZ "t" command uses the DOS console driver for terminal emulation. Standard ANSI.SYS is limited to a small subset of ANSI escape sequences; NANSI.SYS, FANSI-Console and other replacement console drivers provide faster screen updates and better ANSI terminal emulation. DESQview users: make sure "Separate Shift State" is set to "N". (Tnx to Tim Trott for this info.) May 3 1992: Recompiled to correct bad file size/CRC values in DSZ.DOC and DSZNEW, pruned some unused code. No functional changes from April 27 vsn. April 27 1992: The GSZWINDOW environment variable can be set to 1, 2 or 3 to leave the top 1, 2 or 3 lines unmolested. DSZ.EXE is compiled on a newer compiler and now supports file sharing. Bogus/hacked/infected files with early 1992 revision dates have been reported. Dec 13 1991: DSZ and GSZ automatically support Doorway 2.2 without extra commands. The RZ.BAT and SZ.BAT files are supplied for convenience. RZ.BAT allows calling programs that emit an "rz" command to automatically start DSZ from the DOS command prompt. SZ.BAT is a convenient command interface that complements RZ.BAT. You may modify SZ.BAT and RZ.BAT with your favorite options. The GSZ file transfer display now shows a distinct color at the locations where error retries occurred. This gives a visual impression of the distribution of error retries. Oct 15 1991: To accomodate other vendors' programs which do not provide a convenient way to control crash recovery, the "restrict" command security check is not performed if the destination file does not exist.