Strange NETBIND problem :(

[Martin Zugec]

I am using network installation...

Long time ago I decided choosing NIC in menu is not the professional way and I wanted to automate it.

BUILD 0005

---------------------------------------------------------------------------------------------

I used PCIscan, take Vendor and Product number, find the product in .map file.

Now I know the NIC (for example E1000 or b57). This value is stored in pci0 variable.

Then I copy %pci0%.dos driver to Net directory.

The copy system.ini and protocol.ini to Net directory (for example for E1000 there R 2 files: pe1000.ini and se1000.ini. I used "Copy s%pci0%.ini z:\net\system.ini)

----------------------------------------------------------------------------------------------

In build 0006 I changed only one thing - I am not copying protocol and system.ini files, instead I am changing values inside: from ***NIC*** to %pci0%.

Protocol.ini and system.ini FILES R EXACTLY THE SAME as before!!!

But when I run installation, I got error from netbind:

Error: 33 Unable to bind

I appreciate any suggestions

[mattofak]

I may be mistaken, but i think that setup is thinking that %pci0% is now a command instead of a comment or section header. If it now thinks that its not a comment then its like well what do i do here, and cancels, if it thinks that its now a section header, it cannot recognise the device, ie: doesnt know that this is a nic you are trying to install so it cannot bind to it...

Now, i may be completly wrong, but thats what it sounds like to me...

[Martin Zugec]

Thx for reply... Build 0005 is working - no problem at all.

Only thing, that is not working is build 0006 - and the files protocol.ini and system.ini R the same, only one difference is how R they generated! So I know using %pci0% is all right (I use alter.exe protocol.ini "***NIC***" %pci0%, so it only replace string ***NIC*** with value of variable)

[mattofak]

Did you change your hardware or anything, the NIC card you're using might need different driver files, or it might need the native drivers for the platform you're installing.... (i wouldnt think so, but...)

However, are you sure that the files are the same, bit for bit? And are you sure that when you auto generate the files that you're copying the right drivers over? It might be a little strange to the system having the right named device in the ini, but not the right instructions...

Also, i've looked through my collection of nic drivers and i cannot find any literal string "***NIC***", so I'm curious, why do you think it needs to be changed?

[EDIT]

Ah, wait, are you trying to say that you are using the same driver ini's/inf's for all cards and simply changing the named device?

[Martin Zugec]

Ok, I will try to show difference between 0005 and 0006 including files and batch code:

0005

1.) NIC identificator is generated and saved to variable pci0:

%ramd%\files\pciscan.exe %ramd%\files\ndis.map > nul

2.) device is loaded to memory:

%ramd%\files\device %ramd%\files\ifshlp.sys > nul

3.) Protocol.ini and system.ini R copied from ini folder to net folder. In ini folder they R named by NIC identifier, e.g. E1000 protocol.ini files is pe1000.ini:

type %ramd%\ini\p%pci0%.ini > %ramd%\net\protocol.ini

type %ramd%\ini\s%pci0%.ini > %ramd%\net\system.ini

4.) Random computer name is generated:

%ramd%\NET\COMPNAME.EXE > nul

5.) String **COMPUTERNAME** is changed to generated name in system.ini:

%ramd%\NET\alter.exe %ramd%\net\system.ini "**COMPUTERNAME**" "%compname%" > nul

6.) Network connection is established...

System.ini

[network]
filesharing=no
printsharing=no
autologon=yes
computername=**COMPUTERNAME**
lanroot=z:\NET
username=instal
reconnect=no
dospophotkey=N
lmlogon=1
logondomain=DOMAIN
preferredredir=basic
autostart=basic

[network drivers]
netcard=e1000.dos
transport=tcpdrv.dos,nemm.dos
devdir=z:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=z:\NET\Share000.PWL

Protocol.ini

[network.setup]
version=0x3110
netcard=ms$e1000,1,MS$e1000,1
transport=tcpip,TCPIP
lana0=ms$e1000,1,tcpip

[ms$e1000]
DRIVERNAME=e1000$

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[tcpip]
NBSessions=6
DefaultGateway0=0 0 0 0
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$e1000
LANABASE=0

0006

1.) NIC identificator is generated and saved to variable pci0:

%ramd%\files\pciscan.exe %ramd%\files\ndis.map > nul

2.) device is loaded to memory:

%ramd%\files\device %ramd%\files\ifshlp.sys > nul

3.) String **NIC** is changed to %pci0%:

%ramd%\NET\alter.exe %ramd%\net\protocol.ini "**NIC**" "%PCI0%" > nul

%ramd%\NET\alter.exe %ramd%\net\system.ini "**NIC**" "%PCI0%" > nul

4.) NIC driver is copied to NET folder:

copy %ramd%\NIC\%pci0%.dos %ramd%\net\%pci0%.dos > nul

5.) Random computer name is generated:

%ramd%\NET\COMPNAME.EXE > nul

6.) String **COMPUTERNAME** is changed to generated name in system.ini:

%ramd%\NET\alter.exe %ramd%\net\system.ini "**COMPUTERNAME**" "%compname%" > nul

6.) Network connection is established...

System.ini

[network]
filesharing=no
printsharing=no
autologon=yes
computername=**COMPUTERNAME**
lanroot=z:\NET
username=instal
reconnect=no
dospophotkey=N
lmlogon=1
logondomain=DOMAIN
preferredredir=basic
autostart=basic

[network drivers]
netcard=**NIC**.dos
transport=tcpdrv.dos,nemm.dos
devdir=z:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=z:\NET\Share000.PWL

[network.setup]
version=0x3110
netcard=ms$**NIC**,1,MS$**NIC**,1
transport=tcpip,TCPIP
lana0=ms$**NIC**,1,tcpip

[ms$el90x]
DRIVERNAME=**NIC**$

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[tcpip]
NBSessions=6
DefaultGateway0=0 0 0 0
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$**NIC**
LANABASE=0

[mattofak]

i do believe this is your problem...

[ms$el90x]
DRIVERNAME=**NIC**$

the section header is still identifying a NIC i think it should probably be

[ms$**NIC**]
DRIVERNAME=**NIC**$

or am i just misreading your code?

[Martin Zugec]

Ah, how stupid I can be I saw this code at least 100 times and didnt notice

THX for your help, it is true that other people see what we dont