Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/24/2019 in all areas

  1. System_Info is working OK in Windows 7/8/10 and in Win PE. It was just about the extra option to show UUID, where the very useful RegRead solution does not work in Win 7
    1 point
  2. The .NET Framework updates are internationally applicable and do not require language-dependent updates. When installing the .NET Framework, it is possible to install a language pack as desired. In the previous post (https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/?do=findComment&comment=1166316) in the file "Net Framework.txt" are the download links for the language packs included (here I had inadvertently written "Sprachpakete" instead of "language packs" in the description. For example, it installs .NET Framework 3.5 sp1 and then installs the desired .NET Framework 3.5 sp1 language pack (by Sprachpakete). The same with .NET Framework 4. Note: .NET Framework 3.5 sp1 and .NET Framework 4 do not required an English-language language pack.
    1 point
  3. Have generated the required updates for .NET Framework 3.5 sp1 and 4 based on my lists. .NET Framework 3.5 sp1 Updates .NET Framework 4 Updates Archived at WayBack! Note: After the installation of .NET Framework 3.5 sp1 the Windows XP update KB961118 is needed! Furthermore, I recommend KB971314. This update to resolve an issue where included PCL printer drivers are no longer signed after installing Microsoft .NET Framework 3.5 SP1 or XPS Essentials Pack on Windows XP. Update History .NET Framework 3.5 sp1 Update History .NET Framework 4 Note: Furthermore, I have created an update rollup (of the required updates/msp files in a HotIron installer summarized!) for the .NET Framework 3.5 sp1, as well as created an update rollup for the .NET Framework 4, where the installation takes much less time. If you are interested, please send me a PM.
    1 point
  4. An allternative for Win 8/10 would be to use the AutoIt code RunWait(@ComSpec & " /c wmic csproduct get uuid > UUID_Info.txt", @ScriptDir, @SW_HIDE) ShellExecuteWait("notepad.exe", @ScriptDir & "\UUID_Info.txt", @ScriptDir) Or even better and working in Win 8/10 and 10XPE but not in Win 7 $UUID = RegRead("HKEY_LOCAL_MACHINE\SYSTEM\HardwareConfig", "LastConfig")
    1 point
  5. Of course. Now those two other threads are merged into this one.
    1 point
  6. Windows XP has been spotted (specifically an embedded version) in a recent CNBC video:
    1 point
  7. I've used this on Linux and Windows 8.1: https://anydesk.com/ And just now I installed the Windows version on Windows XP without any problems. Phil
    1 point
  8. XPS Essentials Pack (All available languages! The installer of the same name contains a respective MUI file.) Archived at WayBack!
    1 point
  9. well it isn't easy as it seems. KB4493472 was in fact the first update that has broke vmware and avast. (atleast for me though). The servicing stack update didn't change anything for me nor the may updates. The first update that started to solve my problems was KB4499178 so maybe give it a shot in vm? I have some free time tommorrow i will try to install 3 vms and test it, but i suggest to everyone just try the preview. You can uninstall it if it makes some harm to your os.
    1 point
  10. A tour de force, @mixit! I never would have thought uBO could fix this issue. Actually, in my case, it couldn't because when I click on "my filters" an empty filter list comes up - but for some reason I can't type anything on the page! (I'm using the latest legacy uBO version, 1.16.4.10. Unsigned, of course.) So I instead went with the userContent.css solution, and it works perfectly! I'll give it a try on SeaMonkey too. Edit: This works on SeaMonkey too. (Just don't forget to restart the browser when using the userContent.css fix!) BTW, thanks for the heads-up about spoofing "too new" of a browser version. New Serpent versions default to 60.9, and sure enough, Instagram quit working today. I backed off to version 56.0 and it's OK again.... ... except that breaks GitHub so it's a SSUAO for GitHub back to 60.9 again.
    1 point
  11. You guys give up too easily, is this the infamous XP lair of fanatics or not!? Fortunately there is (for time being, anyway) a pretty simple fix for this "video problem". (I use quotes because it has nothing to do with video as such.) You don't need to switch or recompile browsers either - at least not right now over this particular issue. Apparently ESR 52.9 handles CSS flex layout a bit differently, so with the current Instagram code the video and its surroundding elements kindly get the height of 0 pixels... This can be fixed by modifying a surrounding <div> container to use block display instead of flex. If you use uBlock Origin, you can add the following rule to your My filters: instagram.com##div.ZyFrc[role=dialog]:style(display: block !important) (Just make sure Filterlists > Parse and enforce cosmetic filters is checked and that Settings > Default behavior > Disable cosmetic filtering is not checked or is overridden per-site for instagram.com.) The same can presumably be done with other styling/tweaking extensions, only the syntax may be a little different. I don't use anything else, so can't give you the specifics. If you don't use any such extensions and don't want to install them, you can just add the following CSS snippet to your userContent.css file (it's located in the chrome subdirectory under your Firefox profile folder. Edit: as @Dave-H pointed out, the file may not exist yet, in which case just create a new text file, put this stuff in it, and rename the file to userContent.css.) @-moz-document domain(instagram.com) { div.ZyFrc[role="dialog"] { display: block !important; } } (In this case you'll have to restart the browser for this to take effect, only refreshing the page won't make a difference.) BTW, aside from div.ZyFrc[role="dialog"] , simply using div.ZyFrc or div[role="dialog"] also works. I'm just using the more specific condition to hopefully avoid accidentally breaking something else on Instagram (I'm not a frequent visitor there, so I wouldn't know). The mangled class name ZyFrc is pretty likely to change when they rebuild they code, and using the role-based version without a class name may survive that. Or it may not - as we know web devs need to constantly tweak their stuff, even when it's not broken... So this may need to be revisited. Edit: Forgot to give kudos to @Mathwiz for narrowing down the problem and linking to this change list with hints to flex layout being the problem. Edit 2: I tested this style fix on ESR 52.9.0, but I'd be surprised if 52.9.1 would be any different in this regard. ----------------------- In other news, if you're spoofing a more current version of Firefox on all sites with ESR 52.9, apparently you'll have to drop your spoofed version below 57 on instagram starting today, because they seem to have switched over to Quantum-specific code for newer versions and basically nothing works anymore. (If you're using the default 52.9 user agent, you shouldn't need to make any changes because of this - at least it seems to work for me.) It could mean, though, that they'll be dropping support for anything pre-Quantum sooner rather than later, which may also affect the various Pale Moon derivatives, depending on how up-to-date their CSS and JS support is.
    1 point
×
×
  • Create New...