NotHereToPlayGames Posted Tuesday at 09:08 PM Posted Tuesday at 09:08 PM 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."
NotHereToPlayGames Posted yesterday at 11:17 AM Posted yesterday at 11:17 AM 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. 1
roytam1 Posted yesterday at 12:44 PM Posted yesterday at 12:44 PM (edited) supermium v138 can be used here, showing a blank window. v132 can be used but I can't find a way to downgrade my profile. filed as https://github.com/win32ss/supermium/issues/1716 Edited 6 hours ago by roytam1
Dave-H Posted yesterday at 01:22 PM Posted yesterday at 01:22 PM You say a blank window, do you mean that there are no GUI elements visible? I must say that in all the Supermium versions I've used, I've never seen that. 1
roytam1 Posted yesterday at 01:40 PM Posted yesterday at 01:40 PM 16 minutes ago, Dave-H said: You say a blank window, do you mean that there are no GUI elements visible? I must say that in all the Supermium versions I've used, I've never seen that. yeah, a frameless transparent window and supermium doesn't ever try to draw anything on it.
NotHereToPlayGames Posted yesterday at 01:56 PM Posted yesterday at 01:56 PM (edited) 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. Edited yesterday at 01:59 PM by NotHereToPlayGames
ED_Sln Posted 12 hours ago Posted 12 hours ago (edited) 19 hours ago, NotHereToPlayGames said: 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. If you mean this: https://github.com/win32ss/supermium/issues/1596 This has been fixed in 138 R6. The problem was in the instructions; if the processor did not support SSE4.2, this bug could occur. Edited 12 hours ago by ED_Sln 1
NotHereToPlayGames Posted 8 hours ago Posted 8 hours ago (edited) Does not appear to be the same issue. For me, the issue was *ONLY* on Supermium's SETTINGS PAGES and not on visited web sites. Though it is possible that it is related somehow - a font issus is a font issue, whether it be an external page (visited web) or an internal page (settings/flags). Truth be told, I *rarely* actually visit any web pages using Supermium (it did not play well with my old hardware and there is NO USE to use it on NEWER hardware). As it's "last straw", I upgraded it from Win XP x86 to Win 10 *LTSB 2016* and that did MUCH BETTER than trying ported browsers trying to prolong XP. Will be *weeks* (if at all) before I can repurpose my old Intel Core2 Quad Q6700 where this font-indent issue exists. BUT... personal experience being my guide, it will very likely STAY on Win 10 *LTSB 2016* and it will never again "waste my time" attempting to prolong XP. "Been there, done that", as the saying goes. Edited 7 hours ago by NotHereToPlayGames
NotHereToPlayGames Posted 7 hours ago Posted 7 hours ago I should add, we all should consider that Win10 from 2016 through 2019 shoud all be reconsidered here at MSFN as *QUALIFYING* for "older OS's". Here at MSFN, you say "Win10" and all the XP and Vista folks seem to outcast you as not using an "older OS". I am not a fan of any of the "H" versions of Win10+. ie, anything that has a version numbering like 21H2, 22H1, 22H2, 24H2, 25H2, et cetera. But Win10's that PRE-DATE that numbering scheme is VERY MUCH SO an "older OS".
Dave-H Posted 6 hours ago Posted 6 hours ago FWIW, and off-topic, IMO any operating system version which is no longer supported could be said to be an 'older operating system'. That now even includes early versions of Windows 11! 1
VistaLover Posted 2 hours ago Posted 2 hours ago On 12/24/2025 at 3:56 PM, NotHereToPlayGames said: with only 512 GB RAM allocated On 12/24/2025 at 3:56 PM, NotHereToPlayGames said: I can get by with only 512 GB RAM for a lot of XP stuff ... Surely a typo, but you actually mean MB there, don't you ...
NotHereToPlayGames Posted 2 hours ago Posted 2 hours ago lol, good catch... not the first time I've done that typo... a flaw with my keyboard, I'm guessing...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now