
Technical Information
Windows 95 Unattended Install with Madge Smart 16/4 Ringnodes

REF:			TND164D	
AUTHOR:			Desktop Technical Support Group (DTSG)
DATE:			29th May, 1997

NOTE: It is essential that these instructions  are  followed  exactly.
Otherwise Madge cannot guarantee successful unattended  installations.

Synopsis
This  document provides Madge customers with the information necessary
to enable  successful  Microsoft  Windows 95  Unattended Installations
using Madge Smart 16/4 Ringnodes. 

Currently this procedure does  not support the Madge Smart 16/4 PCMCIA 
Ringnode because card services  is started too late in the install for 
the  card  to be operational.  This affects  all vendors PCMCIA cards. 
It  is  recommended  that  portable users copy all of the CAB files to 
the hard disk and install  with  an install script. This has the added
advantage of allowing the user to change their setup later, as the CAB
files remain on  the  hard  disk.

Installation can be  performed from a  Windows 95  image stored  on  a
NetWare  server  or  Microsoft  share.   The  hard  disk of the target
workstation is formatted prior to installation of Windows 95.

Madge Software Required
1. A self-extracting .Exe file  Mdgskel.Exe  provides the Madge  files
   necessary  for Windows  95  unattended  installation for NetWare or
   Microsoft share.  This  is available in the \LSS.500\UNATTEND\WIN95
   directory  of  the Madge Lan Support  Software (LSS) 5.0(2) CR-ROM. 

Some of the software required on  the installation floppy disk must be
obtained from Novell or Microsoft.  The  appendices at the end of this 
document  provides  instructions  to  build an  installation disk from 
either a Microsoft share or NetWare server.



Installation Procedure Outline
1. A  Windows 95  distribution image is created on a Microsoft network
   share or NetWare Server from which the installation will take place.

2. Madge device drivers are  added  to  the  Windows  95  distribution
   image.

3. Madge utility software is  added  to  the  Windows  95 distribution
   image.

4. The Madge sample Windows 95 unattended installation floppy  disk is
   customized.

5. A target  workstation  is  booted  from the floppy disk to commence
   installation.

Procedure

1.  Creating the Windows 95 distribution image

From a Windows 95 workstation,  attach  a  drive  to the network share
directory on which you wish to install the Windows 95 image.

Run the NetSetup.exe program found on the Windows CD in directory : 
\admin\nettools\netsetup.   Set  the  path  to  where  the  Windows 95
distribution image will  reside and select an Install policy of shared
files residing on the local hard disk.  This will place a distribution
image of Windows 95 into the shared directory.


2.  Applying Madge device drivers to the distribution image

Create  a  Madge  Unattended  Install  Disk  for  Installation  from a
Microsoft Share  following  the  instructions in Appendix A or a Madge
Unattended  Install  Disk  for  Installation  from  a  Netware  Server
following the instructions in Appendix B. 
This  disk  will  be  referred  to  as  the  Madge  sample  Windows 95
unattended installation floppy disk.  

Windows 95  is  currently  shipping  with old versions of Madge device
drivers. To  update  all  instances  of  the  old Madge device drivers
requires the use of Infinst.exe which is found on the Windows 95 CD in
directory: 

\Admin\Nettools\Netsetup.   

When  Infinst.exe  prompts  for  an  INF   file, you must  select  the 
Netmadge.inf from the directory \drivers,  on the Madge sample Windows
95 unattended installation disk just created.


3.  Applying Madge utility software to the distribution image

Copy the contents of the directory:  \Imgroot,  from the Madge  sample
Windows 95 unattended installation  disk to the root of the Windows 95
distribution image.


4.  Customising  the Madge sample Windows 95  unattended  installation
floppy disk

The  Madge sample Windows 95 unattended installation disk  needs to be
customized before  an  install can take place.   The  following  files
require modifications:	
      \Autoexec.bat
      \Net\System.ini  (for install from a Microsoft share only)
      \Samples\Msbatch.inf or \Samples\NetWare\Msbatch.inf


4.1  Editing the \Autoexec.bat
At  the top of the \Autoexec.bat there are  three  DOS SET environment
variables:

DestDrv =  This  must  be set to the drive  which will receive the new
           Windows 95 installation, at default this is set to "C:".

Machine =  This  must  be set to the machine  name of the server which
           stores the Windows 95 distribution image.

Share =    If the install is from a Microsoft share,  this must be set
           to the share name on the server which contains  the Windows
           95 distribution  image.   For installation  from a  NetWare
           server  the  variable  should  be  set  to  the  volume and 
           directory containing the distribution image.   For  example
           SYS:DISTRIB\95IMG.

4.2  Editing the \Net\System.ini 

Editing  of  System.ini  is  not  required  if  installation is from a
NetWare server.

At  the  top  of  the \Net\System.ini  there are four settings clearly
marked for customisation.  These four settings are standard System.ini
directives used by Microsoft's Net.exe.  The four settings are :

      Username=
      Workgroup=
      Logondomain=
      Computername=

Note :  Only one  machine  can be present on the network with the same
Computer name.

4.3  Editing the sample Msbatch.inf files
Two sample working unattended  install files are provided on the Madge
sample Windows 95 unattended install disk. The two disks differ in the
type of client to be installed on  the  target  workstation.   For  an
installation from a Microsoft share the Client for Microsoft  Networks
vredir, is used.  For an installation from a NetWare server the Client
for NetWare Networks nwredir,  is used.

\samples\msbatch.inf           Installs vredir for a Microsoft Network
\samples\NetWare\msbatch.inf   Installs  nwredir for a NetWare Network

Edit the  appropriate  file  for  your environment as indicated by the
comments within the file.

Key parameters are  commented  explaining  their  functionality.   For
further information consult the Windows 95 Resource kit.

The  file  may  be  customized  to  meet the needs of your environment
providing changes are not made to Madge specific lines.


5.  Starting the Installation
Insert the customized Madge  sample Windows 95 unattended installation
floppy disk into the client machine and then boot from the floppy disk.

Prior  to  formatting the  hard disk a menu will be displayed allowing
the format to be cancelled.  To suppress this menu,  you  may edit the
config.sys on the boot floppy and uncomment the lines indicated in the
file. 



Appendix A -  Creating a  Madge  sample  Windows 95 Unattended Install
Disk for Installation from a Microsoft Share

Preparation - What you need...
1. One Blank 3.5" HD floppy disk.
2. A working Windows 95 installation.
3. A working Windows v3.11 installation using Microsoft's  Net.exe for
network connectivity.
4. The Mdgskel.exe file from  Madge Lan Support Software 5.0(2) CD-ROM
in the \LSS.500\UNATTEND\WIN95 directory.
5. Pkzip.exe and Zip2exe.exe, or functionally similar tools.


Procedure - Build Instructions
Step 1 - Format  a  3.5"  HD  floppy  disk  and  make  it a Windows 95 
System/boot disk. E.g. From a Windows 95 command prompt type : 

   Format a: /s

Step 2 - Remove  the  hidden,  system  and  read only attributes  from
drvspace.bin and delete it from the root of the new diskette. 

Step 3 - Insert the disk created under step 1,ensure that the skeleton
disk file  (Mdgskel.Exe  from  the  Madge  Lan  Support Software (LSS)
5.0.(2) CD-ROM in  the LSS.500\UNATTEND\WIN95 directory) is accessible
on another drive (In the  example  below the root of  the 'C' drive is
used).  Type the following to expand  the  skeleton file to the floppy
disk :

   a: <Enter>
   cd \ <Enter>
   c:\Mdgskel.exe -d <Enter>

Step 4 - Copy the following files from a  Windows  95   machine to the
\DOS directory on  the  floppy  disk.   The  following  files  can  be
found  in  the  \Windows\Command  directory  on  a  typical Windows 95
machine.

   Emm386.exe
   Himem.sys
   Format.com

Step 5 - Copy  Ifshlp.sys  from  a  Windows  v3.11 machine to the \NET
directory on the floppy disk.

Step 6 - Compress   the   following   files   into  a  self-extracting
executable called Msnet.exe.   All  the  files must be obtained from a
Windows v3.11 installation.

   Wfwsys.cfg
   Ndishlp.sys
   Protman.dos
   Net.msg
   Net.exe
   Protman.exe

One  method  by  which  this can be achieved is to copy these files to
an empty directory.   Use Pkzip.exe  to  compress  all  the files to a
standard ZIP file called Msnet.zip.   Then execute Zip2exe.exe on  the
newly created ZIP file.  The self-extracting compressed Msnet.exe must
then be copied to the \NET directory on the floppy disk.


Appendix B - Creating  a  Madge  sample  Windows 95 Unattended Install
Disk for Installation from a NetWare Server

Preparation - What you need...
1. One Blank 3.5" HD floppy disk.
2. Up  to  date  Novell  DOS  client  files.  Including IPXODI.COM and
appropriate VLM files (see below).
3. A working Windows 95 installation.
4. The Mdgskel.exe file from Madge Networks.
5. Pkzip.exe and Zip2exe.exe, or functionally similar tools.


Procedure - Build Instructions
Step 1 - Format  a  3.5"  HD  floppy  disk  and  make  it a Windows 95 
System/boot disk. E.g. From a Windows 95 command prompt type : 

   Format a: /s

Step 2 - Remove  the  hidden,  system and  read  only  attributes from
drvspace.bin and delete it from the root of the new diskette. 

Step 3 - Insert the  disk created under step 1,  ensure that the Madge
skeleton  disk  file (Mdgskel.Exe from  the Madge Lan Support Software
(LSS)  5.0.(2) CD-ROM  in  the  LSS.500\UNATTEND\WIN95  directory)  is
accessible on another drive  (In the example below the root of the 'C'
drive is used).  Type the following to expand the skeleton file to the
floppy disk :

   a: <Enter>
   cd \ <Enter>
   c:\Mdgskel.exe -d <Enter>

Step 4 - Copy  the  following  files  from  a  Windows  95  machine to
the \DOS directory on  the  floppy  disk.   The  following  files  can
be found in the  \Windows\Command  directory  on  a typical Windows 95
machine.

   Emm386.exe
   Himem.sys
   Format.com

Step 5 - Copy  Ifshlp.sys  from a Windows v3.11 machine  to  the  \NET
directory on the floppy disk.

Step 6 - Compress  up  to  date  copies  of the following files into a 
self-extracting executable called  Nwnet.exe.   All the files  can  be
obtained from Novell:-

   Lsl.com 
   Route.com  (If source routing is required)  
   Ipxodi.com 
   Vlm.exe  
   Auto.vlm  
   Security.vlm  
   Rsa.vlm  
   Redir.vlm  
   Pnw.vlm  
   Nwp.vlm  
   Nmr.vlm  
   Nds.vlm  
   Ipxncp.vlm  
   General.vlm  
   Fio.vlm  
   Conn.vlm  
   Bind.vlm  
   Tran.vlm  

One method  by  which  this  can be achieved is to copy these files to
an empty directory.  Use  Pkzip.exe  to  compress  all  the files to a
standard ZIP file called Nwnet.zip.   Then execute Zip2exe.exe on  the
newly created ZIP file.  The self-extracting compressed Nwnet.exe must
then be copied to the \NET directory on the floppy disk.


Appendix C - Known issues for Unattended installations

1. Outline of problem:-
When using an EISA card with a Locally Administered Address,  the LAA
setting is correctly read by the unattended install process but the 
default value ("") ends up in the registry when the install completes.

This problem was not seen on a Smart 16/4  AT+

Solution:-

A Madge utility REGPOKE.EXE can be used to explicitly assign unique
settings in the Msbatch.inf. (this utility is available on request by
contacting Madge Technical Support)
 

1 - When using a  Smart 16/4 ISA client PnP, PCI or PCMCIA adapter and
specifying Parameters for the ringnode using RegPoke.exe, then Windows
95 does not permit any adapter settings to be explicitly specified in
the Msbatch.inf  for any manufacturers PnP, PCI or PCMCIA adaptrers. 
Default values can be set in the Netmadge.inf on the server,  however
this is of no use for machine unique setting like LAAs (Hence all
machines running the install would receive the same LAA. ). 

The utility RegPoke.exe works around all these problems and thus adapter
settings can be set up in the Msbatch.inf.

Steps;
1  As part of your install copy RegPoke.exe to your machines hard disk,
i.e Make the copy an integral part of the autoexec.bat for your unattended 
install boot disk.

2  In your Msbatch.inf create an install section if one does not already
exist. e.g.
[install]

3  Add the following line to the install section : AddReg=Madge.Regpoke

		[install]
		AddReg=Madge.Regpoke

4  Create a new section in your Msbatch.inf :

		[Madge.Regpoke]

5  In the [Madge.Regpoke] section a line can be added to run RegPoke.exe
at the end of the unattended install.  An example of how to set an LAA of
400000000000 with RegPoke.exe residing in the root of the local hard disk
is shown below.

[Madge.Regpoke]
HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce,"Regpoke",,
"c:\regpoke 400000000000"

RegPoke.exe can be used to set and create any value in the Windows 95/NT
registry using the full set of command line parameters 
(Eg. Thus you can set Maximum Frame Size etc. ). Running RegPoke.exe with
one command line parameter defaults to setting an LAA for a Madge 
Smart 16/4 adapter under Windows 95 only.  

Please note RegPoke.exe is not a release tested product and is used at 
customers own risk.



Appendix C - Known issues for Unattended installations

2. Outline of problem:-

The Customer is not using DHCP.  They have an MSTCP section in their 
MSBATCH.INF but after the install is complete there are no IP settings 
and  DHCP is enabled.

Cards affected - Any PCI or PnP card.

Solution:-

Microsoft have fixed this with the release of  new NETDI.DLL and 
NETDEF.INF files.  These files should be obtained from Microsoft 
and applied to the image according to the instructions provided.

Madge has tested this fix with the following versions:-

NETDI.DLL     dated 19/3/96   284672 bytes    
NETDEF.INF   dated 19/3/96   10846 bytes

TND164D     29th May 1997

