Leaderboard

StartAllBack 3.0.9beta https://s3.amazonaws.com/startisback/StartAllBack_3.0.9d_setup.exe Please care to update translation if you're ok with this

-- Disclaimer -- Those questions in themselves can be regarded (by some) as off-topic here, so providing answers to them might be also construed as derailing the thread ; however, since they were asked by an esteemed member of this community (who has, in the past, also contributed code to these roytam1 browsers), I kindly ask those few "allergic" to off-topic content to move along and ignore this... Now that's been settled : Yes, both official UXP browsers (Pale Moon, Basilisk) could be compiled for MacOS (aka Darwin) with some slight tinkering, because the platform did contain that support; those third-party (beta) builds were never fully endorsed by MCP, but, let's just say, existed on their sufferance . ... The MacOS user community had been mostly active on PM (beta) builds, e.g. https://www.macupdate.com/app/mac/62312/pale-moon And Moonchild was also "generous" enough to accommodate a subforum for Mac users (now locked in oblivion): https://forum.palemoon.org/viewforum.php?f=41 But the leading dev duo (MC+MAT) was never really satisfied with the "efforts" put by the MacOS build maintainers, giving them hard time if/when even slightly deviating from the duo's "vision" of how things should be "properly" handled... All too familiar here by the way they treated feodor's/roytam1's XP forks... Then, Apple gave them the perfect excuse they wanted : last March, the die was cast : End of Macintosh support https://www.palemoon.org/roadmap.shtml This would leave existing users of "macPM" on Intel CPU Macs without future support, a situation reminiscent of XP+Vista users (on older H/W) and MCP's obstinate refusal to support their code/apps on older WinOses... The last macPM release was v29.1.0; the Mac build maintainer (now banned in the PM forums) expressed his intentions to continue releasing Mac builds (by restoring code MCP remove - does it sound familiar?) and, as you'd expect, that caused both MAT+MC to burn fuses... The macPM build was rebranded to White Star since v29.1.1, the author had to evacuate PM forum and move on to his own site ... Another party has rebranded official Basilisk to Silver and offers Mac builds of it, too... https://forum.palemoon.org/viewtopic.php?f=61&t=26686 https://github.com/siggi90/NoobSilver https://dbsoft.org/forum/showthread.php?tid=54 @Mathwiz, I hope I covered your queries somehow...

There isn't much to say , I have to use 32-bit Vista on the damn Haswell . Luckily , I have another platforms to run 64-bit versions. Nothing fixed and it won't be . And even if it will , I'm gonna dump the haswell very soon anyways. A slight off-top , @win32 wrote something about Kaby Lake : "In a series of reboots, all services started and there were no issues with application execution." Kaby Lake (which I now have at my disposal) is not Haswell , of course ! But he didn't tell which update exactly . Win32 , could you join us here and name this update for kabylake , I'll test and write back here, thanks. https://msfn.org/board/topic/183035-will-windows-vista-work-on-amd-ryzen-3-3250u/?do=findComment&comment=1206474

Yeah. i tried it on my lone Haswell board and didn't get any errors upon starting, but after using it for a little bit, I noticed errors. Instead of derailing this thread, I will create a new thread related to the Haswell and later issues and link to it here once it is up. EDIT: Here it is:

I've always "laughed mockingly" at those "allergic types" with their high-and-mighty undertones whenever they chime in with their pretentious "you are off-topic, please return to the topic at hand". These "allergic types" need to grow up! Look at ANY forum and "analayze" their content. Try to find ONE, just ONE, where 90+ percent of the posts are "on-topic" (excluding forums so niche that only 10 members are active versus a forum with 1000 active members). It is HUMAN NATURE for conversations to diverge a tad, SO WHAT. Forums have a tendency, due to HUMAN NATURE, to be oh, just guessing, to be roughly 40% "off-topic". So yeah, "don't waive your bony finger", let the discussion RUN ITS COURSE, period. It is HUMAN NATURE and makes for a more pleasant ambiance than having some "pretentious dude" waive a bony finger at each and every one of those 40% "off-topic" divergences, "you are off-topic, please return to the topic at hand". I'd personally ban the "bony finger" dude over the topic-divergers, but maybe, just maybe, that might be because I just "diverged" herein.

Wow, i never knew how destructive is Moonchild and Tobin, they really destroying everything around them. Fascinating self-destruction. Autism really sucks.

Here you go: ...but I'd believe the code over a screenshot. This is the 'active' content': a.href = "https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/"; a.textContent = "Browsers working on Older NT-Family OSes"; Ben,

Thanks for the quick reply. , @TSNH in your second link (this below) the author says that there is no solution for recent cpus (in my case kaby lake - r) (and i having the INTERACTIVE LOGON problem ) This link is from 2018? New versions have some solution for us? I use a iso from archive.org that all updates are installed. I will download the updates from 2017-2020 (W.Server 2008) and the updates he said. And guys - Another question. do you have the drivers for the intel dual band ac3165 and for the intel usb 3.0 controller? I have try use some drivers from http://retrosystemsrevival.blogspot.com/ <- this guy. In this forum has a xhci drivers 4 vista but media fire link is down Thanks for the time and help @Dixel@TSNH

Have you tried changing the useragent for addons.basilisk-browser.org in 'about:config'? New string: general.useragent.override.addons.basilisk-browser.org Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 Basilisk/52.9.2021.07.19 That allows you to install extensions from there as well (or at least download them and then edit 'instal.rdf' with the appropriate min and max version).

I submit that some will disagree with "change" for no other reason than it is "change". I googled (had to Google that out of curiosity, the "past tense verb" is not supposed to be capitalized) for XP Browser and MSFN.org shows up on Page 1 of the results. I googled for Vista Browser and MSFN.org shows up on Page 2 of the results. These will promote higher on the results pages because of how Google's algorithm works. The more ACTIVE these threads become the HIGHER they rank in ANY search engine list of results, not just Google, at least that's how I understand search engine algorithms. The web browsers discussed here are not really limited to XP. There is a large number of active users in the XP threads that don't even run XP.

Didn't check the other forum, kinda in a hurry now... Are you sure it's the SSD causing the constant light? Try removing the optical drive. Also, there may be a "Drives" tab in the BIOS settings - uncheck all ports except the SDD to check if it makes a difference. Does the light stay even before booting (i.e. in the F12 boot menu)?

Agreed. I didn't go into that much detail, but that is exactly what is happening. uMatrix is blocking the <frame> that contains the results. BUT that doesn't explain why I can get THREE DIFFERENT "RESULTS" all based SOLELY on just changing what is and what is not being blocked by NoScript and uMatrix. My best friend (late 90's, early 2000's) is a retired FBI Agent. Her "job" was quite literally to spend weeks upon weeks on teenager-websites and act like a teenager. You might call it "entrapment" but there are very strict protocols she had to follow and very lengthy documentation. Her "job" was to literally catch criminals inviting teenage girls to become porn stars. So I view all of this "fingerprinting" from a CRIMINAL PERSPECTIVE. I do feel that only CRIMINALS need to be THAT concerned with a browser "fingerprinting" their online activities. I don't really care if my CHURCH website and Pornhub links this computer as having visited both, that isn't "criminal". You can NOT, I repeat, can NOT prevent a browser from being "fingerprinted". Look at it as a credit card number. SIXTEEN digits but the first FOUR only indicate the bank. It is really only TWELVE digits that make a credit card number "unique". So an untrusting website really only needs like TWENTY PERCENT of data that can be obtained via "fingerprinting" and they have you uniquely identified. Even though you have successfully blocked EIGHTY PERCENT of that data. You can not prevent "fingerprinting" - period. And knowing what sorts of criminals my friend has nabbed during her career as an FBI Agent, I fully support "fingerprinting" and the CRIMINALS it has caught over the years. But I digress...

This is an old hardware issue, but one that remains with us. Most manufacturers (at least Microsoft, Logitech and Razer, but probably most others, too), if not all, use Omron D2FC-F-7N microswitches in their mouses, at least for the two classical upper buttons, and usually for all buttons in many-buttoned mice. So the Omron D2FC-F-7N became a de-facto standard (for instance, see the pic collection here). This is a good and sensitive microswitch, based on a single-piece copper-plated steel leaf-spring, which, however wears out due to material fatigue, and starts to behave unreliably. Since it's, by far, *the* most used mouse button, the left upper button is usually the one in which the problem manifests itself, causing double-clicks to occur when one tries to single-click. There are various solutions around the net for this problem, assuming one does not want to replace the mouse: 1) Of course, the definitive one is to substitute the misbehaving microswitch. Since the Omron D2FC-F-7N microswitches are available on e-Bay for under US$5 a pair, that's the solution I favor, and have used to keep my three Intellimouse Optical v 1.1 mice working (I have already substituted the left upper button microswitch twice in each of them, and still have not seen the problem happen with any of the other buttons). 2) Then, there is the leaf-spring remove-retension-reinstall solution, which is pretty well described here (how to fix the 'double-click' problem on your G7 mouse), but which I was never able to do (all I accomplished was to make the already bad microswitch completely unresponsive). If one manages to perform it correctly, it should prolong the life of the microswitch somewhat. 3) Finally, there's an interim software solution, which really helps overcome the double-clicking on single-clicking issue, in its initial stages, although it gets innefective as the spring gets worse. This is the freeware program MouseFix (direct download), by Daniel Jackson. His MouseFix page (please scroll way down) is worthy of reading, and also offers the program's source code. The usual way of running MouseFix is simply to add a link it to the Startup folder in the Start Menu... however, since MouseFix hooks one of the mouse events, this leads to the cursor becoming unresponsive at times, due to it being run at Normal priority. My solution is to set it to High or, even better, RealTime priority. To do this automatically on startup, edit the Target field in the link to MouseFix, so that it becomes: C:\WINDOWS\system32\cmd.exe /c start "" /B /REALTIME "C:\Program Files\MouseFix\MouseFix.exe"if your copy of MouseFix is at C:\Program Files\MouseFix\, or adjust the drive and path as needed, and set the Run field to Minimized. This'll start MouseFix with RealTime priority, eliminating all unresponsiveness. BTW, there's KB266738 (and its 2003 version), but IMO that MS document induces one to check many things pointlessly, inspiring false hopes, before coming round to realize it, in fact, is a hardware problem. There's also a still open thead, from 2005, at neowin about it, and I cite it here as one of sources of part of the info above, and for its historical value.