Leaderboard

For those with access to the MEGA folder, you will notice two .7z files: vistaexkernsetup_11222020.7z is an installer for the newest set of extended kernel files. Must be run as admin. One improvement in the new files is the removal of subsystem version checking, so you don't have to change Firefox's Subsystem version from 6.1. SetWaitableTimerEx has been added as well, which allows Office 2019 setup to run, but its version check is very complicated. Another function needs to be added for Office Click-to-Run components to run anyway: mfplatsetup.7z is an installer for Windows 7's Media Foundation files, which are used by recent Firefox-based browsers.

This is an updated tutorial of the one cluberti posted here. To get started you need the Windows Performance Tools Kit. Read here how to install it: http://www.msfn.org/board/index.php?showtopic=146919 Now open a command prompt with admin rights and run the following commands: For boot tracing: xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP Attention: Some users reported that they get a bugcheck (BSOD) when using the DRIVERS flag in the boot trace command. If you get this, use system restore to go back to a working Windows and run the command without DRIVERS xbootmgr -trace boot -traceFlags BASE+CSWITCH+POWER -resultPath C:\TEMPAlso change the name in the command to generate the XML. I've send some dumps to Microsoft, they look at the issue right now. For shutdown tracing: xbootmgr -trace shutdown -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Standby+Resume: xbootmgr -trace standby -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Hibernate+Resume: xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPreplace C:\TEMP with any temp directory on your machine as necessary to store the output files All of these will shutdown, hibernate, or standby your box, and then reboot to finish tracing. Once Vista/Server 2008(R2) or Windows 7 does reboot, log back in as necessary and once the countdown timer finishes, you should now have some tracing files in C:\TEMP. If asked, upload or provide the file(s) generated in C:\TEMP (or the directory you chose) on a download share for analysis. Analyses of the boot trace: To start create a summary xml file, run this command (replace the name with the name of your etl file) xperf /tti -i boot_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_boot.xml -a bootNow you see this picture.: You have too look at the timing node. All time values are in ms. The value timing bootDoneViaExplorer shows the time, Windows needs to boot to the desktop. The value bootDoneViaPostBoot is the time (+10s idle detection) which Windows needs to boot completly after finishing all startup applications. those values show you a summary. The MainPathBoot Phase PreSMSS Subphase So if the time takes too long for you, look inside the <PNP> node which driver is loading too slowly. SMSSInit Subphase So if the SMSSInit Phase takes too long, try to get an graphic card driver update. WinLogonInit Subphase If you have too long WinLogonInit Time, open the etl file and scroll to the service graph and look for a long delay. In this example the service SavService (Sophos Anti-Virus\SavService.exe) is part of the Plug and Play group and causes a delay because the service takes too long to start. Try to get an update for the hanging service or remove the software. ExplorerInit Subphase So if the ExplorerInit phase takes too long, make sure you minimize the services which use a lot of CPU power and make sure your AV Tool doesn't hurt too much. If it doesn't change the tool and try a different. The PostBoot Phase If post boot takes too long, reduce the number of running applications at startup with the help of msconfig.exe or AutoRuns. When you have a HDD (no SSD!) and you want to speedup the boot, run the optimization from this guide: http://www.msfn.org/board/index.php?showtopic=140262 Analyses of the shutdown trace: The shutdown is divided into this 3 parts: To generate an XML summary of shutdown, use the -a shutdown action with Xperf: xperf /tti -i shutdown_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_shutdown.xml -a shutdownOpen the XML and you see this: It shows you the most relevant data. <timing shutdownTime="23184" servicesShutdownDuration="1513">The shutdownTime is in this example 23s. Stopping the services takes 1.5s which is fast. Next you have an entry for all sessions. Starting with Vista, all services run in Session 0 (Session 0 Isolation) and each user gets his one Session (1,2,..,n). sessionShutdown sessionID="1" duration="3321">shows the time which it takes to stop all applications which the user is running. In this example it takes 3.3seconds. UserSession Phase sessionShutdown sessionID="0" duration="1513">The value sessionShutdown sessionID="0" shows the servicesShutdownDuration. So you can see which service takes too long to stop. SystemSession Phase In both cases expand the node and look at the shutdownDuration value. It helps you to identify a hanging application are service. KernelShutdown Phase To calculate the time spent in KernelShutdown, subtract the time that is required to shut down the system and user sessions from shutdownTime. In my example: KernelShutdown = 23184 - 3321 - 1513 = 18350 In this case the 18.35 seconds are very slow. In the <interval> you see an entry ZeroHiberFile which takes too long. In this expample the user enabled the Option ClearPageFileAtShutdown under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management to 1. This overrides the hiberbation file with 0 to delete personal data. This causes the huge slowdown. Setting this option to 0 would save 12.64 seconds of shutdown time. That is all you need to analyze slow shutdown issues. Analyses of the Hibernation trace:: To generate the XML, run this command: xperf /tti -i hibernate_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_hibernation.xml -a suspendAnalyses of the Sleep/Resume trace:: xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspendOpen the XMLs and look for long BIOS init times and services/application which take very long to suspend and resume. For deeper analysis refer to the Sleep and Hibernate Transitions part of theWindows On/Off Transition Performance Analysis Guide from Microsoft. The pictures Shutdown_cancel.png, Shutdown_picture.png and Boot_MainPathBoot.png were taken from this Windows On/Off Transition Performance Analysis Guide. Read it if you need more information. // Edit: 2010-11-28 Add the explanation of the boot process // Edit: 2010-10-11 added the optimization guide // Edit: 2010-10-09 If you get a BSOD (Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) while making traces, REMOVE ALL USB DEVICES and reboot! When making a new trace remove the DRIVERS flag from the command line! // Edit: 2010-02-04 Added the -noPrepReboot command at shutdown tracing to prevent the preparatory reboot during a shutdown/rebootCycle trace. Usually, the reboot is required to ensure a consistent machine state before the first shutdown if multiple traces are being taken. // Edit: 2010-05-08 Added the link to the Visual Studio 2010 Diagnostic Tool as alternative download to get the Windows Performance Toolkit Installers. Added some pictures.

I was wondering how much you guys pay in other countries. I live in the Czech republic and I pay around 30 dollars for 120 down and 12 up. It is really stable, but since I do not live in big city like Prague this is the absolute best I can get here. https://prnt.sc/vp52nn

I edited this to slowly update this list with working games. My tested games: Call of Duty Modern Warfare - Has rendering issues (as of vk3d version 2.1, the game renders half properly, but crashes on startup) Cyberpunk 2077 - Devs says that the game should work properly only on amd hardware, but in my case rtx 2060 runs the game just ok. Every 2 hours the game freezes (aprox.) Devs game list: AC: Valhalla The Division Control Death Stranding Devil May Cry 5 Ghostrunner Horizon Zero Dawn Metro Exodus Monster Hunter World Resident Evil 2 / 3 D3D12 Library https://github.com/HansKristian-Work/vkd3d-proton/releases

100/20 (avg 94/18) $45 (promo rate, will go to $70 in a year)

Boot from your Windows 8.1 USB, do a shift+f10, and go to your system32 folder. delete kernel32.dll rename kernel32.dll.bak kernel32.dll Repeat this for user32, shell32, ole32, dwmapi, uxtheme.

CHKDSK /f IMHO

New ASUS SABERTOOTH X99 & ASUS Z10PE-D16 WS XP x64 Drivers: (07-18-2018). Device Drivers: Intel(R) C610 series X99 chipset LPC Controller - 8D44, Intel(R) C610series X99 chipset PCI Express Root Port #1 - 8D10, Intel(R) C610 series X99 chipset PCI Express Root Port #3 - 8D14, Intel(R) C610 series X99 chipset PCI Express Root Port #4 - 8D16, Intel(R) C610 series X99 chipset SMBus Controller - 8D22, Intel(R) C610 series X99 chipset SPSR - 8D7C, Intel(R) C610 series X99 chipset USB Enhanced Host Controller #1 - 8D26, Intel(R) C610 series X99 chipset USB Enhanced Host Controller #2 - 8D2D This is a mixed archive of some new July 2018 compatible / stable XP x64 drivers for the SABERTOOTH X99 & Z10PE-D16 WS motherboards. Please be careful to match the drivers to the appropriate devices for your motherboard within device manager. Be sure to make a Backup of your Operating System always before ever proceeding with installing new drivers. Some of these drivers if not most of them can possibly work with other X99 or related motherboards. Download Link: http://www.mediafire.com/file/yv3n8li3ov5skwt/SABERTOOTH_X99_%26_Z10PE-D16_WS_XPx64_%2807-18-2018%29.rar/file Enjoy! - XP-x64-Lover

Hello everyone, I've been using XP for over 12 years and have not had to fiddle with it much all that time, ... Until now. It has finally decided that some software that it has aquired doesn't agree with it. It has been so long since I had to play with OS's that I have forgotten all the techniques and tricks to re-install it successfully. But thats what I think I'm going to have to do. So I've come here to get some advice on how to proceed.

From Belgium, hello @mattrix and welcome to MSFN! I hope you enjoy the forums! Have a nice day. hpwamr

I hate when people use that responsive web design with some heavy java script on their websites..

Not on play store but Youtube Vanced is worth trying for a better Youtube experience.It's good, free and no ads at all

This topic was moved into funny farm and was originally about something else. I don't remember what it was about. But that is not important anymore. Now this thread is about:

The last Windows 9x official NVidia Video Driver Version 81.98 and the unofficial Version 82.69 both hang during Shutdown when used with 6xxx or 7xxx Video Cards. I have analyzed the problem and it appears that one of a couple of System Broadcast Message Call never returns. I have developed a Patch to bypass these Messages. This Patch is for Windows 98SE and Windows ME. It has not been tested with Windows 98FE or Windows 95. Since this Patch only affects Shutdown Functions, it should not have any affect on normal operations. Boot to DOS seemed unaffected on the one machine I tested. I have not tested Suspend or Hibernate as my test machine didn't support it before. I have not tested 82.16 or 82.69, but other people have. The Patch is applied to the WINDOWS\SYSTEM\NVCORE.VXD File as follows: Version 81.98: (Revised 07/29) 144: 24 -> 3B 31F35E: 9E 55 E5 FF -> C2 05 00 00 31F924: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -> 3C 04 74 08 3C 25 74 04 3C 32 75 02 B0 52 89 44 24 04 E9 C5 4F E5 FF Version 82.16: (Revised 07/29) 144: AC -> C3 31F6E6: E6 54 E5 FF -> C2 05 00 00 31FCAC: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -> 3C 04 74 08 3C 25 74 04 3C 32 75 02 B0 52 89 44 24 04 E9 0D 4F E5 FF Version 82.69: (Revised 07/29) 144: C8 -> DF 329802: DA A7 E4 FF -> C2 05 00 00 329DC8: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -> 3C 04 74 08 3C 25 74 04 3C 32 75 02 B0 52 89 44 24 04 E9 01 A2 E4 FF Revised 07/29/15 to include third System Message for Windows ME

This mod takes the start button from the early Longhorn builds and puts it into Windows XP's explorer. The start button shown below is the only modification to explorer. Installation Instructions: 1. extract the archive containing replacer.cmd and the modded explorer 2. Locate the original explorer.exe in x:\Windows 3. Open replacer.cmd, drag said original explorer.exe into replacer.cmd, press enter 4. Drag the new explorer.exe file from the archive in (_XPmodded for x86 and XP_x64_modded for x64), press enter 5. Reboot and enjoy NOTE: Installing service packs (including uSP4) will probably undo this, take this into consideration when installing. Credits: Most go to DeviantArt user Rafax64, I used the bitmap from his modded explorer. This is also where replacer.exe came from. Rafax64 modded explorer: https://www.deviantart.com/rafax64/art/Longhorn-Explorer-Mod-for-XP-132097072 Download link: https://drive.google.com/file/d/1I0mLHemUrzbPZO01QxIm8oGvz4QAXiG0/view?usp=sharing

Get the Extended Kernel32 to release quality 1st, before engaging in an even more difficult project. Your dispersiveness undermines your credibility. With all due respect.