Who does this apply to?

Anyone using trying to connect their legacy DOS 6.xx or Windows 3.1x computer to a Microsoft Windows based server (Windows 3.11/Windows95/WindowsNT) using Microsoft Networking.  Note that Windows 3.11 is also known as Windows for Workgroups

This applies to ANY VERSION of Solution System 2 or CaseBASE for DATIS.

Issues Covered

• Client software connecting your computer to Microsoft Networking File Server.

Client Updates:

What is "Client Software"?

The software that is used to connect a computer to a network server, or a Windows based computer sharing resources is usually called 'client' software.  It is also sometimes referred to as the network's workstation components.

Client software is what lets your computer take advantage of network resources in a Windows based network.  When you are using DOS Networking Add-On, Windows 3.1x Windows for Workgroups, Windows 95 or Windows NT's peer-to-peer networking, you are using a Microsoft Networking network.

Is your Client software up to date?

As you probably know, Microsoft is always updating it's software based on user feedback and the discovery of bugs.

Database programs typically push networks to their technical and physical limits.   Unlike sharing a single wordprocessing document on a network, a database is accessed by multiple users, simultaneously - creating both network traffic and concurrency issues (Concurrency is the technical term for the possible conflict between two processes for the contents of the same record or file, or for the privilege to change data in a record or file).

DOS based programs use a file and record locking strategy that goes back to MSDOS version 3.1.  This locking standard is often referred to as "DOS 3.1 File and Record Locking" or "DOS 3.1 Sharing".  DOS based database programs rely on this standard in order to manage multiple users accessing and updating database records at the same time (concurrently).  If this standard isn't adhered to properly, database file corruption and odd database application behaviour can occur.  These problems are usually very frustrating and highly difficult to solve. 

The first thing you can do to save yourself a whole lot of anquish is to ensure your client software is up to date.  As of the writing of this product bulletin (November 10, 1997), Microsoft has updates available for it's DOS 6.xx/Windows 3.1x/Windows for Workgroups Add-Ons products.  Since Microsoft considers DOS and Windows 3.xx to be obsolete products, it is most likely that these links represent the final versions of those networking clients.

DOS 6.xx and Windows 3.1x/Windows for Workgroups Add-Ons

Another hint:

EMM386.EXE and HIMEM.SYS play very important roles in memory management.  This is particularly important in management of the Upper Memory Block - this is where software and hardware can come together to create the most frustating problems.  You should always try to get the latest versions.  EMM386.EXE and HIMEM.SYS are not tied to the version number of DOS - so you can take these files from your latest Windows 95 installation and copy them to your DOS based computer and they should run fine.  ACSL does not advocate software piracy, but, if you own the Windows95 and DOS copies, we don't see Microsoft objecting to this practice - particularly if it resolves your problem with their software.  Otherwise, you can download the last recommended update of EMM386.EXE and HIMEM.SYS from the Microsoft support site.

Server Updates

Microsoft distributes fixes to its NT family of Windows server products in the form of 'service packs'.  Service packs are a component based approach to bringing your networking software up to date.  It is recommended that before you call any vendor for software support to complain about abberant behaviour of your file server or application program, that you ensure you have installed the recommended service packs from Microsoft (or else your software vendor will tell you to call them back after you've installed the service packs).  In many cases, this is a legitimate response.   For instance, Service Pack 5 for Windows NT 3.51 is critical for solving a whole bunch of networking level problems.  In some cases, one service pack can represent literally hundreds of tiny fixes by Microsoft.  Its always best to play it safe and up to date.

Below are the links to the Microsoft download site that houses these service packs.   Again, this is as accurate as of November 10, 1997, so you may want to double check to see if these are the latest service packs if you are viewing this document, say, by the second quarter of 1998.  Windows NT Server 4.0 is Microsoft's current release, so it is most likely that if any new service packs appear, it will be for 4.0.

Windows NT Server 3.1

Windows NT Server 3.5

Windows NT Server 3.51

Windows NT Server 4.0

Be sure you download the latest recommended service pack for your file server's microprocessor - which will generally be Intel x86 based.

It is beyond the scope of this bulletin to discuss how to apply these service packs, but there should be instructions and product notes accompanying these service packs.   If you are stuck for finding a qualified vendor to perform these service packs, give ACSL a call, and we can send out a technician on an hourly time and materials basis.

Also see:

RFCB Caching and Opportunistic Locking in Windows NT 3.51 or Higher

Windows 95 - Windows NT buffering Problem

Windows95-OSR2 Message- "this program performed an illegal operation..." system error