Windows 95

Shortcuts must be set to connect to drive letter paths instead of the UNC naming terms. Network drives must be mapped with drive letters first.

Possible problems with index corruption due to timing and cache problem with older vredir.vxd files.  You should update Win95 machines with vredir.vxd version 4.00.1116.  If you are using a NT4.0 Server, you should make sure that Opportunistic Locking is disabled.  This locking has been found to corrupt a database index.  Problems are resolved using Windows98 OSR2.

Printers no longer need to be captured. Printer ports can be captured to LPT ports 1-9. If you are using an NT Server, Windows2000 Server, or Workstation version, you can set them up as a print server and map all your printers to through that machine.

Printers may use Windows UNC names.  For example:  (\\servername\printername) You will not be able to print to your local printer using the UNC shared printer name.  To print to your local printer using the  UNC name, you must first map and share the local printer on an Windows NT/2000 machine.  Then set up the printer in SNAP-2-IT to send the print job to the shared UNC name on the NT/2000 machine.  The print job then gets redirected back to your local printer.

Windows only and USB printers must use the "snapwp" SnapWinPrint Utility.  This utility can also be used to fax through any Windows Fax/Print Utility like WinFax.

Windows NT3.51, NT4.0, Windows2000 Servers & Unix Servers

Shortcuts must be set to connect to drive letter paths, instead of the UNC naming terms. Network drives must be mapped with drive letters first.

Opportunistic Locking should be turned off when using Windows95 workstations.  Caching issues can corrupt a database index file.  Windows95 workstations should be updated with vredir.vxd version 4.00.1116.  We recommend minimum Windows98 OSR2 workstations.

Printers may use Windows UNC names.  For example:  (\\servername\printername) You will not be able to print to your local printer using the UNC shared printer name.  To print to your local printer using the  UNC name, you must first map and share the local printer on an Windows NT/2000 machine.  Then set up the printer in SNAP-2-IT to send the print job to the shared UNC name on the NT/2000 machine.  The print job then gets redirected back to your local printer.

Windows only and USB printers must use the "snapwp" SnapWinPrint Utility.  This utility can also be used to fax through any Windows Fax/Print Utility like WinFax.

Novell 3.12, 4.11, & Above

Some versions of the Windows95 32bit Novell Client uses Opportunistic Locking.  This Locking feature must be turned off. Contact Novell for the latest 32bit Client version that has disabled this feature.  Opportunistic Locking can cause database index damage.

Printers may use Windows UNC names.  For example:  (\\servername\printername) You will not be able to print to your local printer using the UNC shared printer name.  To print to your local printer using the  UNC name, you must first map and share the local printer on an Windows NT/2000 machine.  Then set up the printer in SNAP-2-IT to send the print job to the shared UNC name on the NT/2000 machine.  The print job then gets redirected back to your local printer.

Windows only and USB printers must use the "snapwp" SnapWinPrint Utility.  This utility can also be used to fax through any Windows Fax/Print Utility like WinFax.

If you need to capture above LPT3 you will need to go into the network properties for the Novell Client and increase the number of LPT ports that can be captured. This must be done on each client.  The default is set to three.

Lantastic

Lantastic 6.0 or older

Must load DOS "share.exe" in the AUTOEXEC.BAT file before Lantastic loads. You may use Lantastic's internal file sharing if you download the current patches for the "server.exe" and "redir.exe" from Artisoft.

Lantastic 7.0

No reported problems using Lantastic's internal share.

SNAP-2-IT needs to be installed on the file server drive only. The "files=" statement in the config.sys file must set to at least 30 for each workstation, "Files=30". The file server should be able to open at least 20 files per workstation. For example, if there are 5 workstations, the file server should be set to be able to open 100 files (20x5) plus whatever the file server needs.

Network notes:

The program SNAP-2-IT needs to be installed on the file server drive only.  The default folder/directory that the software installs to is "\snap".  Workstations simply need to create a shortcut to the "snap.exe" program.  There is a "snap.ico" icon located in the "snap" directory/folder.  The "Suspend in background" option in the "miscellaneous" tab of the shortcut properties must be unchecked.

Program updates and rebuilding index lists will run much faster when you run them from the file server for Lantastic, WFWG, Windows95/98, and Windows NT. Novell server updates must always be done from a workstation.

Remote access to SNAP-2-IT can be done with a modem and PcAnywhere. Wide Area Network connectivity through DSL/Cable TCP/IP access can be done with Microsoft NT4.0 Terminal Server and Citrix Metaframe or Windows2000 Server Terminal Services.