Leaderboard

Sumatra PDF 3.3 Ported by Barcode http://www.filedropper.com/testpdf2

I appear to have exhausted all reasonable options for modifying the import table aside from rebuilding it from scratch. But shell32 calls over 1200 functions so that is practically impossible. The procedure for doing this on x86 is considerably easier thanks to PE Maker. So I decided to call NtQueryInformationFile instead and now Waterfox Classic 2020.3.1 including e10s works. We are back on track. Even took a peek inside Server 2019's uefi.sys and dxgkrnl.sys. The latter has what appears to be calling dozens of functions missing from ntoskrnl.exe , yet uefi.sys only has about 4.

PE Maker is incompatible with x64 files. While it will show some basic information about x64 files, you cannot edit them nor manipulate their import/export tables. Use CFF Explorer to change the subsystem versions (they will appear in the table that appears after clicking "optional headers").

Hi siria, thanks for your help, you're wonderful! My YouTube search engine for RetroZilla uses similar, Sports Car GT example: https://www.youtube.com/results?search_query=sports+car+gt+scgt+%2Cshort ... appending +%2Cshort (%2C = comma) returns videos < 4 minutes. ... similarly +%2Clong think gets > 20 minutes. Figured it was just a UA issue as RetroZilla connects to the site, just doesn't load functionally. Had some success with an Opera v9 string, until it failed. Your Googlebot UA string works well. Will updated the RetroZilla Community Edition thread with this valuable tidbit. Thanks again :)

as least I knew git commit 8b37ac1bf00199d4654d09b876991e737d8d3197 is OK, trying next commit. yep the condition is getting worse, but it is not easy to move out from here.

Just to make things easier, I created an installer for it http://nojus.trexion.com/local/tmp/SumatraPDF_3.3XP.exe

@roytam1<-- Hope this is okay to say it here. https://www.cnn.com/2020/06/30/asia/hong-kong-china-national-security-law-intl-hnk/index.html Hong Kong is about to be governed by a law most residents have never seen. And it's already having an effect ; 2020.06.30 RT ... Just saying that I pay a bit of attention to HK News. Not looking to start up a political discussion here. But I guess now , that you (HK) have less freedom than you once did. Be well , and thanks on the RT Browsers.

struggling along too... they are breaking layouts faster than one can look, and workarounds too, GRR Someone explained that a classic youtube addon simple sets the UA to googlebot. Funnily it vanished from Chrome's addon repo. Now tried that googlebot UA too - and YES! At the moment that seems my only chance to see the homepage (without search access), or search results - but only if URL is known, called e.g. from bookmarks. And isn't it funny: They CAN still show a NICE, simple layout, no prob at all, but only allow it to search bots! Access to Youtube Search: https://www.youtube.com/results?search_query=cats&search_sort=video_date_uploaded Youtube last working USERAGENTS: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) Mozilla/5.0 (compatible; bingbot 2.0; +http://www.bing.com/bingbot.htm

I think this is the Windows 7 hotfix applicable to this situation: https://support.microsoft.com/en-us/help/2615701/-logon-process-initialization-failure-error-message-and-the-logon-process-does-not-start-in-windows-7-or-in-windows-server-2008-r2 But for some stupid reason it keeps redirecting me to a failed attempt to sign in to a M$ account. And of course the hotfix system has been dismantled so no attempts at comparison can be made between that and regular Windows 7 files, in order to backport to Vista. But I don't think that is the exact problem, as this is from late 2011 and Haswell was only released in 2013. And it also doesn't mention the behaviour where the logon process does initialize but other services don't. And I'm sure there are many people who are using Windows 7 without this hotfix and never having logon process issues on Haswell and later. It's not in Simplix pack and it doesn't appear that a future update superseded it unless the modifications made in this hotfix were discreetly carried over to later versions. But for what it's worth, it appears that the changes were mostly in kernel32.dll (which is broken up into several files on Windows 7) as well as the Local Session Manager. Plus WOW64 and Terminal Services. But I'm not sure what these changes are. I also found some potential registry-based solutions for dealing with individual services not starting up: https://support.microsoft.com/en-us/help/943996/some-services-do-not-start-in-windows-vista-and-windows-7 Also, did the logs/event viewer produce any information of substance? @burd And I just checked out 372.90's kernelmode (NVLDDMKM.SYS) driver. Only one function missing in ntoskrnl.exe, which is memcpy_s. The usermode Direct3D shim driver (nvumdshimx.dll) is missing the following functions in user32.dll: GetDisplayConfigBufferSizes QueryDisplayConfig DisplayConfigGetDeviceInfo Those functions are also called by the 372.70 version of the file. Maybe that's why you get such crappy D3D performance with those drivers! I'm definitely adding those ones to user32. UPDATE: turns out 365.19 also does call them. But they also don't support 1000 series where this problem happens. And MS is lying about DisplayConfigGetDeviceInfo being in Vista: https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-displayconfiggetdeviceinfo I certainly don't have it and I do have every update up to Vista's EOL.

I don't think I can thank you enough for keeping the unloved but adorable Vista alive with a project like this! <3 You could consider putting up a separate message board for Vista stuff tbh, it might be worth it given how much of a niche it is even in the MS dev community heh (heck there's an Aero-esque theme for phpBB 3.2.x, lol)

Yes! So only user-specified programs can use the kernel extensions, which can easily lock out malware that relies on W7+ functions yet doesn't have local/manifests specified for it. I'd think that it would work for installers as well, as all program-linked libraries will call the local dlls instead of the system ones. Bootstrapped ones that check for OS versions are gonna be harder to work of course, but a few posts back I found a solution for new GIMP installers with general advice applicable to installers of such stubbornness. You can use Orca to modify/drop LaunchCondition tables in msi installers. For everything else, version spoofing through Application Verifier will work. In cases where a bootstrapped installer in a temp folder checks as well, you just need to get the name of that installer (but not path) and feed it to Application Verifier.

I think this is probably what you were trying to say, but I will do it myself as well nevertheless: Windows 10 is and should be NT 6.4. I don't see such a huge change that would justify it being "NT 10" except for marketing purposes..and I mean, it should probably suggest progress..and sound fancy. Somehow it does eradicate the initial value that these version numbers had, but oh well. I wouldn't be surprised if by 2023 Windows 10 will be rebranded into "Windows". Feel free to add any additional knowledge or things that I have missed, my knowledge in that area is more than shaky. But hey, this is the perfect place to learn, I have found out many interesting things while browsing through this forum. I fear I am an average Windows user at heart, after all!

Vista and Windows 2000 are the last two major revisions to the Windows NT kernel (NT 10.0 doesn't count since it was hastily bumped from 6.4 at the last minute and 1507 doesn't really add much from 8.1 win32-wise). Lots of major functionality that we take for granted, like USB mass storage support (2000), desktop composition (Vista) and proper NT DirectX support (2000) was introduced in those two OSes, with their minor kernel revisions adding relatively minor things or ones that were of poor quality, like XP's firewall and WLAN client; the former didn't support blocking outgoing connections and the latter doesn't support connecting to WPA2-EAP networks (or maybe it does but I couldn't manage it with the built-in client; had to use Boingo client that also works on Windows 2000). Vista fixed them both.

if file size is not too important, then vlc player 1.1.9 should work well as the last officially working, assuming you're using a cpu that uses SSE2 or newer ( i think from 0.8.6e and newer, they require SSE2 based cpus?, but i don't know if this is true or not ). i use vlc player 0.8.6d on windows 2000 because it seems to give a good balance by supporting older SSE only based cpu but also being modern enough to do work with most files and have decent quality and reliability, though a large part why i use 0.8.6d is because with version 1.1.9, the size of my archived package would then become a bit large, possibly preventing me from burning onto cd-rw / cd-r discs that can only do a max of like 677 MB or so ( i can't really remove anything else ). i don't see a reason to use newer than 1.1.9 unofficially, but that's a route you can experiment with if you use some kind of unofficial update rollup / extended kernel configuration. sorry, i don't have experience with the other things you mentioned. below is a link for vlc versions you can download - http://download.videolan.org/pub/videolan/vlc/

Even in 2018 it was crazy; less than three years after Windows 10 was released, yet that's all my new HP laptop officially supported (what a mess that thing is). But if I bought a laptop in 2004, three years after Windows XP came out, I would have official support for not just XP, but 2000, 98 FE/SE and even NT 4 (ThinkPad T41)! And that laptop has sleep-related bugs with Windows 10 that the officially-unsupported 8.1/2012R2 doesn't have! Even with all of the MS lock-in, relatively few new win32 API functions have been added after Windows 8 so it looks like forcing software incompatibility with Vista exkernel/7/8.x will be difficult for years to come.

You can use local user accounts on the later versions of Windows too. As for the second statement which is probably made for Windows 10 I totaly agree with you.

How will Tobin feel about this? There has only been one minor glitch where the title/URL/bookmark/tab bar briefly expanded when I was on YouTube. But I may have seen it before on 2012R2. Waterfox Classic 2020.3.1 is working too, but only in non-e10s mode (same as Pale Moon). I need to finish up SetCurrentProcessExplicitAppUserModelID in shell32.dll before e10s will work, it appears. I finished implementing CoGetApartmentType in ole32.dll, and it appears that dwmapi.dll is OK with stubs since the OS doesn't actually use the functions that newer Firefox-based browsers ask of that file. And there are some extra functions in user32.dll and uxtheme.dll that will be needed to make Firefox 68.9 ESR happy. More updates: K32GetModuleInformation will be added to kernel32 to accommodate SeaMonkey 2.53.x. And the thing that keeps e10s from working in Waterfox is that earlier one part of SetCurrentProcessExplicitAppUserModelID was bugged in a way similar to that of SetThreadErrorMode a few pages back. Problem is that NtQueryInformationProcess is not imported by the original Vista file, and there is no room to expand the import table (and I haven't found a good way to move import tables in x64 binaries yet). So first I tried adding NtQueryInformationProcess as a subroutine to shell32.dll. But that causes waterfox to crash with a BEX64 error (related to DEP/NX). And NtQueryInformationProcess has a syscall function in it. According to Intel 64 manual, syscall is a "Fast call to privilege level 0 system procedures". And as such, it is inappropriate for shell32 and should only be in ntdll.

Oh wow, this is AMAZING. If someone would have told me about this before I read this topic, I would have told them to stop dreaming. I mean, this is a huge deal for Vista users. I could even imagine extended hardware support through drivers thanks to this. Since I do feel like Vista has been "killed-off" artificially, with most companies putting XP and Vista in one box, even though Vista and 7 are mostly identical. Just like 8 and 8.1, in my opinion. But then again, I am sadly not very tech-savy, even though I'd wish to be! At least I have basic knowledge, I suppose.

One solution for XP diehards might be to use Yandex 17.4.1, which is based on Chromium 57. I just installed uBlock Origin 1.24.4 from chrome web store and it seems to be working, even though I flagrantly disregarded Yandex instructions to get extensions from the Opera addons site (where installation of UBO on Yandex is prohibited).