Yea, I can confirm the MD5 hash of the PRISM.zip that I installed PRISM from a few months ago does not match what you show above - Data.zip hash is correct on my system, though.
File hash from PRISM.zip downloaded on 5/12/2020 from SA DL's:
AVCS4 - (hashed file via MD5) "D:\VG Files\PRISM.zip" = 2AE1DBC99990DAE85864BFF550FAE0C0
File hash from Data.zip downloaded on 7/19/2020 per Private Message re SA DL's:
AVCS4 - (hashed file via MD5) "D:\VG Files\VG PRISM\Data.zip" = 6A5122F9101B5B114A68D682255E6E01
just downloaded and checked PRISM.zip from SA DL's:
AVCS4 - (hashed file via MD5) "D:\VG Files\NEW PRISM\PRISM.zip" = DF3F3E87C7518E2D52940F2D1D13C9FC
Found the problem there, of course.... It seems there is a new file that was not present before, clearly I missed an update - my bad. Re-download the PRISM.zip from SA files, delete everything in the local PRISM folder (except Data.zip) and re-extract from new PRISM.zip. Password is remembered and everything, and
was able to login without issues...
Problem solved - thought we merely got the note with last Update to install new Data.zip, and that is all... but I've been busy with my AVCS4 voice control project, when I read this line,
Updated PRISM client .. Data package was also updated.
I think I might have come off it thinking I just needed a new Data package, and that's on me. Sorry for taking up your time.
I blame m823us
He should have caught my mistake and downloaded the new PRISM Client as well as Data.zip, thanks a lot, mate! (j/k lol)
