This is no request thread! HP COMPAQ bioses, how to modify the bios?

Discussion in 'BIOS Mods' started by Yen, Aug 6, 2009.

  1. TTAV134

    TTAV134 MDL Expert

    Mar 1, 2009
    1,559
    623
    60
    hi,

    Why have you used this tool?

    Your bios F.01 04/24/2009 is SLIC 2.1

    if you want to check the table use this http://forums.mydigitallife.info/showthread.php?t=6925
     
  2. engage16

    engage16 MDL Junior Member

    Jul 30, 2009
    51
    0
    0
    Everest doesn't detect bios slic's properly, yes it will tell you what version your running, 2.0 or 2.1 but the emulated tag shows up on actual slics occasionally as well as emulated ones from a loader...
     
  3. ssk3071

    ssk3071 MDL Novice

    Sep 16, 2009
    6
    0
    0
  4. andmail

    andmail MDL Junior Member

    May 11, 2008
    83
    2
    0
  5. TTAV134

    TTAV134 MDL Expert

    Mar 1, 2009
    1,559
    623
    60
    hi,

    no you cannot.
     
  6. matej123

    matej123 MDL Novice

    Jan 26, 2008
    1
    0
    0
    Hi,
    Thank you all for trying so hard. It seems to me that we would need some fresh ideas. However, I think there are still some open questions regarding current flashing procedures using memory patch.
    1. I was wondering if any one of you have tried to change all three parts of slic2.1.bin (header starting with SLIC....HPQOEMSLIC-MPC..., RSA1 part and HPQOEMSLIC-MPCWINDOWS...) when using memory patch. Current procedure focuses only on the last part and ignore the header and the RSA1 part, which are also different in slic2.1.bin compared to slic2.0.bin.

    2. Why are there two occurences of the slic table in the first place, if only one in the protected area is needed? As I understand, after flashing modded bios, the first slic table (Exxxx-EFFF0) is changed but not the second one?

    thank you again.
     
  7. Snout

    Snout MDL Novice

    Jul 29, 2009
    2
    1
    0
    I haven't taken the time to read all 70 pages of this thread, but I will share my experience with the forum. I managed to get SLIC 2.1 on my Compaq Presario desktop (which is the equivalent of an HP Pavilion) by using the HP Motherboard DMI Tattoo Utility 5.01 to update the DMI Tattoo.

    I did a lot of experimentation and found out that, at least on my Compaq, there was no valid SLIC in the BIOS itself. Replacing the dummy SLIC table in the BIOS file itself with a valid SLIC and flashing it made no difference -- the same SLIC always showed up. What I discovered was that the DMI Tattoo Utility writes an encoded version of the SLIC table to the DMI area and at boot time this info is copied to the real SLIC table. The SLIC you see has nothing to do with the BIOS file that has been flashed on the machine. Earlier versions of the DMI Tattoo Utility put SLIC 2.0 in the DMI but version 5.01 installs SLIC 2.1, so once I'd updated the DMI with the Tattoo utility I had no problems activating Windows 7.

    If you're finding that your BIOS ROM file either contains no SLIC yet one appears after the machine has started, or that modifying the SLIC table in the ROM and flashing it doesn't change anything, the solution I found might be the one you need.

    I do not have an HP or Compaq laptop to investigate but there does exist a similar DMI tool for those machines, so they may require a similar method.

    Sorry if I'm repeating information that has already been posted here, but I could find absolutely no information on this subject when I did this back at the beginning of August.
     
  8. tamarinde

    tamarinde MDL Novice

    Aug 16, 2009
    28
    0
    0
    Would be nice if you could give us this DMI tool so we could test.
     
  9. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,440
    1,594
    180
    These tools are for Pavillion/Presario only

    sebus
     
  10. tamarinde

    tamarinde MDL Novice

    Aug 16, 2009
    28
    0
    0
    I tried the tool on a 8710p but it needs a Build ID and FeatureByte.
    These 2 I can not find anywhere, I could try to input something random but I dont want to risk bricking my laptop.