Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/21/2020 in all areas

  1. It's official but not on ftp.mozilla.org.
    2 points
  2. I've attached RAR5 compressed files with lists of download links for all official updates for Vista 32-bit and 64-bit Post SP2 up to April 2017. Includes all language packs for Vista, IE9 and local Help update. Also included are Ultimate Extras, Optionals and .NET Framework 3.5 SP1 / 4.52 with updates. Superseded updates are not included except for a few ones just to satisfy Windows Update. Hotfixes are not included, unless available through Windows Update. Someone please mirror them on Web Archive. ASAP. EDIT: Updated files with .NET Framework 3.5 SP1 Language Packs. Installing System Updates: If you want to install a language pack, you must do it first, by downloading and running the language pack executable. 1) Download all files from Main_URLs.txt to the same folder. 2) Using WinRAR, sort files by type and unpack all .MSU files to the same folder, overwriting existing files. Then you may delete the .MSU files to save space. 3) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 4) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 5) Run Main_Part1.bat, Main_Part2.bat and Main_Part3.bat. At the end of execution of every batch file, Windows will restart automatically. 6) Optionally you may install local copy of Help update (LangPacks_Help_URLs.txt) and the IE9 language pack (LangPacks_IE9_URLs.txt). PS: It'll take a while to install all 210+ updates. Installing .NET Framework 3.5 SP1 / 4.52 with updates: 1) Download all files from NDP35_45_URLs.txt to the same folder. 2) Unpack the WindowsVistaSP2_x86_Installer.rar or WindowsVistaSP2_x64_Installer.rar (just batch files) to the same folder where you extracted the files. 3) Open a Command Prompt with Administrator privileges and switch to the folder where the update files are. 4) Run NDP35_45_Install.bat, if needed Windows will restart automatically. 5) Optionally you may install a language pack (LangPacks_NDP35SP1_URLs.txt and LangPacks_NDP452_URLs.txt). Installing updates for optional features (only if you have installed IIS, IIS ASP, IIS FTP or Telnet from Program and Features Control Panel extension) Download all files from Features_URLs.txt and run the following .MSU packages if you have installed: IIS: KB4012373 IIS ASP: KB2124261 IIS FTP: KB975254 Telnet: KB960859 and KB3020393
    1 point
  3. Steam All of these require a steam.cfg to block updates. In the Steam folder, create a steam.cfg file, and edit it with notepad to say "BootStrapperInhibitAll=Enable" (Without quotes) and save it. Certain older Steam builds might require a patched packageinfo.vdf file. More info here The November 26th, 2018 Steam build does still work today (Even a Steam build from late 2014 can still login to this day), but it has some game compatibility issues. For example, Garry's Mod, which still officially supports even XP, will not launch with this version of the Steam client. Downloading games has been broken for some users, but it can be fixed by modding a certain file. There's a January 4th, 2019 Steam build, released after Steam dropped XP and Vista support, but works just fine on both XP and Vista. This can play better with some games, and I've confirmed that unlike the Nov 26th client, Garry's Mod works great with this client. The build was released on January 8th, 2019, but the build date is shown as January 4th, so it's listed as January 4th here. If you want to extract the client from it's package files, and confirm that it's unmodified, I've uploaded everything you need to extract the client here, Windows XP/Vista, and 7 x64 can be used to extract the client, but if you extract it on 7 x64, you'll be left with the 7 x64 CEF, which doesn't work with XP/Vista. Steam (Vista Extended Kernel) The Oct 2nd, 2019 Steam build is pretty recent, so most games still work, but some games, like Rust, which require the Steam API v20 don't work with it. There are some file modifications that are required to get it working. It still works with the browser from the XP client, but mouse scroll is broken, and it doesn't work too well with the modern Steam site. This client also is the last client to come with version 72 of CEF, which can be used if you rename the Windows 7 x64 CEF folder to cef.winxp in Steam\bins\cef, then add -no-cef-sandbox to the Steam shortcut target. It does have some issues though, but they could possibly be fixed if it were possible to make Steam treat Vista x64 exactly like Windows 7 x64. If you know how to do this, let me know. One final issue with the client is that you can't sign out of friends, so you'll always appear as online. The latest Steam build works with the file modifications, but there's no browser, which, because the new library UI is a webview, you'll be stuck using small mode. Other than that, it's quite good, but it still suffers from not being able to sign out of friends too though. I have a pre-modded copy of the June 6th, 2020 Steam client linked here. I based it off of that version since -no-browser works with it. You could try modding newer clients linked here, but for now I think it's all that'd be needed for gaming on Vista. The June 6th client is getting a bit old, and I haven't been uploading clients anymore as my upload is very slow, but I have a friend that made a 2020-10 modded client, which works with newer versions of Rust and probably TF2. There is a CLI Steam client which works on Vista, but the website it's hosted on is involved with software piracy, so I won't mention anything else about it. Origin There was a separate XP and Vista client in 2015, but Origin then decided to break it in 2016. From what I can see, you'd need to spoof your Windows version to attempt to install normal Origin. Also, Origin likes to update all the time recently, which will require you to reinstall it all the time. I haven't tested if the client even launches on Vista, it might need to be modded in some way. Origin also likes to lock out older clients for some reason, so you might need to make any older versions report as a newer version to Origin servers if the newer version doesn't work. I don't know much about modding Origin and I haven't tried much, so this is pretty basic. GOG Galaxy I've done some testing, and have found GOG Galaxy 1.2.34.10 to be the newest(?) working version on Vista. (Might require extended kernel) GOG Galaxy 1.2.37.7 is the first I've tested to not work on Vista. It's the CEF that's broken, so it might be possible to port the older CEF to newer builds, but I'm not going to bother with that. I have not tested GOG Galaxy 2.0. Other Game Clients Uplay has a older version that still works with Vista, and from what I've seen, it's still fully functional to this day, so in this regard, Uplay is actually the best in something for once. Legendary is a free and open source alternative client for the Epic Games Store. I don't know if it works on stock Vista, but it likely does. I recommend everyone use this client even on 7 and newer instead of EGS, as EGS is owned partly by Tencent, so lots of telemetry in the official client is guaranteed. Playnite is similar to GOG Galaxy 2.0, as it's meant to combine Steam, Origin, Uplay, and more all into one client, but it doesn't officially support Vista, and I haven't tested it on Vista.
    1 point
  4. From Belgium, hello @pool7 and welcome to MSFN! I hope you enjoy the forums! Have a nice day. hpwamr
    1 point
  5. Try and see. That equates more or less (more less than more) to one of the possible usages of winnt32, i.e. using the syspart switch: but no, it won't work, unless you dd the whole disk or however the volume information and disk signature (much more complex than the manual way already suggested to you. jaclaz
    1 point
  6. Here are a few pieces of useful information that are related installing Windows 2000. 1. Use AHCI and integrate only the storage driver for the specific storage controller you have with nLite. 2. When integrating Intel drivers, you can only pick one PCI ID or the installer errors out saying "iastor.sys is corrupt", so choose the one that matches your storage controller. You can use Easy2Boot to check the PCI ID of your storage controller. 3. Install Windows 2000 from an optical disc whenever possible, even if that means buying blank discs.
    1 point
  7. huh, did something break or get screwed up in .1 that was not broken in .0 ?? (about the horrible freeze/lag/screen flicker) and yea, same about the icons graphic, not showing in chrome.
    1 point
  8. Let me repeat a question that went by unanswered in the past... Is it possible to use the SSEPlus project as a SSE2/3/4/xxx emulator in your builds? Would it be simple enough change for you to consider it (as in a batch of "Replace All" on the source) or it would need too much work?
    1 point
  9. Is it me, or lots of people think that WiFi == Internet?
    1 point
  10. Update (11/30/2020): The new KernelXE thread is now called "KernelXE - My Unofficial Windows 2000 Kernel", making this thread completely obsolete. Summary: KernelXE is based on kernel32 from WildBill's KB2479629-v3 and includes all of the functions present find in BlackWingCat's kernel32. KernelXE also includes a few functions not found in either kernel32 from WildBill's KB2479629-v3 or BlackWingCat's Extended Kernel. Some full functions have been used in KernelXE instead of the stubs in BlackWingCat's Extended Kernel. Download Functions: New in KernelXE: BaseSetLastNTError (from One Core API) CreateRemoteThreadEx (from One Core API) RestoreLastError (redirected to RtlRestoreLastError from ntdll) EncodeSystemPointer (redirected to RtlEncodeSystemPointer from ntdll) DecodeSystemPointer (redirected to RtlDecodeSystemPointer from ntdll) Full functions that are stubs in BWC's kernel32: GetSystemDEPPolicy SetProcessDEPPolicy GetProcessDEPPolicy GetFirmwareEnvironmentVariableW SetFirmwareEnvironmentVariableW GetFirmwareEnvironmentVariableA SetFirmwareEnvironmentVariableA CancelIoEx CancelSynchronousIo CheckForReadOnlyResource CheckRemoteDebuggerPresent SetSearchPathMode PowerClearRequest PowerCreateRequest PowerSetRequest Known Issues: A Microsoft Visual C++ Runtime Library error appears when running VMware Tools. (Solution) Some other dlls from BWC's Extended Kernel might behave erratically because of the fact that KernelXE is based on WildBill's kernel32. Note: VMware Tools must be installed before KernelXE.
    1 point
×
×
  • Create New...