InterLinked
Content Type
Profiles
Forums
Events
Posts posted by InterLinked
-
-
36 minutes ago, VistaLover said:
Seems like the classic Tragedy of the Commons problem here...
0 -
2 hours ago, vxiiduu said:
Whoops, I forgot to include the MUI file. I put it in the repo now, just download the whole repo (Code->Download ZIP) and run snippingtool.exe and it should work.
Works like a charm, thanks @vxiiduu
Windows 7 Ex, or Windows 7++, whatever you want to call it, is working great!
0 -
1 minute ago, vxiiduu said:
Yes, if you are going to make the EXE yourself, the original source EXE must be from Windows 10 1507. 1809, for instance, doesn't work because they changed the snipping tool to include some annoying UWP banner ad (which you don't want anyway). If you want a pre-made EXE it's available on my github under the SnippingToolEx repo. Obviously MS doesn't care enough to take it down.
Hmm, when I open the one on the repo, I just get this:
Is there something else I need to do besides downloading that? I don't seen an mui, for instance, so I'm assuming that's only for packing and not on the Win7 end.
0 -
On 1/2/2022 at 3:06 AM, vxiiduu said:
It has been done. The delay functionality is working. Works on Vista and 7 (and probably 8, 8.1 as well).
This Snipping Tool is from Windows 10 1507 (the RTM release). The SHA-256 hash of the original SnippingTool.EXE is "fccf231e0e4437baba86f64752e13562c9a2aa2d699a8dae7fafc85b48da4aa8"
Porting requires 2 hex edits: one to change the NT version from 10.0 to 6.0 in order to trick Windows into running it, and the second to bypass some licensing/permission check that Microsoft put in.
Dunno if it's fine to distribute the .EXE here (probably not), hence why I only include instructions.
These instructions ONLY WORK FOR x64 Snipping Tool. If there is a big demand I can also work out how to do it for the 32-bit Snipping Tool as well.1. Obtain Windows 10 1507 RTM x64 ISO, open with 7-Zip, then open sources\install.wim with 7-zip
2. Go to Windows\system32 and drag SnippingTool.exe to desktop (or some other location)
3. Next to SnippingTool.exe, make a folder called "en-US" (or whatever your language code)
4. From your 7-zip window, go to Windows\system32\en-US (or whatever your language code) and drag SnippingTool.exe.mui into the "en-US" folder you made in step 3
5. Open SnippingTool.exe in HxD or some other hex editor
6. At offset 0x120, change "0A 00 00 00 0A 00 00 00 0A 00 00 00" to "06 00 00 00 06 00 00 00 06 00 00 00"
7. At offset 0x1D19C, change "40 55 41 54 41 55" to "B8 01 00 00 00 C3"
8. At offset 0xF6B0, change "B8 FA 00 00 00" to "B8 2C 01 00 00"
9. Save file and exit hex editorAt this point, you can simply open the edited SnippingTool.exe and get the Windows 10 snipping tool as pictured. You may also replace the Windows Vista/7 stock snipping tool with this one if you desire.
For reference, the SHA-256 hash of the modified SnippingTool.exe is supposed to be "c60898fb4ea6984aaee1f2d3c9b73560bf0aaff64b9855e3d58e9855f3836433""It runs but only displays an error box with no text!"
This is caused by incorrect MUI file, or incorrect placement of the MUI file.
As in picture, en-US folder should be next to SnippingTool.exe, and SnippingTool.exe.mui should be inside that folder. And keep in mind, everywhere I say "en-US", this means the language code used by your system. For example, ja-JP or fr-FR for Japanese and French respectively.Edit: Add bug fix for ghost menu entries in certain circumstances (this bug happens in win10 as well)
Sorry, bit late here, but just getting the opportunity now to go ahead and try this out.
Does it have to be W10 v1507? I do have access to some Windows 10 systems, but they're all newer than that. I'm assuming copying the SnippingTool.exe from those wouldn't work?
Just a bit annoying to have to download an ISO for an OS I don't itself need, but as the hard work here has really been done, I can't complain too much
Thanks again! Now that the one feature out of, uh, one features that Windows 10 actually has that older Windows doesn't, I guess Windows 7 has "useful feature parity" with Windows 10/11! SuperWindows, here we come!
0 -
6 minutes ago, Reino said:
I believe StackOverflow.com has updated their javascript code. I'm using the latest NM28 ('palemoon-28.10.4a1.win32-git-20220226-ba47fad4d-uxp-c403014cb-xpmod-sse.7z') and I can't post answers or add comments anymore. Has anyone else experienced this?
Yup, it was working for me in Chromium 70 with the latest Chromefill (https://github.com/InterLinked1/chromefill) until about 2 days ago.
Looks like one of those "Unexpected syntax ." errors in both Chromium 70 and New Moon. Unfortunately, this will be difficult to polyfill.
Probably not even anyone at SO responsible directly, but one of the stupid libraries used somewhere on the site, so they don't even know it's happening.
I'd think posting answers would work since JS isn't required, but yeah, comments, voting, etc. definitely is broken now.
0 -
6 minutes ago, UCyborg said:
Since SeaMonkey was mentioned, the browser part looks interesting. Similar to classic Firefox GUI wise, but different enough that extensions need some amount of tailoring towards it. At first glance, it may have a little bit more support for web bells and whistles than UXP browsers or maybe SeaMonkey has something that UXP doesn't or the other way around.
I'll give it a spin, curious about memory usage, leaks in particular. I have a hard time imagining classic Firefox like browser that frees all associated memory when closing sites/tabs.
That stupid web app I have to suffer with at work...those NPCs there finally broke working JavaScript for good so a bunch of pages don't load anymore in current versions of UXP browsers, SeaMonkey, Chromium 71 >=...
You mean Chromium < 71, right?
A lot of breakage seems to have happened right around there.
See release notes, "Specific Polyfills": https://github.com/InterLinked1/chromefill
6 minutes ago, UCyborg said:I haven't checked the corresponding Firefox version... Guess I need another browser just for that piece of crap.
As it should be!
0 -
37 minutes ago, xpandvistafan said:
@win32 @asdf2345 Both MEGA links are now dead, any alternatives?
I spent way too long putting this together: https://w2k.phreaknet.org/vista/
0 -
30 minutes ago, NotHereToPlayGames said:
The Post Office is a much larger waste of money, in my humble view.
Between 2007 and 2020, the US Government has had to bail out (ie, taxpayer money) the Post Office pretty much each and every year to the total of $78 billion spanning those years.
The Post Office is *NOT* supposed to be funded by TAXPAYER FUNDS. Let alone each and every year!
That is simply downright false.
The post office is peanuts compared to other rampant government spending.
Military funding alone is on the order of a trillion a YEAR.
78 billion over 12 years is NOTHING in comparison.
Post office is a basic service that at least services the public good, unlike most things in society...
Time to end subsidies to cell phones and divert that to landlines and the post office instead, so we can maintain our basic public infrastructure, not toxic useless crap.
1 -
13 hours ago, Dixel said:
I'm sure all of you are aware that Russia placed enormous amounts of war arsenal (and some say approx 125-150 thousands of cannon fodder too) extremely close to the European borders .
Not to mention russian fleet in 240km of Ireland's shores , right above the data/internet cables for war "exercices". Why no one says anything about the catastrophic impact on the climate ?
All of that efforts that @Mr.Scienceman2000and @Gansangriff were doing all these years (using old phones , saving the planet) are in vain.
Anyone ? Silence ? And what about the poor animals killed ? Poor Irish fish ? No protests against near russian embassies ! Where is Greanpeace ?!?!?
That's what I thought...
Ever wondered why the "greens"(reds) only oppose UK/US and not Chino-Russia ?
Well , one can't bark at the master . Here's a short but sweet explanation and a bit of history of this "movement". Esp. about the current German ones.
Original :
https://twitter.com/andersostlund/status/1485121247440773125
The same , conveneint to read (merged)
https://threadreaderapp.com/thread/1485121247440773125.html
BTW , this is not over and looks like far from it , you can watch some pretty interesting footage here , many videos added daily.
https://twitter.com/EndGameWW3
Will continue to limit yourself ? lol
Not sure where you got the idea that nobody cares about this, but most "real" environmentalists that likewise also decry all of this as well.
If you think about it, resources that go towards so-called "national defense", e.g. artificially devoting resources towards blowing up other people or countries, is a complete unproductive use of resources, sustainable or note.
If you were paying attention, surely you must know that right now in the U.S., people are outraged about the enormous spending bill giving the Pentagon nearly $1 trillion is budget appropriation.
Slashing national defense is certainly an important step that can be taken here.
0 -
3 minutes ago, NotHereToPlayGames said:
Sorry. I'm from a family of six kids. So I mispoke. "Recycle" to me is when my older brother doesn't use his bicycle anymore so I claim it as my own.
That's not Recycling, that's Reusing- much better!
0 -
7 minutes ago, NotHereToPlayGames said:
I agree also. I did not say to put it in the dumpster. I said to recyle it
Basically the same thing... "recycling" electronics means destroying them for scrap metal or shipping them to the Global South where slave labor disassembles them. Complete joke.
Recycling is just a consumerist way to get people to endlessly consume.
I'm not saying don't recycle and go to the landfill instead, but don't be fooled that it's this 100% green process that makes things disappear into the ether...
2 -
4 minutes ago, NotHereToPlayGames said:
Sometimes it's just "time to".
I don't believe in a "throwaway society", my everyday belt is the same belt I wore in the 90s.
But us Americans especially, we tend to collect a lot of "junk". I support "recycling" so most of my stuff doesn't land in a "dumpster", but sometimes "junk is junk".
"Baby Boomers" are particulary bad. They are the offspring of parents that lived through the Great Depression (I knew one that put WATER on her breakfast cereal instead of MILK).
Gen X'ers, Y's, Millenials - we don't want your "junk". I know far too many in my generation "saddled" with inheriting 3 bedroom houses where two of the bedrooms, the garage, and the attic is nothing but miles upon miles of JUNK.
I'm not trying to sound insensitive or heartless - but do us a favor and unload your own junk and don't make us recycle it for you.
Speaking colloquially, of course. You/your is not a "person", but a collective-whole.
But anywhoo...
agree with @soggi
One man's trash is another man's treasure.
I recycled a CRT monitor last year, and I still feel bad about it, since it basically work perfectly fine; same with a 2001 laptop (didn't have the charger for it). I'm sure somebody in the area might have wanted them; but logistically I couldn't have coordinated at the time, and I did salvage a bunch of other stuff.
I also have a background in telephony, and typically old analog or electronic phones get scrapped but they always work perfectly fine, but I will salvage whatever of those I can.
You always have to be on the lookout...
1 -
13 hours ago, Mathwiz said:
Ironically that may be the solution: CRTs just don't "do" sub-pixel font rendering. I guess in theory they could, but you'd have to set up a custom screen resolution that exactly matched the details of the CRT's shadow mask, and only a Trinitron-style CRT could possibly work with ClearType.
OTOH, a CRT may make things worse on an OS that "assumes" sub-pixel font rendering is always possible.
For me it would make worse... I salvaged a CRT monitor that was in the recycling pile a few months ago for an "additional" monitor, never mind that it took up half my desk space on its own.
Didn't work too well, as I got serious eyestrain from it to the point of being almost half blind in one eye (went away after it was turned off for 20 or 30 minutes). I think it might have been some radiation leakage when turning it off or on, since it made some crackly sounds and when turning it on subsequent times, if I looked in the other direction, I didn't quite have that issue.
Nonetheless, a bunch of nicer Dell LCDs were getting recycled not much later, so I sent the CRT back to the recycling pile and picked those up instead! In fact, I'm using one of those monitors right now! (It's the super-duper Dell monitor from 2007 that has every connector known to man on the back - seriously there are like 10 or 15 inputs - VGA, DVI, HDMI, DisplayPort, S-Video, USB, etc. It's the same one that gets really hot - hotter than a computer would, typically, as heat dissipation's apparently nonexistent on this thing.
13 hours ago, Mathwiz said:FWIW, I don't think Win 7 is "evil," but if you can't stand to look at it, it's pretty useless to you.
(I do have a few very old but working CRT monitors lying around; if anyone wants one PM me. Pay for shipping and they're yours.)
I had one as well that I offered at the time; nobody bit so who knows where it is now.
A real shame, as I don't discount the value of CRTs in and of themselves, but practically speaking, they didn't make sense for me. Still a shame to get rid of it though.
13 hours ago, Mathwiz said:As for myself, sub-pixel font rendering has always looked great as long as the colors involved were black and white; but when other colors get used, it starts to look pretty awful.
Looks fine. Unfortunately we're all trying to render that image on our own monitors, so it may not look to us the same way it looks to you!
I had no idea the vagaries of font rendering were causing so many of us so much grief. Too bad M$ isn't listening. Now, what were we talking about again? Oh, yes....
I never thought I'd say this, but thank M$ for IE!
Indeed... I'm more upset with browsers that push their own crap JS "standards" than those that simply follow the rules (like IE11 does, more or less...)
I was writing some JavaScript yesterday for a websockets-based application, and as I was referencing different things (I usually do PHP for web programming, rarely JS, since I rarely have a legitimate need for it) I found one that said "won't work on < IE 8" and at the time that was posted, that would have been a serious concern. Even now, that's about as much compatibility as I'm willing to trade off: anything I do has to work in IE11 if reasonably possible (I think websockets aren't supported, but my realtime chat service has an AJAX-based fallback so that service still works fine in IE11).
0 -
Just now, D.Draker said:
You missed that more than two years ago . Windows 7 support ended on January 14, 2020
I think maybe he's referring to when Microsoft actually drops support for it completely (when ESU and POS ends) as opposed to what they want consumers to think.
Regardless of the availability or PR campaign Microsoft is running, Windows 7 is still supported at least until next year.
0 -
14 minutes ago, D.Draker said:
I feel you man !!! Windows 7 is the worst nightmare and you're absolutely right : NO way to turn it off on win7 !!! Yet you're mistaken about Vista . It can be switched OFF completely !
Do not consider yourself somewhat special though , I too can see the bloody dancing pixels. I think most folks won't notice because of their junk monitors though.
Windows 7 is pure evil.
Here's the proof with AA on and OFF on Vista .
And here's my upvote for ya , of course.
If I disable smoothing in Windows 7, it looks like this:
Isn't that the same result?
And here it is with dark theme in Windows 7:
I fail to see how WIN7 is evil... Win8+ though, yes, definitely!
0 -
58 minutes ago, InterLinked said:
So why not turn off ClearType then?
Presumably that is unchecking "Smooth edges of screen fonts"?
What if you use Windows Classic?
0 -
3 hours ago, NotHereToPlayGames said:
Totally agree on font rendering. Win 7 and Vista anti-aliased ClearType-tuned fonts give me migraines.
Win 10 does not (no interest in even trying 11). I'm not talking just Chrome font rendering, the entire Windows GUI gives me migraines due to font blur, in ALL applications.
The "edgy" fonts in XP are far from 'perfect', but at least they do not send me to the ER or put me in dark closet for four hours waiting for a migraine to subside.So why not turn off ClearType then?
Presumably that is unchecking "Smooth edges of screen fonts"?
0 -
Just now, Mathwiz said:
Well, at least Micro$oft uses Javascript to remove the "browser not supported" banner, rather than just looking at the User Agent and "assuming" the browser isn't supported! Most sites just don't work at all if the Javascript errors out, and/or give "browser not supported" if the UA is unexpected, even if the page's Javascript does work!
The https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-createwindowexa page renders correctly in 360EE v13, but shows "browser not supported" in Serpent 52 even with 360EE's user agent.
That said, there's nothing on that page that requires any particularly advanced Javascript. Micro$oft just wants you to use their Edge - and of course a Windows version that supports it (not to mention a PC that will run that Windows version). How dare you try to browse a Micro$oft site with XP!
Yeah, what surprises me most is how they even cannibalized their own product (IE) in doing so.
IE 11 was/is actually pretty decent, at least when it came out and it worked pretty well with everything. It still works with everything I do since I don't do anything too radical in my web dev/design.
But now, if you go to a MSFT site, they deliberately break it and try to get you to use edge.
At least I'm using Windows 7.... no Edge crapware on here, so it can't force open a different browser on me!
0 -
19 minutes ago, Mathwiz said:
Looks like an add-on for the globalThis polyfill should be targeted to NM 27, since globalThis is apparently implemented in UXP (NM 28, etc.) already.
NM 27 isn't UXP? (Apologies for the ignorance, but I've only used 28...)
19 minutes ago, Mathwiz said:Speaking of polyfills, I poked around in JustOff's github-wc-polyfill add-on a bit. It seems to implement custom elements, which has been a JavaScript standard for some time, but still not implemented in UXP.
But his add-on limits the polyfill to GitHub/GitLab. Anyone know why? Since it's a standard, I'd think you'd want to add it to all Web pages, wouldn't you?
It looks like some of the code specifically targets GitHub webpages (DOM parsing), so I'm not sure how much of that would generalize, so it's not as simple as changing the permissions as with the manifest.json for a Chrome extension.
Might be helpful though in terms of things to add on!
0 -
12 minutes ago, NotHereToPlayGames said:
Bummer, I was hoping this would "unbreak" my water bill web page but it doesn't.
Are these errors polyfill-related?
Polyfills fix JS-deficiencies in the browser, it's not likely polyfill related, per se, a polyfill *might* be able to fix it.
I also saw several "XYZ" undefined errors on some things that don't quite work yet. I think a couple more polyfills are needed for this to unbreak close to most sites.
Most helpful errors are in the developer console (F12):
If you go to the Console tab, the raw JavaScript errors are printed out there. Best to use those rather than what's on the page itself, though in this case, it's probably similar by the looks of it. The console will also show you the exact JS that crashes the page.
1 -
6 minutes ago, UCyborg said:
Actually, the link I posted is actual 70.0.3650.0.
While this one is 70.0.3650.1.
6 minutes ago, UCyborg said:Actually, the link I posted is actual 70.0.3650.0.
While this one is 70.0.3650.1.
Yeah... that's the latest 70 version, no? One minor version higher than the other one.
1 -
5 minutes ago, UCyborg said:
I don't think you can "polyfill" nullish coalescing operator. It's occurring more frequently so good luck with the modern web on old browsers.
I think it could be fixed by processing all the JS and doing some kind of find and replace, maybe.
How to do that, I'm not sure yet.
5 minutes ago, UCyborg said:I think Iron from that screen was supposed to be 70. I got this particular installer since it's not in the official archive: https://www.filepuma.com/download/srware_iron_64bit_70.0.3650.0-20779/
Some downloads there are definitely wrong, Iron 70.0.3700 was actually Iron 71.something.
Yeah, it *used* to be there but it's not anymore it seems.
It's in the Wayback Archive though - the latest 70 version with the old UI is linked here: https://w2k.phreaknet.org/
0 -
@Mathwiz recommended I post this here:
7 hours ago, Mathwiz said:Thanks, @InterLinked! Now I finally understand what a "polyfill" is!
Same reason there are multiple versions of 360EE: the older versions are lighter and thus run better on older hardware.
Which reminds me: your ChromeFill extension would be great for 360EE v11, which is based on Chromium 69. Lots of folks don't want to run the RAM-hogging v13. So you might want to post in the 360EE threads too.
BTW, the globalThis polyfill won't be as useful on NM 27 as on 28 because, of @roytam1's builds, only UXP browsers like NM 28 support Javascript modules. But it's probably still worth doing if possible.
I use Iron 70, which is a Chromium-based browser version from 2018.
Recently, there was a "great purge" in browser support caused by some newfandangled JavaScript popping up everywhere at once: https://blog.interlinked.us/66/when-the-world-wide-web-goes-on-strike-how-do-you-fight-back
I ended up writing a simple Chrome/Chromium extension to automatically polyfill webpages so things that stopped working in the browser, like StackOverflow, now fully work again.
This doesn't unbreak *EVERY* site (at the moment, only the globalThis polyfill is included) but the goal over time is to expand support by addressing all these breakages and unbreaking them.
Here is the project: https://github.com/InterLinked1/chromefill/
I imagine older versions of 360EE would likewise benefit. Newer, recent versions will not benefit.
1 -
4 hours ago, UCyborg said:
No, you're not.
Which version is this? Seems newer than what I'm using.
I did notice the "Unexpected token ?" error. I took a look and it almost looks like invalid JS to me, they weren't using it as the ternary operator. I'm not sure what the polyfill/fix for this is yet.
Some things I use are still broken, affected by issues other than in or in addition to just globalThis. Hopefully, we can add more support for these other things over time.
0
My Browser Builds (Part 3)
in Browsers working on Older NT-Family OSes
Posted · Edited by InterLinked
File complaints with all these websites.
They need to know that blindly using breakage-causing JS code is NOT okay!
I complained to GitHub and they reverted enough breakage that it now works in Chromium 70 again though New Moon 28 is still broken.
Though it's a losing battle for sure... as of a few days ago, GitHub file uploads are now once again broken... it's like whack-a-mole, you polyfill a "bug" in their JS, and soon enough, a new one crops up again that breaks the whole damn site again.
What we really need is some of extension to replace all the JS on websites with the JavaScript they used two years ago, pulling from the Internet Archive or something.
That might actually work - scrape the JS for sites that are broken now, using old JS, and see if they start working again...
Maybe we can get a list of changes going and replace the diffs we see.