Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Posts posted by Maxfutur

  1. On 6/11/2013 at 10:35 AM, Acheron said:

    Recently I have posted a number of fixes for you to test.
    Please report your testing results here.


    Jun 11, 2013 - Remove redundant START /WAIT commands. Add OnePiece Internet Explorer 8 Addon support. Fix integrating KB942288, KB961118 catalog files.  Support changing temporary SOURCESS folder path through answer file. Miscellanous changes and code fixes. Beta KJun 17, 2013 - Extract Windows Media Player 11 files to TEMP\WMP11 folder. Fix default SOURCESS path. Fix copying all files without exclude.txt Beta K v2Jun 27, 2013 - Increased command prompt screen buffer and window height. Changed project documentation urls to Mim0s site and updated MSFN forum links.  Prevent deletion of project files when SOURCESS path is set to the HFSLIP directory. Added support for updating uncompressed sysoc.inf.  Removed OS checks when integrating Windows Installer 4.5. Thx to tomasz86.  Changed Addon extraction code to fix short name issues. Also thx to tomasz86 for reporting and fixing this. Beta K v3Sep 01, 2013 - Merge a few lines from HFSLIP 2.0 branch. Only delete TEMP folder content, not the folder itself. Beta K v4Feb 23, 2014 - Block integration of WUDF 1.7 (WMP11) if found in source. Add support for integrating KB2878379. Beta K v5Feb 27, 2014 - Simplify file registration code and move commands from generated HFSLIP.cmd to HFSLIPWU.INF. Beta K v6Jun 25, 2015 - Fix HFSLIPSVC variable is used before declaration issue. Thx to Jakson and tomasz86. Beta K v7Aug 01, 2015 - Improve slipstreaming of Internet Explorer 8 files with long names. Beta K v8Aug 15, 2015 - Enable redirecting of HFSLIP command output by specifying OUTPUTFILE in answerfile.    Use PEChecksum instead of modifyPE on Windows Vista and higher. Fix integrating xpsp4res.dll. Beta K v9


    Anyone have a backup of the tool? :whistle:

    The attachment gives the 500 internal error when trying to download.

  2. WannaCry Fix for XP:

    2017-04 MS17-010: SMB Server Critical KB4012598 WindowsXP-KB4012598-x86-XXX.exe


    2011-04 MS11-020: SMB Server Critical KB2508429 WindowsXP-KB2508429-x86-XXX.exe



    Description: A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

    Architecture: X86

    Classification: Security Updates

    Supported products: Windows XP

    Supported languages: Arabic , Chinese (Simplified) , Chinese (Traditional) , Czech , Danish , Dutch , English , Finnish , French , German , Greek , Hebrew , Hungarian , Italian , Japanese , Korean , Norwegian , Polish , Portuguese (Brazil) , Portuguese (Portugal) , Russian , Spanish , Swedish , Turkish

    • Upvote 1
  3. On 01/05/2017 at 2:24 AM, ruthan said:

     I cant control mahine, throught network (Remote desktop), because there is not user password for admin or network driver missing too.

      Edit: Some silent installer of Intel USB3 or realtek NIC drivers inserted into Start up folder could be a solution, if something like this

    Could you try Teamviewer QuickSupport into the Start up folder to control the machine?


    I wonder if you already achieve the USB3 drivers setup.

  4. Microsoft Security Advisory (2916652)

    Improperly Issued Digital Certificates Could Allow Spoofing

    Monday, December 09, 2013
    Version: 1.0
    At this time, no update is available for customers running Windows XP or Windows Server 2003, or for customers who choose not to install the automatic updater of revoked certificates.

    Microsoft security bulletin summary for December 2013

    MS13-097 2898785 replace 2888505 in MS13-088
    MS13-098 2893294 replace None
    MS13-099 2892075 replace None
    MS13-101 2893984 replace 2883150 in MS13-081
    MS13-102 2898715 replace 2849470 in MS13-062

    That's what we have for this month.

  5. For almost 2 years i used HFSLIP for slipstream (after nuhi went on "vacations") and after slipstreaming, used nlite for components removal + config + tweaks.

    In XP, i had modified the original source reg files with the tweak that makes quicklaunch bar to show in taskbar, disable annoying WGA "update", and few more tweaks that i needed so, everytime i use HFSLIP & nLite i didn't include a regfile to integrate.

    Do a test, maybe it works much better than "like 'out of the box'" and i say 'maybe' because there are unnofficial updates.

  6. Suggestions:

    - Enable 'Back' button on ISO creation page, to go directly on Location (second page).

    (In some scenarios even at the begging you know that you will need to edit your installation through 2-3 times process via nLite.)

    Enable 'Back' button and change to 'Start over'

  7. Today we will have many updates in MS13-081:

    Windows XP Service Pack 3 - (2847311) - Remote Code Execution - Critical - Replaces: - 2753842 in MS12-078

    Windows XP Service Pack 3 - (2862330) - Elevation of Privilege - Important

    Windows XP Service Pack 3 - (2862335) - Elevation of Privilege - Important

    Windows XP Service Pack 3 - (2868038) - Elevation of Privilege - Important

    Windows XP Service Pack 3 - (2883150) - Remote Code Execution - Critical - Replaces: - 2876315 in MS13-076

    Windows XP Service Pack 3 - (2884256) - Elevation of Privilege - Important

    Internet Explorer 8

    Windows XP Service Pack 3 - Internet Explorer 8 - (2879017) - Remote Code Execution - Critical - Replaces: - 2870699 in MS13-069

    Internet Explorer 6 (Optional IE 8 Fix)

    Windows XP Service Pack 3 - Internet Explorer 6 - (2879017) - Remote Code Execution - Critical - Replaces: - 2870699 in MS13-069

  8. 2. The boot sector included in nLite is old. MS uses a new boot sector in their officially-integrated XP SP3 disc. I don't know much about the boot code, but when you extract and open it with a hex editor, the new boot sector has this ASCII string:

    The old one has only 'SETUPLDR.BINBOOTFIX.BINI386'.

    The 'AMD64' that you have seen in the boot sector, is for XP x64.

  9. Now you restart the same thing except you load "Last Session". nLite will show you that you have SP1, that you choosed to "integrate a SP" and to "Remove components", I suspect AT THAT POINT, it has already "detecte/reads/decided" that the components listed for removal in the ini files are "present or not" and thus "to be removed for real or ignored". ...but Blaster Removal Tool is NOT present yet. This results in the fact that AFTER you integrated the Service Pack, you are presented with the list of components to be removed, but "Blaster removal tool", altough being listed (like your 1st time), is now still unticked. So Same source, same actions, different results. Same for few languages.

    That's why I say that the presets should (if possible) be rechecked after the SP (or any pack) is integrated, just before presenting the list of components to be removed.

    May i ask you if you have a localized setup of nLite?

    It can be a "normal" behavior in nLite in the case of, when you use a localized nLite (translated to your language), nLite only Save to your "Last session.ini" what is translated, if an option is not translated or its ID is not integrated in the translation file, is not going to be added to the "Last session.ini" file and there is when you get "the unticked" option.

  10. There is confusion with presets, as you start piling up last sessions, they would need to be merged

    The first times that has really been a nightmare, also because I didn't expect such behaviour (after the first image I was like: "my nLite settings..wtf!?").

    Luckly, now I don't need to change much configs. :sneaky:

    A nLite auto-merge feature or a global setting or, at least, some warning.. would be nice.

    My main complaint is that it modifies a lot of setup files to remove comments and white space on every run. This makes it harder to compare the differences when using version control to check what changes are made.

    I would like to have a detailed info tab in nLite which describes exactly what files are modified and why it is necessary to make those changes. It should also explain what nhelper.exe is doing and why it is added.

    I totally agree with this!!

    That would be useful also when you need to add manual tweaks.

    I disagree somewhat with you guys.

    Piling up last session preset is not a big deal once you understand its behavior.

    You can use names or numbers or a combination of them.

    There are 2 preset files, both have the same name with the difference in "_u", wich is used by the unnattended settings, any preset that you have with whatever name you have changed, it is going to be recognized by nLite. For me has been very easy to find 6 presets after try&error, i started by renaming with names.

    The difference between one or the other i have found with 'beyond compare' (trialware), not a big deal.

    I prefer to keep off too many details because it would be too much work and it will take too much room in the screen, i like the last nLite behavior (v1.4.9.1).


    I think that it is very easy to add, and is related to last session presets, add rename last session on preset selection after its first time of nLite use.

    Additional to it, option to add/edit a description in the preset in the same section, useful when using more than one OS or nLiting the same OS in a different way.

    One more, pre-set a name to a new "last session file that is going to be created with nlite" instead of leave it by default.

    Has been a long time that i haven't used nLite, my last updated source is somewhat outdated, maybe a year but i used HFSLIP for slipstream and nLite for component removal, tweaks and unnattended source.

  11. Well, it may be so, perhaps you are right. Yet I would use an antivirus program for Windows to check a Windows partition, just to be sure.

    While not being specific with antivirus, is better to do scans from linux because there is a chance that viruses get hidden for antivirus for windows.


    I'm going to talk about kaspersky because i have used sometime ago. When it runs installed in windows environment, you can do a live CD/DVD (from the installed kaspersky) to scan your computer in case that "kaspersky for windows" didn't found anything or windows got scr**ed by some kind of virus. Well, this "live CD" runs only in Linux, if you try, you'll notice when it starts loading linux modules.


    So, as you stated "an antivirus for Linux would check for linux viruses", is not right and the best option to check for virus in windows, is from Linux because the virus can't hide or protect itself in any running process (sometimes these virus are running its own modules as a service to protect itself from antivirus, can't remember a name to tell but there are many of them acting like that).

  12. I do call my ISP tech support around once a month and i laugh when they ask for my OS because my answer is "linux", then they go to the hardware and i say "the cablemodem is wired only, power unplugged for minutes or all night because there is no button reset". That takes less than ten minutes to have it fixed by increasing something where they are or just get the answer "a technician is heading to your home tomorrow".

    The problem has been that technicians do a barely good job when they come to check and/or repair, the bad thing is an expensive monthly billing with any kind of tech support included, needed or not.

  • Create New...