Sandstorm Enterprises® : LANWatch® for DOS FAQ
Sandstorm Enterprises® Niksun
LANWatch® for DOS FAQ

Q: Which LAN interfaces can I use with LANWatch for DOS?

Q: What if I want to run LANWatch in a Windows DOS box?

Q: How do I monitor serial line traffic?

Q: What if I can't find a Packet Driver for my network interface?

Q: What can I do if Install won't start due to insufficient memory?

Q: Why doesn't setting bandwidth=100 in lanwatch.ini have any effect with LANWatch 4.0?

Q: Why does LANWatch not use EMS when other programs have no problem using it?


Q: Which LAN interfaces can I use with LANWatch for DOS?
You can use any interface that supports the Packet Driver specification. If drivers and installation instructions aren't included on a floppy or CDROM shipped with the interface, check the manufacturer's web site (we maintain a list of sites, but information included with your interface may be more up to date).

Back to top

Q: What if I want to run LANWatch in a Windows DOS box?
In order to run LANWatch in a Windows 95/98 DOS box, you must get ndis3pkt from www.danlan.com. This will provide a packet driver interface for LANWatch in a DOS box. To use it, you must have installed LANWatch to use the packet driver interface. It is not possible to run LANWatch in a Windows DOS box from Windows 2000 or XP.

Back to top

Q: How do I monitor serial line traffic?
LANWatch for DOS lets you monitor serial line traffic on another computer using a special 2 headed serial line cable. Please contact Sandstorm Enterprises Sales at sales@sandstorm.net or by telephone at 1-781-333-3200 to find out more information on either purchasing or building this item yourself.

LANWatch for DOS cannot monitor serial line traffic on the computer that LANWatch for DOS is running upon, due to the nature of DOS. To perform this, see the LANWatch FAQ.

Back to top

Q: What if I can't find a Packet Driver for my network interface?
If either a Novell ODI driver or a Microsoft NDIS version 2 driver is available for your interface, you can get the DIS_PKT or ODIPKT adapter module from www.danlan.com. These provide a Packet Driver interface conversion function.

Back to top

Q: What can I do if Install won't start due to insufficient memory?
The solution to this problem is to free up extra memory. Try commenting out as much as you can from your config.sys and autoexec.bat files. Even Packet and NDIS drivers can be commented out during the installation as LANWatch does not look for loaded drivers during the installation procedure.

Back to top

Q: Why doesn't setting bandwidth=100 in lanwatch.ini have any effect with LANWatch 4.0?

The solution to this problem is to call Technical Support at 781-333-3200 to get an updated LANWatch 4.1 that fixes this problem.

Back to top

Q: Why does LANWatch not use EMS when other programs have no problem using it?
There is a problem in LANWatch which requires that the EMS page frame fall on a 64K boundary. For example: E000 and D000 are acceptable. E800 and D800 are not acceptable. Note that problems have been reported in EMM386.EXE version 4.4 (this shipped with Windows 3.1 and early versions of DOS 6). You should make sure you are running version 4.49 which shipped with DOS 6.2 and later.


Sandstorm's Products grey arrow
Order / Get a Quote grey arrow
Contact Us grey arrow
Back to topgrey arrow
Sandstorm Enterprises develops
tools with sharp edges®
for information security professionals.
Site materials © 1998 - 2010 Sandstorm Enterprises, Inc. The Sandstorm logo®, LANWatch®, NetIntercept®, PhoneSweep®, Sandtrap®, TCP.demux™, Single Call Detect™, Tools with sharp edges®, Rapid Event Analysis™, and Sandstorm Enterprises® are all trademarks or registered trademarks of Sandstorm Enterprises, Inc.