A. You have a PEER TO PEER WINDOWS 95 network for the First Resort program.

This Document is for WIN95 PEER environments ONLY. First Resort supports Novell, Peer to Peer 95, and NT.

B. You have First Resort installed in the standard directory C:\ACCOUNTS

The First Resort software is loaded to one of the Windows 95 workstations in the \ACCOUNTS directory. I will refer to this workstation as the HOST workstation. Although it is not a problem to run the program in a non standard directory, upgrades can have trouble if not installed in the default location. Be aware of this and if not in a standard directory, consider moving the program to the default area. Also our tech staff will expect the program in the default directory, and if not there it makes support difficult. The peer to peer network is made up of up to five workstations. For First Resort needs, we designate one of the Windows 95 workstations to be the Host Workstation, and all others will map a drive to the C:\ of the Host. For the purpose of this document I will distinguish the workstations as HOST and CLIENT, where the HOST is the workstation with First Resort loaded on the C:\ACCOUNTS, and CLIENT has a drive F:\ mapped to the C:\ of the HOST.

Check the following Standard Problems

1. All users need complete rights to the accounts directory.

This is a problem that will only occur on the CLIENT workstations. The HOST workstation will never have a rights issue. This is because the HOST has the First Resort program running on the C: drive which is a local hard disk for that machine. If the CLIENT workstation does not have rights, First Resort will not work properly. One sure way to check for rights on the CLIENT workstation is get a DOS window and change the directory to F:\ACCOUNTS. Try to create a dummy file, if it works and you are able to save it then no problem. If you get an error saving the file then we need to fix it. For example from the F:\ACCOUNTS on the client workstation type….

Test using EDIT (or) Test using FILE CREATE

EDIT TEST.TST DIR *.EXE > TEST.TST

(type some stuff)

(save the file) TYPE TEST.TST - see if dir *.exe output is echoed

ALT-F S - to save

ALT-F X - to exit

TYPE TEST.TST - see if file saved

If you get an "ACCESS DENIED" or "CANNOT CREATE OR RETRIEVE FILE" error then the HOST workstation does not have full rights set to the C:\ACCOUNTS directory. To fix this problem go to the HOST workstation and do the following…. START PROGRAMS WINDOWS EXPLORER. Under the icon MY COMPUTER locate the C: drive which should have a hand icon under the drive showing it is a shared drive. With the mouse over the icon hit the RIGHT BUTTON and select SHARING. Make sure ACCESS TYPE is set to FULL. This should open up the rights for all CLIENT workstations. Make sure to click on OK to save the setting. There is no need to reboot, try one of the tests above to verify the fix.

2. Workstation has enough File Handles

Not having enough file handles can report 2 types of errors. Symptom #1 is an error saying "Not enough file handles". Symptom #2 is an error saying "FILE XXXX does not exist, Hit Y to create…". In both cases the file in question is there and the workstation cannot open it due to a lack of file handles. The problem is that the file is really there, and our software from the error thinks it is not and will try to create a new one. The program will not overwrite the data, so not to worry. To fix this problem, edit the file C:\CONFIG.SYS and make sure the following line is included at the end of the file or increase.

(To fix the file handles issue add this line, or locate and increase the existing number, in C:\CONFIG.SYS)

FILES = 120 (Max FILES=250)

3. F: needs to mapped from the CLIENT workstation to the C: of the HOST workstation.

When running the First Resort program on the HOST workstation, you will run it from the C:\ACCOUNTS directory. On the CLIENT stations, you will need to map a drive letter F: to the C: of the HOST. First Resort expects the C: of the host to already be set up as a shared drive. To verify this go to windows explorer of the HOST machine and locate C:. It should have a icon picture of a hand under the drive signifying it is a shared hard drive. Next you must map a drive letter F:, setup as a permanent mapped drive on each of the CLIENT workstations using windows explorer. To do this on each CLIENT workstation do the following…. Click on START PROGRAMS WINDOWS EXPLORER. Next select TOOLS MAP NETWORK DRIVE and it will bring up a window with a DRIVE, PATH, and option for RECONNECT AT LOGIN. First Resort recommends you use F: as the drive letter. Also make sure to check ON the reconnect at login box. Then you must give the path which follows the following format \\HOST_NAME\DRIVE_NAME. You need to know you HOST_NAME and DRIVE_NAME. To determine this go to the HOST workstation and do the following…. To locate the HOST_NAME go to START SETTINGS CONTROL PANEL NETWORK. Next click on the IDENTIFICATION folder and locate the field COMPUTER NAME, that is the HOST_NAME field. Next on the HOST double click on MYCOMPUTER icon. Next move the mouse over the C: DRIVE and click on the right button, and select SHARING. Locate the field SHARE NAME, that is the DRIVE_NAME. Now you can fill out the mapping path described above in the format \\HOST_NAME\DRIVE_NAME. Make sure to click OK when done filling out that dialog box. Reboot the CLIENT workstation and get a DOS prompt. Next type F: and see if the prompt changes to F:. Then test by typing CD \ACCOUNTS to see if you can get to the accounts directory. AVMAIN will then start the First Resort program. Repeat this drive mapping on each CLIENT workstation. Remember the HOST will not need to do this as it uses C:\ACCOUNTS, not F:\ACCOUNTS.

4. F:\ACCOUNTS cannot be in the search path.

If Accounts is in the search path, it will cause program problems with First Resort. To check to see if it is, do the following. At a DOS prompt type "PATH" and look at the output. You should get a response something like ….

PATH= C:\;C:\WINDOWS;C:\WINDOWS\COMMAND;…….;F:\ACCOUNTS

In the above example, F:\ACCOUNTS appears in the search path. This is NOT GOOD, and must be removed. Each machine on the network including the HOST may have this set up improperly. You will locate the PATH command in you C:\AUTOEXEC.BAT and you must remove the occurrence for \ACCOUNTS. Reboot the workstation to take effect and type PATH at a DOS prompt to verify it is gone.

5. AVMAIN & RGMAIN & FORESITE MUST RUN WINDOWS95 COMPATIBLE VERSIONS.

This problem is related directly to Win95 peer to peer networks. If you are running a 95 peer to peer then you must be using the versions of the software listed below or newer. Older versions of the software do not have Windows file locking available, so make sure your software is running at least versions higher than the ones listed below, and First Resort RECOMMENDS YOU RUN THE LATEST VERSION. Win95 compliant versions are…

AVMAIN Version 9.16 or Greater First Resort Main Program

FORESITE Version 1.15 or Greater Foresight Program

RGMAIN Version 1.33 or Greater Report Generator

6. Workstation must has enough conventional memory 570K or More.

This is one of the most common errors with First Resort. The symptoms can be numerous including errors that do not seem to relate to memory in any way. The typical crash is that you will be running the program or shelling to and from First Resort, and it will kick you out of First Resort and echo many different unrelated errors. You can isolate the problem by going to another workstation and try the same operation there. If the error is the identical error as the first station, then it is most likely a problem in the database, and a rebuild or another fix must be applied. If the operation works, than we have proved that is a workstation problem, most likely a memory problem. So, if you have suspected memory problems you will have to optimize the workstation to increase to LARGEST EXECUTABLE PROGRAM SIZE to 570K or More. Remember since your workstation is a WIN95 Machine, this 570K number is not a rock solid number. This is because the 95 Machine handles the Memory much better than older DOS workstations. To test the Memory type MEM at a DOS prompt.

Look for the line that says …

"Largest executable program size 520K (532,720 bytes)"

In this case example the workstation has only 520K we want 570K or more.

Fixing this problem can be complicated, and you should consider bringing in your local hardware support person with experience optimizing memory on workstations. Remember to use only standard Memory Managers HIMEM.SYS and EMM386.EXE NOEMS. If you try to optimize the memory using special packages like 386MAX or QEMM you will most likely run into trouble. If your WIN95 Machine has trouble we at First Resort setup the config.sys and autoexec.bat with conservative settings listed below. Remember Windows 95 does not usually put HIMEM & EMM386 in the config.sys, we are forcing them in due to the fact that your workstation is getting memory related errors. Always backup the old copies so we can fall back on them if the fix does not work. Also, do not be alarmed if no copy of C:\AUTOEXEC.BAT and C:\CONFIG.SYS exist, just create them. You will have to reboot for the fix to take effect.

EDIT THE C:\CONFIG.SYS EDIT THE C:\AUTOEXEC.BAT

DEVICE=C:\WINDOWS\HIMEM.SYS SET NWLANGUAGE=ENGLISH

DEVICE=C:\WINDOWS\EMM386.EXE NOEMS PROMPT $P$G

BUFFERS=40,0 PATH C\WINDOWS;C:\WINDOWS\COMMAND

FILES=120 SET TEMP = C:\TEMP

DOS=HIGH,UMB

FCBS=16,0

(YOU SHOULD HAVE A DIRECTORY C:\TEMP)

7. SYSPARM.SYS is setup for the correct Network Type

The sysparm.sys file lives in the accounts directory, and it is the file First Resort uses to tell the program how to do the file locking. The problem is if this file is not setup for the correct file locking it will case corruption of the First Resort data files, or it will cause the CLIENT stations to not work at all. If the sysparm.sys is setup for Novell, the client stations will get an error "THIS PROGRAM HAS PERFORMED AN ILLEGAL OPERATON" and kick you out of the program. This file is created automatically if not already present, and in some cases the user can overwrite the file and upon recreation there is always the possibly of setting file locking the wrong way. To see if your sysparm.sys is correct do the following. From any workstation go to the \ACCOUNTS directory and type the following "TYPE SYSPARM.SYS". The sysparm.sys file is a binary file, so you will see a lot of special characters on the screen. On the first line, the 3^rd character must be a 'W'. The possible characters are N - Novell, P - Standalone PC, W - Windows NT or Windows Peer to Peer. If it is not a 'W', then the file locking will not work properly. To fix the problem, rename the sysparm.sys file and run avmain to create a new sysparm.sys file.

1. RENAME SYSPARM.SYS SYSPARM.OLD
2. AVMAIN
3. (ENTER THE DATE), (ENTER W for WINDOWS PEER) (THIS CREATED A SYSPARM.SYS)

If you're still having network problems, consider these more advanced network fixes.

1. Run the configure program for the NIC cards and make sure all advanced features are shut off.

NIC means Network Interface Card. Some network cards with advanced features enabled can cause data corruption. For example the INTEL ETHERNET EXPRESS NIC can cause data corruption. It will occur if the card has an advanced option called "CONCURRENT PROCESSING" enabled. It is possible that other network cards do the same, but as of now no others have been found. If you are having constant data corruption issues, consider running the NIC configuration program for each NIC on your network including the HOST and shut off all high level functions such as "CONCURRENT PROCESSING".

2. VIRUS scan all workstations HOST and CLIENT.

As we are all aware, viruses are a problem. Although no documented problems can be directly attributed to viruses, when having trouble, run a virus detection program on all workstation and even the HOST to test for possible infection. First Resort recommends MCAFEE as Norton 3.0 and 4.0 may cause workstation problems with the First Resort program. It has been known to produce the error "SHARING VIOLATION".

3. Consider running a packet analyzer program to watch for bad net cards.

So you tried everything and you are still having network problems, and constant data corruption. Consider having your support person run a network PACKET ANYALYZER program to look at network packet information. This program can point out hidden NIC failure and other network issues that are not clearly visible. A bad NIC can cause a lot of trouble on a network.

********** TROUBLE SHOOTING TECHNIQUES ********

If the program fails on CLIENT workstation A with error XX, go to another CLIENT workstation and try the same operation. If the error is XX on CLIENT workstation B then It is a strong possibility the problem is the HOST or First Resort Data, which points to a database rebuild or a setup problem on the HOST. But if it fails on CLIENT workstation A and works on CLIENT workstation B then it is a problem with the CLIENT workstation A, pointing to a memory issue or file handle issue or some workstation issue..

If the CLIENT workstation is having trouble, check the same operation on the HOST workstation. If it works at the HOST, then there is a Peer to Peer network issue not setup right. Check the rights, search path, mapped drive, and even memory or file handles tests to isolate the CLIENT error. If the HOST also fails than we are again looking at an First Resort data problem, pointing to a database rebuild.

OUTLINE FOR INSTALLING A PEER TO PEER NETWORK.

In Peer to Peer setup each machine has the potential of being a HOST, but for us only one machine is the HOST. We need to do a little background work in preparation for configuring the Win95 workstations.

Prepare the following tools and topology for the Network

1. Have your Windows 95 CDROM or Floppy Disks handy.
2. Assign a Computer Name to each workstation on the network. (Think about naming the HOST workstation HOSTPC)
3. Assign a Name for each hard disk you plan on sharing across the network.
4. Assign a Name for each printer you plan on sharing across the network
5. Locate the Windows 95 NIC driver for you Network Interface Card.
6. Know and have setup the IRQ and I/O ADDRESS for each NIC on the network.
7. Assign a Name to the entire Network to use (Workgroup Name)
   

Installing the Peer to Peer

Assuming you have the NIC installed and configured on each workstation. Also assuming the network cable is in place using COAXIAL or RJ45 & HUB. Assuming the workstations are all Windows 95. Assuming all printers are installed on each workstation that uses a printer.

1. First we must go to each workstation and install the Network Drivers, Interface Card Drivers, and File and print sharing. During this phase it may prompt you to restart the workstation. Answer NO to restart workstation until you have completed this section. For each workstation do the following…

1. Go to Control Panel
2. Go to Network
3. I am assuming you have no drivers currently listed, although you may have NIC drivers or DIAL-UP already listed
4. CLICK ADD CLIENT ADD MICROSOFT CLIENT FOR MICROSOFT NETWORKS.
5. Next it will bring up a window on you NIC driver if no driver is installed, You may have the driver disk provided by the NIC company and you can click on HAVE DISK. Or you may add one of the drivers provided by Windows 95. If you do not have this driver disk, or the driver is not supplied by Windows 95, you cannot continue. For the purpose of this example we will assume you have a MICRODYNE NE2000PLUS card configured to IRQ - 5, and I/O 340.
6. Select Network Card Driver. Select Novell/Anthem, and NE2000 PLUS (Microsoft if option for Novell or Microsoft).
7. Highlight the new adapter card entry and click the PROPERTIES button
8. Click on the Resources Folder.
9. Enter your IRQ and your I/O recorded for the NIC of this workstation.
10. Click CLOSE and Locate the IDENTIFICATION folder and click it to activate.
11. Enter the Computer Name recorded for this workstation.
12. Enter the WorkGroup name for the entire network to use.
13. Enter a description of your choice
14. Click OK when complete.
15. Click on the Access Control Folder and make sure Shared Level Access is set.
16. Click OK when complete
17. Click the FILE and PRINT SHARING button on the configuration folder
18. Make sure to check on the SHARE FILES and SHARE PRINTERS button.
19. Click OK and when it asks to restart say OK.
20. When the station restarts it should give you a LOGIN, just hit enter.
21. REPEAT THIS PROCEDURE FOR ALL WORKSTATIONS ON NETWORK.

After the procedure is completed and each workstation is rebooted, you can check to see if you were successful by opening NETWORK NEIGHBORHOOD icon on your desktop. Under entire network you should see each computer name listed on each of the workstations in the network. Do not continue until this works.

2. On the HOST workstation, we need to set the hard drive as a shared volume. You can do this to more workstations, but for First Resort needs, we only need to do this to the HOST workstation that will have the hard drive containing the C:\ACCOUNTS directory.

1. On the HOST start explorer, START PROGRAMS WINDOWS EXPLORER.
2. Locate the C:\ on the tree listed and move your mouse over the icon.
3. Click your right button and select SHARING
4. Click on SHARED AS.
5. Enter a HARD DISK NAME recorded earler.
6. Click on ACCESS TYPE FULL
7. OK to save, results activate without restarting.

3. Map a Drive Letter F: on each of the CLIENT workstations to point to the host computer hard drive C:. DO THIS ON ALL WORKSTIONS BUT HOST.

1. On CLIENT start explorer, START PROGRAMS WINDOWS EXPLORER.
2. Click on TOOLS, then MAP NETWORK DRIVE
3. You have three fields DRIVE, PATH, and RECONNECT AT LOGIN.
4. First Resort recommends you use F: for the Drive
5. Click on RECONNECT AT LOGIN
6. For the path the format is \\HOST_PC_NAME\HOST_HARD_DISK_NAME. You must enter the names you recorded earler.
7. REPEAT THIS FOR ALL CLIENT BUT NOT THE HOST.

4. You are now ready to run First Resort on the Peer to Peer network. You should create an icon on each workstation to run First Resort. You can always access First Resort by getting a DOS prompt and changing the directory to F:\ACCOUNTS on the CLIENTS and C:\ACCOUNTS on the HOST. To run the program type AVMAIN in the ACCOUNTS directory. To create the icon do the following.

1. Move the mouse to an open spot on the desktop and click the right button. Select NEW SHORTCUT enter (C:\ACCOUNTS\AVMAIN or F:\ACCOUNTS\AVMAIN) depending on HOST or CLIENT enter a name of your choice choose a icon of your choice FINISH.
2. Do this for every machine on the network.

5. Next project is to setup the network printers. Assuming each printer is installed on the workstation in question, and prints from windows, and assuming each workstation hosting a shared printer has file and print sharing setup (completed in step #1). For the workstation that has the printer installed to LPT1 or LPT2, we must set the printer to be a shared printer. For the workstation that is going to use the shared printer provided, we must capture the printer port and assign it to the shared printer.

1. FOR EACH WORKSTATION HOSTING A PRINTER WE MUST MAKE THE PRINTER A SHARED DEVICE
2. Click START SETTINGS PRINTERS
3. Click the right button on the windows printer driver for the printer to be shared and select SHARING
4. Click on the SHARED AS and enter a PRINTER NAME recorded above.
5. Click OK to save.
6. Repeat this for each workstation and printer to be shared, all using unique names.

6. Next we need to CAPTURE THE PRINTER AND PORT FOR EACH WORKSTATION that wants to use one of the shared printers.

1. On each workstation that wants use of a shared printer, we must capture the printer port LPT1: and/or LPT2:. A maximum of two parallel printers can be used by First Resort. For workstations with the printer physically located on LPT1: and/or LPT2: no setup needs to be done.
2. Open printer page START SETTINGS PRINTERS.
3. Move mouse to a empty spot on print page and click right button selecting CAPTURE PRINTER PORT.
4. Select LPT1: or LPT2: for the Device.
5. Enter \\COMPUTER_NAME\PRINTER_NAME recorded earler.
6. Click on reconnect at login.
7. Test printing from First Resort. From any screen hit CNTRL/D and L,1 for LPT1: or L,2 for LPT2:.