win32

Yeah, it can be temporary. The change in OS identifier is instant and quite simple. Chrome 49 is definitely workable. Firefox 52.9 ESR as well, though you'll have to find a workaround to deal with the extension signature validation issue. Serpent 52 is the newest version and is updated weekly. There's also a Serpent 55 but it's rarely updated and different branch. should work though. And roytam1 also releases New Moon 28.x.x on the same weekly schedule, which is a fork of Pale Moon. And I just booted into my win2k VM with Office 2007. Even with no fcwin2k entries and the OS identifying as good ol' 5.00.2195 SP4, Office apps opened without issue. weird.

I've done 2010, documented it in another thread a couple months ago. Installation of the full suite failed due to inability to start the "Office Software Protection Service", but I got PowerPoint Viewer 2010 running somewhat stable in a debugger. The only visible change will be "5.01.2600 Service Pack 3" under Windows 2000 in the System control panel applet. CMD will stay the same (actually BWC replaced it with XP's, so the copyright date is now 2001 instead of 1999). Don't knock the XP components though - the Device Manager in our win2k is actually the one from XP SP2 which makes it easier to see hardware IDs. You could always change it back when you're not using Office. I was thinking of blackwingcat's packages for stuff like .NET 3/4, VC++ 2017 etc. That stuff isn't intended for XP or newer. The newest Chromium browser is 360 Extreme Explorer (Chromium 69). It still has some issues with extensions and you may want to go for the Russian repack instead of the official Chinese version. But Advanced Chrome 54 works too. For firefox-based browsers, check out @roytam1's work (and @i430VX's installer). It works very well, extensions and all. Serpent 52 is my main browser.

Yeah, I did install SP3 with no ill effects. But yes, I was unable to uninstall Office 2007. Not even RipOutOffice2007 worked! Though there is a manual removal guide: http://web.archive.org/web/20090717095827/https://support.microsoft.com/kb/928218 You may want to use NNN4NT5 so the whole system thinks it's XP, as I described earlier. The only reason why you'd need to change it back to 2000 after that would be to install MS OS components destined for Windows 2000.

No, just the main executable for each program.

Same instructions, but just replace "setup.exe" with the office executables. The font thing is also odd. It should come with calibri. Have you done a search for calibri.ttf in \WINNT\Fonts? Do other fonts work? And the msvcr90.dll thing can be solved by replacing riched20.dll, as was explained earlier in this convo.

Use fcwin2k on every Office application executable so they think they're on XP.

Yes. You can't slipstream the extended kernel easily though. Everything should go to plan.

I've run it on Windows 10 before. No ill effects whatsoever. Same with Windows 2000, but I couldn't get to work in XP x64. All Windows Updates have a command line switch to extract files without installing any components. It looks like the installer is running, but all it's doing is copying files to a specified location (in HFSLIP's case, it's specified beforehand).

Unfortunately, distribution of Windows OS files (or other commercial/proprietary software) is not allowed on MSFN. But if you were to temporarily disable UAC, delete everything inside the SOURCESS folder and rerun HFSLIP 2000, you'd probably get a working setup.

No. It really hurts the OS' performance.

The options window should always come up when the extended kernel setup is loaded. The large text box on the right of the options window will explain the rationale behind each checkbox. The Vista MUI one should definitely be always checked, XP-compatible winsock is specified as causing freezes with browsers and security software but I'm running fine with it installed, and may be necessary for Outlook 2007 to work properly as I said earlier. The slow bootup is not usual behaviour, and something may very well be broken. Are IE6, DX9 and WMP9 present?

I didn't know that you were going to run HFSLIP on an NT6 system. In this case, I'd strongly recommend approving the UAC prompts (or disabling it altogether). The update installers are supposed to execute, but with an "extract" switch to prepare for integration into the install media, not for installation on the machine itself. SOURCESS is the folder containing your newly slipstreamed Windows 2000 source. It also creates a bootable ISO containing the same files.

I'm sorry for all of the confusion I'm creating, but I only brought up nLite because I assumed that you wanted to integrate AHCI drivers (because F6 can be a pain on anything without a floppy drive). HFSLIP is its own command line application. I need a refresher for the exact procedure of operation, but the readme should explain the most basic instructions. You will not need USP 5.1 with the HFSLIP 2000 FullPack integrated.

I do not believe that there have been recent tests of Outlook with the newer extended kernels, complete with the XP-compatible winsock. So it may work now.

Go here (https://mega.nz/#F!2lBVBBLI!WqmqhpxuX0qyCY1LiX4-gw) where you will find an "HFSLIP" and then "FullPack" folder. Download the 7z file in the second folder. N.B. use nLite on your win2k source before HFSLIP, or else you will be in for even more pain. No, you only need extended core if you need to use incompatible XP drivers, > 4 GB of RAM and/or more than 2 CPU threads. Offhand, you can just go to the bitmaps of ntoskrnl.exe, find the boot screen for your version of win2k, then open up a copy of the original ntoskrnl.exe, export the bitmap from the original, then paste it into the modified one. It's a lot easier than for XP because it doesn't use a weird custom color palette. Of course, you will need to replace the file from another OS.

Do you have Platform Update and Platform Update Supplement installed? If it's just a matter of a few files, you could try to copy them from Windows 7.

Were you actually able to run the unpacker under win2k? I couldn't and had to do it in XP. But yes, this version cuts out most if not all of the Chinese telemetry, as confirmed by kerio not bombarding me with connection requests. I still can't get uBlock Origin to install though (in win2k). But uMatrix does work better than it did about seven months ago. Unfortunately youtube doesn't work very well, as it shows me nothing but blank video thumbnails, which appears to be the fault of uMatrix. If only google ads didn't have crypto mining routines and redirects galore... SetThreadDescription and DiscardVirtualMemory are key missing APIs in kernel32.dll.

fcwin2k should work just as good for installing Chrome. WMP 9 definitely works for me, and @blackwingcat has made special versions of WMP10 and 11. I found this thread, which mentions a possible solution to the osetup.dll error: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_install-mso_other-mso_2007/installing-office-2007-from-a-download-file-fails/cc2f6a2b-4312-454b-b172-a08c01085556

That's for the chrome tool. for fcwin2k, you do the following: 1. click "refer" next to the "File" field at the top of the window. 2. point it to setup.exe 3. Select "Windows XP" from the "OS Ver" drop-down box 4. Click "CompatSave" then "CompatRun" As for the stability of the extended kernel, no. If even WMP is broken, you may want to start over.

I don't know what to tell you. I have successfully installed Office 2007 in various win2k configs, including with USP 5.1, HFSLIP 2000 FullPack slipstream, etc. Do you have .NET 2.0 installed? Have you tried using fcwin2k instead?

The extended kernel updates riched20.dll. So extract the contents of the USP 5.1 executable with 7zip, where you'll find riched20.dl_, extract riched20.dll from that and put it in system32.

You should try replacing riched20.dll in system32 with the one from XP SP3 or win2k USP5.1.

You can just run them.

You'll find NNN4NT5 (along with fcwin2k, which is for tricking individual programs), in the cab file downloadable here: http://blog.livedoor.jp/blackwingcat/archives/1949743.html

NNN4NT5.exe is the name of the file. Some people have had to install the extended kernel twice to get the start menu folder to appear.