
Mathwiz
MemberContent Type
Profiles
Forums
Events
Everything posted by Mathwiz
-
Win7 End Of Support - KB4524752 MS Nagging Has Started
Mathwiz replied to WalksInSilence's topic in Windows 7
The legal way to get the POSReady '09 updates also required payment (for POSReady '09). I suppose a distinction could still be made: if the POSReady '09 XP hack wasn't published until after POSReady '09 was no longer available for sale, then the hack could be considered not stealing since you couldn't buy it from M$ anyway. But it does seem like a rather fine line we're not crossing. At any rate, perhaps a more acceptable route would be to do what POSReady '09 did: spoof a different Win 7 version, perhaps Server 2008 R2. It would be more challenging than the XP registry hack - I think you'd need to hook GetProductInfo, so it would require some programming - but sounds prima facie doable. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
You could also try petrus's suggestion: That idea should work with any FF-derived browser (NM, Serpent, Navigator, etc.) -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
I haven't read the topic (registration required, and it's not a big enough deal to bother registering) so I'm just guessing that they're following Google's timeline for Chrome, rather than M$'s timeline for Win 7 itself: As to Win 8, it's interesting that it's newer than Win 7, but also hit EoS earlier (since everyone was "supposed" to upgrade to 8.1). So if/when they do stop supporting Win 7, they might just set the minimum required version to 8.1 and we'd all be out of luck. But it may also have to do with programming. Another guess of mine is, it's not really any harder to support Win 7/8 than it is to support 8.1. If so, MCP may not see much advantage in cutting off Win 7/8 support in terms of removing code from the product. The chance to remove code and make the browser package smaller seems to have been one of their motivations to drop XP support (less sure about Vista) back in the day. You were perfectly clear; that's why I said you probably wouldn't like my solution! FF 52 doesn't support SSUAOs (at least, not without considerable tweaking), so an extension like "Good Twitter" is needed to send Twitter a different UA (so their Web server will use the old interface). However, this also causes Twitter to send the audio that @roytam1's built-in support wouldn't have handled correctly, but since you're (of necessity) using Primetime with FF 52, it plays fine anyway. As for getting it to work in NM, his built-in support is probably getting the sampling rate wrong somehow. Unfortunately I don't think anyone yet knows quite how to fix it. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
OK, so it appears that, to avoid distorted audio, you have to include Gecko and/or Firefox in the UA - but then, you either get the new Twitter interface or the mobile version of Twitter (depending on the spoofed FF version), neither of which you want. (Side rant: I wish Twitter and other Web sites would quit doing this! Just because your company's marketing geniuses think everyone will love whatever new UI you've cooked up doesn't mean it's true! And obviously you still support the old interface - so is it that hard to give folks a "new/classic" interface checkbox in your user preferences screen, instead of making them fool around with user agent strings?) I think I have a solution, but I'm not sure either of you will like it. This solution requires FF 45 or Serpent. Use the Pale Moon or IE user agent to get the old interface (and distorted audio) To fix the audio, turn off the internal A/V support (in about:config, set media.ffvpx.enabled to false); instead, install the Adobe Primetime CDM. That should play the audio without distortion. (Installation instructions are a few threads below this one.) In Vista and above, you could use the WMF support built into Windows instead, but IIRC, WMF in Vista has bugs of its own with Twitter, so on Vista you may want to use Primetime anyway. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
Looks like Cloudflare updated their TLS security. Old versions of wget no longer work (even with up-to-date OpenSSL). New wget versions work fine. Same is probably true of browsers. Which browser is having the problem and what message is it giving you? -
Windows Media Center EPG ending in January 2020
Mathwiz replied to Vistapocalypse's topic in Windows 7
That's true. Most folks under 30 probably only watch traditional TV for sports, or maybe because the business they're patronizing has a TV on. Most of them stream pretty much everything else. WMC and similar software is just for old-timers like me who refuse to let go of our dinosaur viewing habits. It's ironic, therefore, that the two biggest features Micro$oft removed from WMC over its lifetime were the sports line and Netflix. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
Try this SSUAO: general.useragent.override.twitter.com = Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9 "FF compatibility" spoofs FF 68.9 ESR. The one @roytam1 gave you spoofs IE 11. The one above spoofs FF 52.9 ESR. If the source code was illegally leaked then of course the links posted by @sparty411 and @Zero3K(and quoted by @Snear) should be deleted immediately. We can't put MSFN at legal risk. But banning seems like an over-reaction at this point. I see no evidence that @Zero3K was aware the source code was illegal when posting those links. -
Windows Media Center EPG ending in January 2020
Mathwiz replied to Vistapocalypse's topic in Windows 7
ATSC 3.0 doesn't have a hard cut-over date like the transition from analog to digital did. And for the next few years, stations have to continue broadcasting at least their primary channel in ATSC 1.0 if they decide to broadcast in ATSC 3.0. And the FCC doesn't even plan to ever mandate ATSC 3.0 tuners in new TVs! So I don't think we'll see an end to ATSC 1.0 broadcasts anytime soon. At any rate, though, that's a tuner issue. Presumably, once ATSC 3.0 tuners hit the market, SiliconDust will make an HDHR with them, and you can just put one on your network. There's a question of whether it'll be compatible with current models, and if not, whether drivers will be available for a product as old as WMC, but I'll cross that bridge when I come to it. That's correct. Unless you're using cable TV with a CableCard tuner, you don't need WMC. Any other PVR freeware would do. (Is MediaPortal still maintained? That one looked like the best alternative a few years back when I was considering my options.) But as always, it's a hassle to switch; so as long as WMC is working for me, I'll stick with it. Kind of like Windows XP, Vista, 7.... PSIP guide length varies greatly from station to station and from market to market. In my market (D/FW) most stations broadcast 2 days of guide data. PBS leads the pack with 3 days! A few only give 12 or 24 hours, though. At one time, I looked for programming that would convert PSIP guide data to WMC's peculiar format, just in case it ever came to that point. I found something that I thought would work, but since Microsoft's guide was working, I never tried it ... if SD ever goes away, I don't know if I could find it again.... but my standalone DVR will use PSIP data if/when its Internet guide goes away, so I can fall back on that while I consider my PC options. Again, I'll cross that bridge when I come to it. -
Windows Media Center EPG ending in January 2020
Mathwiz replied to Vistapocalypse's topic in Windows 7
Actually I'm OTA I think I saw that once, but not since I switched. It's possible the nag comes from one of two .dll's I've long reverted: markup.dll and StartResources.dll. The M$ guide update process regularly replaces these .dll's, so if you have the latest/not-so-great versions from M$ on your system, you may get the nag. Usually I'd notice those .dll's had been updated because the old, defunct "Sports" line and/or the Netflix app would disappear, so I'd shut WMC down and revert them from backups. It's possible I saw the nag during a time when the updated .dll's had been installed. Switching guide providers seems to have stopped the periodic update of those .dll's (another reason I don't want to switch back), but if you don't have older versions to revert to, you may be stuck with the nag. -
Windows Media Center EPG ending in January 2020
Mathwiz replied to Vistapocalypse's topic in Windows 7
Well, I already paid six bucks to Schedules Direct to get me through March. Now that I've made the switch, I don't think I want to go back. Still, it's good that M$ has backed off its plans to EoL their free guide for now. I set EPG123 to retrieve up to 21 days. I've never gotten that much, but it's consistently given me about 16 days, give or take a day - more than I get on my DVR+. Also the images for the shows are finally correct (I kept getting wrong ones with Rovi). -
Win7 End Of Support - KB4524752 MS Nagging Has Started
Mathwiz replied to WalksInSilence's topic in Windows 7
That seems suspicious to me. Why do we need a servicing stack update at end of service? The vagueness of that description doesn't exactly quell my paranoia. For now, I think I'll pass. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
GitHub relies way too much on the UA, and none of our browsers provides GitHub with a suitable UA out of the box (or .7z). Well, Serpent 52 does, but only in "native" move (not in FF-compatible mode). So Iset an SSUAO with Serpent 52's native UA string, Mozilla/5.0 (Windows NT 6.1; rv:52.0) Goanna/4.4 Basilisk/52.9.0, for github.com (to be consistent and safe, I also set the same SSUAO for githubassets.com and githubusercontent.com, although I don't think those are strictly necessary). Note that FF 60.9 also works, but the MCP's latest browsers now default to FF 68.9, which doesn't work (unless you're running a Quantum browser). It's nonsense like this that makes me somewhat sympathetic to what Google is proposing to do with user agents. Web sites should base their functionality on the capabilities of the browser, not its version or what OS it's running on. I've been wondering the same thing. My first thought was that the vulnerability probably affects versions based on FF 49, when the JS engine was rewritten, or later; if so, then FF 45, NM 27, ArcticFox, etc. wouldn't be vulnerable. But as you say, the javascript.options.ion pref does exist in those older browser versions, so I'm not all that confident about that assessment. -
@Destro and @TechnoRelic - I like both of your suggestions. (But don't forget we need a name for MailNews too, even though it isn't a browser.) But Moonchild might think of "Wolf Moon" the same way @roytam1 thought of "Royfox;" it would be best if he's OK with whatever names we choose. I can't see Moonchild or @Matt A. Tobin having objections to "celestial" names in general; after all, the latter suggested Neptune as a name. And I think it's OK to acknowledge the Pale Moon heritage of whatever we end up calling New Moon, as long as it's not so similar that folks might think MCP created these. @TechnoRelic's names seem to me to be in the "sweet spot" where the names are different enough (especially with the RFox prefix) to avoid confusion but still subtly give credit to the original works.
-
Glad you hear you got it working again. It was a rough few weeks, I'm sure - and right around the holidays too.
-
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
The latter pref is the one you need for general browsing, and it is supported in current browser versions. (AIUI the "chrome" pref is for the JS in add-ons and such.) Sadly, setting this false results in a significantly slower browsing experience here at MSFN. Even this results in a painful performance penalty on my home PC (not the best, but it is a 64-bit dual-core AMD, so it shouldn't be that horrible). So I think using @roytam1's latest versions (if you can use them), and leaving these prefs at their default, is the best choice. -
Beware of Office 2010 Updates!
Mathwiz replied to Dave-H's topic in Pinned Topics regarding Windows XP
So, taking off those "deny" permissions fixed it. I guess from now until Office 2010 EoS, I'll need to delete the Excel.Sheet.12\shell key and re-import my custom changes after each month's updates. The only thing I can't figure is why a "security update" even bothers resetting those registry entries. Maybe it just runs "Repair Office Installation" under the covers after it replaces the files included in the update. -
Beware of Office 2010 Updates!
Mathwiz replied to Dave-H's topic in Pinned Topics regarding Windows XP
Found it! I actually have two Excel versions on my VM: Excel 2000 and Excel 2010. Because I want .xls files to open in 2000 and .xlsx files to open in 2010, I altered the shell registry entries for both. Otherwise double-clicking a spreadsheet file tries to use DDE, which tries to open the sheet in whichever version is open. Obviously, if 2000 is open and I double-click an .xlsx file, that fails miserably. But I've been having a problem: something keeps going in and resetting all my shell registry entries, forcing me to fix them over and over. So I went into regedit and revoked permission to change these entries. And guess what? It's these monthly "security" updates that have been resetting my shell registry entries! And now that it's not allowed to do that any more, the update fails to install. -
Beware of Office 2010 Updates!
Mathwiz replied to Dave-H's topic in Pinned Topics regarding Windows XP
Presumably not, but I do have Excel 2010 installed I'll try downloading it and installing it manually, I guess -
Beware of Office 2010 Updates!
Mathwiz replied to Dave-H's topic in Pinned Topics regarding Windows XP
My copy of Office 2010 has graph.exe, although I confess I have no clue what it does! KB4484236 installed the fixed graph.exe just fine, but for some reason KB4484243 didn't install on my system. -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
@msfntor: Session Tickets exist for performance, not for security. If enabled, they avoid renegotiating TLS for every HTML download from a given server. But it was recently discovered that they can be abused for tracking you. Thus Pale Moon (and thence New Moon) have them disabled by default. If you want to enable them, you'll have to toggle pref security.ssl.disable_session_identifiers to false in about:config. But you'll make it a little easier for the Goog to track you online. -
I wouldn't hold my breath for FF 57 for XP (it's Quantum), but FF 56 might be possible. He has to figure out how to deal with the Rust framework on XP, which ain't easy, but he has made some progress....
-
I don't remember seeing that but I like it too, particularly for @roytam1's SSE version of FF 45 ESR. It concisely says exactly what it is. But for the present let's try to stay focused on MCP's forks, New Moon and Serpent, and MAT's forks, Borealis and Interlink. Those are the ones that keep causing us grief. Edit: Attaching @siria's logo. Looks like it might be a natural for Draconis, or whatever we end up calling Serpent (if we stick with the serpent theme, that is).
-
This is what @Matt A. Tobin said when he suggested the code names he used: So yes; those "in the know" might get that Freestyle, e.g., is the media-focused browser of the bunch. But we don't have to use those particular names; they just comprise a theme for those "in the know." True, I didn't know those code names either until @Matt A. Tobin suggested them. But no one needs to understand the theme to use the names! If you open it up to all M$ code names (not just XP versions), you have some better choices IMO. For New Moon, Triton is an obvious choice (it's a moon, after all); Aurora is the obvious choice for Borealis. The artwork to use for both is obvious too. We could reuse Whistler (and the artwork @Matt A. Tobin et al. came up with for that name) for Interlink, and stick with Freestyle and Moebius for Serpent 52 and 55, respectively. First, folks were complaining about the lack of choices. But now, a poll would probably look something like this:
-
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
I doubt the OS version has much to do with it as long as it'll run ffmpeg, handbrake, or whatever. What you really need (especially if you're transcoding and not just remuxing) is a fast CPU with lots of RAM. Which work machines are more likely to have than home ones.... -
My Browser Builds (Part 2)
Mathwiz replied to roytam1's topic in Browsers working on Older NT-Family OSes
I feel your pain. Way back on page 3 of this thread, there's a batch file that I wrote, which will download either of those browsers for you, ask you if you want to download & install LAV filters for h.264 video support, and if you press Y, will download & install the correct file for you! You can rerun it every time there's a new FF 45 and/or Arctic Fox version to download. The browsers will be unpacked into directories firefox-45 and arcticfox-27, so point your shortcuts there. (If they exist, your previous directories will be renamed to firefox-45-old and arcticfox-27-old first, so you can go back to them if the new versions don't work right.)