Leaderboard

Yes, but it was me who tried it on a G3420, not D.Draker, and it worked on a desktop PC. Again, Pentium G3420, 32bit XP. I assume they did something to that driver since it'smarked as "FORCED", but I hadn't dig deep enough to be sure.

Ok. No problem.

I totally agree with you! But then again, 5437 was written for XP, while 5445 can't even allocate VRAM properly.

6.14.10.5437 (14.51.11.5437

WinXP + Chrome requires some jumping through hoops in order to "green padlock" ELLIPTIC CURVE certificate algorithm. https://stackoverflow.com/questions/33922231/why-cant-windows-xp-handle-newer-ssl-certificate-versions

Yep, a bit strange. But as I have already described, my 360Chrome 13.5 Build 1030 Redux initially also reported no secure connection to the website https://chi.uk2.net/ using ProxHTTPSProxy, i.e. no green padlock. Only after I had deleted all certificates in the Certs folder and updated the cacert.pem certificate inside the ProxHTTPSProxy installation, 360Chrome immediately reported a secure connection after a restart and showed the green padlock. However, recognising valid certificates has always been a problem in almost all 360Chrome versions for Windows XP. TBH, I very rarely use 360Chrome only to check sites for browser compatibility. I generally surf with Mypal 68 (is now running great ) and New Moon 28, and I try to open the more modern, very bloated sites with Thorium. If all else fails, I use my Android tablet.

That's good. But in your original screenshot there wasn't a green padlock.

Or have I overlooked something?

@Dave-H Just for fun, I tried to open the website https://chi.uk2.net/ in 360Chrome 13.5 Build 1030 Redux. I got no green padlock and the hint the connection is not secure when connected in both ways, directly or via ProxHTTPSProxy. I then closed the proxy, deleted all certificates stored in ProxHTTPSProxy's Certs folder and performed an update of the cacert.pem file. I then started the proxy and called up the website https://chi.uk2.net/ again. Now, the connection is reported as secure with a green padlock. Here is a screenshot: I don't know why your credentials are no longer filled in automatically when connected directly but I assume it is certificate related due to the age of 360Chrome. In any case, you should not forget to maintain your ProxHTTPSProxy installation in terms of its certificates, i.e, purging the Certs folder and executing the cacert Updater from time to time.

I can't compare with the current ungoogled 127, but the last one I made comparisons (v.111) with either of the famous Chinese forks, they alll rendered much better on all OS.

Intel-FORCED-5x32-Haswell_6.14.10.5445-drp.exe for 32 bit, respectively.

The full name, I know it. Old links are gone, maybe @K4sum1 will find it. Intel-FORCED-5x64-Haswell_6.14.10.5445-drp.exe

A set of good vitamins usually helps,

I'm an advanced developer. I maded alot of WinXP projects but I kinda ran out of ideas so post whatever you want. you can make it imaginary and hard as possible or just a normal idea.

https://www.howtogeek.com/113439/how-to-change-your-browsers-user-agent-without-installing-any-extensions/

I've never heard of these browsers before, but if we assume they are based on Firefox, here you go: "User agent override in firefox". https://www.whatismybrowser.com/guides/how-to-change-your-user-agent/firefox

Issue with accessibility as it stands today is that it hasn't been maintained since esr52 was forked not to mention Pale Moon front-end wise is still like 75% Firefox 24 so its accessibility fe bits don't match.. Would have to swipe from Basilisk to fix it up.

Another crash, after I connected with RDP; this time I got the backtrace: explorer.exe caused an Unknown [0xC0000374] Exception at location 00007FFFCD7BC8F9 in module ntdll.dll. AddrPC Params 00007FFFCD7BC8F9 0000000003B00000 00007FFFCD833908 00007FFFCB1CF000 ntdll.dll!RtlReportFatalFailure+0x9 00007FFFCD7BC8C3 0000000000C554B0 00007FFFCD8338B0 0000000000000008 ntdll.dll!RtlReportCriticalFailure+0x97 00007FFFCD7C595A 0000000000000008 00000000080403E0 0000000000C40000 ntdll.dll!RtlpHeapHandleError+0x12 00007FFFCD7C5C3A 0000000000C40000 00000000080403F0 0000000000000000 ntdll.dll!RtlpHpHeapHandleError+0x7a 00007FFFCD7D1C35 00007FFFCCEA0000 00007FFFCCEAED0E 00007FFFC2C70B70 ntdll.dll!RtlpLogHeapFailure+0x45 00007FFFCD6EC3AC 00000000080403E0 0000000000C40000 0000000003AFDB80 ntdll.dll!RtlpFreeHeapInternal+0x84c 00007FFFCD6EAFF1 00000000080403F0 0000000000000000 0000000000000000 ntdll.dll!RtlFreeHeap+0x51 00007FFFCABF1C7F 00000000080403F0 00000000080403F0 0000000000000000 KERNELBASE.dll!LocalFree+0x2f 00007FFF89DA6BD6 00000000032F3460 0000000003AFDB80 0000000000000000 StartAllBackX64.dll!Uninstall_AllUsersW+0x6d3a 00007FFF89D71E05 00000000032F3460 0000000000000000 000000000002035A StartAllBackX64.dll!PickGlyphDlg+0x16bb9 00007FFF89D7286C 0000000000000000 0000000034F8B0F8 0000000080000022 StartAllBackX64.dll!PickGlyphDlg+0x17620 00007FFFCCEB89A1 00000000C0000388 00007FFF89D727DC 000000000002035A user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB865C 0000000000000000 0000000000000000 0000000000000000 user32.dll!DispatchClientMessage+0x9c 00007FFFCCEC3B9D 0000000000000000 00000000015EDE20 0000000003CF9AA0 user32.dll!__fnDWORD+0x3d 00007FFFCD753FE4 00007FFF89D54A87 00000000032E4D00 0000000000000000 ntdll.dll!KiUserCallbackDispatch+0x24 00007FFFCB1B2754 00000000032E4D00 0000000000000000 00000000000700DD win32u.dll!NtUserDestroyWindow+0x14 00007FFF89D54A87 00000000032E4D00 0000000003AFE060 0000000000000000 StartAllBackX64.dll!GlassControls+0x505f 00007FFF89D54BF6 00000000000000D8 0000000003AFE060 0000000000000000 StartAllBackX64.dll!GlassControls+0x51ce 00007FFF89D86800 0000000000000000 000000000120AA70 0000000000020350 StartAllBackX64.dll!LoadSVG+0x690c 00007FFF89D7286C 0000000000000000 0000000000000000 0000000080000022 StartAllBackX64.dll!PickGlyphDlg+0x17620 00007FFFCCEB89A1 0000000000020350 00007FFF89D727DC 0000000000020350 user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB81EB 0000000000000001 0000000000000000 0000000003AFE4B4 user32.dll!CallWindowProcW+0x8b 00007FFFB38A8252 0000000000000001 0000000007DC7210 0000000000020350 comctl32.dll!CallNextSubclassProc+0xb2 00007FFFB38A8178 0000000000000000 0000000000000000 0000000000000452 comctl32.dll!DefSubclassProc+0x88 00007FFF89BD6149 0000000003AFEAD0 0000000000000064 0000000000C40000 DarkMagicX64.dll!0x6149 00007FFFB38A8252 0000000000000001 0000000000000000 0000000000020350 comctl32.dll!CallNextSubclassProc+0xb2 00007FFFB38A8037 0000000000000000 0000000000000000 0000000000000000 comctl32.dll!MasterSubclassProc+0xa7 00007FFFCCEB89A1 0000000000020350 00007FFFB38A7F90 0000000000020350 user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB81EB 0000000000000000 0000000000000000 0000000000000000 user32.dll!CallWindowProcW+0x8b 00007FFF89DBBDEC 0000000000000000 0000000000000000 0000000003AFEA28 StartAllBackX64.dll!DllGetClassObject+0x1810 00007FFFCCEB89A1 00000000C0000388 00007FFF89DBBA60 0000000000020350 user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB865C 0000000000000000 0000000000000000 0000000000000000 user32.dll!DispatchClientMessage+0x9c 00007FFFCCEC3B9D 0000000000000000 0000000003AFEAD0 0000000000000000 user32.dll!__fnDWORD+0x3d 00007FFFCD753FE4 00007FFFCCEB7F68 0000000003AFEB38 0000000000000008 ntdll.dll!KiUserCallbackDispatch+0x24 00007FFFCB1B1554 0000000003AFEB38 0000000000000008 0000000000000000 win32u.dll!NtUserMessageCall+0x14 00007FFFCCEB7F68 0000000000020350 00007FFF89DC0000 0000000000000000 user32.dll!SendMessageWorker+0x278 00007FFFCCEB7C87 000000000120C340 0000000003AFEC61 0000000000020336 user32.dll!SendMessageW+0x137 00007FFF89DB737B 0000000000010552 00007FF700000030 00007FF79EDDF3E0 StartAllBackX64.dll!Uninstall_AllUsersW+0x174df 00007FF79EA498EE 00000000000005B8 0000000000010552 0000000003AFECD0 Explorer.EXE!CTray::_HandleDisplayChange+0x7a 00007FF79EA0F993 00007FF79EDDF3E0 0000000000020336 00000000000005B8 Explorer.EXE!CTray::v_WndProc+0xaf3 00007FF79EA2B4CC 0000000000000000 0000000000000000 0000000080000022 Explorer.EXE!CImpWndProc::s_WndProc+0x8c 00007FFFCCEB89A1 0000000000020336 00007FF79EA2B440 0000000000020336 user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB81EB 0000000000000000 0000000003AFEFB0 0000000000000000 user32.dll!CallWindowProcW+0x8b 00007FFF89DBB6DC 0000000000000000 0000000000000000 0000000080000022 StartAllBackX64.dll!DllGetClassObject+0x1100 00007FFFCCEB89A1 0000000000000388 00007FFF89DBADF8 0000000000020336 user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFFCCEB865C 0000000000000000 0000000000000000 0000000000000000 user32.dll!DispatchClientMessage+0x9c 00007FFFCCEC3B9D 0000000000000000 0000000000000000 0000000080000022 user32.dll!__fnDWORD+0x3d 00007FFFCD753FE4 00007FFFCCEC26BF 00007FFF89D727DC 0000000003B0B3E0 ntdll.dll!KiUserCallbackDispatch+0x24 00007FFFCB1B14D4 00007FFF89D727DC 0000000003B0B3E0 0000000000000001 win32u.dll!NtUserPeekMessage+0x14 00007FFFCCEC26BF 0000000000000001 0000000000B9D800 0000000000000000 user32.dll!_PeekMessage+0x3f 00007FFFCCEC258C 0000000003AFF598 0000000000000000 0000000000000001 user32.dll!PeekMessageW+0x9c 00007FFF89DBAC20 00007FF79EDDF3E0 0000000003AFF5F9 00007FF79EDDF7F0 StartAllBackX64.dll!DllGetClassObject+0x644 00007FF79EA2A226 0000CBAB2F0A3605 00000000031B9AC0 000000000000282A Explorer.EXE!CTray::_MessageLoop+0x86 00007FF79EA2A110 0000000000000000 00000000031B9AC0 000000000000282A Explorer.EXE!CTray::MainThreadProc+0x60 00007FFFCB8560DD 0000000000000001 00000000031B9AC0 0000000000000000 shcore.dll!_WrapperThreadProc+0x11d 00007FFFCC1B257D 0000000000000000 0000000000000000 0000000000000000 KERNEL32.DLL!BaseThreadInitThunk+0x1d 00007FFFCD70AF28 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!RtlUserThreadStart+0x28 Additionally, my window metrics (window border thickness, scrollbar size, titlebar size) were reset.

Hi @TheLeftOldComputer! Many antimalware programmes are no longer compatible with Windows XP but ClamWin has always been. Unfortunately, it does not have a real-time protection. Only an additional tool called Clam Sentinel which has no longer been developed for years and never was a good one. It could only use ClamWin to scan downloaded files. So what about a programme based on the open source ClamAV with its virus definition databases which offers real-time protection? Or a fork of ClamWin with real-time protection and still compatible with CPU's only having the instruction set SSE? Kind regards, AstroSkipper

That web site has the most gigantic of header sections I think I've ever witnessed!

@sparty411 Are you sure about your specifications regarding your internet speed? The unit mb/s does not actually exist. You wrote 300 mb/s. Did you really mean 300 MB/s or perhaps 300 Mbit/s? If you really had a speed of 300 MB/s, then that would be a line with 2400 Mbit/s, which I have never heard of existing for a normal citizen. At least here in Germany. I assume you rather meant 300 Mbit/s (Mbps in English, and very rarely can also found the unit Mb/s).

Just an idea. Have you already patched and removed the limit on TCP connection attempts in the tcpip.sys file in your Windows XP installation? And don't forget to adjust your MTU and RWIN values as Windows XP does not do it automatically! This can be easily done, for example, with the tool SpeedGuide.net TCP Optimizer, currently in the version 4.1.1. The correct MTU value mainly depends on your internet provider and can even be determined with the SG TCP Optimizer tool in the corresponding tab. A suitable RWIN value can also be manually calculated and set in the registry, of course. All values should be then tested to find the optimal ones. In any case, be aware that such fast connection speeds as you are using today didn't exist when Windows XP was developed and still maintained. TBH, I don't know whether Windows XP with its very old network drivers is at all able to handle such high speed you mentioned above. The old Internet tariff I booked years ago has a speed of 25 Mbit/s only, which I can achieve in full on my Windows XP computer, but only with optimal settings mentioned above. However, my old processor wouldn't be able to cope with any more, either. And regarding the QoS Packet Scheduler, I deactivated it from the very first on my standalone Windows XP desktop computer long, long time ago.

Yes, indeed!

Found the fix! Disable 802.11n Mode

Is this browser equipped with its own set of certificates? Looks like so.

"Universal VESA/VBE Video Display Driver" https://yeokhengmeng.com/2016/04/installing-windows-xp-on-a-modern-unsupported-haswell-system-in-2016/ *not tried myself

Important to note, this says the man who generally don't use China soft. See? I'm being objective and not biased.

Toolbars are available if you unlock the taskbar.

Is easily blocked with a primitive extension,

G3420, desktop version, not laptop, and I had no Aero on Vista with that XP driver, of course. As a note, I tried a driver which they marked as "FORCED" (written in capslock). Sorry, don't remember the exact version.

BSOD stop 50 indicates that invalid system memory has been referenced. Most likely due to the inability to set proper memory allocation since Intel Driver and Intel chipset uses your usual system RAM sticks, it doesn't have its own memory, unlike most dedicated GPUs.

Did you also try the most recent version Mypal 68.14.3b? As @feodor2 mentioned in a previous post, he has made a lot of changes and corrections in this new version.

And which driver do you attempt to mod? Is it DriverVer=01/30/2014,6.14.10.5449?

They can't, drop it. I tried. Even if you would, you'd still encounter severe bugs later on. From what I 100% know, only the earliest Haswell may have a small chance.