Embedded XP evaluation kit problem?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

I am encountering some problems with xpe evaluation toolkit:
Firstly, I was doing remote booting for diskless system, target +
server(development) systems were interconnected through cross cable. I set my
target pc bios for lan boot, followed all steps of msdn for remote booting,
used win2k3 server for assigning IP to target pc thru DHCP. I followed exact
steps, but i got prblem...."no boot file received". After a while i tried to
do remote boot with same steps, it worked...

Seconldy, I made an ELTO cd. It booted my target pc. I was doing soemthing
and windows got stucked, so i restarted my pc. I dont know y, but it gave
"blue screen stop 7b error". I rebooted again and it worked fine

Why my images acting so unreliably? Why I am geeting such errors at
run-time? And why they go away when i reboot same image with same settings?
Can anyone please tell me?

Best Regards,
-- Sana Z.
 
Sana,
I don't have answers but since there has been no other reply I'll say that I
have been using remote boot for 1.5 years and anytime I've experienced a
problem such as you describe it has been because of some mistake I made or
some networking problem unrelated to XPe. IIRC, "no boot file received"
usually means that an IP address was assigned and the boot server is OK but
it did not provide an image. The reason can be as simple as you have
specified an image file in the RBS administration screen that doesn't exist.
Look closely at the client screen when you have such an error and you should
see a PXE error code and error description. Usually that information is
sufficient to quickly understand what is wrong. For a deeper dive you can
use Ethereal (I recommend that you install Ethereal on your server for such
possibilities) to see the DHCP and proxy DHCP transactions although that
isn't usually necessary. Sorry, I know even less about El Torrito.

RHL
 
Hi Roger,

As I mentioned, I did not do ANY change, except I booted my target system
after a while. It might be networking problem, but teo pcs were connected
through cross cable. And that cable is working fine too. I don't know why I
got that error and how it went away.

thanks for your concern,
-- Sana
 
This may have absolutely nothing to do with it, but I have seen 2 XP pc's
connected together, with DHCP, and DHCP would be quick and other times it
would take forever.

I have also had problems where the ethernet adapters failed to go to the
automatic IP Address and have stuck at 0.0.0.0, unplug then plug back in
and everything fine.

99.9% of our stuff is done with a laptop plugged into the client via X-over
cables. I see some really weird things sometimes.

Richard
 
Back
Top