Skip to content
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 for NT 5.1 #8

Open
andika207 opened this issue May 28, 2023 · 10 comments
Open

support for NT 5.1 #8

andika207 opened this issue May 28, 2023 · 10 comments
Labels
wontfix This will not be worked on

Comments

@andika207
Copy link

this utility doesn't even work on WinXP.

@Endermanch
Copy link
Owner

What's the point of making it work on Windows XP if Windows XP is the product you're activating? It's 2023, nobody uses Windows XP at this point.

I mean, considering I am using pure WinAPI for the user interface and OpenSSL for the elliptic curve arithmetic (which can very likely be compiled for Windows XP), I guess it could be possible for the project to support Windows XP. I don't see a need for it, though, especially that you will not be able to run it on Windows XP without prior activation of the system.

@Endermanch Endermanch added the wontfix This will not be worked on label May 28, 2023
@Leandro2905
Copy link

Leandro2905 commented May 30, 2023

What's the point of making it work on Windows XP if Windows XP is the product you're activating?

That's the point, you NEED to make it work on the product since is the SAME product that you work to activate it.

It's 2023, nobody uses Windows XP at this point.

Nobody? Really? What about millions of people and the government of Armenia? They are nobody?

I don't want to offend you, i just point some of your discrepancies to your argument.

@scrutinizer80
Copy link

It should run on the target OS in order to provide a full offline 'turnkey' solution, simple & elegant. Why having depend on access to other devices?

@cleanremote
Copy link

What's the point of making it work on Windows XP if Windows XP is the product you're activating?

What kind of dumb logic is this... It's like making a Windows 10 activator and then not making it compatible with Windows 10. So what's the point of it?

It's 2023, nobody uses Windows XP at this point.

Wrong!

you will not be able to run it on Windows XP without prior activation of the system.

Wrong!

@andika207
Copy link
Author

@Leandro2905 @scrutinizer80 @cleanremote
THANKS, you guys have already closed his mouth for me.
regarding the ''nobody uses XP in 2023'' remark I just get to ignore and laught

@pottzman
Copy link

pottzman commented Jun 4, 2023

What's the point of making it work on Windows XP if Windows XP is the product you're activating? It's 2023, nobody uses Windows XP at this point.

I mean, considering I am using pure WinAPI for the user interface and OpenSSL for the elliptic curve arithmetic (which can very likely be compiled for Windows XP), I guess it could be possible for the project to support Windows XP. I don't see a need for it, though, especially that you will not be able to run it on Windows XP without prior activation of the system.

Considering that the activator has the ability to generate an Installation ID and then store the Confirmation ID to the system then the ability to run on Windows XP should really be a priority otherwise you should really remove the buttons/ability to do it....as it serves no purpose anymore.

@techguy16
Copy link

@andika207 are you using the correct version of XP? This keygen is for XP VLK only.

@TrialMedusa64
Copy link

VLK=Volume License Key

@nroach44
Copy link

It's 2023, nobody uses Windows XP at this point.

Nobody? Really? What about millions of people and the government of Armenia? They are nobody?

Why is a Government needing a keygen for software that hasn't been support for NINE YEARS?

@Yarpopcat08
Copy link

What kind of dumb logic is this... It's like making a Windows 10 activator and then not making it compatible with Windows 10. So what's the point of it?

I believe, an activator and a keygen are a bit different.
Taking in mind, that this keygen is developed for research purposes, and never meant to be used in real "production" environment by anyone it doesn't really make that much sense to make it work on NT 5.1... But if You are aching to make it work on holy Windows XPюша, then compile it for NT 5 Yourself. What's the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

10 participants