08/11/95 History for D70x14 =================== All the utilities and files listed below have been modified during the last year. This update brings all those changes together and the fixes which have been implemented earlier as patches are now included as source fixes. Checksums ========= 7,657 7-31-95 7:00A 1305 ASSIGN.COM 60,273 7-31-95 7:00A E732 CHKDSK.EXE 59,029 7-31-95 7:00A EAFE COMMAND.COM 39,845 7-31-95 7:00A A669 DEBUG.EXE 27,646 7-31-95 7:00A 4496 DELPURGE.EXE 16,476 7-31-95 7:00A D965 DISKCOMP.COM 16,649 7-31-95 7:00A A077 DISKCOPY.COM 36,373 7-31-95 7:00A D413 DPMS.EXE 107,728 7-31-95 7:00A 8580 EDIT.COM 183,809 7-31-95 7:00A 8A75 EMM386.EXE 9,974 7-31-95 7:00A 4322 EXE2BIN.EXE 19,618 7-31-95 7:00A CEEA FDISK.COM 104,265 7-31-95 7:00A 3C60 FILELINK.EXE 22,929 7-31-95 7:00A 099B FORMAT.COM 14,976 7-31-95 7:00A C6A6 HIMEM.SYS 33,390 8-11-95 9:01A E6EB HISTORY.TXT 25,783 7-31-95 7:00A AD8C IBMBIO.COM 30,884 7-31-95 7:00A 681D IBMDOS.COM 40,647 7-31-95 7:00A 0F1B KEYB.COM 31,936 7-31-95 7:00A F878 LOCK.EXE 16,727 7-31-95 7:00A 6CE5 MEM.EXE 2,561 7-31-95 7:00A 3DD4 MEMMAX.COM 2,825 7-31-95 7:00A AD82 NLSFUNC.EXE 35,705 7-31-95 7:00A 6B6B NWCACHE.EXE 34,308 7-31-95 7:00A 7991 NWCACHE.OV1 30,206 7-31-95 7:00A 56C6 NWCACHE.OV2 21,860 1-23-95 7:00A 1FEB NWCDEX.EXE 22,876 1-23-95 7:00A 8DEE PRINT.COM 1,982 4-01-94 8:55A 8C8D SETFIFO.EXE 4,881 7-31-95 7:00A B9B5 SHARE.EXE 7,881 7-31-95 7:00A A71E SUBST.EXE 45,696 7-31-95 7:00A 8175 TASKMGR.EXE 12,604 1-23-95 7:00A D819 TREE.COM 104,754 7-31-95 7:00A 519C UNDELETE.EXE 13,640 1-23-95 7:00A 1836 XDEL.EXE 22,622 1-23-95 7:00A E5B4 XDIR.EXE SYMPTOM (02/22/95) ASSIGN.COM (1.05) Both utilities no longer display invalid (beyond LASTDRIVE) drives as assigned/substituted. SOLUTION Overwrite the ASSIGN.COM file in the NWDOS directory with the new ASSIGN.COM. SYMPTOM CHKDSK is not compatible with Stacker 4.0 drives. (05/08/95) CHKDSK.EXE (1.21) /B option should now disable all prompts. If /WP was specified the system would crash in some situations after CHKDSK terminated and the next app was started. An invalid pointer was used when Stacker was not found which could occasionally hang the machine. SOLUTION Overwrite the CHKDSK.EXE file in the NWDOS directory with the new CHKDSK.EXE file. This version of CHKDSK.EXE includes a /NS command line parameter to instruct CHKDSK to not do internal Stacker checking on a Stacker 4.0 drive. SYMPTOM (09/13/94) COMMAND.COM Using copy on the POWERLAN 3.1 network now works correctly. Has TRUNAME support which refers to command/path handling. 01/23/95) COMMAND.COM Has TRUENAME help support which refers to command/path handling Removed closing handles 5 and 6 during abort from critical error or INT23 Enabled semicolon(;) to start a comment in a batch job SET now removes leading blanks, commas, semicolons and equal signs, but keeps blanks in the variable name (not only in the value). Changed critical error message dispatcher Enabled UNC filenames for file processing command. This requires VLMs dated after Oct 07 1994. There are some limitations when using this on PNW: a) PNW does not support a primary server (thus if the current drive is not a PNW drive you can't access some default server without specifying the server's name). b) PNW does not support accessing a volume on a server where no drive/port is mapped/captured to. c) Accessing \\SERVER\VOLUME with an invalid VOLUME succeeds partially Made renaming possible for all kinds of directory specifications for the destination (eg. \, dir\, dir, ..) - worked previously only for DIR Disabled interpretation of single ! in if condition (02/17/95) COMMAND.COM OR within an IF statement was not working. Command extensions through INT 2F AX=AE01 could return a zero size command which was still processed. (05/08/95) COMMAND.COM LOGIN_NAME, P_STATION, and STATION pseudo-environment variables work now without NETX being installed. FULL_NAME however has not been converted due to the large amount of changes that would be required here. This makes LOGIN_NAME now working on PNW given that the current drive is a PNW mapped drive. In low memory situations a temporary buffer was not freed preventing commands from succeeding which require memory (mainly COPY). This addresses a problem with CoorsLink. (07/31/95) COMMAND.COM Now returning error code from last executed program the same way as MS-DOS does (DMAKE, a share-ware make utility, depends on that). If loaded transient, upper memory is now used for the resident part, and high memory is no longer allowed. The memory allocation strategy is now preserved. Memory allocation strategy is now always set to conventional first fit upon load and restored to whatever value it was on exit. SOLUTION Overwrite the COMMAND.COM file in the root directory with the new COMMAND.COM. SYMPTOM (03/21/95) DEBUG.EXE (1.41) DEBUG no longer destroys root mappings whe started with remote drive being current. (05/08/95) DEBUG.EXE (1.42) I and O commands (in enhanced mode) now support ports outside the PC range (>=0400h) and size specifiers B, W, and D (the last only on 386+ processors). SOLUTION Overwrite the DEBUG.EXE file in the NWDOS directory with the new DEBUG.EXE file. SYMPTOM (07/31/95) DELPURGE.EXE (1.01) DELPURGE did not show correct last modified date when file was deleted while DELWATCH was active. SOLUTION Overwrite the DELPURGE.EXE file in the NWDOS directory with the new DELPURGE.EXE file. SYMPTOM (07/31/95) DISKCOPY.COM, DISKCOMP.COM 2.04 No longer changes fields other than the serial number in extended boot records during copy (DISKCOMP could show differences between source and destination after a successful DISKCOPY). No longer unnessecarily formats floppies (was formatting when the logical characteristics did not match, now checks only the physical characteristics - number of tracks, sides, and sectors). SOLUTION Overwrite the DISKCOPY.COM, DISKCOMP.COM files in the NWDOS directory with the new DISKCOPY.COM, DISKCOMP.COM files. SYMPTOM (03/16/94) DPMS (1.1) DPMS fixes minor problems from the original shipping version. Note: This vesion may cause a problem with PKUNZIP 2.04g causing a reboot with DPMS, NWCACHE and (DPMI=ON and/or MULTI=ON). The temporary workaround is to use this an older version of DPMS *or* turn off MULTI and DPMI. Engineering is aware of this issue and is working on a solution. (9/21/94) DPMS (1.2) DPMS is incompatible with 386MAX when 386MAX has been configured with the EMS=0 option. DPMS has been modified to inform the user to reconfigure 386MAX to use the NOFRAME option instead. (11/15/94) DPMS.EXE (1.3) fixes a machine reboot problem seen when MULTI and DPMI are enabled, NWCACHE is loaded and PKUNZIP is executed. (01/23/95) DPMS.EXE (1.4) INT 67 calls are made if running Windows in enhanced mode and EMM386.EXE's multitasking support is not enabled. As a result of these changes, code to restore 0E's entry in DPMS' IDT when quitting Windows should have been removed and this has now been done. (02/23/95) DPMS.EXE (1.41) Reduced memory requirements when running under XMS on 386. (07/31/95) DPMS.EXE (1.42) Now using XMS 3.0 functions if possible. No longer crashing if client calls interface function from protected mode with stack within the first 4Mb when multitasking EMM386 was loaded and Windows is running (primarily affected is DPMSTEST.COM provided with the DPMS SDK). With VCPI and large amounts of memory present DPMS clients could not allocate more than about 8Mb altogether. With EMM386 MULTI/DPMI=ON and Windows started with exactly one outstanding return from a protected mode call-up Windows would reboot during load due to a stack fault at ring 0. With large amounts of memory split into many blocks initialization could crash. This is now avoided if XMS version is 3.0+, for versions less than 3.0 the situation is unlikely to occure as only memory up to 64Mb can be managed. SOLUTION Overwrite the DPMS.EXE file in the NWDOS directory with the new DPMS.EXE. SYMPTOM (07/31/95) EDIT.COM (2.01) Edit was displaying only subdirectories which matched the mask given for files, now all subdirectories are displayed. Possibly also other misbehaviors affected. SOLUTION Overwrite the EDIT.COM file in the NWDOS directory with the new EDIT.COM SYMPTOM (07/31/95) EXE2BIN.EXE (1.01) Presence of extensions in the user specified name(s) is no longer SOLUTION Overwrite the EXE2BIN.EXE file in the NWDOS directory with the new EXE2BIN.EXE SYMPTOM (07/12/94) EMM386.EXE This version has a fix to enable CodeView 4.1 to work when DPMI is enabled. There is still an outstanding problem which occurs when DPMI is set to OFF and this will be addressed at a later stage. Other fixes: NE2100 causing a DMA failure problems with second DMA controllers on ps/2 & comptabiles using channels 5,6 or 7 (08/10/94) EMM386.EXE This version of EMM386 fixes a problem with Borland C++ v4 whereby if the multitasker was loaded VCPI memory would not be freed after BCC32 had been run. (10/03/94) EMM386.EXE (3.04) The fix for the DOS 4GW problem. EMM386 now has a new command line option PIC=ON/OFF if it is set to on VCPI apps will be told the PIC has not been revectored. Please note that it must be set to OFF for normal operations. It seems to get all the games working on the single tasking EMM386 but a couple still fail on the multitasking EMM386 (DOOM 1 and RAPTOR are the two that we are aware off) If you are running on the multitasking EMM386 DPMI must be off. The help screen will give full details. A batch file which does the following before the game is started is recommended: DPMI OFF EMM386 PIC=ON This will set EMM386 and DPMI correctly for games to run. (10/03/94) EMM386.EXE (3.05) This fixes a screen corruption problem with the Dell Latitude when running on the multitasker. Help put in for NOEMS and NOVCPI. PIC state displayed if changed. EMM386.EXE 3.07 Both multi and single tasking memory managers had a memory allocation problem (crashing of the VLMs at load) on EISA machines having more than 16Mb. Master Of Magic (MicroProse) did not run. IP is now correctly updated when instructions that cause a GP fault are traced in a debugger. Accessing DRx registers with DPMI and/or MULTI turned on (CodeView 4.10) is now possible. Resizing an XMS block from 0 to a positive size is now possible under EMM386 MULTI. A problem with this was observed with the FlashTek DOS Extender. Fixed problem with Borland 3.1 IDE debugger. (05/08/95) EMM386.EXE (3.08) Borland's TDX will now work with DPMI=ON. WordPerfect 6 for DOS will now work on PS/2 machines. Fixes a problem with DBase 5 rebooting computer. (07/31/95) EMM386.EXE (3.09) Fixed a problem in handling instruction emulation when the code prefix 0F was present. XMS 3.0 extended functions were handled incorrectly. XMS function 08 now returns maximum possible values if real values would not fit into return registers. Intel SatiFAXtion now working regardless of DPMI or MULTI enabled. There is still a problem if FAXTSR is loaded, Windows was started and terminated again, and then TaskMgr is started FAX.EXE will refuse operation with no error information. If any of the conditions is not met, everything seems to work fine. UMB blocks beyond segment F000 were not exported to Windows, this caused Windows to crash if such a UMB block was included with the multitasking version of EMM386. Total memory size being managed is no longer limited to 64Mb with MULTI/DPMI enabled. There was no limit without either of these options. DPMS client calls to V86 mode procedures could return with interrupts disabled under EMM386 with MULTI/DPMI enabled although they were on in protected mode before and were not turned off in V86 mode. With MULTI/DPMI=ON it is now possible to use memory ranges in the video memory area as upper memory (specifically the monochrome range B000-B7FF was targeted) or to backfill video memory to extend conventional memory and still run TaskMgr successfully. MEMMAX -V did not work if additionally to the /VIDEO option /USE or /INCLUDE were used to map another part of video address space as (permanent) upper memory (eg. V=A000-AFFF U=B000-B7FF). Memory reserved through /VIDEO is now allocated so that DMA into that region is possible without error or data corruption. XMS handles can now be grown even if physically contiguous memory directly following the current block is already used. With TaskMgr running, certain MultiTasker API function calls that use DS as an input parameter could crash with a page fault. With /GATEA20=INT15 specified or detected, false A20 gate failures could have been reported. Memory above 16Mb was not recognized on some Compaq ISA machine. SOLUTION Overwrite the EMM386.EXE file in the NWDOS directory with the new EMM386.EXE. SYMPTOM (07/31/95) FDISK.COM (1.76) With redirected input for automated hard drive installation user had problems that characters other than the languages YES- and NO-characters were interpreted as NO. Now all input other than these two characters is considered as invalid and discarded. SOLUTION Overwrite the FDISK.COM file in the NWDOS directory with the new FDISK.COM SYMPTOM (05/08/95) FILELINK.EXE (3.01) FileLink would display garbage if more than 1000 directory entries were found in one directory. FileLink could occasionally appear to hang during file transfers. SOLUTION Overwrite FILELINK.EXE in the NWDOS directory with the new FILELINK.EXE SYMPTOM (07/31/95) FORMAT.COM (2.06) No longer physically formats floppies which have already the correct physical format but had a different logical format before. SOLUTION Overwrite FORMAT.COM in the NWDOS directory with the new FORMAT.COM SYMPTOM (05/10/94) HIMEM.SYS fixes EMS page frame problems. (03/29/95) HIMEM.SYS Fixed problem with corruption of excluded memory. (07/31/95) HIMEM.SYS 2.32 XMS handles can now be grown even if physically contiguous memory directly following the current block is already used, also specifically handles which had no memory allocated to them can now be reallocated correctly. SOLUTION Overwrite the HIMEM.SYS file in the NWDOS directory with the new HIMEM.SYS. SYMPTOM (08/01/94) IBMDOS.COM IBMBIO.COM SHARE.EXE New IBMDOS and IBMBIO files, fix a problem with VM Boot, where a program called FSFILTER.SYS is installed, taking over INT 21. This does not return the SETVER value in AX, so the version number we get back is invalid. The SETVER version is now poked into the PSP during the INT 21 call, so if something takes over INT 21 we do not use the return value as the version number. Fix to IBMDOS.COM and SHARE fixes a problem where files that were open on a PNW server could be renamed by a client. These files are rebuilds, and contain all previous fixes. ***THESE THREE FILES (IBMBIO.COM, IBMDOS.COM AND SHARE.EXE MUST BE USED TOGETHER - DO NOT MIX WITH OLDER VERSIONS*** Other fixes: Accesing a Stacker 4.0 volume would cause EMM386 protection errors to occur if users had Stacker 4.0 on their hard disk before installing Novell DOS 7. (3/18/94) A double \\ appearing with NetWare 4.x LOGIN.EXE (3/25/94) The system sometimes reads beyond the end-of-chain when corrupt directory entries are encountered. The key combinations of ALT-T and ALT-Q not working correctly with the Colorado Tape Software. Problem initializing DCA's IRMA 3270 emulation software. (6/7/94) Unable to start a DOS session under OS/2 due to SETVER returning an invalid version number. SETVER returning an invalid version number during a VM boot in which a 3rd party device driver takes over INT 21. Accessing a network path greater than 66 characters when using VLMs. After trying to to CD, TREE, XDIR, XDEL, etc. the drive mapping appears to be invalid. (10/06/94) Fixed a problem when remote booting where an attempt was made to load the NWDOS.386 VXD. This fix stops the attempted loading the NWDOS.386 VXD, which is no longer needed, as it could not be loaded after a remote boot process. (05/08/95) IBMBIO.COM INT 2F AH=13 no longer destroys AX (VGACopy crashed due to this). 'SC' memory block signatures are now applied correctly. DRIVPARMed 1.44Mb drives can now be formatted correctly. DRIVPARM can now be used for 2.88Mb drives as per doc. Size of driver to be loaded high now calculated correctly if .EXE file. Ctrl-F5 and Ctrl-F8 are now treated the same way as F5/F8 (MS-DOS 6.2 does so). Keyboard interface now uses enhanced functions on enhanced keyboards. 2.88Mb floppies are now correctly detected even if they are reported as type 04 instead of 05/06 from BIOS. Atari floppies can now be read. FASTOPEN now defaults to 0 as MS-DOS does. HIINSTALL does no longer prevent correct assignment of MCB owners for system MCBs after CONFIG.SYS processing. (11/15/94) IBMDOS.COM (Common to all languages) This version of IBMDOS.COM contains all previous patches. (02/05/95) IBMDOS.COM Load path during EXEC is now parsed to not contain and . and .. entries; also UNC filenames are now handled correctly here. Volume label can now be deleted through server function call. Observed problem Lotus 123 v?.?? not loading. FCB accesses were not working on SUBSTed or ASSIGNed drives. Users would get critical errors 'FCB unavailable' when attempting to access an FCB opened on such a drive. On directory searches the volume label bit takes now precedence over all other bits. Not doing so caused the new CBT install to fail. Lantastic 5.0 now works correctly. (05/08/95) IBMDOS.COM Fixed memory allocation problem seen with Borland DPMI apps were memory was allocated from UMB while UMBs were linked in MCB chain but memory was allocated from conventional memory only. FindFirst/FindNext now correctly handles VOLUME attribute set along with other attributes in search flags. Free memory blocks in upper memory could be left unconcatenated in certain situations. File specifications with embedded redundant backslashes were rejected on MSCDEX (NWCDEX) but allowed (simply removed) by MS-DOS in the same situation. This resulted in files not being found by certain utilities. (07/31/95) IBMBIO.COM No longer fragments upper memory during HIINSTALL if there is a chunk larger than 96kb available (which eventually lead to not being able to load the program in UMB at all). Device drivers loaded with DEVICEHIGH are now all put into one memory arena. Internal UMB allocations during boot are now also prefixed with the correct internal header. Both changes make the result more look like MS-DOS'. (07/31/95) IBMDOS.COM Memory is now allowed to be allocated from UMB if UMBs are linked into chain, allocation strategy is set to conventional, and there is not enough conventional memory to fulfill the request (MS Windows has a problem with disallowing UMB allocation completely in this situation). DELPURGE and UNDELETE showed garbage time stamps for deletion time when listing pending delete files. On INT 21 AX=5D06 calls with certain values loaded into the DX register the system could crash. SOLUTION XCOPY the new IBMBIO.COM and IBMDOS.COM to the root directory using the /HR switch. Then, use ATTRIB -A +R +S +H to give the file the System, Read-only and Hidden attributes. Example #1 -- from the command line, issue the following separate commands: XCOPY A:\IBMBIO.COM C:\IBMBIO.COM /HRV ATTRIB -A +R +S +H C:\IBMBIO.COM XCOPY A:\IBMDOS.COM C:\IBMDOS.COM /HRV ATTRIB -A +R +S +H C:\IBMDOS.COM SYMPTOM Loss of characters and speed of transmission issues during serial communications. SOLUTION Use SETFIFO.EXE. This utility allows the user to set FIFO buffers of 1, 4, 8, or 14 bytes. This may solve both speed and loss of characters issues during serial communications--possible only on a 16550 UART chip. SYMPTOM (09/29/94) SHARE.EXE (1.01) Share will now allow file access if file is read only,existing mode and requested mode are compatability mode and read only mode. int 21 ax=3d00 is the DOS call affected. Added setting of the sharing kernal flag during installation Added check for zero sharing record offset in SFT entry. (02/01/95) SHARE.EXE (2.03) SHARE now allocates lock and file space dynamically which allows for either /F:60000 or /L:4900. One lock can be traded now for 12 bytes of file space. MS Access 2.0 required for a large database merge more than the 1024 locks that SHARE was limited to before. (05/08/95) SHARE.EXE (2.04) SHARE was crashing on load when NCACHE2 was loaded before and both were using HMA. SOLUTION Overwrite the SHARE.COM file in the NWDOS directory with the new SHARE.COM. SYMPTOM (11/18/94) KEYB.COM (2.09) Code added to: a) process Ctrl Tab b) support the Brazilian keyboard. (02/22/95) KEYB.COM (2.10) Shift Tab and Ctrl Tab are now both working. If for national keyboards the AltGr variant of a key is undefined this is now treated as normal Alt (rather than ignored) to be MS-DOS compatible. (05/08/95) KEYB.COM (2.11) KEYB was crashing on load when NCACHE2 was loaded before and both were using HMA. (07/31/95) KEYB.COM (2.12) Corrected hungarian enhanced keyboard layout. SOLUTION Overwrite the KEYB.COM file in the NWDOS directory with the new KEYB.COM. SYMPTOM (02/28/95) LOCK.EXE Pressing Ctrl-Break before or when entering the password does no longer crash the system if BREAK was set to ON. (07/31/95) LOCK.EXE (2.01) LOCK now waites correctly for the first pop-up when the system is still active. If the password input box was popped up with the right key on 102-key keyboards, or if LOCK was started in non-TSR mode with being hit on the numpad it could behave incorrectly. SOLUTION Overwrite the LOCK.EXE file in the NWDOS directory with the new LOCK.EXE. SYMPTOM (05/08/95) MEM.EXE (1.09) Total upper memory is now computed correctly. MEM was crashing if NCACHE2 was loaded due to corruption of the HMA free block chain, it is now checking for this. (07/31/95) MEM.EXE (1.09) MEM still has problems with NCACHE2 having been loaded and unloaded; this is due to corruption of the HMA allocation chain and there is no reasonable way for MEM to cope with that, the only workaround is to specify /USEHMA=OFF for NCACHE2 if it is to be unloaded later or to neither display the HMA contents nor the summary of all memory types with MEM (which means not using switches /A and /F and no switch at all). Now using XMS 3.0 function first for determination of free XMS memory on 386+ processors. SOLUTION Overwrite the MEM.EXE file in the NWDOS directory with the new MEM.EXE. SYMPTOM (05/10/94) MEMMAX.COM Some secondary command processors (such as a DOS shell) can no longer change the memory state. (03/21/95) MEMMAX.COM MEMMAX now can enable/disable upper and video memory without being run from the master command processor. Specifically this allows these commands to be used from 3rd party shells like 4DOS. (07/31/95) MEMMAX.COM (2.01) MEMMAX +-V now updates the UMB root DOS internal variable to reflect the change correctly when doing DOS memory allocations with specific allocation strategies. SOLUTION Overwrite the MEMMAX.COM file in the NWDOS directory with the new MEMMAX.COM. SYMPTOM (07/31/95) NLSFUNC.EXE (3.03) NLSFUNC was crashing on load when NCACHE2 was loaded before and both were using HMA. SOLUTION Overwrite the NLSFUNC.EXE file in the NWDOS directory with the new NLSFUNC.EXE file. SYMPTOM (03/14/95) NWCACHE.xxx With VERIFY = ON statistics were in the range of several giga requests. SOLUTION Overwrite the NWCACHE.xxx files in the NWDOS directory with the new NWCACHE.xxx files. SYMPTOM (08/16/94) NWCDEX.EXE This version includes the following fixes. Implementation of a new (missing) function INT 2Fh, function 150Fh (Get_Directory_Entry). This was done for an application called REEL MAGIC. For this application there was also a change made to INT 2Fh, function 1505h (Read_VTOC) to return a large initialised buffer. There was a change made to Find_Next which fixed the problem related to the installation of NetWare 4.1 from the CD. There was also a change made which stopped the '.' and '..' being displayed in the root. One application fixed by this was REEL MAGIC. SYMPTOM (11/16/94) NWCDEX.EXE fixes several problems. Speeds up CD ROM access considerably. On detecting that a disk has changed during a chdir/openfile/get file attribs/dir entry/findfirst, changes to the root. On calling Int 21/60, the fully expanded path was previously 'Cdex. X:\filename'. This has now been changed to \\X.\A.\filename which is what MSCDEX returns. This former discrepancy was highlighted in BYTE. Fixes a problem seen when CDs are changed and DPMS is loaded. Updates a) device info word (drive number is 0 based) and b) device driver pointer (points to CD's current directoy structure) entries in the SFT so that they are MSCDEX compatible. Will not automatically return an error during a chdir/openfile/get file attribs/dir entry/findfirst operation, if the CD has been changed and the current directory is the root. If the current directory is a subdir and the volume has changed, an error is returned. Fixes a problem seen with the game Critical Path. Fixes a problem to allow the game MYST to install. This must also be used in conjunction with the new IBMDOS.COM dated 11/15/94. Fixes a problem reported with INT 2F / Func. 110C. (12/13/94) NWCDEX (2.5) a) fixes a problem seen when a CD file's extension is greater than 3 characters (maximum of 30 characters possible). In this case, a findfirst/next would not ignore the additional characters, and would therefore conclude that the extension did not match the search extension. Effectively, this meant that some file's were invisible when a DIR was executed. This problem was seen on a COREL CD. b) MSCDEX's INT 2F/1510 (Send device driver request) initialises the subunit field of the device request header based on the drive number supplied in CX, whereas NWCDEX does not. NWCDEX.EXE is now compatible with MSCDEX in this respect. c) fixes a problem seen when accessing subdirectories on machines with multiple CD-ROMs (>5). NWCDEX (2.6) a) Fixes problem seen with LACERTE Tax Software b) Modifications made to ensure subfunctions 1105,1116,111B, 110F, and 150F will fail on finding a \\ in the pathname. (01/23/95) NWCDEX (2.7) Fixes a problem where handles to the CD-ROM device drivers remain unneccessarily open after NWCDEX initialization is completed. SOLUTION Overwrite the NWCDEX.COM file in the NWDOS directory with the new NWCDEX.COM. SYMPTOM (08/15/94) PRINT.COM A new version of PRINT.COM for all languages. This version fixes a problem of hanging after the PRT-SCR key has been pressed due to incorrect resoration of INT 05, INT 00, INT 04, INT 06. It has also been modified to leave TAB expansion to the printer and the Get_Installed_State is now returned in AL and not AX. SOLUTION Overwrite the PRINT.COM file in the NWDOS directory with the new PRINT.COM. SYMPTOM Loss of characters and speed of transmission issues during serial communications. SOLUTION Use SETFIFO.EXE. This utility allows the user to set FIFO buffers of 1, 4, 8, or 14 bytes. This may solve both speed and loss of characters issues during serial communications--possible only on a 16550 UART chip. SYMPTOM (02/22/95) SUBST.EXE (1.03) Both utilities no longer display invalid (beyond LASTDRIVE) drives as assigned/substituted. SOLUTION Overwrite the SUBST.EXE in the NWDOS directory with the new SUBST.EXE file. SYMPTOM (08/26/94) TASKMGR.EXE (2.01) This version fixes the problem where if the server were loaded with taskmanager the SFT file count would not be updated on termination of taskmgr causing possible file corruption. (11/17/94) TASKMGR.EXE (2.02) Fixes a problem with BREQUEST. It will also make Taskmgr more stable with the network loaded. Fixed problem with PeachTree V8 hanging. Now keeps screen parameters for 80x25, 80x28, 80x43, and 80x50 modes upon load and restores them on exit. (07/31/95) TASKMGR.EXE (2.02) XMS upper memory blocks are now treated the same as normally allocated UMBs when instancing memory. TaskMgr when loaded from a network drive could cause the connection to the appropriate server being terminated. If LOCAL HANDLES are set to TRUE, all handles are now instanced instead of just two. SOLUTION Overwrite the TASKMGR.EXE file in the NWDOS directory with the new TASKMGR.EXE. SYMPTOM (10/03/94) TREE.COM (1.61) Fixes system crash when trying to display paths greater than 66 characters. SOLUTION Overwrite the TREE.COM file in the NWDOS directory with the new TREE.COM SYMPTOM (07/31/95) UNDELETE.EXE (2.01) UNDELETE did neither show nor restore last modified date correctly when recovering file that was deleted with DELWATCH active SOLUTION Overwrite the UNDELETE.EXE file in the NWDOS directory with the new UNDELETE.EXE SYMPTOM (10/10/94) XDEL.EXE (1.46) Fixes 3 problems: 1. System crash when trying to recursively delete paths greater than 66 characters. 2. Current directory removed when recursively deleting from the parent dir (eg. "xdel .. /sd"). 3. Top-level directory not removed when password protected. SOLUTION Overwrite the XDEL.EXE file in the NWDOS directory with the new XDEL.EXE SYMPTOM 10/03/94) XDIR.EXE (2.06) Fixes divide-by-zero error when trying to recursively display paths greater than 66 characters. SOLUTION Overwrite the XDIR.EXE file in the NWDOS directory with the new XDIR.EXE ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------