NotHereToPlayGames

I've seen that also. BUT... only in a VM (XP x86) with only 512 GB RAM allocated, so I shouldn't have expected too much anyway. I can get by with only 512 GB RAM for a lot of XP stuff (even 3D CAD), but definitely not for "semi-modern" web browsers. In my case, the GUI *eventually* showed up. *IF* you let it just sit there for FIFTEEN MINUTES or more and don't touch the mouse or keyboard the entire FIFTEEN MINUTES.

Update. I still cannot do a screencap yet (new computer does not get internet connectivity until *after* I get the OS rebuilt to my "liking"). I installed Supermium v126 R7 inside a Win10 VM on my new Intel Core Ultra 7 and Supermium v126 does *NOT* have the font-indent issue. This issue is DEFINITELY hardware-related and it has ALWAYS existed (all versions of Supermium except maybe the most recent) on my 17/18yr old Intel Core2 Quad Q6700. And yeah, bad habit, but I always reference my computers by their CPU and not their GPU. I kind of doubt that I will bring the Q6700 back to life just for the sake of a font-indent issue screencap on old-versus-new Supermium. A font-indent issue that was present both "direct" and "inside a VM" on the Q6700 but does *not* effect (affect?) my new hardware.

Oh, I should also point out that the old Q6700 also had recent issues with WebGL. Or shall I say what a few here at MSFN perceived as possible WebGL. BUT... If one digs further into MapQuest (one of two web sites being tested at the time), it does *NOT* technically use WebGL. Per AI enquiries - "MapQuest.js, integrates with Leaflet.js, which primarily uses standard web technologies like Canvas and DOM rendering, rather than relying fundamentally on WebGL for its core functionality."

I never dived into any. I do not keep Supermium around and only ever run it from inside VM's that have never seen Supermium until the run. So always brand new profile, directly as-is from the distributed .zip, never the .exe. Again, I may have been one version off as I didn't notice until yesterday that there is a very recent new version which may or may not have the font non-indent first letter half-missing. I may grab a screencap eventually, even if only found in older versions, so that others know what to look for. But... Um... Very, very low priority...

I personally like "numbers". Browser benchmarks, CPU benchmarks, forum post view counts, read counts, and even REPUTATION POINTS are *IMPORTANT*. ***BUT*** MSFN has proven that "reputation points" are *NOTHING* more than a "game" that people here play EACH AND EVERY DAY. I've come to see them as *FINE ART*. We have members NO LONGER active members whose "rep points" have TRIPLED now that they are NO LONGER ACTIVE MEMBERS. Look up the "value" of fine art *after* the artist or author passes on. I just sit back and laugh. And ramble about it every once in a while.

Or are we trying to count how many times a "bot" stumbles upon an MSFN Thread ???

Technically... Counting replies is legit. But counting views also counts "bots" and not real "people". At least on many other forums. The "view" count is meaningless and misleading. REPLIES on the other hand can be considered an "important tool for the author of an article".

Can't. I am in the middle of replacing my 17/18yr old Core2 Quad Q6700 computer with my new gift-to-self (take advantage of seasonal sale pricing). A screaming fast (compared to everything else I have) Intel Core Ultra 7 265. And no, sorry to say, but Supermium will *never* be used on this new computer, sorry, it just isn't. From memory, without screencapping, it's any-and-all input dropdown boxes in the GUI. Text inside the input dropdown is shifted to the left and half of the first letter is not present, buried by the input field border/padding. To be fair, the Supermium I had on the Quad Q6700 "might" have been a version old, not the most recent.

Lucky you! My fonts in Supermium have ALWAYS been offset on the left. Strictly referring to GUI fonts, in XP and 10. Fonts rendered on web pages have always been fine. Thorium had this font alignment issue also. But I only ever tried one or two Thorium versions so unsure if ever fixed.

That's one thing I never liked about XP's default setup. Something like "C:\Documents and Settings\YourName\My Documents" might not seem like much at first, but those 47 characters is using up 18% of your allotted 256. The thing that always annoyed me is that Windows would run everything just fine, even if you exceed 256, *UNTIL* you go to copy/archive the files and only then does Windows throws up a name-too-long error. Even though it's been using those names as-is without any issues.

Agreed! I shouldn't have tied to CPU but rather tied to GPU. My bottom-line remains the same, same EXACT browser profile, both Serpent 52 and Chrome 140) *DOES* work on my "i7+gpu hardware" but does *NOT* work on my "core2+gpu" hardware. I won't really be digging in deeper here either. My *LIMITED* tests *reveal* (at least between two of my computers) that this is clearly HARDWARE-RELATED (and perhaps even with about:config "flags" as a WORKAROUND for said hardware). And we would need details on the Original Poster's HARDWARE to go any further.

<del>

<del>

<del>

I can report that on my end (Serpent 52 and Chrome v140 on Win10) that various WebGL web sites *DO* work on my Intel i7-4770 but do *NOT* work (same exact Windows install, same exact browser profile) on my Intel Core2 Quad Q6700. On my i7-4770, it *seems to be* tied to having five monitors and Serpent 52 has to be forced to use what about:support labels as #2 (by disabling #1 in Device Manager). So HARDWARE *does* dictate whether the map will load or not!

For the record, WebGL is (and always has been) *ENABLED* on my profiles. MSFN Membership (at the time) "hype and propaganda" and "overly-paranoid" had it disabled in the uploaded/shared 360Chrome config. Only to later be ENABLED because most "this web site doesn't work" were dang near always tied to WebGL. ie, I eventually started IGNORING the "overly-paranoid".

There is no map in Chrome v140 on Win10 either. (for reference)

See here for more - https://help.pdf-xchange.com/pdfxe6/index.html?command-line-options_ed.html I'm afraid that if you find command lines "too confusing" then I'm not going to be able to assist any further. I've provided what the DEVELOPER HIMSELF/HERSELF cites for setting file associations.

Whatever is easiest for you, OPEN AN ADMIN COMMAND PROMPT and direct it to the FOLDER CONTAINING your "PDFXEdit v6.exe". Then perform BOTH of the following (unsure if which is performed first is important or not, this was the order the DEVELOPER indicated): "PDFXEdit v6.exe" /fileassoc:user=no "PDFXEdit v6.exe" /fileassoc:user=yes This really really REALLY should solve your problem - IT IS DIRECT FROM THE DEVELOPER OF PDF-XCHANGE (but the VIEWER instead of the EDITOR, this method is supposed to work for both).

Try this. 1) Open FILE EXPLORER (even if you have alternative file manager, please open FILE EXPLORER) and navigate to your "PDF-Xchange Editor v6 Portable" folder. 2) Click ONCE inside the address bar so that the entire folder PATH is highlighted. 3) Do CTRL-C on keyboard to copy that hightlighted PATH. 4) Now open a COMMAND PROMPT WINDOW *AS ADMIN*. 5) Type "cd " (c d SPACE) without the quotes then CTRL-V then hit ENTER. ie, an ADMIN COMMAND PROMPT from the directory CONTAINING your "PDFXEdit v6.exe" file. 6a) Now do *BOTH* of the following (no!, the second one does not 'replace' the first one, the first one MUST be executed to establish LOCAL MACHINE registry configuration). 6b) In that ADMIN COMMAND PROMPT, enter and execute the following INCLUDING the quotes around the .exe file name: "PDFXEdit v6.exe" /fileassoc:user=no 6c) AFTER doing the above, do the BELOW in that ADMIN COMMAND PROMPT (this sets CURRENT USER registry configuration that is USELESS without the LOCAL MACHINE registry configuration also in place): "PDFXEdit v6.exe" /fileassoc:user=yes 7) REBOOT YOUR COMPUTER - *required* for additions to LOCAL MACHINE and CURRENT USER registry hive changes to *take effect* 8) double-click on a .pdf file and (fingers crossed), it SHOULD launch PDF-Xchange Editor *and* open the file you double-clicked

Here's where I would go next "if it were me". The pop-up box contains a list of programs that are PROPERLY embedded within the OS Registry. Scan that list for something that should be "rare" within the OS Registry, search for THAT PROGRAM in the OS Registry. You should be able to find WHAT populates that pop-up list. Now you know WHERE to ADD your preferred pdf file "handler". edit - I kind of have to assume that you have a PATH issue, you are associating pdf files with an EXE (with spaces in the name!) but nowhere is the PATH (also containing spaces!) to that EXE being defined. SPACES have a way of "breaking" things if not properly accomodated for. Why "all of this" is just now hitting your setup is definitly a mystery. My assumption is a "registry cleaner" was used, but that is just an assumption.

There *MUST* be something different between the two OS Registries (not to state the obvious, as I'm sure you already know this). Many associations are much more complicated than "OpenWithList". I guess all I can suggest at this point is to search for any-and-all pdf ocurrences in that 2nd W7 Pro's registry and compare to the computer where you are having the issues. There's (obviously) something different between the two and it basically "has to be" at the registry-level. ps - I can't help but "laugh" when BACKUPS contain issues that the backup was resorted to in order to FIX the non-backup. not laughing "at you", laughing because this happens at work *ALL THE TIME*, "backups" are never TESTED and when they go to get USED, the department finds them to be *USELESS*.

There isn't supposed to be. A true "portable" will *NOT* be associated. If you want the association, you should probably be using the "regular" version instead of the "portable" version. "Portable" versions are generally for people that do *NOT* want the file associations. Your list does *NOT* narrow things down for me, they all do not create the "bin" / "profile" the same way. But if you do not have any issues running the program THEN opening a .pdf, then your "bin" / "profile" SHOULD be okay (ie, not corrupted). Again, if you want OS-Level ASSOCIATIONS, you technically shouldn't be using the PORTABLE version. Because there are "mime types" and GUIDS and CLSIDS and ProgIds and namespaces and file PATHS and other things to also "associate" above-and-beyond a simple "OpenWithList". ie, things that over-simplified "registry cleaners" would have wiped clean and all you are trying to bring back is the "OpenWithList" - won't *always* be enough (sometimes it is).

Not sure on Win7, but never trust an Uptime claim on Win10. Why? Because you can "hibernate" and then leave the computer in the attic for DECADES. Then launch it DECADES later and the "uptime" will SAY it has been "up" for that ENTIRE time.

Do you have a link of where you obtained PDF-Xchange?