Leaderboard

A very strange situation on the x86 side of things; it appears that in general for some imported ntdll functions on x86, they crash when being imported. Forward exporting functions doesn't seem to work either. But replicating the ntdll function in kernel32 works fine (in the case of RtlSetThreadErrorMode). But what about NtQueryInformationProcess and the like? You can't put stuff that interacts with ring-0 all over the place! I'm not sure what exactly is wrong, but it may be some strange artifact of WOW64 switching/thunking. I have yet to test any kernel extensions on a pure Vista x86, but I did make an attempt at kernel extensions on XP x86 for a specific purpose and did not have issues with import calls failing much like on Vista WOW64. With these discoveries in mind, my solution to this problem is to take one of the components of the x86 ntdll wrapper, ntnew, which was to house the code for the new x86 ntdll functions, and add the new x86 kernel32 functions to it, thus it will now be known as ntk32.dll. This is how this wrapper will be structured: Programs needing new ntdll functions: call ntext.dll instead, which will forward new functions to ntk32.dll. Programs needing new kernel32 functions: call kernel32.dll, which is the existing one augmented with an expanded export table, which in turn will forward new functions to ntk32.dll. Hopefully this should maximize portability of the x86 extended kernel components between WOW64 and pure x86 Vista. I just hope that calling the Nt/Zw* functions will be successful as that has yet to be tested and I wonder if it will be possible from ntext as opposed to ntdll. That will be a major setback if it cannot. UPDATE: NtQueryInformationProcess called through ntnew (have yet to implement kernel32 stuff in there yet), is working.

Wow ! This is just wow ! Fellow members , where are your likes !? Win32 , by pure x86 Vista you mean RTM ?

That sounds good, I'll give it a try. Thanks to Sampei.Nihira for posting the link. Update: just installed it and now the github pages are coming in. Thanks again since I use that site quite a bit and don't have to rely on quantum. I haven't even bothered to infest my system with any chromium versions.

UXP browsers like NM28/St52 are no longer supported by Microsoft-owned GitHub, as they now only target the four "major" browsers, all some form of Chromium forks (Google Chrome, Mozilla Firefox[Quantum] > 68.0, Opera, Microsoft [Chr]Edge) ; they're now using Chromium-only frameworks like WebComponents/Custom Elements/Shadow Dom etc, that the UXP platform doesn't support currently, and is, to be realistic, still far away from supporting in the (near?) future... In the specific case of GitHub, a true life-saver is the legacy extension referenced just three posts above by @Sampei.Nihira, github-wc-polyfill, currently at version 1.1.7 ; unlike NM28, in St52 it would install (and eventually update) right out of the box, without tinkering with its install.rdf file; you have to be, though, on a fairly recent version of Serpent 52, as it relies on APIs found in relatively recent UXP snapshots (anything within the last 4 months should be OK, if you ask me...).

SP2 is the intended target, but it is possible that this wrapper could be adapted to RTM versions of kernel32 and ntdll.

I'm too late! Only now I came to know about R.Loew's amazing work towards making Windows 9x usable even now. What a legend he was!!! Very saddening news. RIP R.Loew . You will be gone but NEVER forgotten

So do I......hahaha

Selectable 100G and more partition and quick format partition are  available for Windows 2000 Setup. Although it is not extended kernel , but it is very long time issue for windows 2000 users :3 I released Japanese and English version .

So you've just confirmed everything that I wrote , you need to look at >supported devices list< first , about "nv_dspi.inf" it was a simple typo , not sure why you even brought that up if you already found that device in officialy >supported devices list<. About "beleive" , supported devices list is the official Nvidia statement and absolutely true . About your laptop , you need to make sure that it DOESN'T have OPTIMUS tech., since it won't work with Vista at all . And I think that it DOES . And all future laptops you're gonna buy , just make sure they don't have optimus too , or try to find a modded BIOS , where it is disabled . But it is recommended for advanced users only.

... Wrong link there (to the test site itself!) Should've been: https://forum.palemoon.org/viewtopic.php?f=70&t=25830&p=205294 BTW, many thanks for raising this "there" (as you seem to be one of the very few that can coexist in both "camps" , without being given the "enemy agent" (and other, more derogatory) "accolade" by you know who... As the case is, @JustOff once more pinpointed correctly and swiftly the culprit ; too bad Moonchild (instigated by you know who) recently ostracised him from the core of the MCP devs... IMHO, he was the only one really sane person among them...

The HD Audio Controller is a "PCI device" in the Intel chipset (alongside sata, usb) through which the "hd audio bus" device is accessed. To identify unknown devices, you could use a program that has a vendor database included, such as AIDA64/Everest (commercial trialware) - Devices->Physical,PCI, Unknown Devices PCI32 (old, out of date) or System Information Viewer (freeware) among others. Or throw drivers at them until one sticks. I like the above programs because they don't download random potentially unwanted drivers. PCI bus 0, device 27, function 0 could be an audio device, but I am not certain. It's 27 on my systems, and the ID matches some integrated audio.

Yes , this may very well be true . I would strongly advise against replacing it , esp. for those who love HD content. As you all know , Win 7 is just so much worse in terms of h264 files playback , and pretty much everything else. They look washed out , pale , etc. And for those who simply can't live without firefox, why not do it locally ?

To be honest you only need brain to stay secure. No matter what kind of OS you run. Microsoft is desperately trying to kill off Windows 7/8.1 They only do things to help windows 10 marketshare. Like releasing d3d12 for windows 7, but intentionaly crippling performance on windows 7. They even did not bother with the release for windows 8.1 Microsoft became really evil lately. They are hungry for marketshare since iOS beat them in USA.