Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Leaderboard


Popular Content

Showing content with the highest reputation on 12/12/2018 in all areas

  1. 1 point
    Features: - Install Windows 2k/XP/2003/2008/2012/Vista/7/8.x x86/x64 - Practically runs even on the most minimalistic WinPE - Choose able drive letter for the new Windows installation - Install Windows also if nlite/vlite has remove winnt32.exe/setup.exe - Integrate Drivers: normal PNP and Textmode Drivers also - patch uxtheme to allow unsigned Themes - Some tweaks - Support "Windows to Go" for Windows 7 and later installs - Supports WimBoot option for Windows 8.1 Update 1 - supports all current WIM files: WIM/SWM (XPRESS / LZX / XPRESS HUFFMAN = Wimboot compression) - supports unencrypted ESD files (LZMS compressed WIM) Not Supported: - No Windows embedded version (this includes WinFLP) - No Installation onto USB disk *New* only Windows 7 and later - No upgrades of existing installations As some may know the last version 1.5 had only Support for Win 2000/XP/2003. Fujianabc present an very easy approach to install Windows 7 NT 6.x fast installer basically it's simply applying the windows image from install.wim and generating the boot files. He also discovered that the drive letter of a Windows 7 image can be (opposed to Vista) easily changed. So I have added that way of installing to WinNTSetup. For the driver installation: Every driver added in NT6.x windows will be added to the driver store. So it's not recommended to add countless driver, but rather more really required ones. NT5.x massstorage driver integration is possible thanks to Mr dUSHA powerful MSSTMake.exe tool To the Unattend option: It's possible to use an unattend.xml to run the Setup unattended. But as the actual WinPE Setup Phase isn't effective in that way of install, all Winpe related settings inside the unattend.xml won't be applied. Ini config file It's possible to save all GUI-settings to a ini file: push Ctrl + S to save all settings to an ini. push Ctrl + L to load all settings from an ini. A WinNTSetup.ini file in the same dir as the app itself will be loaded automatically at startup. It also can be selected via command line: WinNTSetup.exe /cfg:"C:\mysettings.ini" more command line options To install Windows in a VHD file: - requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source - create a partitioned VHD and assign a drive letter (push Ctrl + Shift + V to use build in diskpart wrapper for this) - select the VHD drive as installation drive (make sure you boot drive ist a active primary partition on a physical disk) If you get an Antivirus warning from your AV software, please report it to them as a false positive and let them check it. Current Version: 3.9.4 WinNTSetup3.rar
  2. 1 point
    WindowsPE uses the same method that Windows OS itself does as far as I'm aware. See here for an explanation from MS: https://support.microsoft.com/en-us/help/937251/disk-drive-numbers-may-not-correspond-to-the-sata-channel-numbers-when
  3. 1 point
    Sure, "regsvr32 DWMGlass.dll" still works. Installer now automatically registers DLL only when you select Aero Glass design.
  4. 1 point
    * additional changes to match acrylic design (installer provides option which design to use) HKCU\Software\Microsoft\Windows\DWM\ - CustomThemeReflection - file with texture that is stretched over whole desktop and rendered above glass regions (default is Aero Glass Win7 reflection texture) - CustomThemeMaterial - file with texture that is rendered (tiled) above glass regions (default is Acrylic noise texture) - ColorizationGlassReflectionIntensity - opacity of reflection texture (default = 0) - MaterialOpacity - opacity of material texture (default = 4)
  5. 1 point
    Nicely done, and thank you! My only quibble is with KB4471984, which I suggest ought to be described as KB4471990 was, to show it contains the three security only npdXX files. Also one addition: for those who demand everything, the December Malicious Software Removal Tool, KB890830 is out there at the MS Update Catalog as well. (It's easily overlooked, as the same file apparently works on Win 7 and Win Server 2008 R2 as well.) As for this being "my job" ... well, no. The thing is, I'm multi-booting on this system with Win 10 v1809. Win 10 v1803, Win 7, and Vista. And for most of this year, since the unveiling of the Spectre and Meltdown vulnerabilities, it's seemed sensible to keep control of system updates in my own hands rather than trust MS system updates to make everything right automatically. To do that, I have to go out to the MS Update Catalog site at least once a month and see what's there. Since I'm looking at updates for three operating systems, adding a fourth is no big deal. And then I might as well share what I've learned with other Vista users, who are by definition compatriots .... and if I screw up, as alas happens now and then, we've all got GreenHillManiac to chomp down on that big cigar and set things right! What else? There are updates aimed specifically at .NET 3.5 this month, which is kind of ... unusual. Unusual enough that noting them specifically is probably worth doing. Generalizing wildly, some .NET patches conflict with others, and some don't. Specfically, there are a batch of .NET 2 patches, generally with names like WINDOWS6.0-KBXXXXXXX- .... MSU, that everybody ought to have on their system (or at least try to have; some of these get obsoleted and won 't install). There are some .NET 3.5 patches, named NDP3.5xxxxx or such, and they ought to be installed. Then there are .NET 4 patches, an unholy mess. These last have numbers like 4.0.X, 4.5.X, 4.6.X, and 4.7.X. The 4.0 series is aimed at Win XP, I suspect. People with 4.5 and 4.6 versions of .NET can't use the 4.0 patches. People with 4.5.0 can install 4.5.1 patches and 4.5.2 and so on, but not 4.6.X or 4.7.X patches. However, people with 4.6 can install 4.7 patches -- in fact folks at MS sometime seem confused, and you'll get something described as a .NET 4.6 patch at the MSUC site which refers to itself as a .NET 4.7 patch during installation. Hmmmm. I seem to have made a post here even if Tamris did do the heavy lifting this time. Christmas season, I recall, and this was a present. Thank your for the lovely gift, Tamris!
  6. 1 point
    Happy Holidays indeed. Enjoy this graphic from a Windows XP Winter FunPack:
  7. 1 point
    Okay, so updates for this month seem to be: KB4471325 - Security Monthly Quality Rollup for Windows Server 2008 KB4471319 - Security Only Quality Update for Windows Server 2008 KB4471990 - Security and Quality Rollup for .NET Framework 3.5 SP1, 4.5.2, 4.6 (and 4.6.1) for Windows Server 2008 SP2 KB4470640 - Security and Quality Rollup for .NET Framework 4.6 (and 4.6.1) for Windows Server 2008 SP2 KB4470637 - Security and Quality Rollup for .NET Framework 4.5.2 for Windows Server 2008 SP2 KB4471102 - Security and Quality Rollup for .NET Framework 3.5 SP1 for Windows Server 2008 SP2 KB4471984 - Security Only Update for .NET Framework 3.5 SP1, 4.5.2, 4.6 (and 4.6.1) for Windows Server 2008 KB4470500 - Security Only Update for .NET Framework 4.6 (and 4.6.1) for Windows Server 2008 KB4470493 - Security Only Update for .NET Framework 4.5.2 for Windows Server 2008 KB4470633 - Security Only Update for .NET Framework 3.5 SP1 for Windows Server 2008 KB4470199 - Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 I think that's all of them, and seems they have decided to make 2 more .NET rollups in case people want either only updates for 3.5 or only for later ones? Or did I just unnecessarily post too many updates? Also, as usual, it's better if you wait at least a week before installing them, we never know what MS might have messed up in any of the updates this time. And I hope Mike won't be mad at me for stealing his job this 1 time lol.
  8. 1 point
    Happy holidays to you and everyone! (and xp too;)
  9. 1 point
    Looks like I'm not the only nut case here. Happy Holidays!
  10. 1 point
  11. 1 point
    I am unpinning this topic as it should be fixed now in the latest release. Keys are now generated regardless the HyperV flag and both HyperV on and off keys are accepted.
  12. 1 point
  13. 1 point
    Is there written something incomprehensible on the website?
  14. 1 point
    Presentation Hello everybody, i'm skulltrial or samuka, from Betaarchive and i'm here to present my project called Shorthorn, the biggest mod for XP/2003 and it keep aliving. The most known module or subproject is One-Core-API, the base to get compatibility of newer applications designed for Vista+ systems. Site Shorthorn project now has official site: shorthornproject.com You can found links to download, material to read and others. Screenshots Shorthorn has a long history. Many things was made. You can see a litle artifacts here:
  15. 1 point
    Not at all. It's a sad day. Every time a technology that gives one a hardcopy of what one buys dies is a time some of our collective freedom is lost. You must understand one has a book or a CD/DVD with a .pdf, or with music, or whatever, one owns that... one has a text into kindle or a music in iTunes one got nothing, and it can be taken from one anytime with little or no explanation and no money back, because one had previously given them the right to do it, when buying that. Ever heard of the memory hole?
  16. 1 point
    Registry settings to import as a .reg file after installing the latest cumulative IE8 update:
×
×
  • Create New...