Yup, exactly those registry files. Didn't realize I had to go to Wow6432Node - do you think it could be a part of the problem? The contents of the installscript.vdf doesn't refer to Wow6432Node, it simply omits it:
Code:
"InstallScript"{
"Registry"
{
"HKEY_LOCAL_MACHINE\\SOFTWARE\\SEGA\\Medieval II Total War"
{
"string"
{
"Language" "english"
"DistributionSource" "steam"
"Version" "1.03.000"
"AppPath" "%INSTALLDIR%"
}
}
"HKEY_LOCAL_MACHINE\\SOFTWARE\\SEGA\\Medieval II Total War\\1.00.0000"
{
}
"HKEY_LOCAL_MACHINE\\SOFTWARE\\SEGA\\Medieval II Total War\\1.02.000"
{
}
"HKEY_LOCAL_MACHINE\\SOFTWARE\\SEGA\\Medieval II Total War\\1.02.001"
{
}
"HKEY_LOCAL_MACHINE\\SOFTWARE\\SEGA\\Medieval II Total War\\1.03.000"
{
}
}
"Run Process"
{
"DXSetup"
{
"HasRunKey" "HKEY_CURRENT_USER\\Software\\Valve\\Steam\\Apps\\4700"
"process 1" "%INSTALLDIR%\\dxsetup\\DXSETUP.exe"
"NoCleanUp" "1"
}
}
}
Do you think changing that could make it work? The references the right path to the DXSetup.exe file, but not to whatever is in those registry keys? Maybe that's why it changes the key "DXSetup" in "HKEY_CURRENT_USER\\Software\\Valve\\Steam\\Apps\\4700" to 1, but not the "Installed" key?
And I have tried both installing in the default Steam directory (in Program Files (x86)) and on my E drive. I'm currently installing Kingdoms as well as the base game on my E drive, though, maybe it'll work.
And I'd have to disable UAC and take ownership of the C drive before installing for it to make a difference? And why does it make a difference?