Show messages:
1-6
7-26
27-46
47-51
From: Michael Gibson
Hi Spartan,
re:
> What I'm asking is how the programming handles that bit. Is there a specific file that contains the expiration date and relevant code?
Yes, it's part of the code in the main program module file moi_lib.dll .
> And if that's the case, can the files be modified?
Yes, it's possible to do that, it's called "cracking":
https://en.wikipedia.org/wiki/Software_cracking
But usually it's done by people who are distributing pirated versions of the software.
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Gotcha.
Admittedly, I had entertained the idea of cracking - though:
A.) I'd put the kibosh on the idea after thinking it through, and:
B.) it woulda been for personal use anyway had I cracked it,
so there's that.
That said, my line of thinking often goes toward "can it be done" more than "should it be done" and "what are the repercussions thereof" - hence my asking in the first place.
From: SPARTAN-D421 (SIERRA-D421)
Further question: is there (at minimum) one more beta build after this, or is V5's public release the next release?
(also, will V5 be the same price as V4 when it releases?)
From: Michael Gibson
Hi Spartan,
re:
> Further question: is there (at minimum) one more beta build after this, or
> is V5's public release the next release?
There will be at least one more beta.
> (also, will V5 be the same price as V4 when it releases?)
Yes.
Thanks,
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Right. Thanks. Just wanted to be sure.
Show messages:
1-6
7-26
27-46
47-51
