Supermium

[NotHereToPlayGames]

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]

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.

[roytam1]

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.

[Dave-H]

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.

[roytam1]

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]

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 20 hours ago by NotHereToPlayGames

[ED_Sln]

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 4 hours ago by ED_Sln