
Technical Information
Windows NT v4.0 Unattended Install with Madge Smart 16/4 Ringnodes

REF:			TND161F
AUTHOR:			Desktop Technical Support Group (DTSG)
DATE:			28th May, 1997

NOTE: It is essential that these instructions are followed exactly. If
they are not, Madge cannot guarantee the final results. 

Synopsis
This  document  provides  Madge  customers  with  the  information  to
complete successful  Windows NT v4.0  unattended  installations  using
Madge  Smart 16/4 Ringnodes.

Preparation

* A  Windows  NT  v4.0  distribution  image  needs  to be created from
  which the unattended installation will take place. This is explained
  in step 1 below. 
* The Madge Windows NT driver Mdgmport.sys v2.21 or newer  needs to be
  applied to the Windows  NT distribution image.   This  procedure  is
  explained in step 2 below.
* The  Madge  custom  registry file (SYSTEM) must be applied to the
  Windows NT  v4.0  distribution  image.   The  instructions  for this 
  procedure are given below in step 3.
* A script file called Unattend.txt  contains  the  custom  parameters
  which controls the unattended installation procedure.   Instructions
  for creating this file  are  given  below in step 4,  and an example
  unattend.txt is included at the end of this document.
* Considerations when completing a Windows NT  v4.0 unattended install
  on a machine with PCMCIA Network adapters is covered in step 5.
* Starting  the  Windows  NT v4.0 installation is documented in step 6
  below.
* To create a network boot diskette use the NT 4.0 Client Administrator
  Utility - Make network installation startup disk.
 
Procedure

Step 1 - Creating the NT Image on the distribution server

A  shared  directory  must be created on the distribution server where
the Windows NT v4.0 image  will be stored.   Create a directory on the
distribution server called \nt4image and make this accessible over the
network.

The  Windows  NT  v4.0  CDROM  directory  structure  is  based  on the
processor  architecture  of  the machine to which the install is to be
applied.  The \i386  directory  contains  the  install image for Intel
processor based machines.   To  create an unattended install image for
Intel based machines, the contents of the Windows NT v4.0 CDROM  \i386
directory  should  be  copied to the newly created shared directory on
the distribution server.

Example :  Given the  NT v4.0  CDROM  is drive D: and the distribution
server's shared directory is C:\nt4image.  The copy command is : 

    xcopy d:\i386\*.* c:\nt4image /s/e.


Step 2 -Applying the Madge Network Driver to the Windows NT v4.0 image

The Madge network driver  must be contained in a special sub-directory
of the shared Windows NT v4.0  image  directory  on  the  distribution
server.  This directory is : $oem$\C\Mdgmport\


Example : Given that the shared Windows NT v4.0 image directory on the 
distribution server is : \nt4image

The directory where all the Madge driver files are located is : 

    \nt4image\$oem$\C\Mdgmport\

(This specific path is referred to in the Unattend.txt
[SelectedAdaptersSection] with the parameter  c:\mdgmport)

The  \nt4image\$oem$\C\Mdgmport\  must  be  created  and all six files
included with the Madge Smart Miniport driver Mdgmport v2.21 (from the
Madge Lan  Support  Software (LSS) 5.0(2) release) should be copied to
the \nt4image\$oem$\C\Mdgmport\ directory.

     	\nt4image\$oem$\Mdgmport\Mdgmport.sys
				\Mdgmport.bin
				\Mdgncdet.dll
				\Mdgmpdlg.hlp
				\Mdgmpdlg.dll
				\oemsetup.inf

Step 3  - Applying  the  Madge  Custom Registry File to the Windows NT
v4.0 image.  This step is only required for unattended installations
when the client is using a PCMCIA adapter.  

Copy the file SYSTEM (Found on the Madge Lan Support Software (LSS)
5.0(2) CD-ROM in the \LSS.500\UNATTEND\NT4 directory) to  the  Windows
NT v4.0  distribution  image  directory  and overwrite the file called
System._

Example : Given that SYSTEM has been copied to a:\ then :

    copy a:\SYSTEM  \nt4image\system._


Step 4 - Customising the NT v4 Unattend.txt file
A  sample  Microsoft  unattend.txt  file  can  be  found  in the \i386 
directory  on  the  Windows  NT  v4.0  CDROM.   Sections in the sample 
unattend.txt need to be changed  to  configure  the  system  for Madge
Smart Ringnodes.

The [network] section should look very similar to the following :

[Network]
InstallAdapters = SelectedAdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = Madge

The entry InstallAdapters= specifies the name of the  section  in  the
unattend.txt which  contains  definitions  of  the Network adapters to
be installed. In the above example a section [SelectedAdaptersSection]
must also feature in the unattend.txt.

The  [SelectedAdaptersSection]  is  used  to  explicitly  specify each 
network adapter by name,  where the driver files  are  located and the
section in the unattend.txt which specifies  any  adapter  parameters.

The preferred method is to use auto-detect option.  The 
[SelectedAdaptersSection] and [OEMCardParameters]  for  auto-detect is
below:

[SelectedAdaptersSection]
MDGMPAUTO = OEMCardParameters,C:\Mdgmport

[OEMCardParameters]

Note: the  [OEMCardParameters]  selection is  empty  as  all  the card
resource parameters are found automatically.

The [SelectedAdaptersSection] for a Madge Smart 16/4 PCI (BM) Ringnode
is below:

[SelectedAdaptersSection]
MDGMPPCIBM = OEMCardParameters,C:\Mdgmport

The  entry  OEMCardParameters  in  the above [SelectedAdaptersSection]
specifies the  name  of the section in the unattend.txt which contains
the adapter parameters to be  placed  in  the  Windows  NT v4 registry
for the associated network adapter.

The entry following OEMCardParameters in the above 
[SelectedAdaptersSection] and separated  by a comma is the name of the
directory where the Madge driver files are located.   In  the  example
C:\Mdgmport was used as this is directly referencing the path  
\nt4image\$oem$\C\Mdgmport\ which was created in step 2.

The Madge Smart Ringnode identifier ( in this case : MDGMPPCIBM ) must
match an adapter name from the [OptionsTextENG] section  contained  in
the Madge OEMSETUP.INF.  This adapter name must also correspond to the
Madge Smart Ringnode in  the  destination  machine  (i.e.  The machine
on which the install is being performed ).   An extracted 
[OptionsTextENG] section from the Madge OEMSETUP.INF follows :

[OptionsTextENG]
    MDGMPAUTO  = "Madge Automated Smart Ringnode Installation"
    MDGMPISA   = "Madge Smart 16/4 AT Ringnode"
    MDGMPATP   = "Madge Smart 16/4 AT Plus Ringnode"
    MDGMPATPE  = "Madge Smart 16/4 AT PnP Ringnode"
    MDGMPISAC  = "Madge Smart 16/4 ISA Client Ringnode"
    MDGMPISACP = "Madge Smart 16/4 ISA Client Plus Ringnode"
    MDGMPPC    = "Madge Smart 16/4 PC Ringnode"
    MDGMPEISA  = "Madge Smart 16/4 EISA Ringnode"
    MDGMPMCA   = "Madge Smart 16/4 MC Ringnode"
    MDGMPMC32  = "Madge Smart 16/4 MC32 Ringnode"
    MDGMPSM16  = "Madge Smart 16 Ringnode"
    MDGMPPNP   = "Madge Smart 16/4 ISA Client PnP Ringnode"
    MDGMPPCI   = "Madge Smart 16/4 PCI Ringnode"
    MDGMPPCIBM = "Madge Smart 16/4 PCI Ringnode (BM)"
    MDGMPPCMCIA = "Madge Smart 16/4 PCMCIA Ringnode"

The recommended option is to use the MDGMPAUTO parameter for ALL 
types of Madge Smart Ringnodes.

See the sample Madge Unattended.txt file for an example of the use 
of the driver parameters in the Unattended.txt.


All values specified in the [OEMCardParameters] section are 
automatically placed in the Madge registry key: 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\mdgmportX\Parameters  

where "X" specifies the adapter instance of the Madge Smart  Ringnode.
For every Madge Smart Ringnode the bus  type  and  bus  number  of the
adapter must be specified in the [OEMCardParameters] section.

The list of values for the adapter bus type are :

ISA 	= 	1
EISA 	= 	2
MC 	= 	3
PCI 	= 	5 

As some machines have multiple busses of the same type,  the  instance
of the bus to which  the  Madge  Ringnode is attached must be defined.
In most cases bus  number is zero,  as there is generally only one bus
for each bus architecture in a single machine.  

Below  is  an example [OEMCardParameters] section for the Madge Smart 
16/4 PCI Ringnode(BM):

[OEMCardParameters]
BusType=5
BusNumber=0

Non  PCI  adapters  require  more settings in the  [OEMCardParameters]
section to identify the network adapter's resources.   For  example to
complete an unattended install of Windows NT v4.0  with  a Madge Smart
16/4 AT Plus Ringnode requires the specification of IO  Location,  IRQ
and DMA channel.  The IO location must be specified in decimal  ( E.g.
0a20 = 2592 , 1a20 = 6688 , 2a20 = 10784 ,  3a20 = 14880 Etc. ).  

Below  is  an example [OEMCardParameters] section for the Madge Smart  
16/4 AT Plus Ringnode using DMA channel 1, IRQ 3 and IO location
0a20. 

[OEMCardParameters]
Iolocation=2592
IrqNumber=3
DmaChannel=1
BusType=1
BusNumber=0


Step 5 -  PCMCIA  Network  Adapters  and  Windows  NT  v4.0 Unattended
Install

During the Windows  NT  v4.0  installation  the Microsoft PCMCIA Point
Enabler allows  only  interrupt 10 to be used for PCMCIA devices.   If
you wish to use a different interrupt,  you can but  the  PCMCIA  card
will not be operational during the setup phase.   To  set an interrupt
number other than 10 then use the parameter  InterruptNumber=nn in the
[OEMCardParameters] section (Note:This is different from IrqNumber=nn,
used for ISA adapters).

No interrupt setting  is  required  in the [OEMCardParameters] section
for the Madge Smart PCMCIA Ringnode if you choose to use interrupt 10.
A sample [OEMCardParameters] section for a Madge Smart PCMCIA Ringnode
follows :

[OEMCardParameters]
;Note 768 == I/O 300H
Iolocation=768
BusType=1
BusNumber=0


Step 6 - Starting the Windows NT 4.0 Unattended Installation
For example to start an unattended installation where :

* Drive Z: on the machine  waiting  to  receive  Windows NT, is mapped
  to the \nt4image shared directory on the distribution server.
* The unattend.txt file is located in Z:\

Type the following :

	Z:\>winnt /b /u:z:\unattend.txt /s:z:\ 

/b=setup diskettes are not created
/u=unattended install
/s=location of NT source files

Sample Madge Unattend.txt file


[Unattended]
OemSkipEula = yes
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = winnt
OverwriteOemFilesOnUpgrade = no
KeyboardLayout = "United Kingdom"

[UserData]
FullName = "Desktop System Test"
OrgName = "Madge Networks Ltd"
ComputerName = MADGE-PC
ProductId = "Enter your Product ID here in the form xxx-xxxxxxx"

[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT) Greenwich Mean Time; Dublin, Edinburgh, London"

[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 640
YResolution = 480
VRefresh = 60
AutoConfirm = 1

[Network]
InstallAdapters = SelectedAdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = Madge

[SelectedAdaptersSection]
;Madge Smart Automated 16/4 Ringnode Installation
MDGMPAUTO = OEMCardParameters,c:\mdgmport

;Madge Smart 16/4 PCI Ringnode (BM)
;MDGMPPCIBM = OEMCardParameters,c:\mdgmport

;Madge Smart 16/4 AT Plus Ringnode
;MDGMPATP = OEMCardParameters,c:\mdgmport

;Madge Smart 16/4 PCMCIA Ringnode
;MDGMPPCMCIA=OEMCardParameters,c:\mdgmport

[OEMCardParameters]

;***********
;Madge Smart 16/4 PCI Ringnode (BM)
;PCI Bus uses BusType 5
BusType=5
;This specifies which bus the NIC is on
BusNumber=0
;***********

;***********
;Madge Smart 16/4 AT Plus Ringnode
;Iolocation=2592
;IrqNumber=3
;DmaChannel=0
;ISA Bus uses BusType 1
;BusType=1
;BusNumber=0
;***********

;***********
;Madge Smart 16/4 PCMCIA Ringnode
;BusNumber=0
;BusType=1
;IoLocation=768
;***********


[ProtocolsSection]
NBF = NBFParamSection

[NBFParamSection]


	

