Announcement Banner
UNSOLVED

MGEnginIR

updated

22 years ago

M

MGEnginIR

3 Posts

0

22176

August 5th, 2004 17:00

RIS GX280 Problem

When I start to RIS a GX280 I get this error:

*** Hardware Malfunction

Call your hardware vendor for support

NMI: Parity Check / Memory Parity Error

*** The system has halted ***

I tried it on two different GX280 systems and still the same error.

  • MGEnginIR

    3 Posts

    383

    0

    Posted August 6th, 2004 16:00

    I got my RIS to work.

    This delt with the NIC for some reason.

    I inserted/replaced 3 files in the i386 folder.  These files were downloaded from Broadcom's website.

    b57w2k.sys                             7/26/2004

    b57win32.inf                            7/26/2004

    b57xp32.sys                            7/26/2004

    I was installing XP Pro the the GX280.

    I hope this info helps anyone else thats having similar issues.

  • Bootie76

    7 Posts

    383

    0

    Posted September 7th, 2004 08:00

    Im having the exate same problem and I tried your solution but it did not work.

    Then I read in the FAQ on Broadcom that you had to modify the INF fil http://www.broadcom.com/drivers/faq_drivers.php#80 but that didnt work either...

    MGEnginIR did you do anything else that update the driver to the newest?

    Message Edited by Bootie76 on 09-07-2004 11:16 AM

  • tmeyer100

    5 Posts

    383

    0

    Posted September 15th, 2004 20:00

    He just solved my Dell GX280 WinXPSP1 issue. I was receiving the "network card driver" error when I attempted a RIS image install off Win 2000 Server. I spent 2 WEEKS working on this, and i'm estatic that its finally working. I should have checked Broadcom's site more thoroughly to find out about removing those entries from the INF FIle.

    **** Follow these very carefully and you MUST change these in 4 places,  on both your standard winXP flat image(ex:winxpsp1.pro) plus your custom RIS image (ex:winxp_sp1). You should have this INF driver in the I386 and $oem$ directories for each image. CHANGE ALL FOUR!!

    http://www.broadcom.com/drivers/faq_drivers.php#80

    1. Modify the b57xp32.inf file
    2. In the .inf file that is to be placed in the RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder, remove NTx86.5.1 in two lines (see the following example):
      Original                            Revised 
      [Manufacturer]                      [Manufacturer]
      %BRCM% = Broadcom, NTx86.5.1        %BRCM% = Broadcom
      
      [ControlFlags]                      [ControlFlags]
      ExcludeFromSelect = *                ExcludeFromSelect = *
      
      [Broadcom.NTx86.5.1]                [Broadcom]
    *** Dont forget to restart the bin information negotiation layer on the Win2000 SVR!
    

    Message Edited by tmeyer100 on 09-15-2004 04:04 PM

  • Bootie76

    7 Posts

    383

    0

    Posted September 16th, 2004 07:00

    But I allready tried that. Right now Im using the modified Broadcom inf file but still getting the *** Hardware Malfunction *** error.

    Im completly lost.

  • tmeyer100

    5 Posts

    383

    0

    Posted September 16th, 2004 15:00

    When you created the original WinXP RIS Image, was it with similar GX280 PC?

    My problem was a Network Card Driver error, not hardware malfunction error. I would delete the RIS image off your server, and then reimage the origianl PC. Have you installed XP SP1 or SP2?

     

     

    Message Edited by tmeyer100 on 09-16-2004 11:46 AM

  • 383

    0

    Posted September 17th, 2004 18:00

    For what it's worth, I ended doing the following to get the latest Broadcom drivers (7.80) working with an XP SP2 RIS image.  I edited the b57win32.inf file in both the i386 and $oem$.....\NIC directories as follows:

    • Delete the [Broadcom] section
    • Delete the sections headed “32-bit Windows 2K Install sectionsâ€� until you get to “32-bit Windows XP Install sectionsâ€�
    • Delete the sections headed “Windows 2k common sectionsâ€� until you get to “32-bit Windows Xp common sectionsâ€�
    • In the [Manufacturer] section, modify the following line like so:
    %BRCM% = Broadcom
    • In the [Broadcom.NTx86.5.1] section, modify the section header to read [Broadcom]

    I think the problem is that Broadcom unified (to some extent) their Win2K and XP drivers, so you have to strip the Win2K info out of the INF file for the XP drivers to get XP RIS to grab the right drivers.

    --Toby Ovod-Everett

     

  • 383

    0

    Posted September 17th, 2004 19:00

    From further experimentation, I've been able to verify that doing this to the b57win32.inf file in the dir_name\$oem$\$1\Drivers\Nic directory is a BAD idea. That results in a successful install, but then the NIC has to be uninstalled and reinstalled once the machine gets imaged. Using the original b57win32.inf file in the dir_name\$oem$\$1\Drivers\Nic and only making the edits to the one in the dir_name\i386 directory gets the desired behavior.

    Sorry (hey, this second problem has been confusing me for months!)

    --Toby Ovod-Everett

  • 383

    0

    Posted September 17th, 2004 19:00

    Other things to keep in mind:

    • If you were previously using the 7.43 release, you might want to remove the b57xp32.inf and b57xp32.cat files it installed since those are no longer part of the 7.80 release and may confuse things.  Those will show up in both the dir_name\i386 and dir_name\$oem$\$1\Drivers\Nic directories.
    • My standard procedure when I muck with anything in the i386 directory is to stop BINLSVC, delete the *.PNF files, start BINLSVC, wait 2 minutes, and then attempt a RIS build.  Note that it will take BINLSVC several minutes to recreate the PNF files, so if the RIS install appears to hang, look in the i386 directory and watch it creating all the PNF files.

    --Toby Ovod-Everett

  • tmeyer100

    5 Posts

    383

    0

    Posted September 20th, 2004 18:00

    What is the exact error that you are receiving? I am somewhat confused on what issue you are having.

    Is it Network Card/Drivers related or something else????

     

     

  • Bootie76

    7 Posts

    105

    0

    Posted September 21st, 2004 10:00

    If I insert another net adapter into the machine and use that instead I have no problem. Its only when using the onboard net adapter.

    The error im getting is exactly the same as the first poster. A bluescreen telling me there is some hardware error.