1. Detecting EU version
Gents and Ladies,
maybe this solution is too easy, but:
how about running a known CRC check against "ex.exe" etc,
and comparing that against known results?
Rob won't have to change a thing, and as a bonus if the executable
was tampered with, eg virus alteration, the CRC check would not check out?
I have copies of most PD and official binaries since v1.4, so I could
write this function if others are interested?
Yes, I know its not as good as a native function provided by Rob, but
that would ideally need retrofitting which is rather unlikely!
HTH
Alan
2. Re: Detecting EU version
Alan Oxley wrote:
>
> Gents and Ladies,
> maybe this solution is too easy, but:
>
> how about running a known CRC check against "ex.exe" etc,
> and comparing that against known results?
> Rob won't have to change a thing, and as a bonus if the executable
> was tampered with, eg virus alteration, the CRC check would not check out?
I'm surprised you didn't see the problems with this idea:
1. It prevents Rob from ever fixing even the smallest bug in the
"official" release - which, as we know, tends to be the *only* release
for a year or two. Very puzzling to get a message saying you need "2.5"
when you *are* running 2.5, but the library which is reporting the error
was written for the previous (un-bug-fixed) crc.
2. How do we ever guess the crc's of versions 2.6, 2.7, .... etc. so that
our programs can also run on those? Crystal balls don't work, you know.
Irv
3. Re: Detecting EU version
Alan Oxley wrote:
> Gents and Ladies,
> maybe this solution is too easy, but:
>
> how about running a known CRC check against "ex.exe" etc,
> and comparing that against known results?
> Rob won't have to change a thing, and as a bonus if the executable
> was tampered with, eg virus alteration, the CRC check would not check
out?
Good idea, and you can use the ready functions and constants
of the standard RDS sanity.ex program, if you want.
[snip]
Regards,
Igor Kachan
kinz at peterlink.ru
