Leaderboard

MT: Well possible some of us are not the brightest here when it comes to computer science, but the fault for this misunderstanding here is your's. Not indicating what you're talking about exactly, using dev-speak, and clearly talking to RT in first post. Especially not bothering to mention to normal users who are not clairvoyant that "ShellService" might have anything to do with "Set Default Browser". That's absolutely not obvious, just a chance for blind guessing. Then again, it probably was your intention, to get more opportunities for jerking around. RainyShadow said: > As a last resort, you can try to use Control Panel > Folder Options > File Types > and manually change the assotiations. When using that method, this great little tool is an easier alternative: https://www.nirsoft.net/utils/file_types_manager.html One possibility for example is to open it and search inside where the current default "iceape" is used, then copy those lines for another browser. Am no expert for that stuff either, but guess at least four entries should be set: For ".html" and ".htm" and "http" and "https"

@Matt A. Tobin Nobody is required to know everything about the crap some self-important jerk is doing over the internet. Now, would you, please, remove yourself from here until you fix your attitude! @TechnoRelic As a last resort, you can try to use Control Panel > Folder Options > File Types and manually change the assotiations. No clue if it will work though, if the stupid browser is broken, As a quick test try dragging a .html file over to bnavigator.exe and select "Open with".

Wouldn't the OS-level SHA-2 support be sufficient? And which Rust are you talking about? The programming language upon which newer Firefoxes are built, or the game? I'm trying. I'd really love to have Vista running stable on my Kaby Lake laptop as well. 2012R2 looks like Windows 1, and having Vista's UI would be a major improvement (I'm also going to work on getting graphics drivers like my Intel HD 620 ones working too). I had previously narrowed it down to the function LoadLibraryExW, and I recently installed Windows 7 build 6519 which has a very similar version of the function, and also doesn't have those bugs. But simply transplanting the function failed, as it resulted in a BSOD where "the system couldn't find the file specified (@98w9asoise590dj.dll [or similar nonsense file name])". But after trying a few more things, I think I've narrowed down the problems to one particular part of the function. But making a good patch will be very challenging. What also doesn't help is that this laptop has broken hinges, so I can't bring it to where I am half of the time.

yeah, thats not the same as right click -> page info -> permissions which has no problem. anyway, this is fixed in repo and next build should have this fix applied.

To prevent user confusion, I strongly recommend disregarding the tutorials and contacting me directly instead about the extended kernel. The original post was removed as it was continuing to confuse users. There will be further discussion about the evolution of the extended kernel in the coming pages.

The bootsect.exe need depends on which OS you partition and format the USB stick. Windows 2000 and XP have a single type of PBR code/bootsector. Vista and later will automatically use their own bootsector but there is this tool, bootsect.exe that can write either the /NT52 bootector (please read as 2000/XP one) or the /NT60 one (Pleae read Vista/7, etc. one). If you have on the other PC where you partition/format the USB stick 2000 or XP you don't need to run it. If you have on the other PC where you partition/format the USB stick Vista or 7 you need to run it with the /NT52 swotch to change the PBR. http://vm1.duckdns.org/Public/IntegrateDrv/IntegrateDrv_1.1.9.zip contains BOTH the 32 bit and 64 bit executables, the 32 bit one is in \IntegrateDrv\x86\ See the picture on the given page: http://vm1.duckdns.org/Public/IntegrateDrv/IntegrateDrv.htm You want to extract somewhere the whole \IntegrateDrv\ folder, then navigate to the \IntegrateDrv\x86\ and run the IntegrateDrv.exe from there. jaclaz

@Dave-H The two (semi-universal) versions of HDAICOUT.HDA I mentioned both sent (after an intitial Codec Reset) six SET-verbs to ALL widgets in range 02-1F (30 widgets). Widgets listen only to verbs they are programmed for (and must conform to Intel's High Definition Audio Specification), otherwise verbs are neglected. So those versions are not codec-specific. True is: your system needed HDAICOUT.HDA, doesn't work out-of-the-box without.

You can try to use the Winnt32 approach with Windows 2000: http://reboot.pro/topic/18107-integratedrv-install-xp-2003-to-a-usb-30-disk-and-boot-from-it/ You need to make an on USB "localsource" with Winnt32 running on another PC, then add the Wait4UFD driver, then add the AHCI/SATA driver with integratedrv. Will it work? Cannot say. Personally I would still try making a plainer attempt with no AHCI, via DOS and WINNT.EXE on FAT32. https://msfn.org/board/topic/181798-the-installation-of-windows-2000-was-blocked-in-lenovo-g500/?do=findComment&comment=1186272 jaclaz

you may reset "shell.checkDefaultClient" in about:config, close browser, set IE as default, reopen browser and it should ask you to set default.

Download the oldest chipset drivers for your board, let them extract, then install them using device manager. Do not install AMD PSP or PCI. ESPECIALLY NOT PSP.

I wouldnt have the first clue how to make them show up.

Hi, I'm pool7. Long time lurker... Used to have an account up until at least July 1st (last email I received from a topic I was subscribed to) Tried to login today; my account was apparently deleted (I'm guessing due to inactivity). I'm interested in old Operating Systems and software, mainly from the 90s onwards. Always looking for tweaks, customization and improvements.

it's not that simple as replacing functions, many of them are done in pure assembly. unless sseplus uses system-wide trap or this can't be done.

According to Microsoft, the end date for Windows 7 ESU updates is January 10, 2023. The end date for POSReady 7 is October 12, 2021. And look at this: If you apply ESU to POSReady, you get updates until October 14, 2024! If we were able to trick Windows Update to thinking Windows 7 supports ESU and POSReady, that would mean an extra 4 years of support! And provided that Windows Server 2008 has extra support, it also has up to January 2023, meaning more support for Vista, and if we apply Embedded updates, that means more time! Although considering Windows Vista support ended for Windows Update, that would probably not happen.