---------------------------------------------------------------------------- Backup Exec for NetWare - Windows Client & Agent Version 7.01 Revision 4.103 Copyright 1993, 1995 Arcada Software, Inc. All Rights Reserved. ---------------------------------------------------------------------------- README.TXT updated 07/27/95 WINDOWS REQUIREMENTS: ===================== You must be running Windows 3.1 in Enhanced Mode or Windows for Workgroups. In addition, you need to have defined NetWare support for Windows' Network System Settings (configurable within Windows Setup). NETWARE REQUIREMENTS: ===================== In order to run the Windows Client and the Windows Agent, you must run the Novell NetWare requestors. Note: You can determine the version level of the following programs by running them with the parameters specified in the following table. Program Information Example ------- Parameter ------- ----------- IPX -i IPX -i NETX /? NETX /? LSL /? LSL /? IPXODI /? IPXODI /? VLM /? VLM /? IPX/NETX -------- If you are running the IPX/NETX requestors, you need to make sure that your are running the following versions: IPX.COM Version 3.10 or later NETX.COM Version 3.26 or later ODI --- If you are running the ODI drivers (replacement for IPX), you need to make sure that you are running the following versions: LSL Version 2.02 or later IPXODI Version 2.11 or later VLM --- If you are running the VLM driver (replacement of NETX) that came with NetWare 3.12 or 4.01, it should be at or later than the following versions: VLM Version 1.02 When you install the VLM driver, you should use the Novell supplied installation program (DOSWIN Workstation installation for NetWare 4.01). If you merely copy over the VLM files and start using them, there will be several DLL files that will not be updated. This will result in mis-matched NetWare components that will cause run time errors. One symptom of a bad VLM installation is that the Backup Exec for NetWare - Windows Client will not load (you get an hour glass cursor followed by some disk activity and are returned to the program manager). MSIPX ----- This is the IPX that comes with Windows for Workgroups. It is not compatible with the Backup Exec Agent software. See the WINDOWS FOR WORKGROUPS section later in this file for more information. TROUBLESHOOTING: ================ 1 - Sometimes while the Windows Client application is scanning the network for agents, it may stop on a NetWare agent. If this occurs, wait for 2 to 3 minutes. If the Server that is running the agent is very busy, it may pause before moving on to the next agent. If the Windows Client does not proceed to the next agent within a few minutes, you may have some servers that have older software on them. If this occurs, you need to reboot your workstation. When your workstation is running again, create a file called SMDRINCL.DAT in the directory where you installed the Windows Client software (the default is C:\BKUPEXEC\WIN_WS). In this file, place the names of the servers that you want to be able to make selections from. If the SMDRINCL.DAT file exists, only the servers listed plus your default server will be scanned and displayed in your Backup Sources window. Note that if the Backup Server that you are attaching to has a SMDRINCL.DAT file, it will be used instead of the local SMDRINCL.DAT file. Sample SMDRINCL.DAT file ACCOUNT_SERVER CUSTOMER_SERVER ENGINEERING 2 - If you encounter an error in the Windows Client that causes a General Protection Fault (GPF), you will have to reboot your workstation before you can restart the Windows Client. 3 - If, during the install of the Windows Client, you got a message indicating that one or more of your Novell files was found in both the Windows and the Windows System directory, you may have mismatched network access files. There is a group of DLL files that provide network access under Windows. If you are using some DLLs from one version, and some DLLs from another version, you may encounter various error situations. If you are sure that you did not accidentally install only a portion of the network files, ignore this error. Otherwise, you may want to install Novell's most recent workstation updates. The most recent Novell's DOS and Windows client software can be found in Novell's NetWire Compuserve forum. The updates are split up into the following four files: WINDRx.EXE Novell Windows Driver Update File NWDLLx.EXE Novell Windows DLLs Update File VLMUPx.EXE DOS Client Files Update NET33X.EXE NETX,EMSNETX,XMSNETX, & NETWARE.DRV Update File A lower case x indicates the version number of the update. For example, the second version of the WINDRx.EXE update is WINDR2.EXE. WINDOWS 95: =========== Currently, running the Windows client under Windows 95 is not fully supported at this time. We have the following issues with running the Windows client in the Windows 95 environment. Occasionally while scanning the network for NetWare Target Service Agents (TSAs), the following blue screen error is displayed: A fatal exception 0E has occurred at 0028:C001560D in VXD NWLINK(01)+0000484D. The current application will be terminated. The probability of encountering this error can be reduced by using the SMDRINCL.DAT (see TROUBLESHOOTING above) file to reduce the number of NetWare agents that are scanned for. If this error occurrs, you will have to restart Windows 95 before the client can successfully run again. In order to perform backup and restore operations on your Windows 95 system, you will need to install the Backup Exec Windows 95 agent. Please see the Client and Agent Installation chapter of the Backup Exec Administrator's Manual for more information about installing and updating the Windows 95 agent. If you are using a 3C503 Network Interface card in a system which also contains an Adaptec SCSI controller, you may have problems attaching to the local Backup Exec agent. There are two workarounds for this problem. You can change the driver type for the 3C503 card (under "Network" in your control panel settings) and have it use the "Real mode [16 bit] NDIS driver". Alternately, you can use the DOS client in a DOS box to submit jobs for your local Backup Exec agent. WINDOWS FOR WORKGROUPS: ======================= Running the Windows Client is supported with the Windows for Workgroups (WFW) Novell network drivers. However, the Backup Exec DOS Agent (the same as the Windows Agent) requires the use of Novell's ODINSUP network drivers in order to operate reliably. Setting up the Novell ODINSUP driver is highly sensitive to your local networking environment and should be performed by someone who is experienced with Windows network drivers. Consult your system administrator or the files WFWAGENT.WRI and WFW3_11.WRI in the Windows Client directory on your server for instructions on setting up the ODINSUP drivers for WFW 3.1 and WFW 3.11. These files can be viewed using Windows Write (included with Windows). If you already have the ODI drivers running with WFW 3.11, you will still want to view WFW3_11.WRI for instruction on properly configuring it for use with the Windows Client. Note: The default location for the Windows Client directory on your server is SYS:\BKUPEXEC\WIN_WS\WIN31.