This file contains information about AXIS NetPilot including release notes (software version 2.62) ============= AXIS NetPilot software makes management of AXIS Network Print Servers simple and convenient. It runs on Windows platforms that use NetWare and/or NetBIOS/NetBEUI. AXIS NetPilot provides you with following facilities: * installation of new network print servers * modify their configuration * upgrade their software * monitor the printing taking place through the print servers Release Description ------------------- New features: ------------- 1. AXIS print servers with firmware release 6.00 now supported. 2. Support for the AXIS 5470e print server added. Log-Files --------- In the same directory as NetPilot.exe is installed into, there are two logfiles: 1. Upgrade.log (Remembers all upgrades.) Writes about the same info as appears in the upgrade window, so you can see which print servers that had success in upgrading or not. 2. NetPilot.log (Refreshed every time NetPilot is run.) Writes a line every time something unusual occurs. Info about source file, line and (potensially error) code. This information can be very usuful when talking to support. Information ----------- When upgrading a print server, you will only lose all settings if the new software contains new parameters (or new types of old ones). Hardware Requirements --------------------- AXIS NetPilot requires a PC with a 386 or higher processor and at least 4MB of RAM. Software Requirements --------------------- AXIS NetPilot can be used with Windows, Windows for Workgroups, Windows 95, Windows NT and WinOS/2. The network support requirements are: * Windows: NetWare client and/or LAN Server/LAN Manager Workstation Service * Windows for Workgroups: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * Windows 95: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * Windows NT: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * WinOS/2: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) (If NetPilot doesn't display default contexts and a queue volume in the installation wizard when NDS is chosen, the client is probably not configured correctly. Eg "Name Context" and "Preferred Tree" should have values. If NetWare installation (eg queue creation) fails, it often depends on that the user doesn’t have enough permissions (or that the user wasn’t logged in properly when NetPilot was started).) DLLs required ------------- During the installation of the AXIS NetPilot the following DLLs will be placed in the AXIS NetPilot directory: CALWIN16.DLL CLNWIN16.DLL CLXWIN16.DLL LOCWIN16.DLL NCPWIN16.DLL NETWIN16.DLL NWIPXSPX.DLL PRTWIN16.DLL and PCTREE16.DLL (The old NWCALLS.DLL, NWIPXSPX.DLL, NWLOCALE.DLL, NWNET.DLL, NWPSRV.DLL will be removed from the AXIS NetPilot directory if they exist there.) The following DLL will be placed in the Windows/System directory (only if it does not exist already): CTL3DV2.DLL To run AXIS NetPilot without a NetWare client (i.e. using the NetBIOS/NetBEUI protocol), the NetWare DLLs should be in the AXIS NetPilot directory. If you have a NetWare client, the NetWare DLLs can be moved to the Windows/System directory to share them with other applications. Software limitations -------------------- 1. Before uninstalling an Axis Network Print Server which has Remote Printer connections, the user should disconnect all Remote Printer connections using AXIS NetPilot. Otherwise, some information will not be removed from the NetWare File Server. 2. AXIS NetPilot can sometimes fail creating Print Server objects on a NetWare file server when running in Windows NT environment. Therefore the user should create the Print Server object using NWAdmin/PCONSOLE before AXIS NetPilot is used for creating connections. 3. Problems with NetWare Unicode tables. AXIS NetPilot fails to find the NetWare Unicode tables if they are not located in a directory in the local search path. Make sure your local search path includes the NLS sub-directory on SYS:PUBLIC or SYS:LOGIN. Note that a mapping to the *parent* directory is not enough, the path must include the NLS sub-directory. 4. Changing a Print Server's node address in NetPilot may cause problem for NetPilot finding the Print Server again. This is easily solved by restarting NetPilot. 5. To use NetWare Directory Services in NetPilot on Windows 95 with 'Microsoft Client for NetWare Networks with service for NDS', you must be logged in to the NDS tree (and in some cases also have the NetWare Administrator running). No such problems occurs when running Novell's NetWare Clients. 6. The white version of AXIS 560 print server "NPS 560" with software version 5.15 and the Specialix version of "NPS 530" with software version less than 5.21 are not supported by NetPilot, because they don't announce themselves properly. 7. After renaming the print server sometimes uploading the parameter list failed the second time due to faulty internal handling of the new print server name. A workaround is to make a refresh. 8. Running NetPilot on a PC with multiple network cards operating in the same segment in a NetBIOS environment can in some cases prevent NetPilot to find units on one network card. Microsofts knowledge base contains information indicating that this is known problem. 9. NetPilot will not correctly show queues connected via NDS printer objects that are created with other tools (the printer objects names not following NetPilots naming conventions). They will function (print) correctly though. 10. NetPilot (using IPX and NetBEUI) does not support NetWare clients, as Novell Client 5, that uses TCP/IP. AXIS Print Utility for Windows ============================== The AXIS Print Utility is a dual purpose application for network printing in a Windows 3.1 and Windows for Workgroups environment. The functions performed by the AXIS Print Utility are: 1. Install and maintain AXIS Print Server ports as Windows printer ports. 2. Capture and monitor print jobs directed to Print Servers. Requirements ------------ AXIS Print Utility can be used with Windows, Windows for Workgroups. The network support requirements are: * Windows : LAN Server/LAN Manager Workstation Service * Windows for Workgroups : Microsoft Network (NetBIOS/NetBEUI) Print Manager must be activated in both cases. Important --------- AXIS Print Utility must be running when you print through your Network Print Server. Software limitations -------------------- 1. General Protection violation could appear when there is little resources left (both RAM and GDI). More Information ================ If you need more information about AXIS NetPilot, AXIS Print Utility, AXIS Print Monitor or any of the AXIS Network Print Servers, please visit the AXIS WWW Home Page at http://www.axis.com/ . You will be able to download on-line manuals and the latest versions of the software utilities. -------------------------------------------------------------------------------------------- NEW SOFTWARE RELEASE Version 1.00 ==================== Product involved: - Specific software: AXIS NetPilot Release date: Release type: Production Software version: 2.62 Software checksum: - Last preceding release: 2.61 Upgrade instructions: - ---------------------------------------------------------------------- Easy Release Description: New features: ------------- 1. Added support for AXIS 1620 2. Added support for AXIS 1800. 3. Added Support for Intermec EasyLAN 100i Solved problems: ---------------- 1. Unable to set the communication protocol in the NetWare page. 2. Unable to Check DNS in the NetWare page. 3. In the NetWork environment property sheet, AppleTalk page, earlier the Binary type was shown grayed after deleting a printer. 4. NetPilot crashed while installing AXIS 1800. 5. NetWare trees won't show when installing Axis 1800 with NetPilot. 6. Character description of PrintServer Model described when on NetPilot firm is updated is wrong. 7. NetPilot hanged after the NetWare settings during the installation of AXIS 1620 8. In the NetPilot installation Wizard, there is no radio button of NDS Tree, so we can not do settings for NDS while installing AXIS 1620 9. Netpilot crashed while switching between FTP and General Pages when multiple PrintServer properties are selected Recommendation: - An update to this software is necessary, if you want any of the new/corrected features mentioned above. Best regards AXIS COMMUNICATIONS AB Further information is available on request: Appendix A : Detailed technical description of the release. Appendix B : Software limitations. Appendix C : Affected material ---------------------------------------------------------------------- Appendix A - DETAILED TECHNICAL DESCRIPTION OF RELEASE App A 1(1) Product involved: AXIS NetPilot Software version: 2.62 ---------------------------------------------------------------------- New features ------------ 1. Added support for AXIS 1620 2. Added support for AXIS 1800. 3. Added support for Intermec EasyLan 100i Solved problems --------------- 1. Unable to set the communication protocol in the NetWare page. This problem was due to the printserver restarting immediately after setting the protocol. Now the user can change the protocol from DualStack to IPX or IP to IPX or DualStack. 2. Unable to Check DNS in the NetWare page. This problem is solved in this release 3. In the NetWork environment property sheet, AppleTalk page, earlier the Binary type was shown grayed after deleting a printer. Now the user can select from the binay type as well while adding a new printer. 4. Earlier NetPilot crashed while installing AXIS 1800. This was due to NetPilot unable to recognize 1800. This is solved by adding the support for AXIS 1800 5. NetWare trees won't show when installing Axis 1800 with NetPilot. This is solved by adding the support for AXIS 1800 6. Character description of PrintServer Model described when on NetPilot firm is updated is wrong. This problem is solved now. This problem is due to NetPilot doesn't recognize AXIS 1620. This is solved by adding the support for AXIS 1620 7. NetPilot hanged after the NetWare settings during the installation of AXIS 1620 This is solved by adding the support for AXIS 1620 8. In the NetPilot installation Wizard, there is no radio button of NDS Tree, so we can not do settings for NDS while installing AXIS 1620 This is solved by adding the support for AXIS 1620 NetPilot can be used for Axis Print Server products with a software version greater than 5.00. 1. Hardware Requirements AXIS NetPilot requires a PC with a 386 or higher processor and at least 4MB memory. 2. Software Requirements AXIS NetPilot can be used with Windows, Windows for Workgroups, Windows 95, Windows NT and WinOS/2. The network support requirements are: * Windows: NetWare client and/or LAN Server/LAN Manager Workstation Service * Windows for Workgroups: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * Windows 95: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * Windows NT: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) * WinOS/2: NetWare client and/or Microsoft Network (NetBIOS/NetBEUI) 3. DLLs required During the installation of the AXIS NetPilot the following DLLs will be placed in the AXIS NetPilot directory: CALWIN16.DLL CLNWIN16.DLL CLXWIN16.DLL LOCWIN16.DLL NCPWIN16.DLL NETWIN16.DLL NWIPXSPX.DLL PRTWIN16.DLL and PCTREE16.DLL (The old NWCALLS.DLL, NWIPXSPX.DLL, NWLOCALE.DLL, NWNET.DLL, NWPSRV.DLL will be removed from the AXIS NetPilot directory if they exist there.) The following DLL will be placed in the Windows/System directory (only if it does not exist already): CTL3DV2.DLL To run AXIS NetPilot without a NetWare client (i.e. using the NetBIOS/NetBEUI protocol), the NetWare DLLs should be in the AXIS NetPilot directory. If you have a NetWare client, the NetWare DLLs can be moved to the Windows/System directory to share them with other applications. Appendix B - SOFTWARE LIMITATIONS App B 1(1) Product involved: AXIS NetPilot Software version: 2.62 ---------------------------------------------------------------------- 1. Before uninstalling an Axis Network Print Server which has Remote Printer connections, the user should disconnect all Remote Printer connections using AXIS NetPilot. Otherwise, some information will not be removed from the NetWare File Server. 2. AXIS NetPilot can sometimes fail creating Print Server objects on a NetWare file server when running in Windows NT environment. Therefore the user should create the Print Server object using NWAdmin/PCONSOLE before AXIS NetPilot is used for creating connections. 3. Problems with NetWare Unicode tables. AXIS NetPilot fails to find the NetWare Unicode tables if they are not located in a directory in the local search path. Make sure your local search path includes the NLS sub-directory on SYS:PUBLIC or SYS:LOGIN. Note that a mapping to the *parent* directory is not enough, the path must include the NLS sub-directory. 4. Changing a Print Server's node address in NetPilot may cause problem for NetPilot finding the Print Server again. This is easily solved by restarting NetPilot. 5. To use NetWare Directory Services in NetPilot on Windows 95 with 'Microsoft Client for NetWare Networks with service for NDS', you must be logged in to the NDS tree (and in some cases also have the NetWare Administrator running). No such problems occurs when running Novell's NetWare Clients. 6. The white version of AXIS 560 print server "NPS 560" with software version 5.15 and the Specialix version of "NPS 530" with software version less than 5.21 are not supported by NetPilot, because they don't announce themselves properly. 7. After renaming the print server sometimes uploading the parameter list failed the second time due to faulty internal handling of the new print server name. A workaround is to make a refresh. 8. Running NetPilot on a PC with multiple network cards operating in the same segment in a NetBIOS environment can in some cases prevent NetPilot to find units on one network card. Microsofts knowledge base contains information indicating that this is known problem. 9. NetPilot will not correctly show Queues connected via NDS Printer Objects that are created with other tools (the Printer Objects names not following NetPilots naming conventions). They will function (print) correctly though. Appendix C - AFFECTED MATERIAL App C 1(1) Draft texts for manual updates: - Other: - Product involved: - Software version: - ----------------------------------------------------------------------