Corbin Willits Systems ö MIS Division

 

 

Networking Issues

 

1.       If your network has single or multiple Windows NT Servers, do not install NWLink, IPX/SPX protocols on the NT server or clients. This is a known issue acknowledged by Microsoft that in some cases these protocols will cause file corruption. Use TCP protocol only as your default protocol instead.

2.       Do not use any power-saving features on either NT or the clients, other than a screen saver.Ê We have received reports ofÊ ãillegal operationä and General Protection Faultä from some clients that are related to this feature.Ê This problem causes TCP packets to be dropped when the PC 'wakes up' again, causing ProvideX file corruption. (Actually, all hardware interrupts are lost when the PC wakes up).

3.       Do not use network hardware in either the NT server or the clients that is not immediately recognized by the Operating System, causing the customer to install software drivers from the hardware manufacturer.Ê Only customers with 3COM hardware get away with this without major network problems. *ALWAYS* use Microsoft drivers when they are available.Ê Consider moving to other hardware when you can only get drivers from the manufacturer.

4.       PC-Anywhere (Version 7.5) is known to cause file corruption when it is installed on any workstation even if PC-Anywhere is not running. We recommend removing it from any workstation or upgrade to the newest version of it.

5.       Always verify your PCs BIOS. Some PCs do not perform well in a network environment and require BIOS update (Some of the HP Vector and Brio models, some Compaq models. Please check The manufacturer web pages and Microsoft Knowledge Base on the Internet)

6.       Always verify your network interface cards (NIC) with the Microsoft Hardware Compatibility List.Ê Some clients have reported file corruption, network hang ups and Unlock Region failure due to unsupported network cards (Intel EtherExpress Pro/100 PCI, Compaq NetFlex-3 and almost all of the generic NICs)

7.       For 100Base-T Networks cabling is critical verify your cable is CAT5

 

 

Network Configuration.

 

MOM-PVX running in a conventional network puts a tremendous load of packets on the network media.Ê Due to this configuration, the server works as a file and application server leaving the workstation to handle most of the application processing.Ê This fact demands significant workstationâs resources and memory and requires having the network optimized for proper operation.Ê In case your network is configured to run NT servers and multiple applications, we strongly recommend installing the Server/Client (PVX/WindX) version of our software.Ê The Server/Client version requires an extra piece of software running on the workstations (WindX running NTSlave) and an application service running on the server (PVX NTHost).Ê Please call CWS for details.

 

 

Notes on Supported Hardware

 

MOM-PVX version works with most Dot Matrix printers as long as they are Epson compatibles and MS Windows 95/98 and Windows NT/2000 support them.

Serial printers defined as ãlocal printerä on Windows (95/98/NT) in UNIX/AIX system may not work well and it is not recommended.

MOM only supports Laser-checks printing on HP Laser printers. The following model has proven to work well: HP LaserJet III, LaserJet 5Si, LaserJet 4000-4050 and LaserJet 8000-8100 series

Other Laser printers may work well if they can emulate 100% a HP LaserJet printer, however CWS does not assume any responsibility if they do not print as expected.

 

Notes on Unsupported Printers

We have found some of our clients are having serious problems after upgrading to MS Windows platform:

 

-Ê Printronix Dot Matrix (Old printer, No drivers for Windows 95/98/NT)

-Ê Okidata Microline 320/321

-Ê IBM Proprinter 24 XL (Serial interface)