Jump to content

buddha

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About buddha

Contact Methods

  • Website URL
    http://

buddha's Achievements

0

Reputation

  1. 7.103 is what I'm using, and it's still crashing my Proliant DL385. Steps to verify: Build WinPE64 image from Windows 2003 SP1 x64 ISO Slipstream 7.103 driver in with drvinst Boot ISO via Ramdisk using x64 kernel factory.exe -winpe locks up detecting network drivers I've also tried with generic Broadcomm b57amd64.sys version 8.27.1.0 - same result. Awaiting Microsoft's reply.
  2. Interestingly, I've managed to get it working with the HP DL320 by removing all traces of the Broadcom drivers, and using the HP ones (q57 rather than b57). Since the vendor ID's are the same in the inf (I assume anyway), I suspect something in the b57 inf file is causing factory.exe to get upset. If this is true, there's a chance the same could be true of the q57 64 file? I'll investigate more tomorrow. Strange goings on!!
  3. I'm wondering whether it comes down to either playing with the x57xxxx.inf file, or versions of factory.exe - I'm using the default from PE2005 and standard inf at the moment... Your notes would be useful - thanks.
  4. Both. Which leads me to suspect that the problem is w/ Broadcom and factory.exe, not necessarily the architecture. Of course I could be completely wrong
  5. Confirmed with a HP DL320 as well. These have HP badged NICs in, which from the Vendor string look like Broadcoms too - PCI\VEN_14e4. Definitely something fundementally wrong with factory.exe running on Broadcom network cards. Broadcom have some blurb on their site which may be related: http://www.broadcom.com/drivers/faq_drivers.php#79 It talks about RIS but I made the changes anyway, hoping they would help, to no avail. I'll keep looking.
  6. That's fair enough. I wonder if you'd be allowed to pass it on directly to the Microsoft engineer dealing with my case? He just needs enough info to make contact with the group dealing with it internally...
  7. When experimenting with PE last week I couldn't get it to see any NICs! This when building with Win2K3 SP1. I must have been doing something wrong though, since recompiling the image fixed the problems. I use drinst.exe to inject new drivers into the image, and it works brilliantly, with the exception of these Broadcom drivers. I'll try and test with another 2650 and see if it behaves the same.
  8. Oh dear. Microsoft have just refused to take the case on the grounds that it's HP's responsibility as an OEM. HP think it's Microsoft's problem. Jazkal, do you have a bug reference I could take back to Microsoft? If I can persuade my engineer that PSS already have a similar case, he may reconsider my own issue. In other news, I got exactly the same behaviour this morning on a 32 bit Dell Poweredge with a Broadcom NIC. Are there known issues with factory.exe and Broadcom?
  9. Ah, that's useful to know. I'll open a case too. Thanks mate.
  10. Dear All, I'm having problems getting WinPE64 to boot on a HP DL385. The machine contains dual Opteron 2.6GHz CPUs. I've got WinPE64 booting with Smartarray6 drivers loaded, and can see the disks. When running factory -winpe, the machine hangs on the 'Starting Network' phase, and has to be power cycled. I've tried adding the latest drivers from HP's site (the driver file is q57amd64.sys), and removing all other inf files from the amd64\inf directory to see if that makes any difference, to no avail. Compiling with or without /pnp support seems to make no difference. Running regsvr32 netcfgx.dll then winpe -minint also doesn't help - the machine locks up as before. Sadly, I'm now completely stuck. Does anybody have any suggestions as to how I could proceed? Cheers, Paul
×
×
  • Create New...