Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/01/2021 in Posts

  1. a fix is pushed to repo, this extension will be able to be used again in next build.
    3 points
  2. I was expecting to have to switch over years earlier. But somehow I never really did. All the tricks shared on places like this made the difference. Installed and tweaked newer Windows 7 and 10 for people at work, but then got fed-up with it pretty soon, and booted-up XP x86 for myself again. Did install a Linux x64 multiboot like 6 months ago on my main PC. Made it look like Windows XP with Classic UI, including bitmapped font rendering, including all the file icons. I use it sometimes for little things. I am happy with the multiboot setup, the switchover time is not bad (shutdown and reboot). Still have a big list of things that I cannot do in Linux though, or do as fast as in Windows XP. For work I will eventually need a Windows 7 x64 multiboot as well, maybe even 10, though I would rather never use 10...
    3 points
  3. This last version of Open Hardware Monitor that I recommend for Windows XP x86: v0.9.2 Dated 01-03-2020 https://openhardwaremonitor.org/files/openhardwaremonitor-v0.9.2.zip You can forget about these later versions: v0.9.3 and v0.9.3.1-alpha will run in windows XP but gives me a CPU core no.4 load that is obviously wrong at +90%. Not matching the task manager. v0.9.3.5-alpha, v0.9.4, v0.9.5 and v0.9.6 are not Windows XP compatible. Requires .NET Framework version 4.5.
    2 points
  4. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210227-d9301c4-uxp-ad5a13bd5-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210227-d9301c4-uxp-ad5a13bd5-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210227-d9301c4-uxp-ad5a13bd5-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210227-085b7ae30-uxp-ad5a13bd5-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210227-085b7ae30-uxp-ad5a13bd5-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210227-085b7ae30-uxp-ad5a13bd5-xpmod.7z Official UXP changes since my last build: - [widget] Require user interaction when picking files or folders v2 (98f6ad61f) - Issue #1722 - Update about:license (5f1bc2987) - [dom] Update noscript serialization to the changed spec. (77d26e8bc) - [ html parser ] Check for integer overflow when computing new buffer sizes. (525961c26) - [DOM] Don't reveal error details for CORS-cross-origin decoding errors. (b2c0fda77) - [security] Hold mutex when accessing TSI fields. (29271977c) - Issue #457 - Remove duplicate PKCS11 definitions (85b0f705d) - [MFBT] Update lz4 to 1.9.3 (5587b6bf1) - [OTS] Backport some upstream OTS commits. (ad5a13bd5) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Back-end branch pointer update (341c0df89) - [SSUAO] Shut twitter's pointless nagging up. (ecdf0c41d) - Back-end branch pointer update (085b7ae30) My changes since my last build: - widget/windows: fix build if sdk doesn't define FOS_OKBUTTONNEEDSINTERACTION (ad59d4c5f) - mailnews: fix build after API changes in "[widget] Require user interaction when picking files or folders v2" (9149f54e1)
    2 points
  5. Thanks. I have been able to track down why some skins do not have a .srx "override" file and others do. That trick lies within [HKEY_CURRENT_USER\Software\360chrome\default\ui_persist_value] keys stored in "360chrome_1.reg". Doesn't answer your original question but I learned more of the inner workings of 360Chrome :) I think your original question still seems to revolve around "http_nosafe_bar.xml" and "browser_strings.xml", both of which still contains a lot of Chinesse.
    1 point
  6. Installed windows 8.1 earlier, downloaded about 5 different nvidia drivers of which none of them worked. Upon looking at the device list, the 30 series is mentioned on there but the drivers still refuse to uninstall due to hardware compatibility. I really hope someone finds a fix for this because windows 8.1 is a very good operating system
    1 point
  7. Thank you so much for that. I tried it, and actually got offered an update, KB969084! I never thought I'd ever see the yellow shield in the system tray ever again!
    1 point
  8. FWIW I use HWiNFO. The latest version of that still works on Windows 98, believe it or not!
    1 point
  9. Lol I just found out that Extended Kernel is mentioned in the official Windows Vista Wikipedia page (at least the German page). It basically says that an unofficial kernel was released to Vista in August 2020 that adds Win7 SP1 APIs to Vista, allowing modern Firefox/Chrome to run.
    1 point
  10. Well thought i would be long gone, turns out Windows 98 is still my favourite hobby! Been using DOS' 'EDIT' daily. Discovered up to 9 documents can be opened at a time, toggled via View dropdown. Always thought opening a new document over an old one discarded the other, not the case. Just as good as a tabbed text editor. Before opening a tenth document just close one (File -> Close vs File -> Exit) that's no longer needed, you'll get cued if the document changed. Another reminder there's not much new under the sun, developers often just add overhead, eye candy and features that the majority don't want or need. Finished reading a ~100 page PDF entitled Using FreeDOS. Very good read, discusses the history of the project, basic installation and usage, some of the major software, etc. Amazing the project has been in active existence since 1994 and provided DOS support and enhancements many more years than Microsoft ever did. Every time i've accessed FreeDOS the project seems top notch - website, documentation, FreeDOS trial, extra software, etc. Thanks FreeDOS for keeping DOS alive and current. Finished Half-Life (Half-Life, Opposing Force, Blue Shift) months ago using Windows XP with Steam. Finally deleted my Steam account (took some messaging and emails) and threw the game away. It's not like me to throw stuff away but i do not intend to install Steam or play the game again. I also did not want to give the game away, encouraging yet another Steam account, if Steam even allows re-using a game on a different user account. Having grown up old school, Steam and DRM are not my idea of gaming and software ownership. As mentioned sometime before, bought the game in 2005 without realizing it was a Steam release. I know there are work-arounds to extract game data and bypass Steam but that's not what Steam wants so to the trash it went.
    1 point
  11. ntext is deprecated in favour of ntdll, so no modification of executables is necessary to run Firefox/Waterfox. This required patched versions of winload, ntoskrnl, and ci.dll. This makes Vista as a whole easier to modify, but also reduces forward compatibility of the extended kernel (for now).
    1 point
  12. I will use the operating system for as long as I have old computers compatible with it where XP is the best fit, and the increased resource consumption of anything newer would be felt. To throw out a working computer as out of date, or cripple it with bloat to make it so, is an unreasonable proposal. Old applications run on WinXP, and are also much faster. As long as I don't need to exchange bleeding edge file formats with other people, this software serves me better because, in addition to its speed and efficiency, I have also learnt to use it well. It does not require new redistributables or frameworks, or mandatory online components. If I have a goal of using a spreadsheet or encoding video, I default to the oldest tool that can accomplish that. The files produced will also be compatible with the most computer systems, either old or new.
    1 point
  13. Both of these "features" (as I understand them) sends your trackable data to a third-party, the third-party analyzes that data and then reports back if it is 'safe' or not (by their definition, not yours), then the browser proceeds based upon that reply. But WHO is this third-party, WHERE is this third-party ??? I simply do NOT "trust" either one because I don't have ANY information on HOW / WHERE / WHO "behind the scenes". When you rely on an extension such as Adblock Plus, uBlock Origin, uMatrix, Ghostery, Privacy Badger, et cetera, you have a community of users and a plethora of online reviews and critiques to base your "trust" on. In my view at least, relying on something built-in to the browser is like actually thinking that some petty "Do Not Track" 'feature' is really doing anything or that "blocking third-party cookies" actually blocks third-party cookies. I highly prefer my blacklists and my whitelists to be "local" and not sent who-knows-where and analyzed by who-knows-who. I use uMatrix and one-and-only-one list - https://gitlab.com/curben/urlhaus-filter/raw/master/urlhaus-filter.txt Then I use NoScript and only whitelist PARTIAL javascript on a small handfull of websites. If you go to 360Chrome -> Chrome -> User Data -> skin (at least that's the folder structure for the "portable repack") you should find one file with an .srx extension. If you can provide the file name for that .srx file, I might be able to see if that skin is the culprit. Or you could do so some digging on your end, the .srx will unzip with 7-Zip, PeaZip, IZArc, et cetera. There will be an .xml file (maybe two, depending on skin) and a bunch of .png files. The .xml file can be opened in Notepad++ -- look to see if the .xml references OTHER .xml files (if it does, it/they likely reside within 360Chrome -> Chrome -> Application -> 13.0.2206.0 -> skin -> skin.srx which itself will need unzipped. Which also contains http_nosafe_bar.xml and browser_strings.xml, either of which still contains a lot of Chinesse. Hope that helps.
    1 point
  14. I'll keep it going on my 2 Dell Towers on 'bare metal' - they are so old they don't even plug in to the wall - they have a crank in the back Seriously though.. To keep our outdated systems running, we have to 'cripple' much of it and can no longer do what we used to back in its "heyday". I run a pretty basic limited slim installation now. Yeah.. same here - XP is more-or-less for nostalgia sake and project to keep me on my toes
    1 point
  15. New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20210227-355db4de-uxp-ad5a13bd5-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20210227-355db4de-uxp-ad5a13bd5-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20210227-id-eed0566-uxp-ad5a13bd5-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20210227-id-eed0566-ia-41157bf-uxp-ad5a13bd5-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.
    1 point
  16. My installation is a clean SP2 (slipstreamed with Nlite) with a minimum of really needed updates. VC redist , framework , DirectX , fix for HD Audio, etc. Like I said , the programme shows that PCIe gen.2 is actually used , but not to the maximum . Maybe it's the mobo that doesn't like XP , you're right. I will try to reinstall again in some days and get back with the results . This week will be busy. About the upgrade , I'm afraid it's not possible since no other motherboard will fit this housing. About Fujitsu Siemens , they are quite OK in my opinion , yes they do not support OC , but the PC feels snappy enough (at least with Vista) and I like the OLD school BIOS . Windows 7 and XP64 are slow with that PC , like really slow. Like 2x times . Maybe it was designed to run Vista only. I can understand about Win7 being slow , because it actually is slower than Vista on any PC. But about XP64 it is weird , you're right.
    1 point
  17. I have found the source of the problem with HDMI . In case you will ever use Nvidia's HDMI (Azalia) or any other HD drivers you have to install KB901105 x64 before the drivers. V3 worked for me . It's very important to install this KB before. Still , I do not know why the Nvidia CPL shows gen.1 PCI express . Could you look at yours ?
    1 point
  18. @UCyborg, I wanted to ask you , does Nvidia's HDMI work fine for you with XP64 and these drivers ? EDIT . My mobo has PCI express gen.2 . Windows Vista shows gen.2 , but with XP64 Nvidia CPL shows that it's gen.1 only. Any idea why is that ? Also , tried some DX9 games and the performance is much worse on the same hardware and with same driver versions. I'm not going to use it , of course , it's just out of curiosity . Thanks.
    1 point
  19. For that matter there is a folder named "swiftshader" with these files : libGLESv2 and libEGL . So one may may safely delete them from the main folder . I tried it with version 13 and works fine with your test om my 8 years old GPU. I don't have anything older at the moment. And I'm sorry , but you're wrong , please do read before posting . "SwiftShader is a high-performance CPU-based implementation of the Vulkan graphics API12" "NOTE: SwiftShader's OpenGL ES frontend is no longer supported, and will eventually be removed." https://github.com/google/swiftshader It has nothing to do with GPUs . It's CPU only . Besides , it's to be used with Vulkan only. Who has this "vulkan", I mean users with 360 !? So one can safely delete them , at least from the main folder. The less chinese dlls , the better. Also , my advice to you and all English speaking : replace icudtl.dat with the original file from Chrome with the corresponding version.
    1 point
  20. It's junk , just delete it . Seems like yet another spying "feature" . The only needed dlls are : audiomute.dll chrome.dll chrome_elf.dll d3dcompiler_47.dll libEGL.dll SnapPlugin.dll
    1 point
  21. I still use XP as my default OS, and hope to continue to do so for a very long time yet. I have to have Windows 10 as well now because I have programs I need, like Adobe editing and web publishing programs, which now will only run on 64 bit Windows 10. For general use I still much prefer the UI of XP though.
    1 point
  22. This week I had a problem with a Windows 10 VM. The sound dissapeared misteriously. As a friend of mine told, the thing is that the audio service couldn't start due to problem with another things, so I needed to reinstall Windows 10. That VM has dual boot with Windows 7 and Windows 10. Windows 7 there still works properly! That issue only affects Windows 10. And that Windows 10 was a stable version (20H2).
    1 point
  23. Every Lite-On DVD drive I've used has the same issue as in the op. I just either use a paper clip or when I get fed up will replace the drive.
    1 point
  24. Using DISM /online /add-package options https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options
    1 point
  25. With the newest kernel Chromium 90 64bit (installed Ublock ver. 13.x.x) doesn't actually block ads . It says it blocks , but that's not the case. Internal adblock logger says : Uncaught (in promise) IO error: ...: Could not open/read directory (ChromeMethodBFE: 20::GetChildren::1)
    1 point
×
×
  • Create New...