- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pulse,
I've looked into your problem and it seems your R100 has a Intel pro/100 VE network adapter according to this page:
http://www.freed.net/opensource/R100.html
It should work with ris, but with some adjustments according to this page:
http://www.support-netz.de/wml-ris-install100ve.html
If I were you I would try the following:
1. Download the drivers from this page:
Windows* 2000, XP, and Server 2003 Network Adapter Driver Set[/url]
2. Unzip (or execute) the downloaded file to c:\intel10.3 (default)
3. Copy the file C:\Intel10.3\PRO100\WS03XP2K\E100b325.inf to the /var/public/tftproot/WINXP_INF directory in your UDA.
4. Copy the files C:\Intel10.3\PRO100\WS03XP2K\e100b325.sys and C:\Intel10.3\PRO100\WS03XP2K\e100bnt5.sys to the /var/public/tftroot/WINXP_SYS directory on the UDA
5. Recreate the binl cache:
/etc/init.d/binl stop
/var/public/cgi-bin/infparser.py
/etc/init.d/binl start
6. Retry the RIS installation with your laptop
If things do not work out:
1. Check your /var/log/binlserver.log to check that more drivers have been loaded than previously and see if the binlserver correctly handles the binl request made by your laptop and hands the name of a .sys file in response.
2. Check the /var/log/messages to see what .sys file is requested and if the sys file is where it is supposed to be in your UDA. (tftp is case-sensitive!)
3. Paste the proper timeframes of your logfines in this forum...
Good luck!
Message was edited by:
ken.cline@hp.com to shorten the URL