Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
sorry for the long delay in reply - we've been rolling out.
No, i havent had any more success, i did log a call with MS about it, it got escalated to the premier team 3 weeks ago, i sent the guy a copy of my PE build and havent heard back - after repeated calls, and after forking out $300AU for the call. MS are just thieve's... but oh well.
For the moment i am just going with the CD-boot based PE build, it still works, it just takes lonbger and needs the extra step of creating drives (otherwise PE takes D: drive for itself)
It wouldnt surprise me at all if you right about the SCSI thing, but somehow i dont think this one will be solved anytime soon.
Hopefully ms will pull their finger out and release the next version of PE soon which was promised in november 2003.
If they could just address the CD boot drive letter, WMI support and driver support PE would be a fantastic product for building SOE's.
Ris with windows PE help
Rate Topic:
Back to top
#22
Posted 16 February 2004 - 06:32 AM
verukins,
I know what that is like.
We have been doing a bit of research, and we believe it is an issue with the multi-processor HAL. Hope to have a bit more information in the morning. All this time looking at the NIC and SCSI drivers put us off the track.
Good Luck
Cheers
Darren
I know what that is like.
We have been doing a bit of research, and we believe it is an issue with the multi-processor HAL. Hope to have a bit more information in the morning. All this time looking at the NIC and SCSI drivers put us off the track.
Good Luck
Cheers
Darren
#23
Posted 16 February 2004 - 07:13 PM
Well it seems it is HAL related. I think MS may be hinting this in the Support Article 814199
We found that for our servers if we added the following lines to the reminst.sif file it worked for new machines. As this hard codes the HAL, it did break the install on our older machines though.
[Unattended]
OemPreinstall=yes
ComputerType = "Advanced Configuration and Power Interface (ACPI) PC"
I did try the hotfix mentioned in the article and it did not work. I have not spent much time on it as all machines needed for this job use the same HAL.
Maybe you could ask for your money back, as it seems like a bug?
Cheers
Darren
We found that for our servers if we added the following lines to the reminst.sif file it worked for new machines. As this hard codes the HAL, it did break the install on our older machines though.
[Unattended]
OemPreinstall=yes
ComputerType = "Advanced Configuration and Power Interface (ACPI) PC"
I did try the hotfix mentioned in the article and it did not work. I have not spent much time on it as all machines needed for this job use the same HAL.
"verukins" said:
No, i havent had any more success, i did log a call with MS about it, it got escalated to the premier team 3 weeks ago, i sent the guy a copy of my PE build and havent heard back - after repeated calls, and after forking out $300AU for the call. MS are just thieve's... but oh well.
Maybe you could ask for your money back, as it seems like a bug?
Cheers
Darren
#24
Posted 30 October 2006 - 03:14 PM
overland, on Jan 22 2004, 06:18 AM, said:
I have the same problem when tryning to pxe boot Dell PE2550/2650 servers with Broadcom 570x Gigabit NIC. After textmode PE hangs, when it says please wait.
And it works fine on ordinary workstations. And if I use a PE boot CD everything works smoothly...
I've talked to Dell, but it seems like they doesn't know to much about WinPE, yet.
This is very frustrating!
T.
And it works fine on ordinary workstations. And if I use a PE boot CD everything works smoothly...
I've talked to Dell, but it seems like they doesn't know to much about WinPE, yet.
This is very frustrating!
T.
I've had the same problem with the MN32SLI motherboard and the trick was that the mobo had two NIC's on-board. Plugging it into the other NIC resulted in the system booting successfully -- successfully meaning it booted WinPE and got past the "Starting Windows Preinstallation Environment".
