Printable View
just got a toshiba satellite pro L300-19S. trying to make windows xp deploy to it before we get any more
first of all it wouldnt boot pxe properly, so injected the drivers and then that worked. now I'm stuck on when it runs wpeinit it comes up with the never seen before error:
a connection to the deployment share \\server4\distribution$ could not be made. the deployment will not proceed.
anyone encountered this before?
It sounds like you need to update the lan drivers in the Winpe image.
Looking again it looks like it uses a Realtek PCI Express gigabit lan controller so I'm now certain you need to update your image to the latest driver version.
i already put the drivers in out-of-box drivers and did an update where it rebuilt the image, isnt that what you're referring to?Quote:
Originally Posted by PeterW
I'm talking about the WinPE image that is being used to boot the system and connect to the network.
For example you could mount the boot image with imagex and use peimg to inject the drivers into winpe.
oh right, ive done that before, I'll have a go with that, thanks....Quote:
Originally Posted by PeterW
update: injecting the drivers didnt help much, i took the opportunity to adda ping to the startcmd file. although that errors with
"unable to contact ip driver, error code 1753"
i got a couple of the wizard screens tho....
how odd is this: when windows is "loading files", the lan sockets lights are on, (on & activity), when the wizard error hits the lan socket is strangely deactivated and replugging the cable doesnt reactivate it!!!!!
I watched it very closely, the lan deactivates before the windows deployment wizard window appears.
its almost like the lan socket decides to deactivate in the middle of the process.
when you used PXE are you using vesa menu or text menu??
some of my PCs only use text menu..
but i have Windows 2008 deployment and pxe running sweet i can PXE and then select
2008 deployment if i need it.
Really thats surprising, were they the latest vista drivers from realtek here RealtekQuote:
update: injecting the drivers didnt help much,
(I'm assuming its WinPE 2.0)
That sounds right once WinPE loads it needs to plug and play all the devices and takes control of the lan connection loading an appropriate driver if one is available.Quote:
how odd is this: when windows is "loading files", the lan sockets lights are on, (on & activity), when the wizard error hits the lan socket is strangely deactivated and replugging the cable doesnt reactivate it!!!!!
apparently nothing else deploys now either, so its not necessarily the laptop thats at fault, or I've broken it more than it was broken before lol.
Does anyone get the same issue as this?
1. PXE Boot desktop to WDS Server
2. Solution Accelerator screen comes up with Image options
3. Joy
but
1. PXE Boot laptop to WDS Server
2. Solution Accelerator screen comes up with no Image options and then reboots
3. Misery
Doesn't seem to matter which laptop I try (have used Dell Latitudes and Fujitsu Siemens Tablets) I just can't get the imaging process to get to the pick Image task section.
I've injected drivers and the image works fine on the same laptops if I Imagex it from a booted USB hard drive.
It's caught me out before - there are Realtek PCI 10/100/1000 drivers and Realtek PCI Express 10/100/1000 drivers.
What winPE version are you using?
I find its best to use the winPE version that comes with the Windows 7 disc, has the drivers are more update and im sure it contains more drivers, so far haven't had to inject a single driver on my one yet