SE_UTIL Distribution Utility

Home Page
Site Contents

SE_UTIL Distribution Utility

SE_UTIL Distribution Utility by Command Software Systems, Inc.

A. Introduction

SE_UTIL updates F-Prot Professional on multiple workstations in a multi-platform environment. The functionality of SE_UTIL is based on the premise that the update software is stored in a centralized shared location and that the workstations are connected to this shared location via a mapped drive on the network.

SE_UTIL requires that its set of utility files be placed in specific directories that are pre-defined. This utility file set can be installed anywhere on the network so long as a drive is mapped to provide access to the location of its primary directory. For example:

System Administrator Pat Doe has a Novell NetWare 4.1 server and wishes to distribute F-PROT Professional to his workstations. Currently, Pat uses Client32 logins and he knows that executing applications in this type of script requires special syntax [see Novell Network section below]. Pat would like to put any utility files installed to his server under a directory called UTILITY which is on a drive mapped as U:. SE_UTIL must be installed at the root, so Pat will map a drive using the MAP ROOT command before performing any installation procedure. For this example, Pat has mapped the drive as S:.

There are two basic functions of the SE_UTIL utility. The first function allows updating of the workstation�s platform of F-PROT Professional (DOS/ Win3.1x, Win95, and WinNT). The second function allows the Network Administrator to update the platform directories on the shared directories on the server.

B. Installing SE_UTIL

  1. Download the SE_UTIL.EXE file and place it in a directory (by itself) on the Administrator's workstation. Do not place this file on the server drive as errors could occur.
  2. In the unique directory where SE_UTIL.EXE has been placed, type SE_UTIL.EXE [ENTER]. This is a self-extracting file that creates the following files:
    • SETTUP.BAT (installation batch file - requires destination drive letter)
    • CROSSPLT.EXE (self-extracting pkzipped file - extracted by a batch file)
    • READ1ST.TXT (an ASCII version of this file)
    • NEW.TXT (features enhanced by this version of SE_UTIL)
    • SE_UTIL.DOC (this file)
  3. Now we are ready to install the utility to the server. Type SETTUP.BAT S: [ENTER] where S: is the mapped drive specified for the SE_UTIL installation.

Behind the scenes:

SETTUP.BAT extracts the file CROSSPLT.EXE to the local directory. It also expands the subdirectories named UPGRADE and UPDATE. Of the two directories created by this expansion, only the files inside the UPDATE directory will be transferred to the specified server drive.

SETTUP.BAT creates the directory path \CSS\ANTIVIR at the server (drive S: ). It copies the contents of the local UPDATE sub-directory to the file server. SETTUP.BAT will also modify the CHECK.BAT (now found in S:\CSS\ANTIVIR\ ) to indicate which drive is being used for the SE_UTIL utility. This is handled via an environment variable setting, SET SERVDR=S: (or whatever drive letter is being used for the installation).

SETTUP.BAT will create the product directories as well as the product-update directories. The product directory will contain a full product version of F-PROT Professional. The product-update directory will contain only the update files received or downloaded from the Command Software System software libraries on the FTP/WEB/BBS sites.

Hint: The file server must be a mapped drive letter to which users have access. Use the MAP ROOT command to create this mapping if security measures do not allow placing the server copy in the root of the available server drives.

C. Updating the Server

Method 1: Using Diskette Set

Change into the UPGRADE directory on the Administrator�s workstation and type:

      UPGRADE {server} {source drive letter} [ENTER]


This will ask for the F-PROT installation diskette(s). The command copies the appropriate files to the specified directory on the server.

Method 2: Using Product Downloads (FTP ,Web or BBS)

  1. After downloading F-PROT to the local machine, place the downloaded copy into a working directory, preferably one assigned to this task. Then, extract the file by typing its self-extracting file name. Note: if the file has a "zip" extension, you will need to use an unzipping utility such as Pkunzip or WinZip.
  2. After extraction, locate the file named ONEDISK.BAT. This file is used for file placement into the specified directory on the file server. At the DOS command line, run the ONEDISK command as in ONEDISK S:\css\antivir\fpw95 [ENTER]. A table of platforms that you can substitute into the command line per operating system is listed below:
    	F:\CSS\ANTIVIR\FPW		F-PROT for DOS/Win3.x
            	F:\CSS\ANTIVIR\FPW95	F-PROT for Win95
            	F:\CSS\ANTIVIR\FPWNT	F-PROT for WinNT
  3. If you are downloading updates to the platform products, this file set should be placed in the directories associated with their respective platform. These directories are listed below:
    	F:\CSS\ANTIVIR\FPW95UD	F-PROT for Win95 update file
            	F:\CSS\ANTIVIR\FPWNTUD	F-PROT for WinNT update file

D. Testing the update process

To test the updating procedure, change into the S:\CSS\ANTIVIR directory on the server and type:

This will examine your workstation and install the appropriate software. If this test works properly, the administrator can place this command in the Netware login script.

E. Novell NetWare Setup Considerations

The CHECK.BAT file is designed to run within a login script. To use it, place the following command in the login script:

If using NetWare Client32 to connect to a Novell NetWare 4.1 server, use the following syntax instead. Remember NOT to indent this line in the login script:

F. Windows NT Network Setup Considerations

SE_UTIL is designed for Novell NetWare login scripts. However, it can also be implemented on an NT Network. SE_UTIL requires that a mapped server drive be used. Mapping can be accomplished using a command like the one below:

       	net  use  S:  \\NTMAIN\NT40    �-- this syntax varies depending on actual name
All workstations affected should have the same mapped drive prior to use of the SE_UTIL distribution utility. Once this mapping been established, the other properties involved fall into place.

Edit the NT login script to indicate the following syntax:

	NET USE S: \\NTMAIN\NT40		�-- this syntax varies depending on actual name
Running the CHECK.BAT file through the NT login script has resulted in two reported anomalies:
  1. If the user is already running a copy of F-PROT Professional for Windows 3.1, the user may get an error message stating that an existing version of F-AGENT is active. This is because Windows 3.x users already have DVP (Dynamic Virus Protection) running when they log in to the NT system. Unlike the F-Prot Professional setup program, CHECK.BAT does not turn off the DVP. Restarting Windows will eliminate this message.
  2. If the user did not have a copy of F-PROT Professional running on the workstation, the user may get the error message that DVP could not be run as the device driver has not been loaded. As in the above instance, Windows is running when one logs on to the NT server. As a result, the system has already loaded the device drivers listed in SYSTEM.INI. CHECK.BAT adds the device line. However, an attempt to run DVP in the current Windows session would result in aforementioned error message. Again, a restart of Windows would eliminate the error message.

G. Automating Windows 95 and Windows NT Installations

The Windows 95 and Windows NT installations are actually handled by the SETUP.EXE file within the \css\antivir\fpw95 and \css\antivir\fpwnt directories. The SETUP.EXE file uses an initialization file called SETUP.INI. This file can be edited and the administrator can change some of the values registered to create customized installations using SE_UTIL techniques. Unless the .ini file is modified, a user-interactive installation will occur.

Here are suggestions of allowable modifications to the SETUP.INI file that will aid in a silent installation.

  1. Modify value InstallSilent=YES original value NO
  2. Modify value MakeRescueDisk=NO original value YES
  3. Modify value LaunchReadme=NO original value YES
  4. Modify value LaunchFPROT=NO original value YES

H. Automating DOS/Windows 3.1x Installations

By default, the DOS/Win3.1x product is installed automatically. That product installs real-time protection for both the DOS and Windows 3.1x environment. Using a file called SECONFIG.BAT allows you to modify the way SE_UTIL installs the DOS/Win3.1x client applications. SECONFIG.BAT asks several configuration questions regarding how this version of F-PROT Professional can be installed to the client.

I. Support

Further information regarding the SE_UTIL deployment utility and its components is available as part of the README.BAT file. Additionally, the Technical Support Department at Command Software Systems will be happy to provide you with assistance regarding the use of SE_UTIL. Contact Command Software here.

J. Common Questions

  1. I�ve installed SE_UTIL properly but when I test the installation and manually run CHECK.BAT, I keep getting an "Out of environment space" error message. What gives ?

    COMMAND.COM requires environment space to store variables. If enough space is not specified, this error message will appear. Increasing the environment space will be required. If this is Windows for Workgroups (WFWG) 3.1x, use PIF Editor and edit the DOSPRMPT.PIF file to include enough space for the environment. Add /E:1024 on the "Optional Parameters" line. For Windows 95, edit the properties for the MS-DOS Prompt icon and add /E:1024 to the end of the CMD LINE entry.

  2. I want to create an icon in Windows 3.1x to run CHECK.BAT. When I create one and double- click on it, I get an "out of environment space" error message. What should I modify?

    In the program group of your choice, place the icon that will reference CHECK.BAT. Then, select FILE and choose NEW ITEM. Fill in the following values:

    Item name:		CHECK
    Command line:		c:\ /e:1024 /c s:\css\antivir\check.bat
    Working Directory: 	s:\css\antivir
    The above example assumes that the file location for CHECK.BAT is on the S: drive: use the correct drive letter for your system in this command.

  3. I want to create an icon on the Windows 95 desktop to run CHECK.BAT. When I create one and double-click it, I get an "Out of environment space" error message. What should I modify?

    On a blank area of the desktop, click the right mouse button and select NEW, then choose SHORTCUT. Use the BROWSE button to locate CHECK.BAT. After finding CHECK.BAT, click OPEN and then choose NEXT. Type a name for the shortcut, CHECK, and click FINISH. Next, right-click on the icon you just created and choose PROPERTIES. Select the PROGRAM tab and fill in the following values:

    Item name:		CHECK
    Cmd line:		s:\css\antivir\check.bat
    Working:		s:\css\antivir
    Batch file:		
    Run:			Normal
    [x]  Close on exit
    The above example assumes that CHECK.BAT is on the S: drive: be sure to substitute the correct drive letter for your system. Next, select the MEMORY tab and enter the following values:
    	Total: 			400
    	Initial Environment: 	Auto
  4. I�ve put the syntax to run SE_UTIL within the login script but now it is hanging. One error message I am seeing is "MPR not responding". What might be causing this ?

    MPR is an acronym for Multi-Protocol Router. It is installed routinely when Windows 95 is placed on your system. When connecting to a Novell NetWare 4.1x server with Client32 running, it was discovered that there was a syntax problem that could cause this error if SE_UTIL was being used in the login script. The original syntax was:

    	#command /e:1024 /c s:\css\antivir\check.bat
    To correct the problem and eliminate the error, change the above syntax by substituting @ for the # symbol as follows:
    @command /e:1024 /c s:\css\antivir\check.bat