Nov 04, 2014, 08:23 am
Hello! So I've been having this problem for months now, probably about a year, with every CODEX release. It must be something in the way they make their "setup.exe", regardless of the game. Because invariably it gets me the same error:
[Error]
Runtime Error (at -1:0):
Cannot Import STRINGCHANGE.
The error is displayed immediately upon running the setup.exe. If you want a concrete example - just take any game released by CODEX in the last year, it doesn't matter. Alien Isolation, Shadow of Mordor, Call of Duty: Advanced Warfare, anything - works exactly the same way.
So far I've not had such issue with the installation of any other software or releases of other groups.
Now, the important detail - my main OS installation is weird. It's a customized Win7 that you can easily find online, called:
Windows 7 Gamer Edition X64 By UNDEADCROWS
It has had some issues with updating to latest service packs, so that certainly has to do with the problem. Moreover, my current solution to the problem is that I just have another "blank" Windows 7 installation - and I use it for installing CODEX games, it works there. Once installed, I run them from my main OS, no problem. So it's only a problem with the installer. It seems to use some advanced "STRINGCHANGE" function that only runs on latest service packs of Windows 7, or something like that.
I know this doesn't sound like a very important issue, especially since it's clearly related to a very specific customized (and probably buggy) version of Windows 7. That's why I've just been silent about it for the past year. But after searching through the net, I find other people posting about the same problem too. The "Gamer Edition" is popular enough, even if it's a niche OS variant.
And most of all, I believe this problem must have a very simple fix. Like, calling a simpler more basic function for some string operation, instead of a latest version of it that apparently is not supported by such OS variant.
I want to add that I've routinely tried all kinds of things that usually people advise doing: various Compatibility settings, Run as admin, turning off antivirus/firewalls etc. That's not it, it's just a call to some string function that's not supported by this version of Windows 7.
In any case, big thank you to CODEX and all other hardworking groups in the scene. If by chance this message reaches them and they change the building procedure for their "setup.exe" for game installations in the future, that would be great, and I'm sure me and the other users of Gamer Edition Win7 would appreciate it very much.
[Error]
Runtime Error (at -1:0):
Cannot Import STRINGCHANGE.
The error is displayed immediately upon running the setup.exe. If you want a concrete example - just take any game released by CODEX in the last year, it doesn't matter. Alien Isolation, Shadow of Mordor, Call of Duty: Advanced Warfare, anything - works exactly the same way.
So far I've not had such issue with the installation of any other software or releases of other groups.
Now, the important detail - my main OS installation is weird. It's a customized Win7 that you can easily find online, called:
Windows 7 Gamer Edition X64 By UNDEADCROWS
It has had some issues with updating to latest service packs, so that certainly has to do with the problem. Moreover, my current solution to the problem is that I just have another "blank" Windows 7 installation - and I use it for installing CODEX games, it works there. Once installed, I run them from my main OS, no problem. So it's only a problem with the installer. It seems to use some advanced "STRINGCHANGE" function that only runs on latest service packs of Windows 7, or something like that.
I know this doesn't sound like a very important issue, especially since it's clearly related to a very specific customized (and probably buggy) version of Windows 7. That's why I've just been silent about it for the past year. But after searching through the net, I find other people posting about the same problem too. The "Gamer Edition" is popular enough, even if it's a niche OS variant.
And most of all, I believe this problem must have a very simple fix. Like, calling a simpler more basic function for some string operation, instead of a latest version of it that apparently is not supported by such OS variant.
I want to add that I've routinely tried all kinds of things that usually people advise doing: various Compatibility settings, Run as admin, turning off antivirus/firewalls etc. That's not it, it's just a call to some string function that's not supported by this version of Windows 7.
In any case, big thank you to CODEX and all other hardworking groups in the scene. If by chance this message reaches them and they change the building procedure for their "setup.exe" for game installations in the future, that would be great, and I'm sure me and the other users of Gamer Edition Win7 would appreciate it very much.