supermium: Supermium fails to install on older systems lacking presumably SSE3, with the browser itself not getting far enough to create a window.

On systems without SSE3 (very early Athlon 64s, Northwood and Willamette Pentium 4s, etc), attempting to install the browser through the mini installer only creates a tmp folder, without a shortcut or Supermium folder being created. Trying to workaround this by extracting the installer through 7-zip (in which the browser does still open on capable hardware even if it’s been extracted this way) causes the actual Supermium executable to only create around 3 processes before closing without any prompt or “stopped working” message. A debug.log is created, however, and the lines added to it are always consistent with each launch attempt. I did try to log everything I could out of it, but unless I’m doing something wrong (following this) , it doesn’t log anymore than running it normally does. I have attached said log below, however, it doesn’t look very useful in my eyes.

debug.log

I’ll also attach an msinfo32 export of my hardware, with some useless data removed. I’ll summarize it here as well:

Dell Dimension 4500
Windows 7 SP1 with all updates until EOL (not hardware but here for clarity)
ATI All-In-Wonder 9200 (Radeon 9200 with some TV features)
Sound Blaster Live! with the open source kX drivers
Northwood Pentium 4 2.0GHz
and 2GB of DDR1 RAM

report.txt

I’ll also attach an HTML report of my hardware as reported by CPU-Z. GitHub doesn’t allow me to attach HTML files, so I’ll throw it into a standard ZIP file.

CPUZ REPORT.zip

Lastly, even if it’s been already uploaded by me, I’ll show a video of what exactly happens once Supermium is executed. Yes I know there’s a watermark that makes this sound like a joke, it’s the only program I could think of in an instant to record my screen on this single core CPU.

clip0001.webm

I greatly appreciate the work that has gone into this project, and I hope I’m able to help by posting this issue. I’m willing to post any additional information if needed.

Side note, the reason I have Edge installed is because it oddly supports SSE2 systems, even with 109.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 15 (4 by maintainers)

Most upvoted comments

I have removed the SSE3 flag from the build configuration. Does this work? https://github.com/win32ss/supermium/releases/tag/v117-hf

Unless there is some asm or third party component that went its own way.

As with the “graphical weirdness”, Chrome only draws the titlebar, not the side bars. You can set #native-xp-theme in chrome://flags to bridge the gap somewhat.

I’ll see if I can fix the installer. All Chromium components should build without the SSE3 flag, including the mini_installer, and in fact that would be one of the last places I’d expect problems to occur. In fact I will hunt for SSE3 instructions in the installer!

XP (without One-Core-API) is still a little far out. But I do have my custom DLL ready to expedite the porting process and I will test it on some smaller applications soon.

I’ll assume it works, since my SSE2 system is currently unplugged. At least it runs now.

Although it doesn’t matter, 119 still has a supermium_119_32_32_setup.exe installer error.

The problem is that I was not running the installer correctly. I have UAC disabled and I tried normal startup and startup with Administrator rights - that’s from the context menu. These methods didn’t work, but I should have opened the compatibility tab and checked the “Run as Administrator” checkbox there. The installation has been tested on SSE2 CPUs. It’s all working.

I had neglected the installer as I was stuck dealing with other things. I plan on making more substantive improvements to the installer as some other users complained about a lack of a GUI element.

Yes, that would be it. mini_installer spawns setup.exe. Thanks. In fact this is the very first thing called in wWinMain.

As a side note this exposes another issue of the mini_installer: the fact that it is completely silent. It’s wWinMain, as in “probably a Windows GUI application”, but it doesn’t take advantage of this status. So I will be adding some MessageBoxes and other windows to indicate errors to the user, as well as the option to select the installation folder, while restoring the ability to install shortcuts on Vista and below.

I will probably drop the block altogether, in the event that the user installs an SSE2 emulator on their system. That’s a very difficult undertaking because not all SSE2 instructions on MMX-SSE systems result in a #UD but I could see this being attempted in the future.

As with the “graphical weirdness”, Chrome only draws the titlebar, not the side bars. You can set #native-xp-theme in chrome://flags to bridge the gap somewhat.

I’ll see if I can fix the installer. All Chromium components should build without the SSE3 flag, including the mini_installer, and in fact that would be one of the last places I’d expect problems to occur. In fact I will hunt for SSE3 instructions in the installer!

XP (without One-Core-API) is still a little far out. But I do have my custom DLL ready to expedite the porting process and I will test it on some smaller applications soon.

While there could very well be instructions snuck in, another possible case is the installer is intentionally stopping itself when it detects SSE3 is not present. Quoting this document .

“On x86 processors without SSE3 support, running Chrome will result in a crash. The Chrome installer will attempt to exit early, but might also crash.”

But not sure if they’re referring to the Chromium mini installer, Chrome’s proprietary installer, or both.

Edit: Yeah that’s probably it. Changing that 3 to 2 might just make it work, since I’m not sure if supporting anything lower than a Pentium 4 is a goal here. But that might be for the online Chrome installer, not the mini one,

I have removed the SSE3 flag from the build configuration. Does this work? https://github.com/win32ss/supermium/releases/tag/v117-hf

Unless there is some asm or third party component that went its own way.

Mini installer still exhibits the same behavior, but that doesn’t mean there’s not any good news to bring (after extracting the installer manually).

117hf

Don’t know what’s up with the graphical weirdness on the window sides, maybe the redesign doesn’t play nice with no compositing (using XPDM drivers that also can’t accelerate DirectX 9, so SwiftShader is in use by Chrome), or it’s some upstream bug. But that doesn’t really matter right now, it works!