3 replies to this topic

[JohnRottingLiver]

I have used the guide here
http://74.125.47.132...8...;cd=1&gl=us

I dont know how valid it is or of any updated guide. basically i have followed the guide stated above. Made some minute changes. changing XPP.0 to XPH.0 and what not. I am very new to this kinda stuff and dont really know what info you guys need to help me. I can give you guys my log file and ask me anything you need If you need any more info.

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:1F:D0:6C:0B:52 [17/12 17:47:56.703]
DHCP: proposed address 192.168.5.106 [17/12 17:47:58.281]
3820 Request 2 not processed [17/12 17:47:58.328]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:1F:D0:6C:0B:52 [17/12 17:47:58.765]
Previously allocated address 192.168.5.106 acked [17/12 17:48:00.265]
Connection received from 192.168.5.106 on port 2070 [17/12 17:48:00.281]
Read request for file <pxelinux.0>. Mode octet [17/12 17:48:00.281]
Using local port 1846 [17/12 17:48:00.281]
3820 Request 2 not processed [17/12 17:48:00.328]
<pxelinux.0>: sent 31 blks, 15840 bytes in 0 s. 0 blk resent [17/12 17:48:00.375]
Connection received from 192.168.5.106 on port 57089 [17/12 17:48:00.421]
Read request for file <pxelinux.cfg/00000000-0000-0000-0000-001fd06c0b52>. Mode octet [17/12 17:48:00.437]
File <pxelinux.cfg\00000000-0000-0000-0000-001fd06c0b52> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.437]
Connection received from 192.168.5.106 on port 57090 [17/12 17:48:00.437]
Read request for file <pxelinux.cfg/01-00-1f-d0-6c-0b-52>. Mode octet [17/12 17:48:00.437]
File <pxelinux.cfg\01-00-1f-d0-6c-0b-52> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.437]
Connection received from 192.168.5.106 on port 57091 [17/12 17:48:00.437]
Read request for file <pxelinux.cfg/C0A8056A>. Mode octet [17/12 17:48:00.437]
File <pxelinux.cfg\C0A8056A> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.437]
Connection received from 192.168.5.106 on port 57092 [17/12 17:48:00.437]
Read request for file <pxelinux.cfg/C0A8056>. Mode octet [17/12 17:48:00.437]
File <pxelinux.cfg\C0A8056> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.437]
Connection received from 192.168.5.106 on port 57093 [17/12 17:48:00.437]
Read request for file <pxelinux.cfg/C0A805>. Mode octet [17/12 17:48:00.437]
File <pxelinux.cfg\C0A805> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.437]
Connection received from 192.168.5.106 on port 57094 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [17/12 17:48:00.453]
File <pxelinux.cfg\C0A80> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.453]
Connection received from 192.168.5.106 on port 57095 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [17/12 17:48:00.453]
File <pxelinux.cfg\C0A8> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.453]
Connection received from 192.168.5.106 on port 57096 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/C0A>. Mode octet [17/12 17:48:00.453]
File <pxelinux.cfg\C0A> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.453]
Connection received from 192.168.5.106 on port 57097 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/C0>. Mode octet [17/12 17:48:00.453]
File <pxelinux.cfg\C0> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.453]
Connection received from 192.168.5.106 on port 57098 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/C>. Mode octet [17/12 17:48:00.453]
File <pxelinux.cfg\C> : error 2 in system call CreateFile The system cannot find the file specified. [17/12 17:48:00.453]
Connection received from 192.168.5.106 on port 57099 [17/12 17:48:00.453]
Read request for file <pxelinux.cfg/default>. Mode octet [17/12 17:48:00.468]
OACK: <tsize=55,> [17/12 17:48:00.468]
Using local port 1857 [17/12 17:48:00.468]
<pxelinux.cfg\default>: sent 1 blk, 55 bytes in 0 s. 0 blk resent [17/12 17:48:00.531]
Connection received from 192.168.5.106 on port 57100 [17/12 17:48:00.531]
Read request for file <menu.c32>. Mode octet [17/12 17:48:00.531]
OACK: <tsize=55220,> [17/12 17:48:00.531]
Using local port 1858 [17/12 17:48:00.531]
<menu.c32>: sent 108 blks, 55220 bytes in 0 s. 0 blk resent [17/12 17:48:00.640]
Connection received from 192.168.5.106 on port 57101 [17/12 17:48:00.640]
Read request for file <pxelinux.cfg/default>. Mode octet [17/12 17:48:00.640]
OACK: <tsize=55,> [17/12 17:48:00.640]
Using local port 1859 [17/12 17:48:00.640]
<pxelinux.cfg\default>: sent 1 blk, 55 bytes in 0 s. 0 blk resent [17/12 17:48:00.750]
Connection received from 192.168.5.106 on port 57102 [17/12 17:48:03.671]
Read request for file <XPH.0>. Mode octet [17/12 17:48:03.671]
OACK: <tsize=22457,> [17/12 17:48:03.671]
Using local port 1860 [17/12 17:48:03.671]
<XPH.0>: sent 44 blks, 22457 bytes in 0 s. 0 blk resent [17/12 17:48:03.734]


This is all it sshows and the client pc hangs with a blinking cursor at the top left of the screen. any help?

[was_jaclaz]

I have used the guide here
http://www.boot-land...?...ost&id=3390

I dont know how valid it is or of any updated guide. basically i have followed the guide stated above. Made some minute changes. changing XPP.0 to XPH.0 and what not. I am very new to this kinda stuff and dont really know what info you guys need to help me. I can give you guys my log file and ask me anything you need If you need any more info.

WHY?
I mean, when you follow ANY tutorial for the first time, you should introduce NO changes, of ANY type.
Once you have the thing working EXACTLY as stated, introduce changes ONE AT THE TIME, this way you know what is causing the problem.

Since you already introduced changes, you need to list ALL the introduced changes, no matter how "minute" they are or appear to you.

What are the contents of your pxelinux.cfg?


jaclaz

P.S.: now that the board is again working, check the "full" thread :
http://www.boot-land...?showtopic=1961
there is an updated guide and other tutorials too, that you might want to review.
In some cases the different wording of different tutorials may help you better understand the basics, and thus let you find where the problem might be.

[JohnRottingLiver]

I just have a file default in there. no extension. default reads

DEFAULT menu.c32

label XP_HOME

kernel XPH.0

[andriusst]

Looks like your client PC does not execute XPH.0 properly. Usually it should load setupldr (or xppro in your case) which would show on your log file.

Here are several points that may cause your problem:
1. startrom (XPH.0) file may be corrupt or modified incorrectly.
2. Your network adapter firmware may not be compatible with pxelinux version you have. To eliminate this possibility change boot file name in tftpd32 from pxelinux.0 to xph.0 and see if that helps. Or alternatively you can try other pxelinux version (look for updated or older syslinux package)
3. Try using different network adapter to see if that helps

When you get it working you should see the following sequence of files on your TFTPD32 log:

pxelinux.0 (will not see this if loading xph.0 directly)
default (will not see this if loading xph.0 directly)
xph.0 (this is renamed startrom file from Win installation source)
xppro (this is renamed ntldr or setupldr)
ntdetect.XPP (renamed ntdetect)
xppro.sif (renamed winnt.sif)
txtsetup.sif
.
.
mup.sys
mrxsmb.sys
At this point Windows file sharing client should kick in and pull the rest files from shared folder on a server PC. If nothing happens double check if file sharing is setup properly.

good luck,
Andrius

p.s. I have not followed nor am familiar with procedure you provided so there may be some discrepancies in file names.