Is there any manual for BINL?
Guide for BINL server
#1
Posted 05 September 2014 - 06:42 PM
#2
Posted 05 September 2014 - 06:45 PM
Here below a quick "how to pxe boot xp installation thru RIS" to from here :
1-enter startrom.0 as boot filename
2-put winnt.sif as unattended installation file in root folder (see example in zip file)
3-put ntldr (renamed setupldr.exe), ntdetect.com in root folder
4-share the root folder (windows shared, nullsessions enabled) containing a subfolder XP (installation cd files)
5-extract all inf files from lan driverpacks to INF folder in root folder (OR else use a nics.txt file)
6-extract all sys files from lan driverpacks to XP\I386 folder in root folder
#3
Posted 06 September 2014 - 06:21 AM
is it possible to have hardcoded paths for these drivers? Like Driver\INF and Drivers\SYS
#4
Posted 06 September 2014 - 07:44 AM
is it possible to have hardcoded paths for these drivers? Like Driver\INF and Drivers\SYS
i can think of adding a parameter in config.ini if this is what you mean.
#5
Posted 06 September 2014 - 09:11 AM
Yes that would be awesome, instead of putting all the drivers in every WinXP source one folder would neatly do.
#6
Posted 06 September 2014 - 11:13 AM
Not that about the path to the drivers fodler (i386), i cannot alter it :this path is set thru the winnt.sif (see below).
What I would propose is to hardcode the path to the inf folder next to the i386 folder.
This way you have your pxe/tftp root folder containing the following :
-XP
-XP\I386
-XP\INF
-winnf.sif
-startrom.0
-ntdlr
-ntdetect.com
[data] floppyless = "1" msdosinitiated = "1" ; Needed for second stage OriSrc = "\\192.168.1.248\pxe\XP\i386" OriTyp = "4" LocalSourceOnCD = 1 DisableAdminAccountOnDomainJoin = 1 [SetupData] OsLoadOptions = "/fastdetect" ; Needed for first stage SetupSourceDevice = "\Device\LanmanRedirector\192.168.1.248\pxe\XP" [RemoteInstall] ; Avoid automatic format/repartition Repartition = No UseWholeDisk = No [UserData] ComputerName = * ;ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
#7
Posted 06 September 2014 - 07:53 PM
The only thing that BINL looks for is *.sys files, wouldn't be possible to intercept the files according to INF or by NCQ request?
#8
Posted 06 September 2014 - 08:47 PM
The only thing that BINL looks for is *.sys files, wouldn't be possible to intercept the files according to INF or by NCQ request?
This what TPS is doing already : get an NCQ request containing a VID & PID, go thru inf files, send back a driver filename, instructing windows setup to download it and continue the installation.
#9
Posted 07 September 2014 - 04:18 PM
FYI, the latest TPS version can skip the INF folder parsing provided that you have a nics.txt in the root folder (i.e, next to startom.0).
The nics.txt should look like the below :
1022 2000 pcntpci5.sys PCnet 10b7 6055 EL556ND5.sys EL556ND5 10b7 6056 EL556ND5.sys EL556ND5 8086 100E e1000325.sys E1000
The drivers still need to be in the folder mentionned by winnt.sif
#10
Posted 07 September 2014 - 04:46 PM
Awesome this is much easier to use since you don't actually put all inf files in every xp source i have.
Just like shepya's binl server.
#11
Posted 07 September 2014 - 05:09 PM
Glad it helps
I have updated my 1st post above to reflect this last change in the howto.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users