Jump to content

jvidal

Member
  • Posts

    719
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Chile

Posts posted by jvidal

  1. Got another bug for ya, mimo (regarding MRT). HFSLIPC still wants MRT 3.8 and flags 3.9 as unneeded. (probably related to what My2girls dad reported).

    BTW, how do I permanently hide an update I don't want?

    For example: 977377 breaks more than what it fixes, I want it gone for good.

    Also, browser choice for EU countries doesn't apply here (I'm not in europe).

    I want to exclude those FOREVER...

    how?

    bye!

    Edit: forget about the MRT, I fixed it by correcting the typo. Still I would like to know how to exclude unwanted updates.

  2. Hi, Mimo!

    I have some interesting new info.

    There is a newer version of the WMP11 installer, digitally signed on FEB 05 2009 (about a year newer than the previous one).

    The thing is that when using this new installer, the following updates are NOT required (I tested it, some of them even refuse to install, saying that the version of WMP installed already includes the fixes and other are just not wanted by MU/WU and though they won't refuse to install, they don't update any files):

    -WindowsMedia11-KB939683-x86-ESN

    -WindowsMedia11-KB954154-x86-ESN

    (those are the ones that refuse to install)

    And

    -WindowsXP-KB941569-x86-ESN

    -WindowsXP-WindowsMedia-KB952069-v2-x86-ESN

    Of course, replace ESN with whatever language you're using.

    Now, As I see it, there are to ways of dealing with this:

    One would be to make hfslipc aware of the new installer and report missing/needed updates accordingly.

    Or

    (a better one IMO) just remove support for the older installer, advise everyone to switch to the new one and flag those updates as unneeded.

    I hope you can do s/thing with this info.

    bye!

  3. Wow! thanks for the tips tommy!

    BTW, it seems the dll is not relevant and the installer/uninstaller works fine with it in sys32 instead of the flash dir.

    bye!

    PD: what's the deal with the alleged "bad words"? dind't get that one...

  4. I already made the add-on for hfslip...it works, except for the dll which ends up in system32 instead of system32\macromed\flash.

    Maybe a new line in hfslip could do the trick, something like:

    if exists flashut*.dll move <bla bla bla> (I don't remember the exact paths used by hfslip).

    If it does not exist, then nothing is done and keeps compatibility with older versions of flash player.

    And, another line to put the correct entries in txtsetup.sif.

  5. Ok, done.

    After installation (which went fine, by the way), i looked into the system32\macromed\flash folder and found both the .ocx and the .exe file. the .dll file wasn't there, but it seems it's not relevant. It WAS found on system32.

    Then I visited a site plagued with flash content and it looked just fine.

    So, it seems it still works, no mod needed.

    Well, maybe one line could be added for the correct location of the dll file.

    bye!

  6. Sorry to burst your bubble, but the new files are not being ignored. I JUST built an hfsliped CD and the new dll plus the new util file were copied by hfslip. Now, I'm gonna install this CD and see what happens.

    wish me luck!

    If you look closely at the hfslip code, it uses wildcards to deal with the flash files:

    example:

    flashut*.exe (that WILL copy flashutil10h_activeX.exe)

    *flash*.ocx (will take any version of the ocx control)

    and, the new dll file is also handled.

    I see no problem.

    Let's see what happens after instalation (installing as we speak on a VM).

    bye!

  7. you're welcome, Mimo.

    Now, I found a bug:

    Everytime there is a new version, the update checker enters an endless loop until the recursiveness stack overflows, but it keeps going on trying to update.

    When there is no new version, nothing weird happens.

    bye!

    (and thx again for your good work)

  8. It seems to be high priority. The minute after you install WLM14, MU starts asking for it. In the MU site it is listed under "critical".

  9. Ok, it's done.

    After installing, the file was ver. 5768 in system32 and system32\dllcache. MU was completely happy, no 961503.

    Then, I installed WLM 14, the file was still ver. 5768 in both locations. went to MU, totally happy, no 961503 wanted.

    SO, it seems to work!

    thx!

    bye!

×
×
  • Create New...