Jump to content

Super-Magician

Member
  • Posts

    969
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Super-Magician

  1. This was a terrific project in its heyday. Though I haven't been on here much in the last couple of years, I'm also sorry to see it go. Perhaps someday, someone will pick it up again, but OSes are evolving, and there's always a time for the world to move on. Best wishes to you, TommyP, and to Tomcat76, wherever he may be...

  2. I got a crappy loading bar :S

    Don't understand what could have done this?

    This happened on one of my machines too after upgrading (although I went from 6801 to 7000). Not sure what the cause is.

  3. Well, it's been many months since I've visited MSFN, and perhaps even longer since I've visited this particular forum.

    I feel by now that many people in the Windows community have switched over to Vista (even with its many shortcomings and the complaints that people have lodged against it). Nevertheless, have you any news about a possible future stable release of the XP PowerPacker (i.e., v1.0 final)?

  4. I apologize for not updating this in May as I had promised. Unfortunately, my other obligations have cut into the time that I am able to spend in maintaining my personal HFSLIP installations and the concurrent updating of my hotfix collection.

    At this point, I am not sure whether I will still update this list at some point in the future, or if I will simply introduce a new list for XP SP3. Moderators, you may unpin this (and my 2000 list) if you'd like.

  5. If you select option A, HFSLIP should merge DRIVER.CAB and SP4.CAB into a new and recompressed DRIVER.CAB with some updated binaries from your hotfixes. In that case, SP4.CAB should no longer exist in your SOURCESS folder after running HFSLIP, which leads me to think that something went wrong at the point in the process.

    Can you attach your HFSLIP.LOG file?

  6. Super-Magician...

    The only problem with your suggestion is that "IF EXIST HF\WMP11\*.*" always returns "true" and "IF NOT EXIST HF\WMP11\*.*" always returns "false" even if the folder is empty. It's sort of a known limitation of DOS. You need to specify more than that, like "HF\WMP11\w*" or "HF\WMP11\*.exe", though that doesn't really tell us whether the folder is empty or not. One way to do that (without causing an error message to appear) is to create a dummy file, then set a variable based on whether there are any other files in the folder besides the dummy file and delete it afterwards but that would take things too far.

    So I could use "HF\WMP11\*.exe" but I'm not sure if it's really that important. Making this change would require adding the line "IF EXIST HF\WMP11 RD/Q/S HF\WMP11" between the brackets, otherwise people might get an error message like "Folder already exists" when HFSLIP tries to create it. This adds an extra IF condition and I'm not sure it's really worth it.

    Oh, I forgot that there's always the "." and ".." in the filesystem so that command wouldn't work. Yeah, I see what you're saying. I don't think it's worth the extra code either. Thanks for clarifying.

  7. Actually, if the WMP11 folder is not deleted by the time the HFSLIP process exits, then the HFSLIP process must have been interrupted at some point. When including the EXE setup file for WMP11 in HF, the following line takes care of the folder immediately after the components are extracted:

    IF DEFINED RDWMP11DIR RD/Q/S HF\WMP11

    If you run HFSLIP with an empty WMP11 folder, then some errors should be generated by the console while running HFSLIP. Tomcat76 should probably change this line to prevent problems if the WMP11 folder exists but is somehow empty:

    IF EXIST HF\WMP11*.exe IF NOT EXIST HF\WMP11\*.* (

    On the other hand, I noticed an unrelated bug while I was working on my 2000 SP4 source. Even though I'm pretty sure wmfdist.exe (from KB891122) was extracted properly, the system complained about being unable to delete setup_wm.exe from TEMP\WMPCOD. I should probably run HFSLIP again to confirm.

  8. He's not prompted to install those CABs; they're installed automatically without user interaction and then rechecked every time you visit WU/MU. I guess he's just paranoid about having all the ActiveX controls he needs already slipstreamed. :lol: No need for that though if it's installed automatically.

  9. well, I did search and found NOTHING useful.

    I just did another search in the HFSLIP forum and found no less than 13 threads that reference KB888111.

    Simple question: is it supported, YES or NO?

    Yes, that is indeed a simple question. How about a simple answer? At least try to click on my links this time.

    Good day to you! :)

    @Extravert, thanks for trying to help. However, jvidal's question involves whether or not this particular hotfix can be slipstreamed by HFSLIP, not just whether his computer would support it.

  10. First try moving your HFSLIP directory to something like "C:\HFSLIP" so you don't have any spaces in the path. You also have too many updates for IE7 -- KB933566, KB937143, and KB939653 are obsolete.

    Follow Tomcat76's update page to see if you have any other unnecessary fixes in your folder.

  11. Hey, Tomcat76, awesome job on the recent upgrades to the site! It looks very nice! :D

    Anyway, I wanted to mention a minor typo I found. It says "This overrides the INCALLSKINS variable." under the INCALLSKINS variable on the Extras page. Shouldn't that belong under INCWMPCSKIN?

  12. This discussion actually confuses me too.

    He said that Windows Update complains if he doesn't put KB913800 in HF while slipstreaming WMP11. However, when he returns it to the HF folder, WU stops complaining. The fact that KB913800 is ignored doesn't seem to correspond with these observations because the presence or lack of it clearly seems to make a difference. Is it a problem with Windows Update then? I see what you're saying Tomcat76, but based on johndoe74's comments, it appears that you need KB913800 in HF if you want Windows Update to stop complaining, regardless of whether or not it's actually needed in terms of updated binaries.

  13. Maybe this is not right place to ask but sorry from now :D

    *i speak about not public hotfixes*

    Every hotfix does not contain only one file. I have seen some hotfixes mixed each other.

    Bigger KB can include a lower version number file. But other files are newer version.

    And another hotfix may include newer files then bigger KB hotfix.

    Crossed each other. :/

    I would like to know can HFSLIP can choose newer file to slipstream or not? Automaticly i hope.

    Hi Eyren. The COPY and XCOPY commands in the command prompt have a switch that allows you to only copy over files that have a newer modification date. HFSLIP incorporates this directly into the script, so you don't have to worry that files from hotfixes with higher KB numbers are overwriting newer versions from hotfixes with lower KB numbers. In cases where the file dates are messed up and we actually need a binary that was modified earlier, the necessary commands are hardcoded.

  14. The new Integrator version still needs some testing. To do this manual is alot of work and where are alot possible issues during the integration the Integrator can fix all issues witch i know in the moment.

    What is the point of repeatedly telling us that your method works without explaining why or how? Do let us know, because we're all interested. Don't promote the program, however, like Nuhi said.

×
×
  • Create New...