Thanks for your answer 
I've already read this page (http://oss.netfarm.it/guides/), and I've already read the howto. And it didn't worked.
With all due respect I doubt it.
That guide has helped to RIS install more Windows XP's that you can imagine, and the other guide you found and cited:
http://www.promodus.net/linuxris/actually uses Sherpya's tools.
* Can it be a path problem ??
Yes, of course it can, but unless there is an error message of some kind (or a reported "strange" behaviour) it's really hard to say.
* There is a mistake at the step 6?
This:
cabextract ${TFTPROOT}/cdrom/i386/driver.cab -d ${TFTPROOT}/drivers
cd ${RISROOT} && ./infparser.py {TFTPROOT}/cdrom/driversDoes sound "strange", but also compare with the use of infparser.py on the suggested guide (point 4.3):
4.3 Drivers
To make network install working you first need to collect needed inf files from windows
inf directory or from downloaded networks drivers. After you placed needed inf files in
a directory, you should run infparser.py to make the driver cache needed by the binl
server. Same utility can be used to generate a txt file that can be used with the mini
binl server.
Example, if you have placed your inf files in /mnt/disk/ris/inf you should run:
infparser.py /mnt/disk/ris/inf
Then you will have two files: devlist.cache needed by the binlsrv (Python version) and
nics.txt for the native mini binl server.
You need to place your binary .sys driver files in i386 directory of the selected install
path e.g. in /mnt/disk/ris/winxp/I386
So, in any case it seems to me "wrong" to expand the WHOLE drivers.cab and to do it anywhere else but inside \i386.
But could it not be that you simply miss in the XP Source an appropriate driver for the network card of your target machine?
Also you may want to notice how the Sherpya's tutorial uses (point 4.1):
label winxp
kernel winxp.0
Generally speaking, when following a step by step tutorial, you should replicate each step EXACTLY without introducing ANY variation, of ANY kind, for NO reason WHATSOEVER, as they may be REASONS why something is suggested, why it is suggested in a certain form, etc., etc. (compare with "common sense advice" attached to Rules, point #f3):
http://www.boot-land...?showtopic=9101and this does include changing names, paths and directory structures....
Strangely enough
the approach of first doing EXACTLY waht is suggested and only LATER introduce your variations, usually leads to some better results in less time.
You can also compare your structure setup and what not with this seemingly unrelated thread:
http://www.911cd.net...showtopic=16079Drivers and such
If you look at a ris image, you’ll notice that the drivers and inf files are all in the I386 folder. This is a bit different then on your WinXP cd which has everything neatly filed in subfolders. What this means is we need to copy our driver files to the I386 folder. Copy all the files in the I386\Inf to the i386\ folder and then do the same with the files in the i386\System32\Drivers folder. You will end up with a lot of files in the i386 folder. Don’t delete these folders, just copy the contents.
Now, this is the sticky point and the biggest problem with NIC cards. Presuming you copied everything from a BartPE CD image that worked, then your drivers are already in there, but if not, you should copy the SYS and INF files for you network cards into the i386 folder at this time. You can also copy your network drivers from any $OEM$ folder that you may have already created for another image if that’s the case, presuming you have a working RIS install for your particular nic. Once you have done this you have to stop and start the RIS service. This is necessary as the RIS service uses compiled PNF files for it’s drivers and if you don’t restart the service it will not create PNFs for new drivers that have been added to the i386 folder. To do this, from the command prompt on your RIS server, use the commands,
Net stop BINLSVC
To stop the service
Net Start BINLSVC
To start the service
Once the service has successfully restarted you should try connecting to your RIS server and starting BartPe.
Maybe you have to check your source and restart the BINL server as well.
Wonko
