Discussion for users.

[Alex313031]

Hey @retapich and @libreom , I see that you guys use alot of my Windows 7 projects, like Thorium-Win7, Codium, and this.

I appreciate it. Windows 7 forever!! Since you guys have been "loyal" users, I am personally contacting you here to make this a little discussion place where ya'll can get "priority support" for issues and a place for you to make suggestions about features or bug fixes (cant promise anything about any particular issue though).

I am also interested in what systems and OSes you are running my software on, because while I'm assuming windows 7, you guys may be using 8/8.1 or an old linux distro.

[libreom]

Hi, sorry for late reply, I am using windows 7, in Intel core i3-3110m cpu and 4gb ram laptop, also I know using linux but doesn't and this is my primary laptop. I would just like you to maintain thorium-win7 with upcoming versions, thanks. If you can figure out compatibility for later electron versions and patch it to run in win7 even in closed source software it'll be good. If you can figure out running later nodejs and python then it'll also be good also mpv too

[Alex313031]

@libreom Im gonna update Thorium-Win7 with a new M119 build with backported patches from thoirum M120 and M121, and backported security patches from chromium M120. Next release will be based on supermium M121 but idk when that will be.

There are already fixes for later python3 to work on win7 Node 14.x is the last to run standalone on win7 though. I notice you use alot of me electron apps, like Codium lol.

[libreom]

Understood, thanks. Update to 121 build whenever you can/want. Yes, I use thorium-win7(also other builds for Linux,avx2), codium(since original isn't supported anymore in win7), mercury-win7 and armcord

[libreom]

Can you publish SSE4 builds of thorium-win7 M122.0.6261.132 (or later version if it is soon) release like earlier build of M119.0.6045.214

[libreom]

I installed python 3.12 with https://github.com/Alex313031/Python-Win7 , It works. Can you provide or link to node later version builds for windows 7. It would be very helpful. Tried this https://github.com/Alex313031/nodejs-win7 and its origin but it doesn't seem to have binaries. Also just saw https://github.com/Alex313031/node16-win7 are you planning to do this?

[NAKADZI]

@Alex313031 Thank you for paying special attention to your most active users. I'll keep it in mind when I have any problems or suggestions.

I am also interested in what systems and OSes you are running my software on, because while I'm assuming windows 7, you guys may be using 8/8.1 or an old linux distro.

As for this: Thorium is usually used on old PCs, like Intel Celeron D 331, which is paired with 3GB DDR2 and Windows Embedded Standard 7 (which had to be manually configured to resemble Windows ThinPC, as the ThinPC edition does not have a 64-bit installation image; There was also an attempt to use Win8.1 Industry Pro instead of Win7, but there were numerous problems with drivers). By the way, this PC is used for not very serious office tasks in one institution.

I also periodically service similar PCs, and on a large number of them I install the surprisingly fast Win8.1 Industry Pro (with additional performance settings), in which I replace the standard disgusting "Start" menu thanks to this great script (since Open-Shell always loads the RAM by 50+ Megabytes).

And if I have to deal with Linux, I almost always install the latest release versions of distributions such as Devuan ("runit" + "LXQt" DE), SparkyLinux MinimalGUI (+ "Lumina" DE), Vanilla Dpup.

---

@libreom

...Can you provide or link to node later version builds for windows 7...

I think later versions can be made to work with the VxKex project. Have you tried it? I think for it to work properly, you'll need to apply the VxKex parameter to each "exe" file in the program folder.

[Alex313031]

@libreom Gonna publish SSE4 builds with an updated M122 build with lotsa fixes.

Yes, Python3 works fine from that repo.

That guy had binaries, and then he removed all of them for some freakin reason. Im deprecating the nodejs-win7 repo, and instead focusing on the node16-win7 repo, which is based on his but will also have patches for OpenSSL. I will be making builds/installers when I have time. As far as Node 14 goes, you can already make that run with an environment flag. As far as 18, maybe I'll do that in the future, but most of my projects use Node 16, and there are very few projects out there that use Node 18 that wouldn't run into some other problem getting it to build on Windows 7, so.

@retapich Cool. And yes, but it's buggy. It's better to build a patched version and use that. VxKex works wonders for other programs though, without bugs.

[K4sum1]

Not sure if I want to make this a new issue, so posting here. Since there's an official ArmCord Windows 7, what about making GoofCord Windows 7?

https://github.com/Milkshiift/GoofCord

[Alex313031]

@K4sum1 Not to hate on armcord, and I will probably make PRs to fix these, but this fork has more fixes for Win7 and building with Node 16 than the win7 branch upstream, so it is still (IMO), the best Discord client for Win7 currently.

And cool! Another project for me to resurrect Win7 support on lol.

I will start on that right now.

[Alex313031]

@K4sum1 https://github.com/Alex313031/GoofCord-Win7 there you go (just source right now, gotta build)

[K4sum1]

Before you go building, can you check if ping title in window is fixed?

Edit: The code seems quite different, don't think there's any issue here,

[K4sum1]

GoofCord doesn't seem to have portable mode or the code is different, could you add it from ArmCord?

https://github.com/ArmCord/ArmCord/commit/378fef1a0e39854b971f253fb19eb6b5dd9023a2

[Alex313031]

@K4sum1 Added!

Builds coming now.

[Alex313031]

@K4sum1 Here you go > https://github.com/Alex313031/GoofCord-Win7/releases/tag/v1.4.1