i486
YuZhouRen86 improvements?
@i486: It is possible to add @YuZhouRen86 improvements into upstream?
- https://github.com/YuZhouRen86/VxKex-NEXT
Thanks in advance.
Linked to:
- https://github.com/YuZhouRen86/VxKex-NEXT/issues/40
- https://github.com/i486/VxKex/issues/101
- https://github.com/i486/VxKex/issues/36
- https://github.com/i486/VxKex/issues/70
@Mikhail-M12: Yes, I have already spoken about it before, I have done a new ticket and it is linked to:
- https://github.com/i486/VxKex/issues/103
- https://github.com/dotexe1337/VxKex/issues/1
- https://github.com/i486/VxKex/issues/36#issuecomment-2571426455
- https://github.com/YuZhouRen86/VxKex-NEXT/issues/40
Here's few more with various improvements
https://github.com/Aqua-Vision/MgKex https://github.com/ArtP2000/VxKex/releases/tag/v1.1.2.1429 https://github.com/tahaghafuri/vxkex/releases https://github.com/OneForgottenMan/VxKex/commits/main/ https://github.com/ChronoMonochrome/VxKex/commits/master/ https://github.com/NulAsh/VxKex/releases
It’s getting late here, so I need to get some sleep. Tomorrow, I’ll put together a proper thread about our current situation so we can discuss it and hear everyone’s thoughts.
That said, I’d personally love to see everyone collaborate in one central place.
That said, I’d personally love to see everyone collaborate in one central place.
that would be great. right now there are like ten different forks all with different capabilities =p
That said, I’d personally love to see everyone collaborate in one central place.
that would be great. right now there are like ten different forks all with different capabilities =p
I agree. It's awesome to see a lot of people helping keep Win7 going, but it's gotten real confusing!
One more:
- https://github.com/Chuyu-Team/YY-Thunks
- https://github.com/Chuyu-Team/YY-Thunks/releases
@i486: Why not to move the project here, there are @dotexe1337 and @win32ss into:
- https://github.com/kernel-extenders
Or it is needed to recover the @VxKex organization.
Maybe some code to add from?
- https://github.com/kernel-extenders/VxKex
- https://github.com/win32ss/VxKex
If everyone agrees to unify the projects, I will give @vxkex access to the person who takes over the supervision.
@tahaghafuri: It is for this your are in "cc" in this ticket:
- https://github.com/i486/VxKex/issues/104
Devs: @i486, @YuZhouRen86, @dotexe1337 and maybe @win32ss.
Linked to:
- https://github.com/i486/VxKex/issues/101
- https://github.com/i486/VxKex/issues/103
- https://github.com/i486/VxKex/issues/104
- Not mine: https://github.com/i486/VxKex/issues/36
- https://github.com/dotexe1337/VxKex/issues/1
- https://github.com/YuZhouRen86/VxKex-NEXT/issues/40
are those fork even safe for that or risky? because since i use common sense, and you dont know if these are malware or safe. Since i saw changes or that, which the vxiuu version didnt have that, i would curious if they not have issues on that.
No offense, just a check if those are safe, because since some programs dont work with the original vesrion of vxkex.
No offense, just a check if those are safe, because since some programs dont work with the original vesrion of vxkex.
Learn C++, examine the source code and you will know if it safe. If it is, compile from source and use that.
No offense, just a check if those are safe, because since some programs dont work with the original vesrion of vxkex.
Learn C++, examine the source code and you will know if it safe. If it is, compile from source and use that.
VxKex is written by C, not C++
My advice to all of you is this: everyone must develop within the Vxkex-NEXT project. All the code from those scattered branches should be merged into the Vxkex-NEXT project. Stop creating all those messy, chaotic branches. I want this settled immediately—get it done now!
I am collecting in one version, so far 3 versions have been collected. @vxkex
tahaghafuri's vxkex/vxkex has been deleted. Here's an archive: https://web.archive.org/web/20250906092129/https://github.com/vxkex/vxkex/releases Note: it's was a merger of Vxkex-NEXT's older versions and not 1.1.3.1584, the newer version at the time, which led to having older issues from Vxkex-NEXT that got fixed later (vxkex/vxkex/issues/9), and the program couldn't be installed from the original VxKex's 1.1.2.1428 Version. vxkex/vxkex was never updated to fix the issues after the v1.1.6.0 alpha. Edit: KexSetup_Release.exe wasn't saved
