Chip 2004 April

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2004 April / CMCD0404.ISO / Software / Demo / PCDUO / README.TXT < prev next >

Wrap

Text File | 2003-10-01 | 48.6 KB | 1,164 lines

PC-Duo Version 8.10 =================== Release Notes ============= Copyright (c) 2003 Vector Networks and NetSupport Limited. All Rights Reserved. Author : D. Briggs. Revision Date : 1st October 2003 This document contains the PC-Duo PC-PC Remote Control package release notes for Version 8.10. This software is supplied under a licence and may only be used or copied in accordance with the terms of that licence. This software or copies thereof must not be made available to unauthorised personnel. No title to this software nor ownership of this software is hereby transferred. Evaluation copies are supplied for the purpose of evaluation only and must not be resold or passed to any third party without the express permission of Vector Networks Limited. Please note that the licence files (NSM.LIC) for versions of PC-Duo earlier than v8.00 will not work with this release. Please contact your supplier for a new authorisation key where necessary. Please ensure that you have adequate PC backup before you install PC-Duo. You should have an up-to-date Emergency Repair Disk on Windows NT. You can easily make a new one by running RDISK.EXE from Start, Run, or File Manager File Menu, Run. Use the /s command line option so that RDISK backs up the system's security information as well as the main Registry contents. Contents ======== 1 Package Enhancements over the Previous Release 1.1 Screen Capture 1.2 Annotate Screen 1.3 System Snapshot Update 1.4 New settings for DVD Playback and Direct 3D 1.5 Logoff on Disconnect 1.6 Gateway - DNS Name Support 1.7 Gateway - Configurable Polling Interval 1.8 Clients and Groups Display Improved 1.9 DBCS Improvements 1.10 Scripting - Buffer Handling 2 Problems Corrected in this Release 2.1 Multi-monitor Window Dragging 2.2 Clipboard Data could be Lost 2.3 Client reconnects to Gateway 2.4 Print Capture on Windows 2000 Novell Clients 2.5 DBCS Character Set File Transfer 2.6 Execute at Client when Logged Off 2.7 Gateway Key Length is now 15 Characters 2.8 Scripting - Dim as Integer 2.9 Scripting - Do Until 2.10 Scripting - Do While memory allocation 2.11 Scripting - EOF Function 2.12 Scripting - RegCloseKey 3 Known Problems in this Release 3.1 Compatibility with Earlier Versions 3.2 Interaction with Other Remote Control Products 3.3 Windows 2000 and XP Limitations 3.4 Interaction with VMware Guest Operating Systems 3.5 Logoff on Disconnect on Windows 9x 4 Windows NT Support 4.1 Windows Control 4.2 Windows NT Client 4.3 Dealing with Blue Screens on Windows NT 4.4 Locked Desktop treated as Logged Off 5 Windows 9X and ME Support 5.1 Dealing with Fatal Exception Errors 6 Serialisation Options 6.1 Automatic Licensing 6.2 Kit Expiry Date 7 IPX Networks 8 TCP/IP Support 8.1 TCP/IP Windows Sockets 8.2 Connect by Hostname 9 Installation Notes 9.1 Client Installation Notes 9.2 Administrator Privilege Required 9.3 Windows on Windows Support 9.4 Creating a Silent Installation 9.5 Silent Installation Response File Format 9.6 Silent Installation Log File Format 9.7 Silent Installation Errors 9.8 Installing the Gateway 9.9 Installing Client, Control, and Gateway Configuration Files 10 Uninstallation Notes 10.1 Tidying up 11 Diagnostic Utilities 12 Automated Installation with PC-Duo Enterprise 13 Online Documentation 13.1 PC-Duo Resource Kit 14 Vector WWW Site 1 Package Enhancements over the Previous Release ================================================== For full details of product enhancements, please check the PC-Duo Online Help, Introduction, New Features topic. The following enhancements have been made since v8.00 was released:- 1.1 Screen Capture ------------------ It is now possible to capture the contents of the Control's View and Scan windows to a file. New Capture buttons are available on the Control's View Window and Scan Window Toolbars, and Capture Screen commands have been added to the View Window, Tools Menu, and the Scan Window, Client Menu. The screen can be saved in Bitmap (.BMP), JPEG (.JPG), or Portable Network Graphic (.PNG) formats. 1.2 Annotate Screen ------------------- The Annotate Screen tool has been available in previous versions for annotating the Control's screen during a Show. This tool can now be used in the View Window when remote controlling. It is also available at the Client, where it can be started from its shortcut in the PC-Duo program folder. 1.3 System Snapshot Update -------------------------- System Snapshot has been updated to PC-Duo Enterprise v2.01. The enhanced inventory collection uses the Desktop Management Interface (DMI). This can provide accurate information on a variety of device types, including PCI, SCSI, ISA, IDE, PCMCIA, USB, FireWire, and Infra-Red. Additional information on the Client PC Manufacturer, its model and serial number are also available. 1.4 New settings for DVD Playback and Direct 3D ----------------------------------------------- The Advanced Mode Client Configurator, Remote Control, View page now has additional controls over the loading and unloading of the Mirror Driver. This driver is used to intercept the Client's display output on Windows 2000, XP and 2003 operating systems, but it can interfere with the use of DVD players and software using Direct 3D. The new controls allow the Mirror Driver to be loaded when the Client is being viewed or is connected to a Control, respectively. It is unloaded at other times, so the Client user can work normally. 1.5 Logoff on Disconnect ------------------------ The Advanced Mode Client Configurator, Security, Disconnect dialog has been changed to allow Windows 95..ME Clients to be logged off or rebooted when a Control disconnects. Previously, these functions were restricted to logging off on Windows NT or rebooting on Windows 9x. Note that Windows 9x Clients cannot distinguish between logged on and logged off states, so they will always logoff or reboot on disconnect if one of these checkboxes is selected. 1.6 Gateway - DNS Name Support ------------------------------ Clients and Controls can now find a Gateway using a domain name, such as gateway.vector-networks.com, as well as a fixed IP address. The Control's Add a Gateway Wizard and Gateway Properties dialog and both Basic and Advanced mode Client Configurators' Connectivity, HTTP dialog allow either a name or an IP address to be entered. 1.7 Gateway - Configurable Polling Interval ------------------------------------------- The Gateway Configurator includes a new Communications Management Packet Interval (CMPI) setting that controls how often the Gateway and Client check each other's status. The default interval is 60 seconds. 1.8 Clients and Groups Display Improved --------------------------------------- The Control's Clients and Groups folder displays would flicker when there was a large number of Known Clients. This has been improved. 1.9 DBCS Improvements --------------------- The Advanced Mode Client Configurator, Client Interface, Customisable Text page can now be used to display DBCS text when a Control is connecting or viewing a Client. Previously, only ANSI characters could be used. Also, the Control will now display correctly Client and machine names that contain DBCS characters, provided that the appropriate character set is available. 1.10 Scripting - Buffer Handling -------------------------------- The algorithm used to allocate buffers for variables has been improved. String variables can now be longer than 255 characters. 2 Problems Corrected in this Release ====================================== The following bugs have been fixed since v8.00 was released:- 2.1 Multi-monitor Window Dragging --------------------------------- There was a problem with viewing a Client that had multiple monitors when the main monitor was on the right instead of on the left. The Control's View Window could be corrupted when a windows was dragged on the Client. This has been corrected. 2.2 Clipboard Data could be Lost -------------------------------- If a single Control viewed more than one Client at a time, the Client could lose clipboard data if the Control switched between view windows. This has been corrected. 2.3 Client reconnects to Gateway -------------------------------- If a Client lost its connection to the Gateway when the Gateway was restarted, the Client would not try to reconnect until it was also restarted. 2.4 Print Capture on Windows 2000 Novell Clients ------------------------------------------------ When using the Novell Client on Windows 2000 or XP, starting the PC-Duo Client32 Service no longer results in an error message being recorded in the System Event Log. The message was from the Service Control Manager, with ID 7023: The spooler service was shut down: Access code is invalid. 2.5 DBCS Character Set File Transfer ------------------------------------ A problem that affected transfer of files or directories whose names contained DBCS characters has been corrected. 2.6 Execute at Client when Logged Off ------------------------------------- It is now possible to use the Execute at Client function when the Client is logged off. Previously, this function was enabled only when the Client was logged on. Also, the Control checks the execute program path, and if this contains one of "program files", "winnt", or "system32", the equivalent path at the Client is substituted. 2.7 Gateway Key Length is now 15 Characters ------------------------------------------- Previously, some of the dialog edit fields that are used to enter a Gateway Key would allow an over-long string to be entered. The Gateway Key length is now consistent with a maximum of 15 characters. 2.8 Scripting - Dim as Integer ------------------------------ In previous versions, using Dim to declare an unrecognised type such as Boolean resulted in a variable without a valid data type. This will now generate a syntax error. The same problem affected variables declared as Integer, causing run-time errors on arithmetic expressions. These could be eliminated by setting the data type implicitly using an assignment such as x = 1 Now, Dim x as Integer will set the data type of x correctly. The workaround above should no longer be required, although it will still work. 2.9 Scripting - Do Until ------------------------ The implementation of Do Until has been corrected. Previously, Do Until loops would not be executed correctly. 2.10 Scripting - Do While memory allocation ------------------------------------------- There was a problem with memory allocation in the Do While function that could cause RUNSCRIP.EXE and the Script Editor to crash with an access violation. This has been fixed. 2.11 Scripting - EOF Function ----------------------------- There was a synchronisation problem between reading a file using ReadLine and the setting of End of File, as detected by the EOF function. This has been corrected. 2.12 Scripting - RegCloseKey ---------------------------- In previous versions, the RegCloseKey function was not available from the Script Editor's command viewer. If it was not added by hand, the use of RegCreateKey or RegOpenKey in a running Script would result in a handle leak. 3 Known Problems in this Release ================================== If you encounter a problem, please check the notes here before reporting it to your support contact. 3.1 Compatibility with Earlier Versions --------------------------------------- The 32-bit Control will interwork with v3.72 or later Clients. However, new features such as working with the Gateway will not be available unless both Controls and Clients are v8.0 or later versions. We recommend that you do not use the v8 Control with Clients of versions earlier than v3.72. 3.2 Interaction with Other Remote Control Products -------------------------------------------------- As a general rule, it is not advisable to install more than one remote control product onto any PC. The drivers used by the Clients may interact in such a way as to render the entire system unstable. Contact your Vector supplier for assistance if you want to use more than one remote control product on a single Client system. 3.3 Windows 2000 and XP Limitations ----------------------------------- Support for Windows 2000 and XP is not as complete as some other platforms. However it is functional. Please note the following restrictions:- - Fast User Switching is a facility in Windows XP that permits a user to be disconnected temporarily while another user logs in to the system console. In common with many remote control products, PC-Duo is not compatible with this feature and disables it when it is installed. - The mirror driver does not have a Microsoft digital signature. When the Client is installed, the Control Panel, Add New Hardware wizard displays a dialog which states that the GDIHOOK5 driver does not have a signature and asks the user whether they want to continue. This dialog is closed by Setup but it is briefly visible on-screen. - When a Control is viewing a Windows 2000 Client, screen effects such as menu fade and the mouse cursor drop-shadow are disabled. This improves remote control performance. Please contact Vector if you encounter problems with Windows XP. 3.4 Interaction with VMware Guest Operating Systems --------------------------------------------------- There is a problem in the VMware Workstation v3.x SuperVGA driver that causes Guest display corruption when the PC-Duo Client is installed in a Windows NT Guest virtual machine that is running on an NT Host system. There is a workaround for this. Shut down the Guest system and close the VMware Workstation. Then use a text editor to open the Guest system's configuration file (normally called WinNT.vmx). Add the following line:- svga.noRectCopy = TRUE You can then restart VMware Workstation and the Windows NT Guest. 3.5 Logoff on Disconnect on Windows 9x -------------------------------------- Windows 9x Clients cannot distinguish between logged on and logged off states, so they will always logoff or reboot when a Control disconnects if either logoff on disconnect or reboot on disconnect checkboxes is selected in the Advanced Mode Client Configurator, Security, Disconnect dialog. 4 Windows NT Support ====================== This 32-bit kit can install the Client, Control, Gateway, Remote Comms, Online Documentation, Scripting, and System Snapshot modules on Windows NT v4.0 on Intel platforms. Support for Windows NT v4.0 on Alpha processors is no longer available. 4.1 Windows Control ------------------- The 32-bit Windows Control can be used on Windows NT. Please note the following restriction:- - Animated cursors, such as those provided with Windows 95 Plus!, are displayed in monochrome (black and white) instead of colour. 4.2 Windows NT Client --------------------- The 32-bit remote control Client runs as a "Service" on Windows NT. This allows it to start before a user has logged on to NT. A Control user can therefore connect to the NT Client while it is logged off. The Logon dialog box is activated by typing CTRL+ALT+ESC on the Control (not CTRL+ALT+DEL), or using the Client Menu, Send Ctrl+Alt+Delete command. The NT Client reports significant events such as starting and stopping, and any errors, through the NT Event Log. This can be examined using the "Event Viewer" in the "Administrative Tools" group. Look for entries in the System Log referring to "PCIsys". Client usage can also be logged to the NT Application Log or to a log file. Activate this by running the Client Configurator in Advanced Mode. Double- click on "Master Profile" to edit the common settings. Change to the "Security" tab and select the "Enable Logging" check box. Select "Log to NT Event Log" or the "Log to File" radio buttons, as required. The Client logs which Controls connected and when, and any file transfers. Use the NT Event Viewer to look for "PCIapp" entries in the Application Log. The Client Configurator can be used to direct the log file to a server. Use Advanced Mode, switch to the Security tab, enable logging to a file and use the [Browse] button to find the location in the Network Neighborhood. If a username is required to access the server share, it can be entered in the "As User" field. If the account requires a password, press [Set] and enter the username and password. The NT Client can log off or lock the workstation instead of rebooting when a Control disconnects. This avoids data corruption that could otherwise occur if NT is not shut down properly. The check boxes for these options are on the same "Security" tab as the Event Log settings above. If you need to reboot an NT Client by remote control, use the Shutdown option on the Start Menu (NT4), or Program Manager File Menu (NT3), to perform an orderly shutdown and restart. Please note the following restrictions:- - The Client's desktop colour may not be displayed correctly on a viewing Control. - The default behaviour is for a viewing Control to disable the wallpaper and any desktop pattern on the Client. This improves performance, but can be disconcerting for the user. This behaviour can be controlled from the View tab of the Control's View, View Menu, Settings for Client option, or the main View Menu, Settings for Current Configuration option. - It is not currently possible to see an NT Client which is running a full-screen Command Prompt (CMD.EXE) window although typing works. You can toggle back to windowed mode using ALT+ENTER, and view that as usual. Full-screen DOS Boxes (COMMAND.COM) are supported on Intel CPUs only. 4.3 Dealing with Blue Screens on Windows NT ------------------------------------------- When Windows NT encounters a fatal system error, it displays a blue screen and halts. The screen shows the reason for the stoppage, the address of the fault, the module that contains this address, the modules that were loaded in memory, and a stack dump. Windows NT can also be set to dump system memory to a file for later analysis. All of these items can be useful in analysing the problem. If you suspect that the problem is related to PC-Duo, please write down the STOP code, numbers, and addresses from the top of the screen, and the stack dump from the bottom of the screen. Make a note of the load addresses of any modules that are mentioned in the stack dump. These are listed in the middle of the screen. You should always note the module load addresses for the following PC-Duo components if they appear in the list:- CLHOOK4.DLL CLIENT32.EXE GDIHOOK4.DLL (GDIHOOK5.DLL on Windows 2000) PCICL32.DLL PCIHOOKS.DLL PCISYS.SYS This information should be recorded so that it can be sent to your Vector Networks supplier. The system dump file is normally too big to be useful unless you know how to analyse it. Restart Windows NT at this point. If it will not start, try to start in VGA Mode. This mode will not load the GDI display intercept drivers and this will produce an error when the Service Manager tries to start the Client32 Service. The NT Client is able to capture details of faults that occur in the display sub-system. These are logged in file PCIMSG.ERR, which is saved in the WINNT\SYSTEM32 directory. You will have to restart Windows NT before you can check whether or not this file exists. If it does, please send it with the other items. 4.4 Locked Desktop treated as Logged Off ---------------------------------------- If you use the "Lock Workstation on Disconnect" option, the NT Client will lock when the Control disconnects, provided it was logged off or locked when the Control connected. The locked state is treated as if the Client is logged off. This is controlled by a setting in the Client Configuration file CLIENT32.INI. The default setting is:- [Client] CheckDefaultDesktop=1 If this setting is not present, or the value is 0, the Client will treat the locked workstation as logged on. Depending on the Client Configuration, this can interfere with a Control's ability to connect to the PC. This will invalidate the file's checksum. To correct this, it is necessary to use the Client Configurator, in Advanced Mode, to open and then save the file. If the Configurator has not been installed on the Client PC (see Section 9.8 below), you can open the file using a Configurator installed on a separate Control PC. It is necessary to restart the Client32 Service to apply this change. This can be done using the Restart Client shortcut or RESTART.BAT. 5 Windows 9X and ME Support ============================= This 32-bit kit can install the Control, Client, Remote Comms, Online Documentation, and Scripting modules on Windows 95, Windows 98, and Windows Millennium Edition (ME). They should all operate correctly. From v7.0, the PC-Duo Client can be started without a reboot when it is installed on Windows 98 or ME. There is no longer a "Reset Video Driver" shortcut on these platforms. The Client is started from the Registry, using key:- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices Look for string value "PC-Duo Client". On Windows 95, performance and functionality are improved if the Microsoft "Winsock2" update is installed. Please note the following restrictions:- - Dynamic screen resolution changing on a Windows 95 Client is disabled unless the GDI display intercept driver has been loaded through the Registry. Setup does not do this, but the "Reset Video Driver" program will offer you a choice between loading the driver through the SYSTEM.INI, [boot] section, display.drv= line (the default) or the Registry. If you want to use dynamic screen resolution changing, for example using the STB Vision program, we recommend that you test it carefully. It does not work with ATI MACH 64 or Miro cards. - If you experience problems after installing PC-Duo or when viewing a Windows 95 Client, check the display acceleration setting. The method used is described in Section 5.1 part 4, below. If you find that the mouse cursor disappears, reduce the acceleration from "Full". If the Control sees a blank screen when viewing the Client, increase the acceleration setting from "None". If the Control's display is incomplete, try a setting other than "Full". - Animated cursors, such as those provided with Windows 95 Plus!, are displayed in monochrome (black and white) instead of colour. You may find that a black cursor becomes invisible on a black background. - Show over DECnet to four or more Clients may cause the Clients to disconnect. This can be corrected by increasing the PATHWORKS datalink buffers. To do this, right-click on "Network Neighborhood" (or press [Start], Settings, Control Panel, and double-click on "Network"). Highlight PATHWORKS NDIS Support, press [Properties], and then select the "Advanced" tab. Highlight "Buffers" in the property list, and then increase the "Value" from 20 to 40. - There is a fault in the Windows 95 NE1000 and NE2000 Enhanced mode NDIS drivers which makes connecting to Clients difficult, screen updates slow, and it may also make them disconnect. This fault can be eliminated by re-configuring to use either the Real-mode 16-bit NDIS or ODI driver. - A Bridge running on the PATHWORKS for Windows 95 (v1.0 and v1.0A) DECnet NetBIOS transport cannot make a connection to a Client running on the same PC. This is due to a bug in the PATHWORKS DECnet which incorrectly reports a "No Listen Outstanding" error. 5.1 Dealing with Fatal Exception Errors --------------------------------------- If you experience Fatal Exception Errors when starting Windows 95, the following steps should help you to eliminate the problem:- 1 - Start Windows in "Safe Mode". To do this, press the [F8] key while the "Starting Windows 9x..." message is visible after a reboot. Select "Start in Safe Mode" from the menu. This will allow you to use Windows tools to check or change the configuration. 2 - Check the PC-Duo Help, "Technical Reference", "Troubleshooting", and "Error Messages" sections for guidance on particular error messages and problems. 3 - Windows Setup may not have identified your display correctly, so you need to make sure that you are using the correct driver for your display adapter. To examine or change the display driver, right-click on the wallpaper and select "Properties" from the pop-up menu (or press [Start], Settings, Control Panel, and double-click on the "Display" icon), select the "Settings" page, and press [Change Display Type]. The current display driver and files are listed at the top, under "Adapter Type". Make a note of the driver name, version, and the files. If the driver is generic, (like "S3"), then you may find that Windows has a specific driver for your display (such as "S3 Trio32/64 PCI"). Press the [Change] button, and Windows will display a "Select Device" list. Select the "Show all devices" radio-button (at the bottom), and look to see if there is a specific driver listed for your particular display adapter. If so, (and you aren't already using it), highlight it and press [OK]. Windows will need to restart for this change to take effect, but if you have installed a PC-Duo Client already, you should run the "Reset Video Driver" icon from the PC-Duo folder first, or the PC-Duo Client will not be loaded after the restart. 4 - We have found that problems with some displays can be eliminated by reducing the level of acceleration used by Windows. To examine or change this, press [Start], Settings, Control Panel, double-click on the "System" icon, and select the "Performance" page. Press the [Graphics] button at the bottom. Change the Acceleration setting to "None" and press [OK] to apply the change. Restart Windows for this change to take effect. 5 - You can run the "Reset Video Driver" icon from the PC-Duo folder to transfer the PC-Duo intercept driver load command from SYSTEM.INI to the Registry. This generally improves compatibility with display drivers, but is known to cause a problem with Miro displays. 6 - If none of these steps help, you should contact your Vector Networks Supplier. Please provide them with a description of the problem, and details such as the display adapter and driver as requested. 6 Serialisation Options ========================= The licensing mechanism changed from that used in versions prior to v4.10. The new licensing mechanism uses file NSM.LIC (instead of CLIENT.SER). The "Apply a Key" shortcut is used to apply a key for v4.x to v8.x. This is a native Windows program. Note however, that keys are version-specific, so keys generated for version 6.x cannot be used with v7.x software and so on. Contact your supplier if you need a new key for v8.x. Maintained customers can obtain these at no charge. 6.1 Automatic Licensing ----------------------- The licence file shipped with this kit will be converted to give a 30-day evaluation on install. If you have already created a valid licence file using the "Apply a Key" program, copy file NSM.LIC into the same directory as SETUP.EXE, and Setup will use it for all future installations. You may want to save a backup copy of the original evaluation licence file before you do this. Setup can also apply a new licence key to an existing installation. Copy NSM.LIC into the same directory as SETUP.EXE, as before. When you run SETUP.EXE, deselect all installation options (Client programs, etc.), and press [Next>] to continue. Setup will not install any new software, but it will copy the new licence key file. 6.2 Kit Expiry Date ------------------- This kit has an ultimate expiry date of 31-Mar-2004. It can be installed after that date, but will not operate until re-keyed. Contact your supplier for assistance. 7 IPX Networks ================ When PC-Duo Clients or Controls start up on an IPX network, they try to establish which IPX networks are accessible. This allows the Client to make sure that it has a unique name on the network, and it also allows the Control to find Clients attached to remote networks. The Control will report problems to the user if any of the "known" networks cannot be reached, but the long timeout can cause a substantial delay for the Client. The IPX networks that are used can be controlled through the Client and Control profiles. Use the Client Configurator to edit the Client's Master Profile, or the Control Tools Menu, Configurations, Transport and Startup settings for the Control. Select the Transport tab, and enter the networks to be used or ignored as appropriate, or use the [Test] button to do this interactively. 8 TCP/IP Support ================== PC-Duo works reliably over most TCP/IP Windows Sockets network transports. Notes on specific versions follow. 8.1 TCP/IP Windows Sockets -------------------------- On Windows 95 and 98, Windows Sockets transports are loaded by Windows searching the working directory, WINDOWS, and WINDOWS\SYSTEM directories, and then the DOS PATH, for a file called WSOCK2.DLL. If the wrong one is found and used, it may crash Windows. The Windows NT WSOCK32.DLL is normally in the WINNT\SYSTEM32 directory. Windows Show over TCP/IP Windows Sockets cannot display a full-screen DOS box. The DOS box interferes with Windows' timing. Use windowed mode DOS boxes instead. 8.2 Connect by Hostname ----------------------- On TCP/IP networks where the Clients are allocated IP addresses by a DHCP server, the PC-Duo Control can be configured to connect to Clients using their Hostname instead of their Client Name and IP address. At present, the Control does not use the Client's Client Name as a default Hostname. If the Clients are on the local network or are "seen" when the Control browses the network, they will provide their hostnames in their replies to the Control. To store them, select all Clients that appear in the Browse folder, right-click, and select "Add to Client List" from the popup menu. For other Clients, such as those on remote subnets, the Hostname must be provided in another way. For small numbers of Clients, this can be done using the Client Menu, Quick Connect dialog to connect, specifying the network Transport as TCP/IP and entering the Client's Hostname in the Address field. Alternatively, you can edit a Known Client's Properties and copy the Client Name into the Address field. For large numbers of Clients, a Sample Script, HOSTNAME.SCP, can be used to automate the procedure. This can be run using the Script Editor or RUNSCRIP.EXE. It checks all of the Known Clients by reading through the CLIENT.NSM file. Any TCP/IP Clients that do not already have a Hostname are given one, using the syntax shown below:- client_name|>ip_address (client_name)|... For example:- DB-V2K|>90.0.0.127:5405 (DB-V2K)|2|0|Local||||| Once a Client has a Hostname, the Control ignores any IP address that may be stored in CLIENT.NSM. Instead, it uses a Domain Name Server (DNS) or Windows Internet Name Server (WINS) to resolve the Hostname into an IP address. Contact Vector Networks for further assistance with TCP/IP configuration. 9 Installation Notes ====================== This installation kit will function correctly on 32-bit platforms such as Windows 95, 98, Millennium Edition, Windows NT, 2000, XP, and .NET running on Intel processors. It does not support Windows NT on Alpha processors or Windows 3.1, Windows for Workgroups v3.11, OS/2, or DOS. We can also supply kits that use the Windows Installer Service (MSIEXEC). Please contact your supplier for further information on these "MSI" kits. Windows installation is started by running SETUP.EXE from Disk-1. This will start the InstallShield Setup Wizard. Change disks when you are prompted to do so. Help is available during the installation. Press the F1 key for assistance at any dialog box. Setup allows the installer to choose the installation directory and program folder name. The default values are different from previous kits, but if a previous installation is detected, Setup will take the current location and Client settings as defaults for the new installation. You may wish to install this kit to a different location so that you do not overwrite the previous version's files. 9.1 Client Installation Notes ----------------------------- You do not normally need to uninstall or even stop an older version Client before installing a new version. Setup will take its default installation directory from the existing Client (typically C:\PCD32). We recommend that you install the v8 Client to a different directory (e.g. C:\PCD810). If you install to the same directory, you cannot use the old version Uninstall to remove the files, and Setup may need to restart the PC in order to update shared system files. Setup allows the installer to set the Client's transport configuration. This can be modified by the Client Configurator once installation is complete. Setup can also apply a predefined Client configuration. Use the Client Configurator to generate a suitable configuration. Then copy the CLIENT32.INI file into the same directory as SETUP.EXE, and Setup will use it as a default for future installations. If Setup sees a CLIENT32.INI file in its directory, it will offer an "Apply predefined configuration" option. This takes precedence over any existing Client's settings. It is necessary to restart Windows in order to load the Client after it has been installed on Windows 95 or NT. Setup does not normally offer to reboot unless it has to replace a shared or system file. A reboot can be forced by adding AutoReboot=1 to the [Client32] section of the SETTINGS.INI file. For example:- [Client32] AutoReboot=1 If this value is defined, Setup will offer to reboot Windows on completion of the installation. This section can also be used to specify that an icon should be created for the Client in a specific program folder. This is controlled by value Icon=. If this is defined, it contains the folder name. For example:- [Client32] Icon=PC-Duo This is typically accompanied by:- NoAutoStart=1 which causes Setup to remove the wclient= line from the [boot] section of SYSTEM.INI. This disables the normal Client startup on Windows 95. Setup normally creates icons for any program options that are installed. This can be disabled by adding:- CreateIcons=0 to the [Folders] section of SETTINGS.INI. Note that this will leave you with no easy way to run the Activate or Deactivate Client or the Reset Video Driver programs if these are provided for the Client's operating system. The command-line program, PCICONN.EXE, was introduced in v6.10 to implement a Connect to Control request for assistance. PC-Duo Setup can create a "Request Help" shortcut in the PC-Duo program folder if the Control's IP address is specified in SETTINGS.INI. The syntax to use is:- [Client32] CallControl=ip.ad.dr.ess[,shortcut title] The Client uses TCP/IP port 5421 to Connect to the Control, which must be running and Available for the request to succeed. The port number is fixed and cannot be changed. The default shortcut title is "Request Help". This can be replaced by an alternative title if required. The replacement title is delimited from the Control's IP address by a single comma ',' character. For example:- [Client32] CallControl=10.0.0.100,Call Technical Support Setup will create the shortcut in the PC-Duo folder when the Client is installed. Note that Setup will stop a running Client before it starts copying files. If you are installing under remote control, you will lose your connection. When the Client software has been installed, Setup will make the necessary changes to the Registry or to SYSTEM.INI so that Windows loads the Client automatically during startup. Setup may need to restart the PC in order to update critical system files. Please note the following restriction:- - The PC-Duo Client should not be installed on a PC that has another remote control product installed. This can result in system failure as kernel level modules are affected. We recommend that you remove any other remote control programs and restart your PC before you install PC-Duo. 9.2 Administrator Privilege Required ------------------------------------ Installation of the Client or Gateway on Windows NT, 2000, XP, or .NET requires Administrator privilege, as it performs system-level configuration changes. If you do not have the required privilege, Setup will exit after displaying an error message. Administrator privilege is not strictly required for Control installation, but Setup is configured to require privilege in all cases. It is possible to run Setup from a non-privileged account, in which case it will not be able to install the NT Client as a Service. If you need to do this for some reason, change the following line in SETTINGS.INI:- [Install] AdminRequired=1 to read:- AdminRequired=0 Setup will create program icons in a user program group instead of a common program group. If the Client is installed, the "Activate Client" icon command line contains the Client's configuration settings. It must be used from an account with Administrator privileges to configure Windows to load the NT Client. 9.3 Windows on Windows Support ------------------------------ In common with many installers, Setup requires the Windows NT 16-bit Windows on Windows (WoW) subsystem in order to start correctly. 9.4 Creating a Silent Installation ---------------------------------- InstallShield provides a facility for recording user selections during an installation. These responses can be used to provide the answers to questions during a subsequent "silent" installation - i.e. an unattended automatic installation. The procedure for creating a silent installation response file is as follows:- 1 - Copy the Evaluation Kit disk contents onto a suitable common location such as a file server. The directory structure should be such that the files from all of the disks are in the same directory, or they are in DISK1... subdirectories of a common parent directory (e.g. PCD32). 2 - Choose a PC that is typical of a group; 3 - Run Setup from the kit location, specifying the -r (record) command line option. For example:- Run: u:\pcd32\disk1\setup -r 4 - All of the responses that you make will be recorded. The response file, SETUP.ISS, is stored in the WINDOWS directory. See Section 9.5 below for an example of the response file format. 5 - Make selections during Setup that are appropriate for all of the target PCs. Particularly, you should select an appropriate network transport, and not display the Read Me notes or run the Client Configurator. 6 - When Setup has finished, copy the response file back to the kit location, so it is in the same directory as SETUP.EXE. This location can be read-only for the remainder of the installations. 7 - For each target PC, you must arrange for the following command to be executed:- u:\pcd32\disk1\setup -s Setup will look for the response file in the source directory. If it is in a different location, the -f1<path> option can be used to specify the correct path. For example:- u:\pcd32\disk1\setup -s -f1"u:\pcdsetup.iss" Setup also creates an installation log file. If the source area is read-only, or more than one target PC will be performing a silent install, they will be unable to write a log file to that location. The -f2 option provides an alternate path for the log file. For example:- u:\pcd32\disk1\setup -s -f2"c:\pcdsetup.log" The log files can be checked later. See Section 9.6 below for an example of the log file format. If you want to run a silent installation from a location which is not normally accessible and your script makes a NET USE to this location before starting SETUP, and disconnects the USE afterwards, you should use the following command format:- start/wait u:\pcd32\disk1\setup -s -f2"c:\pcdsetup.log" The Start/Wait command forces Windows to wait for SETUP.EXE to exit before it continues. 9.5 Silent Installation Response File Format -------------------------------------------- The contents of a typical silent install response file are shown below. This example is provided for reference purposes. You will not normally need to edit this file. [InstallShield Silent] Version=v7.00 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{55C781E8-CCBD-11D7-82C2-AA0004001604}-DlgOrder] Dlg0={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskOptions-0 Count=8 Dlg1={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdWelcome-0 Dlg2={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdLicense-0 Dlg3={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdSetupTypeEx-0 Dlg4={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskDestPath-0 Dlg5={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdSelectFolder-0 Dlg6={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskOptions-1 Dlg7={55C781E8-CCBD-11D7-82C2-AA0004001604}-SdFinish-0 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskOptions-0] Component-type=string Component-count=1 Component-0=FIRST_TIME_CAPTION Result=1 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdWelcome-0] Result=1 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdLicense-0] Result=1 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdSetupTypeEx-0] Result=Client [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskDestPath-0] szDir=C:\PCD32 Result=1 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdSelectFolder-0] szFolder=PC-Duo Result=1 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdAskOptions-1] Component-type=string Component-count=1 Component-0=APPLY_CONFIGURATION_OPTION Result=1 [Application] Name=PC-Duo Version=8.10 Company=Vector Networks Lang=0009 [{55C781E8-CCBD-11D7-82C2-AA0004001604}-SdFinish-0] Result=1 bOpt1=0 bOpt2=0 Note that this file contains the installation directory, program folder, and configuration selections. 9.6 Silent Installation Log File Format --------------------------------------- A typical silent install log file contains:- [InstallShield Silent] Version=v7.00 File=Log File [Application] Name=PC-Duo Version=8.10 Company=Vector Networks Lang=0009 [ResponseResult] ResultCode=0 ResultCode=0 indicates success. Negative values indicate failure. 9.7 Silent Installation Errors ------------------------------ You may see a ResultCode of -12 if the silent installation procedure does not use the same dialog sequence as the template installation, or an error caused the installation to be aborted. Further information on configuring and running silent installs is available in the PC-Duo Resource Kit. Contact Vector Networks for details. 9.8 Installing the Gateway -------------------------- A separate Setup Type has been added so that the Gateway can be installed without other components such as the Client or Control. Use Custom Setup to install the Gateway with a combination of other modules. 9.9 Installing Client, Control, and Gateway Configuration Files --------------------------------------------------------------- Setup has been enhanced so that it can install copies of the following Client, Control, and Gateway configuration files if they are present in the same directory as SETUP.EXE and the "Apply predefined configuration" option is selected on the appropriate Configuration dialog. Client Files: CLIENT32.INI - The main 32-bit Client configuration file CONTROLS.NSM - The Control list for Request Help and Call Control commands HELPDESK.ICO - Alternative icon displayed in Acknowledgement dialogs Control Files: CLIENT.NSM - The Known Clients database EXECUTE.NSM - Provides values for the Control's Execute at Client dialog GROUP.NSM - The Groups database REMOTE.NSM - Remote Network details SCRIPTS.NSM - Script details for the Control's Scripts Folder TOOLS.NSM - Tools Menu commands Samples of the CLIENT32.INI, SCRIPTS.NSM, and TOOLS.NSM files are provided in this kit. Both Control and Gateway store some configuration settings in the Registry. If the appropriate "Apply predefined configuration" option is selected, Setup can install these from user-supplied files. The Control's settings must be provided in file PCICTL.REG, and the Gateway's in GATEWAY32.REG. Note that Setup runs REGEDIT to install these settings without checking the contents of these files. 10 Uninstallation Notes ======================== You do not normally need to uninstall or even stop an older version Client before installing a new version. If you do use the "De-activate Client" program on Windows NT, you will have to restart the system before you can install a new version. We hope that you won't need to uninstall PC-Duo. Follow this sequence to remove the software from your PC:- 1 - Use Start, Settings, Control Panel, Add/Remove Programs to uninstall PC-Duo. This stops the Client and Gateway and removes any SYSTEM.INI and Registry Entries. It also deletes the program folder, shortcuts, the files in the installation directory, and the driver files from the \WINDOWS\SYSTEM directory on Windows 95. 2 - If the Client was running, you will probably have to restart Windows before all of the files can be deleted. 10.1 Tidying up --------------- On some PCs, you may find that there is a hidden PCD32.GID file left in the \PCD32 directory. This is a Windows Help index file. Use the following DOS command to clear the hidden attribute:- C:\>attrib -h c:\pcd32\*.* You can then delete any remaining files in the \PCD32 directory. On Windows NT, you should also delete the following files from the \WINNT\SYSTEM32 directory:- CLHOOK*.DLL (and CLHOOK*.OLD) GDIHOOK*.DLL (and GDIHOOK*.OLD) PCIGINA.DLL (and PCIGINA.OLD) PCIMON.DLL (and PCIMON.OLD) PCISYS.NTK (on NT only) PCIVDD.DLL (and PCIVDD.OLD) On Windows NT v4, you should also delete the following file from the \WINNT\SYSTEM32\DRIVERS directory:- PCISYS.SYS (and PCISYS.OLD) These odd files will be tidied up automatically in a future release. 11 Diagnostic Utilities ======================== There are no diagnostic programs in this kit. 12 Automated Installation with PC-Duo Enterprise ================================================= PC-Duo can be installed using the Software Distribution feature of PC-Duo Enterprise. PC-Duo Setup can also be used in "Silent" mode to automate Client installation. See Section 9.4 above for further details. Contact Vector Networks for further information. PC-Duo Enterprise is Vector Networks' PC network management package. 13 Online Documentation ======================== The PC-Duo v8.1 User Guide is included in this kit as an Adobe Acrobat Reader-compatible PDF file. Select the "Online Documentation" installation option in Setup to install this manual. It is in the same 9" * 7" format as the printed manual. You can print your own copy of the manual using the Acrobat Reader File Menu, Print command. Use the Print Setup command to change the paper size. 13.1 PC-Duo Resource Kit ------------------------ Additional information on the installation and use of PC-Duo is contained in the PC-Duo Resource Kit. Contact Vector Networks for details. 14 Vector WWW Site ==================== Visit our World Wide Web sites for support, new product, software update, and release information. Point your Web browser at URL: http://www.vector-networks.com