Reply to Message

View discussion in a popup

Replying to:
_the_dude_
Enthusiast
Enthusiast

WiNeOS,

\* Your problem sound like an unsupported network card.

\* Check the /var/log/messages file for the logging of the tftp daemon

\* Check the /var/log/binlserver.log for logging of the binl service

\* It could also be this issue: http://support.microsoft.com/kb/328003/en-us

If I were you I would try to:

\* Download new drivers for your network card (These?: http://ftp.cses.chc.edu.tw/ftp/driver/netcard/realtek/rtl8139d/WIN_XP/ )

\* Put the .INF file in the WINXP_INF directory

\* Put the .SYS file in the WINXP_SYS directory

\* /etc/init.d/binl stop

\* regenerate the binl database

(run either /var/public/cgi-bin/infparser.py or /var/public/bin/infparser.py depending on the UDA version you are using.)

\* /etc/init.d/binl start

Let me know if it worked, and if not, please post bits of your /var/log/messages and /var/log/binlserver.log

Here's a quick description of how the network card driver issue is implemented in Windows and the UDA.

Windows uses the binl protocol to ask the UDA what network driver it requires for the network card that is used. This protocol is implemented in the UDA as a service/daemon. (check out /etc/init.d/binl)

When you import the winxp iso, the UDA gets all the network drivers information files (net*.in_ in the i386 directory) and generates a database (/etc/devlist.cache) whith the information found in those inf files. The inf files tie the network hardware ID to a .sys file.

The .sys files are also imported to the UDA during OS import (the step where the driver.cab is decompressed). The .sys files are extracted to the WINXP_SYS directory.

When the client requests which driver to load, it sends it network card hardware ID to the UDA and the UDA looks it up in the database. If the ID is found it returns the name of the .sys file corresponding to the hardware ID. The trick here is that the UDA binl service tells the client to search for that .sys file in the WINXP_SYS directory.

The client then tries to request and returns (if found) the sysfile that was once in the driver.cab file on your ISO image.

There may be something wrong with the drivers on the WINXP iso (OEM version for specific hardware?) or one of the steps the UDA takes that are described above.

Reply
0 Kudos