This update allows LANalyzer for Windows 2.1 to work with the latest ODI drivers written to the new ODI 4.0 spec. Before this update, the only way to get LANalyzer for Windows 2.1 to work with the new drivers was to use a "shim" (RXMONSTK.COM) that came with VLM 1.2.
However, when you bring up LANalyzer for Windows, the dashboard and station monitor show no activity.
SOLUTION:
Install LZW002.EXE.
Self-Extracting File Name: lzw002.exe
Files Included Size Date Time
..\
LZW002.TXT (This file)
DI.COM 978 4-5-95 11:42:50 am
DI11.COM 30223 4-5-95 11:42:46 am
DI12.COM 10989 4-5-95 11:42:48 am
Installation Instructions:
1. Remove any LOAD RXMONSTK.COM statments that may exist in your .BAT files. (You may also wish to erase RXMONSTK.COM, you shouldn't be needing it anymore.)
2. Erase the "old" DI.COM.
3. Copy the 3 files in LZW002.EXE to the directory where you had the old DI.COM.
4. In order for DI to function properly, you must listed ALL possible frame types under the "Link Driver" section for your NIC driver.
The possible frame types for Ethernet are:
Frame Ethernet_802.2
Frame Ethernet_II
Frame Ethernet_SNAP
Frame Ethernet_802.3
The possible frame types for Token Ring are:
Frame Token-Ring
Frame Token-Ring_SNAP
DI.COM is a small utility that detects the version of your NIC driver and then spawns either DI11.COM or DI12.COM.
DI11 is just the old DI.COM renamed.
DI12 is the new DI for ODI 4.0 drivers.
DI.COM will choose the correct DI for you.
You don't even need to change your batch file for loading the TSRs.
To load DI, just type DI.
To unload type DI -U as before.
The only time you'll notice a difference is when you do a "mem /c".
Instead of seeing DI.COM listed, you will see either DI12 or DI11 listed.
DI will check to see if RXMONSTK is loaded. If RXMONSTK is loaded, DI will ask you to unload RXMONSTK and refuse to load.