1(1) NEW SOFTWARE RELEASE Version 0.01 ==================== Product involved: - Specific software: AXIS NetPilot Release date: 96 10 22 Release type: Production Software version: 1.40 Software media: Diskette 3.5" (HD) Software checksum: - Last preceding release: 1.30 Upgrade instructions: - ---------------------------------------------------------------------- Easy Release Description: 1. Support for NDS Unicode strings where NDS object names are displayed today. Japanese characters are displayed correctly. Where input of NDS object names can be made, input of Japanese characters are allowed and correctly set in NDS, eg queue names. 2. In NetWare added support for login to either a NDS Tree or File Server. This can be done in the Network NetWare page and in the Installation Wizard. The new feature will only be applicable for Print Servers supporting the new functionality of login to the NDS Tree. 3. Shows and allows complete configuration of different brandnames of Axis print servers. 4. Support for the AXIS 570/670 MIO print server. 5. Support for OEM internal cards. 6. The DHCP parameter is added in the TCP/IP property page and in the Installation Wizard. 7. The suggested printer names on the AXIS Installation Wizard's Windows and OS/2 page are changed to '8.3' DOS format (LP1, LP2, CM1). 8. In NetWare. Changed naming of printer related objects on the File Server. 9. Where it is possible to select a File Server they are listed in alphabetic order. 10. Changed text in Installation Wizard, the Network Environments page. 11. The first available NetWare printer object is used when connecting a print queue in PSERVER mode. 12. Problems finding print servers with software version older than 5.20 using the NetBIOS protocol is solved. 13. The problem with finding AXIS 650 is solved. 14. In version 1.30 the TCP/IP property page for AXIS 670 was not shown. This is now solved. 15. In version 1.30 when a print server was uninstalled, monitored printers were not deleted automatically. This is also solved now. Recommendation: - An update to this software is not necessary, unless you want any of the new/corrected features mentioned above. Best regards AXIS COMMUNICATIONS AB Appendix A : Detailed technical description of the release. Appendix B : Software limitations. ---------------------------------------------------------------------- Appendix A - DETAILED TECHNICAL DESCRIPTION OF RELEASE App A 1(1) Product involved: AXIS NetPilot Software version: 1.40 ---------------------------------------------------------------------- 1. Support for NDS Unicode strings where NDS object names are displayed today. This means that Japanese characters are displayed correctly, eg NDS contexts and printqueues. Where input of NDS object names can be made, input of Japanese double byte characters are allowed and correctly set in NDS, eg queuenames. (Double byte implementation means that if the character is not US ASCII, the second byte with data is handled.) 2. Support for new functionality of the PSERVER_NDS parameter. This feature is not yet implemented in the print server, but will be in a near future. It allows either login to a NDS Tree or a File Server. This is done in the Network NetWare page and in the Installation Wizard. The new feature will only be applicable for Print Servers supporting the new functionality. NetPilot will receive information from each Print Server in the VERSION_INFO packet that determines if this new functionality is supported. (Solves support case #56.) 3. Shows and allows complete installation/configuration of all print servers which are BRANDNAME variants of Axis models. (Same functionality supported as for the Axis Print Servers.) All BRANDNAME variants, except print servers with the Axis brandname, are displayed with a common icon. When a flash file is located in the upgrade directory it is displayed. If selected in the Upgrade Wizard information is available about which Print Server models, including BRANDNAME variants, it can be used for. 4. Support for the AXIS 570/670 internal cards fitting into printers with a MIO slot. Shows and allows complete installation/configuration of the AXIS 570/670 MIO. 5. Support for OEM products. Shows and allows complete installation/ configuration of following products: - Intermedium 'IMA PS ET-01' and 'IMA PS TR-01' internal cards - Keun Young 'IPS 960' internal card - Apti 'Print Server' internal card All OEM products will be displayed with a common icon. 6. The DHCP (Dynamic Host Configuration Protocol) parameter is added in the TCP/IP property page and in the Installation Wizard. The parameter is only visible if the print server supports DHCP. In addition, BOOT and RARP are added in the Wizard. The default settings of BOOTP and RARP are the same as in older versions of NetPilot. 7. The suggested printer names on the AXIS Installation Wizard's Windows and OS/2 page are changed to '8.3' DOS format (LP1, LP2, CM1). (Solves support case #290.) 8. In older versions, NetPilot uses 'AXISnnnnnn_PR_port' when creating NetWare printer objects in PSERVER mode. This is now changed to 'PSNAME_port' (where PSNAME is the print server's name and port is e.g. LPT1). For NetWare print queues, '_Q' are used as an extension at the end of the default print queue names when running the Installation Wizard. 9. Where it is possible to select a File Server they are listed in alphabetic order. 10. Changed text in Installation Wizard, the Network Environments page. Now it should be clearer that the unselected protocols are not disabled. (That can however be done after the installation under Properties.) (Solves "support case Xerox".) 11. The first available NetWare printer object is used when connecting a print queue in PSERVER mode, instead of a printer object specifically created by NetPilot as it was done before. (Solves support case #272.) 12. Problems finding print servers with software version older than 5.20 using the NetBIOS protocol is solved. When running IPX and/or NetBIOS this has never been a problem. (Solves support case #792.) 13. The problem with finding AXIS 650 is solved. (Solves support case #741.) 14. In version 1.30 the TCP/IP property page for AXIS 670 was not shown. This is now solved. (Solves support case #757.) 15. In version 1.30 when a print server was uninstalled, monitored printers were not deleted automatically. This is also solved now. (Solves "support case Xerox".) 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: NWCALLS.DLL NWIPXSPX.DLL NWLOCALE.DLL NWNET.DLL NWPSRV.DLL PCTREE16.DLL (new, handle DBCS) and 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: 1.40 ---------------------------------------------------------------------- 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 running in a WinOS/2 or Windows NT environment does not support NetWare Directory Services mode because of improper functionality in the NDS DLLs. 3. AXIS NetPilot can not create Print Server objects on a NetWare file server when running in Windows NT environment. Therefore the user should create the Print Server object using PCONSOLE before AXIS NetPilot is used for creating connections. 4. 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 subdirectory on SYS:PUBLIC or SYS:LOGIN. Note that a mapping to the *parent* directory is not enough, the path must include the NLS subdirectory. 5. 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. 6. 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 NetWare Client 32. 7. 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.