Difference between revisions of "Forum:Transfering slashem save file from 32 bit linux to 64 bit"
Line 7: | Line 7: | ||
:I'm trying now, to transplant the 32 bit binary into the 64 bit machine. But weird permission stuff are needed that i'm not familiar with. If some one could help? :D --[[User:Quantum Immortal|Quantum Immortal]] ([[User talk:Quantum Immortal|talk]]) 21:16, 22 January 2017 (UTC) | :I'm trying now, to transplant the 32 bit binary into the 64 bit machine. But weird permission stuff are needed that i'm not familiar with. If some one could help? :D --[[User:Quantum Immortal|Quantum Immortal]] ([[User talk:Quantum Immortal|talk]]) 21:16, 22 January 2017 (UTC) | ||
− | There is a function in the code called uptodate that will read from the beginning of the save file to get the version info and will check the version number with a call to a function named check_version. Seems there are two numbers it checks: VERSION_COMPATIBILITY and VERSION_NUMBER. If the version number read from the file does not fall in that range, you'll get a "Version mismatch for file <whatever the filename is>." message. Maybe you could use a hex editor to fudge the version number in the save file, but who knows what unintended consequences that may have. Otherwise, you could try running a 32-bit virtual machine with your old 32-bit version of slashem and load the save that way. In practice, my two options seem a bit excessive for trying to rescue a slashem save. | + | There is a function in the code called uptodate that will read from the beginning of the save file to get the version info and will check the version number with a call to a function named check_version. Seems there are two numbers it checks: VERSION_COMPATIBILITY and VERSION_NUMBER. If the version number read from the file does not fall in that range, you'll get a "Version mismatch for file <whatever the filename is>." message. Maybe you could use a hex editor to fudge the version number in the save file, but who knows what unintended consequences that may have. Otherwise, you could try running a 32-bit virtual machine with your old 32-bit version of slashem and load the save that way. In practice, my two options seem a bit excessive for trying to rescue a slashem save. -- G7nation |
Revision as of 15:43, 25 January 2017
I played a bit on an old 32 computer. Naively i thought, that i could simply copy the save file over to my 64 bit computer. But it complained, that there was a "version mismatch" B[ . Any one know how to hack around this?--Quantum Immortal (talk) 18:54, 22 January 2017 (UTC)
- I'm trying now, to transplant the 32 bit binary into the 64 bit machine. But weird permission stuff are needed that i'm not familiar with. If some one could help? :D --Quantum Immortal (talk) 21:16, 22 January 2017 (UTC)
There is a function in the code called uptodate that will read from the beginning of the save file to get the version info and will check the version number with a call to a function named check_version. Seems there are two numbers it checks: VERSION_COMPATIBILITY and VERSION_NUMBER. If the version number read from the file does not fall in that range, you'll get a "Version mismatch for file <whatever the filename is>." message. Maybe you could use a hex editor to fudge the version number in the save file, but who knows what unintended consequences that may have. Otherwise, you could try running a 32-bit virtual machine with your old 32-bit version of slashem and load the save that way. In practice, my two options seem a bit excessive for trying to rescue a slashem save. -- G7nation