|
| Table Of Contents | Index |
RELEASE and RELNET are capable of removing many, but not all, TSR's from memory. If you find that RELEASE doesn't successfully remove a TSR, try RELNET instead. Even with RELNET, however, some TSR's cannot be released without specific internal knowledge of the TSR. Since we don't have (or care about) all such TSR's, RELEASE and RELNET may not be compatible with them. If you find that RELNET won't release a TSR, there is little we can do to help you.
The most common examples of TSR's that can't be released are those that cooperate with other TSR's in memory. Examples include Microsoft's MOUSE driver and its associated MENU program; and the program CED with its "user-installed commands" such as KEYIN, HS, RAW, and others. These programs can be released, but only if all the cooperating partners are released at the same time. CED is well-behaved in that it provides a built-in command (KILL) to release its partners. MOUSE is not so flexible, though.
Another problem TSR (and one that we hear about regularly) is the Token Ring IPX driver for Novell NetWare. For some reason, IBM designed this IPX driver in two pieces: one part that is loaded as a device driver in CONFIG.SYS and another that is loaded as a TSR in AUTOEXEC.BAT. RELNET does not release device drivers in general, and it cannot release the TSR portion of the Token Ring driver without also releasing the device driver portion.
You should almost never use RELEASE or RELNET to release disk caching programs. If you do so, part of the information that should be stored on disk will never be written there, and you may end up with a corrupted disk as a result. If you know that the disk cache uses a "write-through" algorithm (which guarantees that all writes immediately go to disk), or if the disk cache has a "flush the cache" command, then it may be safe to release the cache.
You cannot release the FASTOPEN and APPEND TSR's provided with DOS 3.3 and later. These TSR's patch internal DOS data areas that cannot be reliably located even by MARKNET and RELNET.
You cannot use DISABLE to deactivate SideKick Plus, whose swapping technique is incompatible with DISABLE.
For reasons we haven't been able to determine, when using the combination of PC-DOS 4.00 and 386MAX 6.00 it isn't possible to reload the NetWare NETX shell high after unloading it once using RELNET /U. If you have this problem, we recommend that you toss your DOS 4.00 and upgrade to MS-DOS 5.0.
|
| Table Of Contents | Index |
|
