Open andika207 opened 1 year ago
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.
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.
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?
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!
@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
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.
@andika207 are you using the correct version of XP? This keygen is for XP VLK only.
VLK=Volume License Key
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?
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?
this utility doesn't even work on WinXP.