Update scenario on Windows 95 platform

This section describes the necessary steps to update the code of the TME 10 Netfinity Server V4.0 from any prior modification level to the latest one.. Only update from level 2 to 3 has been tested, and while updates from other level have not been verified, it is applicable.

Limitation

• The AUTOEXEC.BAT file can not have row longer than 124 characters.
• On preparation site the latest modification level has to be installed

How to perform the update on Windows 95

• The first one is to copy all product files
• The second one is to update the configuration file
• The third one is to copy the mouse and keyboard drivers on WIN95/SYSTEM

dir /s /b

redirecting the output in a file with the extension .dir. Delete from this list the configuration file as written in the READ.ME file released with the refresh 3 (you can find this READ.ME under CLIENT95 directory).

ALACTION.INI
PROFILES.INI
CUMULLOG.LOG
PROFILE. PRF
SECIN.INI
SERGUWIN.ERR
SERMODEM.DAT
SERCALL.DAT
SYSINFO.RPT
SYSINFO.HST
MONSCH.INI
MONTHR.INI
MONGUI.INI
MONDATA.INI
PROFILE.DAT
MONCRITF.INI
KARAT.INI
NVDM.CFG
SWPRO\NVDMUPD.*
WORK\*.*
SERVICE\*.*

Then write the rest of the file following the example below:

GLOBAL NAME: NFS.REF.4.0.3
DESCRIPTION: NetFinity Server CLient Windows 95
CHANGE FILE TYPE: GEN
COMPRESSION TYPE: LZW
DEFAULT TOKEN: TargetDir=D:\SVIEWW95
OBJECT: SOURCE
NAME: D:\SVIEWW95\WINV.PKG
TARGET NAME: $(TargetDir)\WINV.PKG
TYPE:FILE
ACTION: COPY
INCLUDE SUBDIRS: NO
OBJECT: SOURCE
NAME: D:\SVIEWW95\NETFINP.PKG
TARGET NAME: $(TargetDir)\NETFINP.PKG
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO
OBJECT: SOURCE
NAME: D:\SVIEWW95\DCAF.PKG
TARGET NAME: $(TargetDir)\DCAF.PKG
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO
OBJECT: SOURCE
NAME: D:\SVIEWW95\INST.PKG
TARGET NAME: $(TargetDir)\INST.PKG
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO

Sample profile.1

The file crepro.exe included in a UPDV403.ZIP file and released with this document will allow you to write this profile.

Run it in this way:

crepro outfile "product dir"

where outfile is the file previously generated by dir /s /b

GLOBAL NAME: NFS.STEP.1.REF.4.0.3
DESCRIPTION: NetFinity Server CLient Windows 95
CHANGE FILE TYPE: GEN
COMPRESSION TYPE: LZW
POST-INSTALL: DPFUPD.EXE /MOD:$(TargetDir)\DPFUPD.MOD
DEFAULT TOKEN: TargetDir=D:\SVIEWW95
OBJECT: SOURCE
NAME: D:\SVIEWW95\DPFUPD.MOD
TARGET NAME: $(TargetDir)\DPFUPD.MOD
TYPE: FILE_WITH_TOKENS
ACTION: COPY

Sample profile.2

The file DPFUPD.MOD is included in the UPDV403.ZIP file released with this document.

GLOBAL NAME: NFS.STEP.2.REF.4.0.3
DESCRIPTION: NetFinity Server Client Windows 95
CHANGE FILE
TYPE: GEN
COMPRESSION TYPE: LZW
DEFAULT TOKEN: BootDir=C:\WIN95
OBJECT: SOURCE
NAME: C:\WIN95\SYSTEM\EQNMOUSE.DRV
TARGET NAME: $(BootDir)\SYSTEM\EQNMOUSE.DRV
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO
OBJECT: SOURCE
NAME: C:\WIN95\SYSTEM\EQNVKB95.VXD
TARGET NAME: $(BootDir)\SYSTEM\EQNVKB95.VXD
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO
OBJECT: SOURCE NAME: C:\WIN95\SYSTEM\EQNCOMM.DRV
TARGET NAME: $(BootDir)\SYSTEM\EQNCOMM.DRV
TYPE: FILE
ACTION: COPY
INCLUDE SUBDIRS: NO

Sample profile.3

After you have prepared these profiles, check if the connection with the server is up. From any command prompt on preparation site, run the command:

nvdm start

to start the Software Distribution Agent on preparation site.

To catalogue the profiles, run the commands below:

nvdm bld profile.1

nvdm bld profile.2

nvdm bld profile.3

To see if the profile have been catalogued correctly, from any command prompt on the server type:

nvdm ls "global name"

Where global name is in GLOBAL NAME section of the profile. After that, you can perform from the server the upgrade

of the code at the latest service level in activate area.

nvdm inst "global_name_1" -w "workstation name" -n -vs -f

Where workstation name is the name of the client you want to upgrade (i.e., nvdm lstg from the server).

Then run the activate to install the product from the service area to the activate area.

nvdm act -w "workstation name"-f

Then:

nvdm inst "global_name_2" -w "workstation name" -f

For the second profile you don't need to install the code in service area, this because this profile run a simple command and it doesn't need to be installed in service area. Then:

nvdm inst "global_name_3" -w "workstation name" -n -vs -f

in the end:

nvdm act -w "workstation name" -f