Building PXE-ready ReactOS
This is a stub. It's conscious unlinked. Please do not remove/delete.
Get Driver
tbd
Prepare RosBe
tbd
Prepare LAN
For this scenario we need two computer. One client (may be diskless or empty HDD), one server (Windows or better Linux). Both have to be connected to the local network.
The server must running a DHCP-server and a TFTP-server. The client need a pxe-ready network card. Most onboard network card are capable.
The Linux way
I used dhcp3 and tftpd-hpa. Use youre favorite Linux and install them. I used Bind at home, but you can leave that out.
# Sample configuration file for ISC dhcpd for Debian # $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $ ddns-update-style none; # option definitions common to all supported networks... option domain-name "home.local"; option domain-name-servers 10.0.0.254; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). log-facility local7; subnet 10.0.0.0 netmask 255.255.255.0 { range 10.0.0.10 10.0.0.19; option domain-name-servers myserver.home.local; option domain-name "home.local"; option routers 10.0.0.254; option broadcast-address 10.0.0.255; default-lease-time 28800; # 8 hrs max-lease-time 86400; # 1 day allow bootp; host myclient { hardware ethernet 00:0F:EA:66:07:48; fixed-address myclient.home.local; filename "pxelinux.0"; server-name "myserver.home.local"; } }
Check if present, xinetd/inetd config for tftpd.
service tftp { disable = no log_type = SYSLOG daemon info log_on_access = PID HOST USERID EXIT DURATION socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -vv -s /srv/tftp/ bind = 10.0.0.254 }
The Windows way
Booting
tbd