Chip Special: Netware

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

/ Chip Special: Netware / Chip-Special_1996-08_NetWare_cd2.bin / content / support / token / 2 / flswks.exe / FLSWKS.TXT < prev next >

Wrap

Text File | 1995-03-13 | 56.1 KB | 1,532 lines

INTEL FLASH ADAPTERS FLASHWORKS INSTALLATION AND USER'S GUIDE Contents Chapter 1. Introduction What is FlashWorks? Is FlashWorks for you? Chapter 2. Installation Overview 1. Install the software 2. Install the adapter and run FlashStart Chapter 3. Updating files on user workstations How it works Getting updated files Updating users Verifying that users received updates Managing the FLUPDATE database Chapter 4. Viewing workstation assets How it works Using the FlashView program Viewing workstation assets Viewing change history Restoring CMOS Saving configuration files in flash memory Adding supplemental information Printing the assets list Chapter 5. Scanning for viruses How it works Creating an antivirus configuration Updating users with an antivirus configuration If a virus is detected Keeping FlashVirusProtect current Chapter 6. Troubleshooting Installation FLSCAN and FLVIEW FLUPDATE FlashVirusProtect Replacing the flash image Second edition, September 1994 Copyright c 1994, Intel Corporation. All rights reserved. Intel Corporation, 5200 Elam Young Parkway, Hillsboro, OR 97124-6497 Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein. The Intel logo is a registered trademark of Intel Corporation, registered in the United States of America and other countries. EtherExpress and LANDesk are trademarks of Intel Corporation. FaxBack is a registered trademark of FaxBack, Inc. Windows is a trademark of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. Ethernet is a trademark of Xerox Corporation. Portions of FlashWorks software licensed from Digital Development Corporation of Phoenix, Arizona under U.S. Patent Nos. ]4,975,950 and 5,121,345. 351076-003 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CHAPTER 1 Introduction What is FlashWorks? Quick multiple-adapter installation Set up a file server only once. Then, when you install an adapter in a user workstation, you're prompted to run FlashStart to automatically configure the adapter and download drivers. Centrally controlled updates Update any file, driver, or flash image on any workstation. Use the FlashUpdate program to schedule updates. When users log in, the FlashDriveCheck program checks to see if they've been scheduled for an update. If so, it downloads the file(s). Asset management Use the FlashScan and FlashView programs to record and view the assets and configuration files of a workstation. FlashScan stores the assets list in the adapter's flash memory. FlashView lets you view the list and a history of changes to the list. Virus protection The FlashVirusProtect program resides in flash memory on each adapter, so it can scan for viruses before and after DOS loads. You can configure what gets scanned and when. Is FlashWorks for you? FlashWorks can save you time and give you more control over your network if both of these are true: _ You use Novell NetWare 3.x or 4.01. _ You're installing more than 10 flash adapters. Otherwise, see your adapter's Installation Guide for installation instructions. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CHAPTER 2 Installation Install FlashWorks software on the server Do this only once, regardless of how many adapters you're installing. If someone has already installed FlashWorks on the file server, skip to Step 2. See page 4 for detailed instructions. Install the adapter and run FlashStart Once you've installed FlashWorks on the server, installing adapters is a simple matter of putting them in a workstation and choosing Run FlashStart from the menu. FlashStart automatically configures each adapter and downloads the drivers. See page 7 for detailed instructions. Install the software 1 Format a DOS 5.0 or 6.x boot disk (FORMAT /S) and keep it handy. If any network clients use DOS 6.x, you'll need a DOS 6.x disk. INSTALL uses this disk to create a boot image for FlashStart. 2 From your workstation, log in as Supervisor (or equivalent) to the server where you want to copy the FlashWorks software. 3 Put a copy of the FlashWorks disk into a drive, switch to that drive and, at the DOS prompt, type: INSTALL 4 Verify that the displayed server is the one you want to use for FlashWorks. 5 Choose the shell service and/or drivers you use: _ If you use NetWare 3.x, choose IPX, DOS ODI, or both. _ If you use NetWare 4.01 (or 3.12 with VLMs installed on the server), choose a shell service: VLM (DOS requester) or NETX. Choose VLM if you use NetWare Directory Services (NDS). In both cases, INSTALL loads just the ODI driver. 6 Enter the path where you want FlashStart to copy network drivers on user workstations. 7 When prompted, insert the DOS boot disk. INSTALL runs DOSGEN. 8 INSTALL prompts for the FlashWorks disk and then asks if you want to add lines to the system login script to run FlashDriveCheck and FlashScan. Press F1 for a description of these utilities. _ Choose Yes to add these lines to the system login script: MAP INSERT S1:=SYS:FLASH #FLDRVCHK #FLSCAN /Q MAP DEL S1: _ Choose No to continue without adding the lines. If you choose No, you'll need to add these lines to the system login script yourself. 9 Choose whether you want user workstations to have virus protection: _ Choose Yes to install FlashVirusProtect when FlashStart runs. _ Choose No to keep user workstations from getting FlashVirusProtect when FlashStart runs. (Even if you choose this option, you can use FlashUpdate or FVPCFG.EXE to install FlashVirusProtect later.) 10 INSTALL lists LAN adapter drivers it recognizes in the server's AUTOEXEC.NCF file. Tag the ones that you want to support FlashStart. If INSTALL doesn't recognize any network drivers, skip to step 13 (you might need to add commands to the AUTOEXEC.NCF file yourself). 11 Enter a unique network number for each adapter you've chosen. Each segment and frame type on a Novell network is identified by a number. Though you can assign the numbers arbitrarily, each must be unique. The network number must be hexadecimal, from one to eight characters. 12 If the AUTOEXEC.NCF file needs additional commands to support FlashStart, INSTALL displays the commands and asks if you want to add them. _ Choose Accept changes to add the highlighted commands to the AUTOEXEC.NCF file. The commands in the AUTOEXEC.NCF file take effect after you reboot the server. The next step tells you how to immediately activate these commands. _ Choose Cancel changes to return to the previous screen. 13 Go to the server console and run the commands to enable the network drivers to support FlashStart: If INSTALL modified the AUTOEXEC.NCF, run FLRPL.NCF or down and restart the server. FLRPL.NCF contains the same lines that INSTALL adds to the AUTOEXEC.NCF file. To run FLRPL.NCF, type this at the server's console prompt: FLRPL FLRPL loads and binds the appropriate frame types to the LAN adapters. If INSTALL didn't modify the AUTOEXEC.NCF, make sure it contains the commands to do this: For ethernet: _ Load the LAN driver, specifying the 802.3 frame type, and bind IPX to it. _ Load the LAN driver, specifying the 802.2 frame type, and bind IPX to it. _ Load RPL.NLM. _ Bind RPL.NLM to the network driver that's bound to the 802.2 frame type. For token ring: _ Load the LAN driver, specifying the TOKEN-RING frame type, and bind IPX to it. _ Load RPL.NLM. _ Bind RPL.NLM to the LAN driver that's bound to the TOKEN-RING frame type. Here are some sample commands: Sample LOAD and BIND commands for ethernet LOAD C:\EXP16 PORT=300 INT=5 FRAME=ETHERNET_802.3 NAME=IPXCARD BIND IPX TO IPXCARD NET=214 LOAD C:\EXP16 PORT=300 INT=5 FRAME=ETHERNET_802.2 NAME=RPLCARD BIND IPX TO RPLCARD NET=215 LOAD RPL BIND RPL TO RPLCARD Where PORT= (port) and INT= (interrupt) are configuration settings for hardware and NET= is the network number. 14 Check to see if the frame types are loaded. Type this at the server's console prompt: CONFIG For ethernet, verify the following: _ One driver uses the 802.3 frame type and an IPX LAN protocol with a unique network number. _ One driver uses the 802.2 frame type and two network protocols: IPX (with a unique network number) and RPL. For token ring, verify the following: _ One driver uses the TOKEN-RING frame type and two network protocols: IPX (with a unique network number) and RPL. If anything is missing, change network driver commands as described in CHAPTER 2. What INSTALL does _ Creates the following directory structure on the file server and copies FlashWorks files there: _ Creates a new user called NWFLASH. It also creates a user subdirectory under SYS:\MAIL and a substitute login script called NWFLASH.LS. FlashStart uses this name to log in to the network and download network drivers. Access for NWFLASH is limited to read and filescan for the LOGIN, MAIL, and PUBLIC directories. Access for the FLASH directory includes read, write, create, erase, and filescan. _ Runs Novell DOSGEN to: - Create NWFLASH.SYS, the remote boot image that FlashStart uses to access the network, and copy it to SYS:\LOGIN. - Copy the files RBOOT.RPL and NWFLASH.BAT to SYS:\LOGIN. _ Copies RPL.NLM to SYS:\SYSTEM if that file doesn't already exist. _ Creates or edits the BOOTCONF.SYS file in SYS:\LOGIN. _ Places commands in your AUTOEXEC.NCF file to support FlashStart and copies those same commands to FLRPL.NCF. (INSTALL makes a backup copy of the original AUTOEXEC.NCF in AUTOEXEC.OLD.) Install the adapter and run FlashStart 1 Turn the power off and remove the workstation cover. Failure to turn power off could shock you and may damage the adapter or workstation. 2 Put the adapter in an 8-bit or 16-bit expansion slot (16-bit slots provide the best performance) and replace the workstation cover. 3 Attach the network cable to one of the connectors on the adapter. 4 Turn the power on. The adapter displays the configuration program running from the flash chip. 5 Choose Continue to display the Main menu. For information about an option, highlight the option and press F1. 6 Choose Run FlashStart. If asked to choose a driver, choose the one your network uses (IPX or DOS ODI). FlashStart configures the adapter and downloads drivers. Does FlashStart take more than a few seconds? If an incrementing counter appears on the screen, FlashStart can't access the Novell RPL boot ROM program. Make sure the network cables are connected properly and the server is set up for FlashStart. 7 When FlashStart displays a message that says it's done, press the space bar to exit the program and attach to the network. If FlashStart doesn't successfully attach, reboot the workstation. FlashStart then runs again and asks you to manually configure the adapter. Edit the settings, if you want. If your second try doesn't work, see Chapter 6, Troubleshooting (CHAPTER 6). What FlashStart does _ Configures the adapter. _ Connects to the network via remote boot (Novell's RPL). _ Downloads selected drivers from the server and saves any existing versions of the driver files with a .OLD extension. _ Edits the AUTOEXEC.BAT file and, if needed, the NET.CFG file on the user workstation, and saves the previous version of each file with a .OLD extension. _ If set up to for VLM support: - Copies .VLM and .DLL files to the Windows directory. - Modifies the Windows configuration files as follows: SYSTEM.INI [boot] network.drv=netware.drv [boot.description] network.drv=Novell NetWare (v4.0) [386Enh] network=*vnetbios,vipx.386,vnetware.386 ReflectDOSInt2A=TRUE WIN.INI [Windows] NetWarn=1 load=nwpopup.exe [Network] Restore=0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CHAPTER 3 Updating files on user workstations How it works Run FlashUpdate (FLUPDATE) to copy new files to the FLUPDATE database on the server. Select users to update FLUPDATE marks the names of these users in its database. You can update any file on user workstations, including: _ Antivirus configurations and pattern files _ Network drivers _ Flash images _ FlashWorks utilities _ Configuration files (such as NET.CFG and AUTOEXEC.BAT) When the user logs in, FlashDriveCheck (FLDRVCHK) runs from the login script, checks to see which users are selected for an update, and downloads the new software. Getting updated files You'll always find the latest version of drivers, flash files, and antivirus files on Intel's electronic Bulletin Board Service (BBS). Follow these steps to contact the BBS: 1 Prepare a modem and a workstation for file transfer. 2 Log in to the BBS and download the file. (For information on accessing the BBS, see the inside back cover.) _ The latest EtherExpress adapter files are in the EtherExpress adapters/Current release software section of the BBS. _ The latest TokenExpress adapter files are in the TokenExpress adapters/Current release software section of the BBS. _ The latest pattern file is in the LANDesk Virus Protect/Current release software section of the BBS. 3 Copy the file to the root directory of a formatted, blank diskette. Updating users 1 Be sure FLDRVCHK is in the system login script. If it's not, run the INSTALL program again or change the login script to include: MAP INSERT S1:=SYS:FLASH #FLDRVCHK MAP DEL S1: 2 Log in as Supervisor (or equivalent) to the server that contains the FlashWorks utilities. Go to the FLASH directory and, at the DOS prompt, type: FLUPDATE 3 Copy the new software to the server. _ Choose Manage software from the Main menu. _ Choose the type of file you want to update. For example, if you want to copy a new antivirus pattern file to the network, choose Manage antivirus software. _ Choose Copy software to server. When asked, insert the diskette and select the file(s) you want. 4 Set up an update: _ Choose Manage updates from the Main menu. _ Choose Update users. _ Complete the form as shown on the next page and press F10. When users log in, FLDRVCHK automatically downloads the new files to the workstation. For flash files, the process takes about 90 seconds. For other files (such as drivers), it takes only a few seconds. Verifying that users received updates You can check the status of updates in two ways: _ Choose Manage user database from the Main menu to display a list of the entire user database. You can see information about any user by highlighting the user name and pressing Enter. _ Choose Manage updates from the Main menu, then choose View status. A list shows the status of all update events (users updated, users not updated, and users that received errors during update). To filter the list, press F9, complete the form, and press F10. If no update occurs... See CHAPTER 6 for a list of possible causes. Managing the FLUPDATE database The FLUPDATE database contains the files you can update users with and a list of users you can update. How it works The FlashDriveCheck utility (FLDRVCHK) adds users to the FLUPDATE database. It pairs the user's name with the workstation node address. Anytime you suspect the user name and node address don't match, delete the user from the FLUPDATE database. (FLDRVCHK adds the correct user name to the database the next time the user logs in.) If more than one person uses a workstation... The first user that logs in is entered into the FLUPDATE database. Deleting users from the database 1 Log in as Supervisor (or equivalent) to the server that contains the FlashWorks utilities. Go to the FLASH directory and, at the DOS prompt, type: FLUPDATE 2 Choose View user list from the Main menu. 3 Tag the user name and press F4. Deleting software from the database 1 Log in as supervisor (or equivalent) to the server that contains the FlashWorks utilities. Go to the FLASH directory and, at the DOS prompt, type: FLUPDATE 2 Choose Manage software from the Main menu. 3 Choose the type of file you want to delete. For example, if you want to delete an antivirus pattern file, choose Manage antivirus software. 4 Choose Delete software. 5 Tag the files you want to delete and press F10. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CHAPTER 4 Viewing workstation assets How it works I. You add the command for FlashScan (FLSCAN) to the system login script so it runs when users log in. II. When users log in, FLSCAN runs. It scans the workstation and stores the information it finds in the adapter's flash memory. III. You run FlashView (FLVIEW) at the workstation to view the information. Using the FlashView program 1 Be sure FLSCAN is in the system login script. If it's not, run the INSTALL program again or change the login script to include: MAP INSERT S1:=SYS:FLASH #FLSCAN /Q MAP DEL S1: Now each time a user logs in, FLSCAN examines that workstation's configuration and stores the information in the adapter's flash memory. 2 At the workstation, go to the DOS prompt, switch to the directory containing FLVIEW, and type: FLVIEW FLVIEW's welcome screen displays first, then its Main menu. Viewing workstation assets Choose View assets from FLVIEW's Main menu. This displays the workstation's current hardware and software configuration. You'll see detailed information about these assets: Hardware Configuration files* ------------------------------------------------------------ Bus Memory CONFIG.SYS Floppy disk(s) Mouse AUTOEXEC.BAT Hard disk(s) Port(s) NET.CFG Keyboard P rocessor(s) SHELL.CFG LAN Adapter(s) Video ------------------------------------------------------------ * FLVIEW displays these files only if you set it to do so with the Select configuration files option. Viewing change history Choose View change history from FLVIEW's Main menu. This displays a record of changes to the workstation's assets. Whenever FLSCAN runs, it compares the new list of assets to the previous one and records any differences in flash memory. Seeing the recent changes can help you troubleshoot problems with the workstation. Restoring CMOS Choose Restore CMOS from FLVIEW's Main menu. This copies the CMOS information stored in flash memory to the workstation's CMOS. Whenever FLSCAN runs, it copies the contents of the workstation's CMOS to flash memory. Use Restore CMOS to restore the workstation's CMOS if it's corrupted. Before choosing this option, first try to manually restore the CMOS settings. Caution Don't choose Restore CMOS if FLSCAN hasn't run on this workstation with this flash adapter. Otherwise, you'll restore the wrong CMOS image to the workstation. Saving configuration files in flash memory Choose Select configuration files from FLVIEW's Main menu. You can then select which system and network configuration files FlashScan saves in flash memory. Whenever FLSCAN runs, it copies the selected configuration files from the workstation to flash memory. You can then view the contents of those files (using View assets) and the changes made to them (using View change history). Adding supplemental information Choose Enter supplemental information from FLVIEW's Main menu. You can then add or change your own notes about a workstation. Use this option to add information such as vendor names, inventory numbers, purchase dates, and phone numbers. The information you add appears in the assets list, so you can view and print it. If you're using LANDeskTM Manager... You can view any supplemental information entered in FLVIEW at the LANDesk Manager control panel. For more information see your LANDesk Manager guide. Printing the assets list Choose Print reports from FLVIEW's Main menu. You can print the current report (with the assets detected the last time FLSCAN ran) or print an older report (with the assets from previous scans still in flash memory). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CHAPTER 5 Scanning for viruses How it works There are two ways to setup virus scanning. From a workstation, you can create a local configuration and run FVPCFG.EXE (see page 20). From the network, follow the steps below. I. You run FlashUpdate (FLUPDATE) and create an antivirus configuration that specifies what and when to scan. II. You select the users you want to update with the configuration. III. When users log in, they're updated with the configuration. The scanner then runs according to how you set it up. What it scans for _ Boot sector and partition sector viruses. In addition to checking for known viruses, the virus checker notices any changes to the boot or partition sector, which might indicate a virus. _ File-type viruses (including system files and application programs). Because system files are vital to computers, they're a common target of virus attack. In addition to checking for known viruses, the virus checker notices any changes to system files. _ Memory-resident viruses. If a virus is found, FlashVirusProtect warns the user before the virus has a chance to spread. The user has several options for eliminating the virus, depending on where it's found (see If a virus is detected below). How it scans _ Before DOS loads. FlashVirusProtect is unique in that it scans before DOS loads; most conventional scanners check for viruses only after DOS loads. The scanner checks boot and partition sectors, memory, and files against a pattern file containing the pattern of thousands of known viruses. (As new viruses are discovered, Intel makes updated pattern files available.) _ After DOS loads. A TSR (terminate-and-stay resident program) checks for boot sector viruses. This guards against infection from floppy disks. After each scan, FlashVirusProtect reports its findings in a file called VPLOG.RPT in the workstation's \VPROTECT.PC directory. Use a text file viewer to view this report. If you're using LANDeskTM Virus Protect... You can view a master report that contains each workstation's report. To do this you must add VPDOCK to the system login script. For more information, see the LANDesk Virus Protect User's Guide. Creating an antivirus configuration You can create as many antivirus configurations as you need. This is useful when you want to scan some workstations differently than others. For example, one configuration called Complete/monthly could scan all files and drives once a month. Another one called Weekly could check all drives and executable files only (more appropriate for normal use) weekly. Here's how: 1 Be sure FLDRVCHK is in the system login script. If it's not, run the INSTALL program again or change the login script to include: MAP INSERT S1:=SYS:FLASH #FLDRVCHK MAP DEL S1: 2 Log in as Supervisor (or equivalent) to the server that contains FlashWorks utilities. Go to the FLASH directory and, at the DOS prompt, type: FLUPDATE 3 (Optional) Install a new virus pattern file. _ Choose Manage software from the Main menu. _ Choose Manage antivirus software. _ Choose Copy software to server. When asked, insert the disk with the pattern file in a drive and select the file. 4 Choose an antivirus configuration. _ Choose Manage software from the Main menu. _ Choose Manage antivirus software. _ Choose Configure antivirus software. You'll see a list of antivirus configuration files. _ Select New Configuration or select an existing configuration file. Enter a valid DOS file name (without an extension) for the name of the new configuration. If you want, also include a description of the configuration. Default configuration lets you change the defaults on which new configurations are based. This is also the configuration FlashStart downloads when it runs on user workstations. 5 Specify the configuration you want and press F10. Antivirus configuration options Anti-Virus TSR Lets you choose whether to load the antivirus TSR. This TSR (which requires 6 KB of memory) detects viruses after the workstation boots (as opposed to scanning before boot up). It checks for viruses in the boot sector of any drive or diskette each time it's accessed. This is especially useful because diskettes are highly susceptible to virus contamination. Default: Off. Pre-boot sector scanner Lets you choose whether the scanner scans the boot sector. Default: On. Pre-boot file Lets you choose whether to run the file scanner. Default: On. You can set the scanner following options for the file scanner: Pattern file Identifies the pattern file (for example, LPT$VPN.047) that is downloaded with this configuration. This file contains thousands of known virus patterns. The scanner uses this to detect viruses. For complete protection, use the most up-to-date pattern file. See page 26 for information about getting new pattern files. (To load the virus pattern file, you need at least 200 KB of uncompressed disk space on the workstation.) Frequency Determines how often the file scanner checks for viruses. Choices are Always (each time the workstation is turned on), Daily, Weekly, or Monthly, starting from when the workstation is initially scanned. Default: Weekly. Files to scan Determines which files are scanned. Choices are All files, Executable files (includes .EXE, .COM, .SYS, .BIN, .OVL files), or None. Most viruses attack program files only, not data files, so selecting Executable files can save time. The default setting is Executable files. Drives to scan Determines which drives to scan. Choices are All drives, Hard drives, or Hard disk boot drive. Default: All drives. Scan compressed drives Determines if compressed drives are scanned. The virus scanner can check compressed files from these compression programs only: Stacker version 3.0 (pre-DOS 6.0) and SuperStor version 2.0. (When setting up Stacker or SuperStor, reserve at least 200 KB of uncompressed disk space on the workstation for the pattern file.) Choices are Yes or No. If you know users aren't using either of these two compression programs on their workstations, set this option to No. Default: No. Escape key Lets you choose whether users can stop scanning by pressing Escape. Choices are Enable or Disable. Default: Enable. Creating a configuration locally You can also create an antivirus configuration at the workstation: 1 Create a subdirectory called VPROTECT.PC under the root directory of the workstation's boot drive. 2 Copy a pattern file (for example, LPT$VPN.047) to this directory. The pattern file must be in VPROTECT.PC. 3 Copy FVPCFG.EXE and DEFAULT.FLS from the FLASH directory on the FlashWorks server to a diskette or a directory on the workstation. These files don't need to be in VPROTECT.PC, but they both need to be in the same directory. 4 Switch to that directory and type: FVPCFG 5 Specify the configuration you want (see the table on the previous page for details) and press F10. 6 Choose Yes to download the configuration to the flash adapter. Updating users with an antivirus configuration Use FLUPDATE to set up an update. For detailed instructions on setting up an update, see page 10. You don't have to use the same configuration on all workstations, but you can use only one configuration at a time on each workstation. If users have Windows When you set up virus protection, FLDRVCHK downloads two programs and copies them to the workstation's Windows directory (if it exists): _ FVPDISP.EXE (virus alert program) This file is required if you load the antivirus TSR on the workstation and want the user to be alerted automatically when a virus is found. To automatically load FVPDISP.EXE on the workstation at startup, add it to the Windows startup group. _ WINTSR.COM (TSR) This file is required if you load the antivirus TSR on a workstation that has a hard disk with 32-bit access enabled. WINTSR.COM (which requires 1KB of memory) must be loaded before Windows loads. To automatically load it at startup, include it in the workstation's AUTOEXEC.BAT file. If Windows is later installed on the workstation... Copy the Windows programs FVPDISP.EXE and WINTSR.COM to the workstation using one of these methods: _ Use FLUPDATE to download the files or to download a new antivirus configuration file (in this case, the files are copied automatically). _ Copy the files yourself from the \FLASH\SOFTWARE\WIN directory on the FlashWorks server. If a virus is detected If FlashVirusProtect finds a virus, it alerts the user and offers several choices, depending on the type of virus: _ The program finds a virus in the boot or partition sector. The user can replace the current boot or partition sector with a clean copy stored in flash memory, or generate a new boot or partition sector. _ The program doesn't find a known virus but detects that the boot or partition sector has been changed. The user can update the copy stored in flash memory (when the user is sure it's not a virus and is the result of some system change), replace the boot or partition sector with a clean copy stored in flash memory, or generate a new boot or partition sector. _ The program finds a virus-infected file. The user can repair or delete the file. _ The program doesn't find a known virus but detects that the system file has been altered. The user can update the copy stored in flash memory (when the user is sure it's not a virus), or continue scanning and reinstall DOS after the scan completes. _ The program finds a virus in memory. The user must reboot the system. The tables on the following pages list the messages and available options that FlashVirusProtect displays when it detects a virus. ======================================================================== FlashVirusProtect Message Table ------------------------------------------------------------------------ Message Action ------- ------ Boot sector A virus has been found in the boot sector. You virus alert! need to restore the boot sector. _ Press R to replace the current boot sector with a clean copy stored in the adapter's flash memory. _ Press G to generate a new boot sector. Generally, you'll want to replace the current boot sector with the copy stored in the adapter's flash memory, unless you know the copy is incorrect for the workstation. (A copy of the boot sector is stored in flash memory the first time scanning occurs. Then, whenever the scanner runs, it compares the current boot sector with the one stored in flash memory and notifies you of any changes.) If you recently moved this adapter to a new workstation, the boot sector stored in flash memory may be incorrect. If you're not sure, replace the boot sector with the stored copy. If that doesn't work and you're unable to boot from the workstation, generate a new boot sector (see description below). Generating a new boot sector-Do this only if you know the boot sector stored in flash memory is wrong or if there is no stored copy. Follow these steps to generate the new boot sector: 1 Find a DOS system diskette that is formatted with the same DOS version as your hard drive and that contains SYS.COM. 2 Put the diskette in drive A: and press any key to reboot. 3 At the DOS prompt, type SYS and the name of the drive you're repairing. For example, SYS C:. 4 Remove the DOS diskette. You can now boot from your hard drive again. ------------------------------------------------------------------------ Boot sector The program has detected a change in the boot sector. change alert! You need to determine if it's a virus. _ Press S to save the boot sector changes in the copy stored in the adapter's flash memory. _ Press R to repair the boot sector. If you've made changes to the workstation that might affect the boot sector, there probably isn't a virus. You'll want to update the copy stored in flash memory. (A copy of the boot sector is stored in flash memory the first time scanning occurs. Then whenever the scanner runs, it compares the current boot sector with the one stored in flash memory and notifies you of any changes.) Changes that affect the boot sector: _ Changing the hard disk's volume or label name. _ Installing a new version of DOS. If you save the boot sector changes to flash memory and later discover that you had a virus at the time, be sure to update flash memory with a clean copy once you've eliminated the virus from the workstation. Repairing the boot sector-If you choose to repair the boot sector, the program assumes you have a virus and gives you the same options as for a virus alert. For what to do, see the solution for Boot sector virus alert! above. ------------------------------------------------------------------------ Partition A virus has been found in the partition sector. sector virus You need to restore the partition sector. alert! _ Press R to replace the current partition sector with a clean copy stored in the adapter's flash memory. _ Press G to generate a new partition sector. Generally, you'll want to replace the current partition sector with the copy stored in the adapter's flash memory, unless you know the copy is not correct for this workstation. (A copy of the partition sector is stored in flash memory the first time scanning occurs. Then, whenever the scanner runs, it compares the current partition sector with the one stored in flash memory and notifies you of any changes.) ------------------------------------------------------------------------ Partition The program has detected a change in the partition sector change sector. You need to determine if it's a virus. alert! _ Press S to save the partition sector changes in the copy stored in the adapter's flash memory. _ Press R to repair the partition sector. If you know you've made changes to your system that might affect the partition sector, you probably don't have a virus. You'll want to update the copy stored in flash memory. (A copy of the partition sector is stored in flash memory the first time scanning occurs. Then whenever the scanner runs, it compares the current partition sector with the one stored in flash memory and notifies you of any changes.) Changes that affect the partition sector: _ Using FDISK to modify the hard disk's partitions. _ Installing a new version of DOS. If you save the partition sector changes to flash memory and later discover that you had a virus at the time, be sure to update flash memory with a clean copy once you've eliminated the virus from the workstation. Repairing the partition sector-If you choose to repair the partition sector, the program assumes you have a virus and gives you the same options as for a virus alert. For what to do, see the solution for Partition sector virus alert! above. ------------------------------------------------------------------------ A file virus The program has found a file with a virus. is found _ Press R to repair the infected file. _ Press D to delete the file. If you know you have a backup copy of the file handy, go ahead and delete the file. Otherwise, try repairing the file. If the repair is unsuccessful, you'll need to delete the file. Don't keep it on the workstation as the file may cause further infection. ------------------------------------------------------------------------ System file The program has detected a change in the system file. change alert! You need to determine if it's from a virus. _ Press S to save the system file changes in the copy stored in the adapter's flash memory. _ Press C to continue scanning without saving the changes. If you know the operating system has recently been changed, you probably don't have a virus. You'll want to update the copy stored in flash memory. (A copy of the system file is stored in flash memory the first time scanning occurs. Then whenever the scanner runs, it compares the current system file with the one stored in flash memory and notifies you of any changes.) If you save the system file changes to flash memory and later discover that you had a virus at the time, be sure to update flash memory with a clean copy once you've eliminated the virus from the workstation. If you haven't made any changes to the operating system, you probably have a virus. After scanning, reinstall DOS. ======================================================================== Keeping FlashVirusProtect current For complete protection against new viruses, you must keep FlashVirusProtect current. It's important that you use the most up-to-date version of the pattern file when scanning for viruses. If you're using LANDesk Virus Protect... You can set it so the pattern files it uses are automatically downloaded to user workstations. To do this you must add VPDOCK to the system login script. For more information, see the LANDesk Virus Protect User's Guide. You'll find the updated pattern file or FlashVirusProtect version on Intel's Bulletin Board Service (BBS). Downloading the file from the BBS 1 Prepare a modem and a workstation for file transfer. You'll need these items to access the BBS and download the file. 2 Log in to the BBS and download the file. (For information on accessing the BBS, see the inside of the back cover.) _ The latest EtherExpress adapter files are in the EtherExpress adapters/Current release software section of the BBS. _ The latest TokenExpress adapeter files are in the TokenExpress adapters/Current release software section of the BBS. _ The latest pattern file is in the LANDesk Virus Protect/Current release software section of the BBS. 3 Copy the file to the root directory of a formatted, blank diskette. Updating users with new program or pattern file Use FLUPDATE to set up an update. For detailed instructions on setting up an update, see CHAPTER 3. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~ CHAPTER 6 Troubleshooting Installation ======================================================================== Symptom Possible solutions --------------------------- ------------------------------------------ The FlashSet/FlashStart _ The flash chip may be disabled. Renable screen doesn't display the flash chip with SoftSet2 or TokenSet. after you insert a new _ You may have previously disabled adapter FlashStart. Run FlashRestore (FLRESTOR) to re-enable FlashStart. _ The flash chip may conflict with some other device. Change the address of the other device, or install the adapter in another computer, run SoftSet2 or TokenSet, and change the flash chip's address. When you select FlashStart _ Verify that RPL is loaded, using the for NetWare, RPL Find Frame CONFIG command at your server console. Count (RPL-FFC) counts If it's not, load RPL (see page 5). indefinitely _ Verify that RPL is bound to the LAN driver, using the CONFIG command at your server console. If it's not, bind RPL (see page 5). _ Check in the SYS:\LOGIN directory on your server. Make sure the files NWFLASH.SYS, NWFLASH.LS, NWFLASH.BAT, and BOOTCONF.SYS exist. If they don't, run INSTALL again. _ Verify that the cable is securely attached to the adapter and that the other end of the cable is securely attached to the correct device. _ If you're not using a new adapter, the connector type may be incorrect. Use SoftSet2 to set the connector type to either Auto-detect or to the connector type you're using. RPL displays "Cannot connect IPX isn't bound to the 802.2 or TOKEN-RING to file server; RPL HALTED" frame type of the LAN driver in the FlashWorks server. Go to the server console, unload RPL, bind IPX to the LAN driver, and choose the 802.2 or TOKEN-RING frame type. Then reload RPL.NLM and bind it to the frame type. During RPL remote boot Either the 802.3 frame type isn't loaded or process, NETX doesn't connect IPX isn't bound to the 802.3 frame type in the to the file server FlashWorks server. FlashStart for ethernet adapters requires that IPX be bound to both the 802.2 and 802.3 frame types. Load and bind IPX (see CHAPTER 2). FlashStart displays Make sure the hard disk has enough free space. "Unable to create a file You need at least 150 KB for drivers, 350 KB on workstation" if you download the antivirus software, or 1 MB if you're using VLMs and Windows. FlashStart tells you it was _ Verify that the drivers were added to successful, but no network the AUTOEXEC.BAT file. drivers load during reboot _ Make sure the workstation has enough disk space for the drivers. INSTALL can't initialize _ Verify that you're logged in, NetWare Directory Services authenticated as ADMIN, and have access (NDS) to a directory service tree. Be sure you're loading VLMs, then log in as ADMIN. _ INSTALL can't find the Unicode tables. Map a search drive to the tables on your network (usually SYS:PUBLIC\NLS). When you run NetWare 4.01 NetWare needs to create a swap file and can't. and FLSCAN or FLDRVCHK, Load HIMEM.SYS at the workstation to eliminate the workstation halts the need for a swap file. For more information about swap files, see your Novell documentation. --------------------------- ------------------------------------------ FLSCAN and FLVIEW ======================================================================== Symptom Possible solutions --------------------------- ------------------------------------------ FLSCAN or FLVIEW doesn't run _ Check the login script to see if FLSCAN ran. The login script may include conditional statements that specify when FLSCAN runs. If FLSCAN hasn't run, either wait until it automatically runs or manually run the program. _ The workstation doesn't contain a flash adapter. Either install a Flash adapter or stop using FLSCAN and FLVIEW on this workstation. No assets display in FLVIEW _ Check the login script to see if FLSCAN ran. The login script may include conditional statements that specify when FLSCAN runs. If FLSCAN hasn't run, either wait until it automatically runs or manually run the program. _ FLVIEW doesn't display hardware and software assets or configuration files until FLSCAN runs. Force FLSCAN to run by logging out, then logging in to the network. FLSCAN displays a banner when it runs. Run FLVIEW again. You've selected configuration _ Check the login script to see if FLSCAN files, but none display in ran. The login script may include FLVIEW conditional statements that specify when FLSCAN runs. If FLSCAN hasn't run, either wait until it automatically runs or manually run the program. _ FLVIEW doesn't display hardware and software assets or configuration files until FLSCAN runs. Force FLSCAN to run by logging out, then logging in to the network. FLSCAN displays a banner when it runs. Run FLVIEW again. The assets and/or Check the login script to see if FLSCAN ran. configuration files have The login script may include conditional changed, but the changes statements that specify when FLSCAN runs. If don't display in FLVIEW FLSCAN hasn't run, either wait until it automatically runs or manually run the program. Information displayed in _ Check the login script to see if FLSCAN FLVIEW doesn't match the ran. The login script may include workstation conditional statements that specify when FLSCAN runs. If FLSCAN hasn't run, either wait until it automatically runs or manually run the program. _ The flash adapter may have been in another workstation before being installed in this workstation. Log in or run FLSCAN again. Then re-enter supplemental information. --------------------------- ------------------------------------------ FLUPDATE ======================================================================== Symptom Possible solutions --------------------------- ------------------------------------------ FLUPDATE's database contains Make sure FLDRVCHK is in the system login script no entries and there are no conditional statements that keep it from running. FLUPDATE's database doesn't _ Make sure FLDRVCHK is in the system login change: users aren't added script and there are no conditional or deleted statements that keep it from running. _ Database may be corrupted. Run INSTALL to reinstall FlashWorks, and choose Create new database. Users log in to the server _ User(s) may already be updated. Check but don't receive updates which users have received updates (see CHAPTER 3 for instructions). _ FLUPDATE didn't find an existing file on the workstation. Check the path selected in FLUPDATE. Make sure it matches the location of the driver on the workstation. _ The user in the FLUPDATE database and the node address don't match the actual user. Delete the user from the database. When the user next logs in, the user name and correct address will be added to the database. Then reschedule the event. _ Database may be corrupted. Run INSTALL to reinstall FlashWorks, and choose Create new database. The software you want to _ Make sure you're using the correct Intel update won't load on the driver or FlashWorks diskette. server _ The file on the diskette may be corrupt or missing. Try a different diskette or download the file from the Intel Bulletin Board System (BBS). For information on accessing the BBS, see the inside back cover. _ One or more program files may be corrupt. Try reinstalling FlashWorks. Users receive updates, but _ Make sure the status screen is refreshed. FLUPDATE shows users as not Choose View status from the Manage updated updates menu. _ One or more program files may be corrupt. Try re-installing FlashWorks. Users don't receive updates, _ You may have updated a file with the same but FLUPDATE shows their name in another location. Check the status as updated search paths to see where FLUPDATE updated the file, and then check the file in those locations. _ One or more program files may be corrupt. Try reinstalling FlashWorks. Users don't receive updates, Erase and restore the contents of the flash chip. and FLUPDATE says the reason For instructions, see the next page. is flash memory is full Reports don't print _ Verify that the network cable is securely attached to the adapter and the printer. _ FLUPDATE tried to print to LPT1 and failed. Do one of these: - Make sure you have a printer connected to that port. - Use the CAPTURE command to redirect this port to a network printer. - Make sure the printer is on line. When trying to copy the Make sure there's at least 200 KB of uncompressed pattern file to the disk space on the workstation. workstation, FLUPDATE says it's out of disk space --------------------------- ------------------------------------------ FlashVirusProtect ======================================================================== Symptom Possible solutions --------------------------- ------------------------------------------ FlashVirusProtect scanner or Check the settings of the antivirus configuration TSR doesn't run as expected loaded on the workstation. For information on specifying an antivirus configuration, see CHAPTER 5. Scanning report says no _ Make sure the scanner is turned on. files have been checked _ Make sure the pattern file is in the directory \VPROTECT.PC. If it's not, reinstall the file. If you're trying to scan a compressed drive, make sure you're using Stacker 3.0 or SuperStor 3.0. Files compressed by other compression programs won't be scanned. Scanner doesn't find a known Make sure you're using the most up-to-date known virus pattern file. To update the pattern file, see the next page. Can't access configuration Make sure the C:\SLOCKFL.CFG file is not file read-only. If it is, change the attribute. If this doesn't help, trying deleting the file. The program will create a new one. --------------------------- ------------------------------------------ ======================================================================== Replacing the flash image file Sometimes the contents of the flash chip (called the flash image) become so fragmented you must replace them. When this happens, a FlashWorks utility displays a message saying there's not enough memory to save the new information. In this case, you must copy a new flash image file to the flash chip. You can copy a new flash image file to the flash chip using one of these programs: _ FLUPDATE _ FLRESTOR (FlashRestore) First, try running FLUPDATE to update the flash image (see CHAPTER 3). If that doesn't work, follow the instructions below. Replacing the flash image file deletes some data entered from some FlashWorks applications and re-enables the FlashStart and FlashSet programs. About replacing the flash image... When you replace the flash image, you will lose FlashVirusProtect's settings and FLVIEW's supplemental information, history log, and saved configuration files. Replacing the flash image 1 Log in to the Intel Bulletin Board System (BBS) and download the flash image file that you need. (For information on accessing the BBS, see the inside back cover.) 2 Copy the flash file and FLRESTOR.EXE to the same directory on a diskette. 3 Insert the diskette into a drive on the workstation, switch to that drive and, at the DOS prompt, type: FLRESTOR /ERASE If the workstation has more than one flash adapter, specify these options: FLRESTOR /TYPE /LOCATION /ERASE Where: /TYPE Indicates the adapter type. Enter one of these parameters: /EE16 for EtherExpress adapters /FL32 for Flash32 adapters /EPRO for EtherExpress PRO adapters /TPRO for TokenExpress PRO adapters If you don't specify the type option, the program restores the flash image file on the first adapter it finds. It searches in the order listed above. /LOCATION Indicates the I/O address or slot number. Use this only if you have two or more of the same types of adapters installed. Enter I/O base address (for the EtherExpress adapters) or EISA slot number (for the Flash32 adapter). For example, if you have two EtherExpress PRO flash adapters and want to restore flash memory on the adapter with I/O base address 310, you would type: FLRESTOR /EPRO /310 /ERASE FLRESTOR copies the flash image file from the diskette to the flash chip. The process takes about 90 seconds. 4 Re-enter erased data in FlashWorks programs. For example, run FLSCAN and then enter supplemental information in FLVIEW. If FLRESTOR says the flash chip is corrupted... Reboot with a DOS diskette (without the drivers loaded), and run FLRESTOR again. Re-enabling FlashStart You can also use FLRESTOR to re-enable the FlashStart program should you inadvertently disable it before connecting to the network. 1 Copy FLRESTOR.EXE from the FLASH directory on the FlashWorks server to a diskette. 2 Insert the diskette into a drive, switch to that drive and, at the DOS prompt, type: FLRESTOR FLRESTOR resets FlashStart so it runs the next time the workstation is turned on. If FlashStart doesn't run, you'll need to erase and replace the flash image by running FLRESTOR with the /ERASE option as described in the preceding section. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <end of file>