Leaderboard

This is what I've been saying ! They showed us no proof. = no screencaps, nothing.

I have installed all .Net-Framework packages fronm 1.0 to 4.0 including all security patches in my system. It's not more insecure as Windows XP itself. Truth be told, several programs as for example Panda Dome need .Net-Framework in one of these versions. Without them such programs won't work. So, be aware of this fact when installing new software!

I can't confirm that statement. I have just tested Panda Dome, and it checked a file that a lot of scanners think is malware. While checking it deleted that file immediately. So, no problems here. Good protection as expected. I performed a second test. I copied two malicious files and two clean files in one folder. Then I started a manual scan of this folder. Both malicious files were recognized and immediately deleted. Panda Dome works exactly as it should be. I assume something is wrong on your side. Panda Dome works reliable, as has been confirmed for years by AV-TEST and others. Proof ? Proof ? As already explained in previous posts, I have carried out my own tests with the result that Panda Dome detected and deleted my malware. However, we all know the real security problem is very often in front of the computer. In such cases, a good program like Panda Dome can't help anymore, either.

I really hate these games. Maybe this world would be salvageable if others were like that. But there would have to be zero exceptions and that'll never happen. No matter how many good people you put together (if there is such a thing), it takes one awful person to ruin it all.

There is a bug with Search Box in Classic Taskbar that if we click on Taskbar while Search Box opened, it doesn't closes the seach box. While in Main Taskbar, if we click on Taskbar while search box opened, it closes the search. This is not there in SAB taskbar. I noticed it today after using my brother's pc. Thanks https://file.io/lhCFB3ohxs8G

better press [F2] to call out prefs windows instead.

this function seems to be broken for a quite long time

I think this might be to do with your WinSAT/WEI score. What does your System Properties show? Graphics scores of less than 3 causes Photo Gallery to disable slideshow transition themes, and you just get a basic fullscreen slideshow without the control bar. It will show at full screen resolution, but smaller images are upscaled to fit the screen. Graphics scores between 3 and 5 gives you the control bar with transition themes, but it won't play at full resolution, hence the pixellation and blurring on the control bar. Graphics scores above 5 should allow you to play the slideshow at full resolution, with the control bar and transition themes. Choosing the 'Classic' theme should stop smaller images from being upscaled to fill the screen. https://web.archive.org/web/20070223111728/http://blogs.msdn.com:80/pix/archive/2006/08/10/694724.aspx This post from 2006 from the developers and comments underneath suggest that you can override your graphics scores via the registry: HKCU\Software\Microsoft\Windows Photo Gallery\SlideShow Type = DWORD Value Name = WinSATScore Value = 100 (for basic slideshow at full resolution, without control bar), 300 (for transition themes and control bar at reduced resolution), or 500 (for transition themes and control bar at full resolution) In VirtualBox, setting the registry value to 500 doesn't seem to increase resolution for me (probably because the emulated graphics isn't good enough), but I have previously managed to do this on a physical machine, and if I recall I think this was what I had to do. However I can't check at the moment due to a failing Vista hard disk and I haven't had time yet to reinstall on a new disk.

if one takes over the dead Basilisk project and keeps using the same UXP platform with no major code changes I see no reason to use it over the original Palemoon now if @basilisk-dev decides to bring Basilisk back with multi-process enabled by default and many other good features that the Palemoon doesn't have then I think it could be a cool workaround. I also started using New Moon 28 but switched to Serpent 52 as soon as I knew it had multi-process functionality

In tracking something else down (below pic), I may have found the bookmark star clickety-clickety-clickety. But may be a long while before I upload another round.

function depends on platform code (i.e. UXP) which MCP removed such function from platform code long time ago, I don't think people can add back this without forking platform code.

The UXP team has already said they have no intention of dropping Windows 7/8 support right now, but if it came down to it yes that is correct. I wouldn't expect that to happen for at least 5+ years.

Correct. I think it's beneficial for Serpent users here and for developers of Windows XP UXP applications to have a direct line of communication with people involved in upstream development. There have been very negative interactions between MSFN members and Pale Moon forum members in the past. I think it is time to move past that and embrace the fact that we all are using code that comes from a shared history and to work towards a common goal of creating browsers that break away from Google's monopoly of the web, regardless of if that code runs on Windows XP or Windows 10 or Linux. This was a consideration when I took over the Basilisk project. I eventually decided that it would not be feasible to do this. Basilisk is an application built upon the upstream Moonchild Productions UXP platform. The upstream UXP platform has no XP support and the UXP development team have no interest in XP support, therefore Basilisk will not have XP support. That being said, if you need Basilisk on XP you can consider Serpent an officially recommended option from my perspective. I appreciate roytam1's work in maintaining Serpent and try to be active in this thread since Serpent is a fork of Basilisk. It is very likely that Serpent bugs will also affect Basilisk. Two reasons: 1 - It was removed from the UXP platform. 2 - There were multiple security vulnerabilities in the multi process implementation that Mozilla was using around the time Firefox 52 was released and UXP was created. Mozilla's current implementation is in Rust so the fixes cannot be backported. There is no plan to add this back at this time.

That is a kind of "wide open" question. -Why did they not charge for it? They can charge for several types of support. It should be noted, some features were developed to meet "paying" client needs. That kind of support is worth a lot of money. Also, having a developer walk you through your difficulties, while using their product, isn't something you'll often get for free. Especially if it is a big project, you needed done yesterday. -Why did they build it in the first place? To make a standardized platform, on top of platforms that are incompatible. Looks good, If you need something to work; but you don't want to rewrite it, for every platform. Why did they make it for Windows, and not just for *nix and Apple/Mac? If you are going to sell advice, on using a wrench, that advice should apply to as many cars as possible. Although, I'm not sure I would consider Windows users deserving? And considering the result that Java is, I'm not sure what kind of respect it is, that you are insinuating the users/companies deserve. You can hold others in poor or low respect. If Java is the symbol of that respect, I am not sure that you are saying anything nice about Windows users. Note: I mean this all kindheartedly. No actual terseness is intended.

Excuse me, could you tell me what is the latest version compatible with XP? I understand the latest one is "PotPlayerSetup-210209.exe" downloaded from "videohelp.com" or is there a newer one.

It's assumed that the browser supports CSS revert keyword. This problem alone can be worked-around by the following user style (using eg. Stylus extension): @-moz-document domain("winraid.level1techs.com") { html { overflow-y: unset !important; } }

... I can also confirm that statement : accessing it from Southern Europe; I'm not familiar with that site, but is the server/hostname "forums.internetfreedom.org" located outside of the GFW (I assume so, because. err, "internetfreedom" is non-existent inside mainland China ) ? Since St52 has its own certificate store, XP's deficient OS CA store shouldn't matter in this case... Does the GFW block access to "fankui.dongtaiwang.net" issued server certs ? (and I see the "taiwan" string in that hostname, so it's more than probable ) ; here's a screengrab of the certs chain when validating the site's certificate: Are you able to VPN/tunnel your way out the GFW and reach that site securely? if yes, you could export the server cert (expires on June 6th 2023) and import it to St52's cert store for the duration it's valid... Have you checked whether the site loads securely on a fresh St52 profile? Have you also tried unselecting the option "Query OCSP responder servers to confirm the current validity of certificates" in "about:preferences#advanced -> Certificates" ? If you can browse SO/SU and similar sites, you'll see that solutions downgrading HTTPS to plain HTTP are not desirable and, hence, very difficult to come across (and your particular use-case is indeed a niche one) ...

Hi, the problem you describe has existed since update > 22624.1470 Before that everything was "normal"

Yes, that is normal. There is no such thing as "hardware acceleration" in XP. And as far as that goes, I personally DISABLE "hardware acceleration" in my Win10 installs also. My browser RAM and CPU is BETTER without using HA. Though multi-monitor systems do "benefit" SLIGHTLY in some graphics "lag" by enabling HA. But if your job function requires screencaps from video presentations delivered via browser, then you must disable HA in order to screencap from those video presentations. "Hardware acceleration" SOUNDS like a neat and novel idea, but I've only had ISSUES every time I've tried it in both Win7 and Win10. And every browser support web site you ever seek advice from, one of the first three answers will always be "did you disable hardware acceleration".

Hi @Davide0033, hello from Belgium and welcome to MSFN! I wish you to enjoy the forums! Have a nice day. hpwamr

It has been a very long time ago since my last post on forum.palemoon.org. The last years, I used this forum to find solutions for problems with addons or websites and still do so. So just in a searching and reading mode.

Ok and okay ... I hope somebody will write this one for me. Roses are red, Violets are blue, A face like yours, Belongs in a zoo. ........:p

Sad to say, nothing shocks me anymore regarding (so called) humanity. As I said, I don't know how to avoid negativity in society.

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20230325-3d31a53d0-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230325-3d31a53d0-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from `custom` branch of UXP: import mozilla upstream "bug 1440809, ensure we don't try to treat non-DOM-Node event targets as such, r=masayuki (89c8025537a5)" (64329d41b) (482f63828) - import from UXP: No Issue - Ensure more OsiSpace (82a2a67f) (5924cbbd2) - import from UXP: [GFX] Add some sanity checks and clamps to SurfaceData calculations. (fd5015fa) (0fe415a94) - ported from UXP: Issue #2155 - Split TDZCheckCache, IfEmitter/InternalIfEmitter, JumpList from BytecodeEmitter (e8fee205) (b3ccbe7bb) - import from UXP: Issue #2155 - Simplify BytecodeEmitter::isRestParameter (da05c050) (c063999c2) - import from UXP: Issue #2155 - Refactor BytecodeEmitter in preparation for *Emitter work (a2fd8846) (ab9ea1208) - ported from UXP: Issue #2155 - Add PropOpEmitter, ElemOpEmitter, NameOpEmitter, CallOrNewEmitter (89e68200) (a2de1d580) - import from UXP: Issue #2155 - Fix BytecodeEmitter::emitArguments for our ParseNode tree (e88f946c) (3daef3c97) - import from UXP: Issue #2155 - Remove now-unused functions (5dc6be1b) (a5602bf09) - import from UXP: Issue #2155 - Fix debug build (76c20301) (c3d752db7) - import from UXP: Issue #2155 - Fix wrong assertion (fbb5f734) (590888c1c) - import from UXP: Issue #1593 - Follow-up: Fix :host matching from inside the shadow tree (7374ca67) (b8320e63d) - import from UXP: Issue #2171 - Skip over shadow nodes that don't have an owning node. (f09d2bba) (e47b2be5c) - import from UXP: Issue #1592 - Part 1a: Prevent crashing if a slot element was selected via DOM Inspector (0232bcdf) (54a68ef66) - import from UXP: Issue #1592 - Part 1b: Move <slot> UA rule to html.css (460e8db9) (16b338382) - import from UXP: Issue #1592 - Part 1c: Pass SelectorParsingFlags as a reference (ab63b7b9) (c71941bf7) - ported from UXP: Issue #1592 - Part 2: Parse ::slotted() pseudo-element as if it were a pseudo-class (77ad970d) (8186d06c3) - import from UXP: Issue #1592 - Part 3: Ensure only tree-abiding pseudo-elements will follow ::slotted() (92b31dd2) (adae2cbc7) - import from UXP: Issue #1592 - Part 4: Walk ::slotted()-containing rules for slottables (518c41fd) (732d49663) - import from UXP: Issue #1592 - Part 5: Use flattened element tree when looking for a parent while matching ::slotted() (8d2533ad) (a93992b32) - import from UXP: Issue #1592 - Part 6: Allow pseudo-classes with a forgiving selector list argument to follow pseudo-elements (91d2b6f4) (4c31da96f) - import from UXP: Issue #1592 - Part 7: Slottables cannot be matched from the outer tree. (19226fd5) (941a8a77c) - import from UXP: Issue #1592 - Part 8: Test the assigned slot for type/class/ID/attribute instead of the slottable when matching ::slotted() (4cd0de04) (572a2aa99) - import from UXP: Issue #1592 - Part 9: Post a restyle event after changing the slot of a slottable (9a071f3b) (b29f97176) - import from UXP: Issue #1592 - Part 10: Slot elements should restyle their parent on attribute changes (bc12e05b) (2c64594e8) - import from UXP: Issue #1592 - Follow-up: Don't post a restyle event if restyleElement is null (b2952274) (90b345d97) - import from UXP: Issue #2161 - Ctrl + Enter should cause keypress event even though the key combination doesn't input any character (078b1b73) (12bbdf34f) - import from UXP: Issue #2135 - Don't discard event state mask when matching ::slotted() or :host arguments (f1699407) (3d31a53d0)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230325-3219d2d-uxp-00534b26f-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230325-3219d2d-uxp-00534b26f-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-20230325-3219d2d-uxp-00534b26f-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.6a1.win32-git-20230325-d849524bd-uxp-00534b26f-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230325-d849524bd-uxp-00534b26f-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230325-d849524bd-uxp-00534b26f-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230325-d849524bd-uxp-00534b26f-xpmod.7z Official UXP changes picked since my last build: - No Issue - Ensure more OsiSpace (82a2a67f0) - [GFX] Add some sanity checks and clamps to SurfaceData calculations. (fd5015fae) - Issue #2117 - Follow-up: Run precomplete cmd during package staging (05d29a53d) - Issue #2155 - Split TDZCheckCache, IfEmitter/InternalIfEmitter, JumpList from BytecodeEmitter (e8fee2056) - Issue #2155 - Simplify BytecodeEmitter::isRestParameter (da05c050e) - Issue #2155 - Refactor BytecodeEmitter in preparation for *Emitter work (a2fd8846b) - Issue #2155 - Add PropOpEmitter, ElemOpEmitter, NameOpEmitter, CallOrNewEmitter (89e682000) - Issue #2155 - Fix BytecodeEmitter::emitArguments for our ParseNode tree (e88f946c0) - Issue #2155 - Remove now-unused functions (5dc6be1bc) - Issue #2155 - Fix debug build (76c203014) - Issue #2155 - Fix wrong assertion (fbb5f7345) - Issue #1593 - Follow-up: Fix :host matching from inside the shadow tree (7374ca671) - Issue #2171 - Skip over shadow nodes that don't have an owning node. (f09d2bba0) - Issue #1592 - Part 1a: Prevent crashing if a slot element was selected via DOM Inspector (0232bcdfa) - Issue #1592 - Part 1b: Move <slot> UA rule to html.css (460e8db94) - Issue #1592 - Part 1c: Pass SelectorParsingFlags as a reference (ab63b7b94) - Issue #1592 - Part 2: Parse ::slotted() pseudo-element as if it were a pseudo-class (77ad970db) - Issue #1592 - Part 3: Ensure only tree-abiding pseudo-elements will follow ::slotted() (92b31dd25) - Issue #1592 - Part 4: Walk ::slotted()-containing rules for slottables (518c41fd7) - Issue #1592 - Part 5: Use flattened element tree when looking for a parent while matching ::slotted() (8d2533ad7) - Issue #1592 - Part 6: Allow pseudo-classes with a forgiving selector list argument to follow pseudo-elements (91d2b6f4c) - Issue #1592 - Part 7: Slottables cannot be matched from the outer tree. (19226fd56) - Issue #1592 - Part 8: Test the assigned slot for type/class/ID/attribute instead of the slottable when matching ::slotted() (4cd0de04d) - Issue #1592 - Part 9: Post a restyle event after changing the slot of a slottable (9a071f3b7) - Issue #1592 - Part 10: Slot elements should restyle their parent on attribute changes (bc12e05bd) - Issue #1592 - Follow-up: Don't post a restyle event if restyleElement is null (b29522749) - Issue #2161 - Ctrl + Enter should cause keypress event even though the key combination doesn't input any character (078b1b73d) - Issue #2135 - Don't discard event state mask when matching ::slotted() or :host arguments (f16994074) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes since my last build: - follow-up rev 24572438, `targetInKnownToBeHandledScope` can be null (af28af9f8) - add comments and formatting in mozilla upstream "bug 1440809, ensure we don't try to treat non-DOM-Node event targets as such, r=masayuki (89c8025537a5)" (64329d41b) - js: add `using js::LifoAlloc` to fix build (e162f075e) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

XP is old but millions of people around the world still use it because they have to for whatever reason. Heck I still boot into it on occasion because perfectly good software like Nero 7.5 won't install on Windows 7+. That was intentional to force users to purchase upgrades. Now Microsoft has upped the game with Windows 11 and unrealistic OS requirements for literally hundreds of millions. Hopefully they'll get slapped with antitrust lawsuits and fines once Win 10 has expired.

and now they're more-or-less in same level.

Thank so much guys, for the support. @legacyfan I think I did watch the first season way back and I did enjoy it so maybe time to give another whirl. @mina7601 when it comes to these meditations videos they are long and not meant to play to the end, only when you've had enough Lol. I purposely selected around 741Hz frequency because with the right headphones it will promote removal of toxic energy and allow the mind to shift focus away from that and I liked that in the video that looks to me like a long walk on a road by oneself and surrounded by just clarity apart form the input of people ... I'm not promoting any agenda and there are drawbacks to being a loner, but for some, its a better alternative for those that struggle with being social such as myself. Please check out the comments on that video - they helped me last night and into today - today was not too bad actually. Ugh ... mercy me I need to get my sense of humor back - I"ll get there and either cheer up (sometimes people take offense to such) or *Perk Up* and allow love and light to make no more room for despair. OK and okay: So.. Here's one. What did one plate say to the other plate? Dinner's on me.:D

clicking the star on the left next to the "click to restore" button three times crashes the browser. just add one bookmark and it will not.

On a positive note: I did get to go see the ducks and feed them but it was cut short due to my anxiety.

Absolutely...anything that benefits XP users is something to be grateful for. For my part I've actually taken a liking to Vista lately. A lot of people tend to think of it as a prototype 7 (which it is), but I see it more as a supercharged XP...better compatibility with modern software and a more powerful kernel, while still retaining many of the little XP 'quirks' that I love. It is the final version of Windows that can truly be made to feel like XP in its day-to-day functionality. While 7 does improve upon Vista in meaningful ways, it also took out many things from Vista that I personally like (including the 'true' 9x Classic theme [as opposed to the 2000/ME-style theme] and the Classic Start menu). Not all of the Classic functionality can be fully restored with 3rd party software, though I commend all who are making programs for that purpose. I'll never sway someone against using XP...it is still a fantastic OS & my go-to OS of choice for single-cores and less than 2GB of RAM. If you have a powerful enough PC, Vista can definitely still rock the house. A fully-updated Vista SP2 installation is as stable as it gets, and very hard to crash. (It's also incredibly beautiful--I smile every time I see the Vista logout screen fade to black during shutdown or restart, rather than just cutting to black. Over 15 years later, Vista still outdoes the most popular OSes of today in its aesthetics.)

Hello @NT-Five (not to confuse with @NT Five ) and welcome to the Forum! The MSI H61M-P31 should be an ideal platform for any XP multimedia etc system... - eventually an NVMe seems slightly exagarated, at least for me standard SSD are suffucent in speed in any situation. - You can find different SATA/AHCI drivers here and find out which one fits best for your situation. the Patch Integrator 3.4.0 is applicable for any personal XP-inst.Iso: you either may rename your iso to "Windows XP Professional SP3 x86 - Integral Edition 2022.9.9 (Vanilla).iso" temoraryly and substitute the one inside or you manage to extract the drivers and include them to your .iso with nlite. Best wishes for your project!

Thank you, Mina, good to be back. Still not at my 100% yet but getting better every day I think.