-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support newer Windows #9
Comments
I'm working in that direction. |
Its done, and ready for testing. |
Many thanks for your efforts 👍 ; I'm quoting you from the
My old laptop comes with Windows Vista SP2 32-bit, was bought in 2008 and has rather under-resourced specs 😞 by today's standards: CPU: Intel Core 2 Duo T5250 @1.50Ghz (SSSE3) win32ss's Thanks in advance for any insight/guidance 😄 ... |
Hello,
yes, now its divided to 2 components, The instructions, which file should be ranamed to replace original is inside archive. |
Thanks for your reply 😄
... How can you be so certain? In your original reply, you advised:
I don't have any choice, do I? Versions of your DLL prior to Best wishes. |
So are you using HDD? I thought you were using an SSD drive in Vista, so I said there would be no acceleration. Ok, I will think about what to do with this. Yes, I will try to do this for x86 systems, not only XP, but also Vista and Win7, |
UPD: seems as worked when running x86 over Win7 x64. Will build it and upload soon. |
... Yes 😉 ; the laptop (Toshiba) came in 2008 with a 128GB HDD, but in 2016 it was cloned/migrated to a 500GB one, which I'm using to this day; two partitions, C+D, with the OS living on the C partition (155GB) ...
FYI, SSDs are to be avoided on Vista, because the OS lacks native utilities to successfully trim SSDs (payware apps do exist):
My iGPU (Mobile Intel 365 Express Chipset Family) with its Toshiba custom driver is already blacklisted by latest Supermium/Thorium: If I force GPU via
Vista SP2 != Win7 SP1 ; I would advise you not to rush things and, for good measure, test/verify on Vista itself 😉 ; I'm under the impression "upstream" lib (progwrp.dll) treats Vista differently compared to Win7, isn't that so? In any case, if it can be done, there's no need to rush it - if it can't be done, then I'm fine with that, too 😜 ; thanks for your precious coding time 😄 ... |
It works same with my alternative, because for API I use XP-compatible mode here. All NT6-specific APIs are emulated (including Vista). PS: Are you alrerady trying latest build 5049 to compare ? |
... I just finished testing your latest release, I'm actually using the portable PAF distribution from https://portableapps.com/apps/internet/supermium-portable so only one Thanks anyway... |
Hm.... thats bad. |
Try todays build 5051. Now should work. I have tested it (for running) on Vista VM. |
The Windows 7 version now runs on One Core API Server 2003 x86. Supermium 122.0.6261.152 (R5) |
Stepman123, |
Yes, that's it. |
... Launching which stays on screen for 2-4secs and then auto-closes 😭 ... FWIW, with these new DLLs of yours I don't get hanged I don't think I should pursue this any more; it'll be a waste of your precious time 😜 ; I'm glad that win32ss's solution just works and I'll have to move on with that: Thanks for trying though, take good care 😄 ! |
Hi, I tested it for running on VM (VirtualPC 2007), but with test set of switches and without portable runner. Thats what I have: Ok, I wil check it with portable runner and without any switches, If it dont works with it. I have no time for testing if with all possible environments, thats sorry. :) The user, which really need it, should help with it. Same was with Win2003 srv, which not runned from initial build and was requered 2-3 iterations. Its because initially was intened for XP SP3 only. |
UPD: yes, It closes, when running without any switches, So I will work more to investigate whats happened. |
I found that the difference is: I use |
Have uploaded new build. Yes, for Vista/Win7 it requeres |
...It's very late at night in my timezone, however:
Adjacent to the AdditionalParameters=--no-sandbox
DisableSplashScreen=false
RunLocally=false
# The above options are explained in the included readme.txt
# This INI file is an example only and is not used unless it is placed as described in the included readme.txt
I did a quick test with latest On a clean/fresh profile, latest Supermium (R5) did launch and stayed open, but:
BTW, I did not try to install any extension from the CWS... When I tried to launch my default/"dirty" profile, it was a complete mess; the session tabs failed to load, the browser kept generating messages/notifications about tabs crashing and, most importantly, extensions crashing (practically all of them); I felt despaired, to be frank 😞 ... While I do have faith in you 😄 , all I can tell you is I feel it's still a long way from final success in the (my?) case here...
While that flag was also needed in the initial releases of Supermium for Win7, it's no longer a prerequisite even on XP with the original
... Take your time, but please do (investigate...) 😜 ... Hitting bed now, finally... |
The success was only "speed and size", in my case, and on XP (Even by "excluding some spare parts of that car"). Initially I dont planned another :) . It was only for me. It seem like more good solution will be to provide another separate version for Vista/Win7, or emulate less API's by XP-compatible calls, which will have almost all API's, redirected to original DLL's. (as original progwrp do same). Because in current variant all calls emulated by XP-compatible API's. It works on my config, But of course not for all configs, as your one. I also dont have real Aero inside VM to check if it really works with aero (And I not using it anywhere). May be it depends on Video-adapter inside VM. I'm do investigating it more in such case.
I'm do testing of it only on special test profile, with But I also checked that it opens pages, of cource, before uploading it. It was ok. May be Aero calls to this mess.. may be some another. |
Im now investigating whats happened with sandbox under Win7 with my implementation.
Its right. |
I have a good news. Done large work by hands. And now it works with Aero and with sandbox enabled on Win7 & Vista. Note that my implementation uses most APIs emulated here by XP APIs, or stubs (as for XP native version), in contrast to original lib, which just redirects its to system libs for NT6. And check it on test profile, before running with a real profile to prevent above accident :) |
Hello, @Vangelis66. I have found that on my 1st test machine with Win7, the Aero interface was not functioning properly, Now it looks like this: You can try how it works. |
Hi @IDA-RE-things 😄 , hope you're well... I have now upgraded to the most current Supermium 32-bit release, My default "dirty" Supermium profile with lots of customisations 😉 in the form of cmdline switches and internal
... and in your Release Notes:
Thus, indeed, I only tested with Well, I have mixed results to report:
a. As the browser was loading, most extensions crashed: b. As the browser was loading, internal (chrome://*) and normal tabs, pinned or not, CRASHED: c. Trying to reload a crashed tab was to no avail (Error Code: STATUS_BREAKPOINT): ... After my initial frustration, it became clear to me that these failures on my dirty profile were due to either
Needless to say, troubleshooting and actual discovery of the culprit(s) took many nerve-wrecking trial-and-error attempts 😠 , which itself took many hours 😞 ... To cut a (very) long story short, the actual culprit was internal flag
I had enabled that flag to "squeeze more" out of Supermium's V8 JS engine (bring it on par with Chrome 125 ?), but this experimental custom flag is the one that is incompatible with build5056 of your libs 😿 ; to use your libs, I have to leave that flag at "default" (or disable it) - that culprit flag works as expected with the official lib, though... If you have some spare time, could you please investigate why Many thanks already, you have done a great job for people on older H/W; and yes, Sm does indeed load somewhat quicker here with your libs compared to the official implementation ( Kindest regards 😃 PS: While I'm running the browser in "portable" mode, I did notice that your libs write to the registry:
Is this absolutely necessary? |
Hello, glad to see.
the registry approach was selected to support inter-process "Screen Saver running prevention" feature, by Power-saving routines. whish are absent on XP and Vista. And about the errors with your "dirty profile"... Yes, seems that some functions called where was stub breakpoints, set by me. |
UPD: have fixed that issue with stub on 1 function (EventRegister), when |
Thanks once again! 👍
I had just generated my own crash dumps, as requested, when your very last comment went public 😉 ... NB: To get back to a working instance of Sm with the
Thanks for this explanation - I guess I could've first read #13 😜 ... |
Hello, I have created and upload build 5061, after fixing another small issue, not touched this topic. |
Great! Many thanks! ❤️
... If I got this right 😜 , for Vista32 I don't need file Congrats! 🥇
That issue was also mentioned in upstream #574 (recovered via Google Cache, as Supermium's GitHub repo has been taken down, hopefully not for long): |
Hello, would you be able to update the Win7 API Redirector to work with Supermium 124? I am using the 64-bit version. |
Hello. Ok, will do this in near days. |
Supermium still depends on progwrp for newer versions of Windows, such as 8.1. I would like to be able to use your alternate library.
The text was updated successfully, but these errors were encountered: