|
| |
Tips for Running BPI on Networks
March 3, 1999 -- BPI Accounting was designed for use on either
standalone PC's, or on networks (LANS). Here are a few ideas on making BPI work right on
networks.
 | LANPAK. Use the LanPak. The LanPak is the part of BPI that makes BPI
perform right on your server. It is a separately installable disk. You always want to
install the LanPak after you have installed all the other modules. If you have reinstalled
BPI, or have installed a version upgrade, you want to reinstall LanPak afterwards.
To install the LanPak, get on a workstation, access MSDOS, change drives to the drive
where BPI is installed (the server's drive, that is, like F:). Then put the LanPak
diskette in drive A: and enter A:INSTALL
|
| WHICH ONES? Which networks does BPI run well on? Novell, Lantastic, and
Windows 95 or Windows 98 networks run right. BPI seems for some reason to crash at
inconvenient times when running on NT. As far as we know, the incompatibility with NT has
not been resolved.
|
| ONLY ONE. Only install the BPI programs on the server -- not on the
server and also on one or more workstations' local hard drive. Apparently, LanPak gets
confused if there are multiple copies of the program installed on the network.
|
| CHECK THE WORKSTATIONS. Make sure that the CONFIG.SYS files are set up
right on the workstations, with FILES set to 99 or higher and BUFFERS set to 30 or
higher.
|
| WIN 95/98 NETWORKS. If you are trying to run BPI on a Windows 95 or 98
network and you get errors referring to "station ID", you need to set the
network default protocol to NetBEUI. Do this through the properties feature of the Network
Neighborhood icon. Then reinstall LanPak, and the problem will go away.
|
| COORDINATE. When you have more than one person using BPI on the network
at the same time, make sure than everyone is out of BPI before you backup your BPI data,
run Reclaim Disk Space, or before you run the Update Company command in Easy History. |
|
