[Mongoose]

Not that I want to dump more work on anyone, but we do have multiple people in the community that are native German speakers, as well as French and Polish off the top of my head.  If they aren't already floating around out there, having multiple translations of the installation instructions could be a huge plus.

[Goober5000]

The new version of the installer will have support for translations.

[Yarn]

Goober, do you plan to have your installer automatically update FS2 installations to 1.20? If so, how will that be done?

[Goober5000]

No, that I don't -- mostly because I don't know what is involved, aside from a new root_fs2.vp.  (I would assume most of the new installations would be from GOG anyway, which is 1.2.)

[jr2]

How about at least a version check, that way if it's not 1.20, an error message will be displayed?

[Goober5000]

It's the same question: how do you check that the version is 1.2?  (Though I suppose you could use an MD5 for that.)

[Yarn]

I'm pretty sure that the EXEs (all three) and the readme are also changed.

In order for us to be sure, someone will have to:

• Perform a full installation of the original English disc release
• Get an MD5 checksum of every file in the root FS2 folder
• Install the 1.20 patch (using the official installer, not Karajorma's manual patch)
• Perform step 2 again with the patched installation

Those two hash lists will tell us which files are added or changed in the 1.20 patching process. Perhaps then these files (which must come from a patched disc installation, not the Sim of the Year or GOG.com version) could be packaged and uploaded somewhere. The installer could then use that for patching.

(I'd do this myself, but I only have the Sim of the Year and GOG.com versions, both of which are already patched to 1.20.)

It's the same question: how do you check that the version is 1.2?  (Though I suppose you could use an MD5 for that.)

Yeah, I'd check the MD5 of root_fs2.vp. If it's the same as the 1.00 root_fs2.vp, then apply the patch; otherwise, don't patch.

[niffiwan]

I have the original English disks, I'll see if I can get the MD5's in the next week (or so).

[jr2]

Can you use a sandboxing program such as Sandboxie and check to see if the patch changes the Windows registry at all?

[niffiwan]

And the md5sum's are...

Code: (original) [Select]

e91f041517c8d76466740fbbe7f965f2  FRED2.exe
910a96bfe91741829eb078fffc6892c7  FreeSpace2.exe
f054c7bd049036e60e974051f2727fc2  FS2.exe
25fdbf1c38a00af40b82fb6fc0ee703f  FS2uninst.dll
dd5fc0aa89ebd424ce15d3d12116abd9  patchw32.dll
3501407628bfb9040aab7ffa0e43aac4  pxo.url
e882f1e37af00511980fa8baa78e15a4  Readme.txt
42bc56a410373112dfddc7985f66524a  Root_fs2.vp
0d662decc0b443ccb8e8aa2e3a0887ce  smarty_fs2.vp
2a47bdf14860071cf0196d92e9ee7c2f  sparky_fs2.vp
97661124cdc47c0a2f0678982b8cbd91  sparky_hi_fs2.vp
f325b9a93bf3178717b3f72317a0a421  squadwar.url
e88f0e0011b3e525a5ad625933684c03  stu_fs2.vp
8ca7330cfe63329b41868efc2e40e048  tango1_fs2.vp
6fb6e9a36248980540155a9777c51c47  tango2_fs2.vp
d42c20b6ffb4782e431899c211ae55c4  tango3_fs2.vp
5a8bcb28ec692a3a2c438268105af364  Uninst.isu
911381d29735fde695647d7388343dd1  UpdateLauncher.exe
d1f3c39d4fe1bbd56b7b06fe66eef4a6  warble_fs2.vp


Code: (1.2 patch) [Select]

9b8a3dfeb586de9584056f9e8fa28bb5  Fred2.exe
091f3f06f596a48ba4e3c42d05ec379f  freespace2.exe
2c8133768ebd99faba5c00dd03ebf9ea  FS2.exe
25fdbf1c38a00af40b82fb6fc0ee703f  FS2uninst.dll
dd5fc0aa89ebd424ce15d3d12116abd9  patchw32.dll
3501407628bfb9040aab7ffa0e43aac4  pxo.url
b4df1711c324516e497ce90b66f45de9  readme.txt
0d9fd69acfe8b29d616377b057d2fc04  root_fs2.vp
0d662decc0b443ccb8e8aa2e3a0887ce  smarty_fs2.vp
2a47bdf14860071cf0196d92e9ee7c2f  sparky_fs2.vp
97661124cdc47c0a2f0678982b8cbd91  sparky_hi_fs2.vp
f325b9a93bf3178717b3f72317a0a421  squadwar.url
e88f0e0011b3e525a5ad625933684c03  stu_fs2.vp
8ca7330cfe63329b41868efc2e40e048  tango1_fs2.vp
6fb6e9a36248980540155a9777c51c47  tango2_fs2.vp
d42c20b6ffb4782e431899c211ae55c4  tango3_fs2.vp
5a8bcb28ec692a3a2c438268105af364  Uninst.isu
babe53dc03c83067a3336f0c888c4ac2  UpdateLauncher.exe
d1f3c39d4fe1bbd56b7b06fe66eef4a6  warble_fs2.vp

And a diff to show which files have changed:

Code: [Select]

1,3c1,3
< e91f041517c8d76466740fbbe7f965f2  FRED2.exe
< 910a96bfe91741829eb078fffc6892c7  FreeSpace2.exe
< f054c7bd049036e60e974051f2727fc2  FS2.exe
---
> 9b8a3dfeb586de9584056f9e8fa28bb5  Fred2.exe
> 091f3f06f596a48ba4e3c42d05ec379f  freespace2.exe
> 2c8133768ebd99faba5c00dd03ebf9ea  FS2.exe
7,8c7,8
< e882f1e37af00511980fa8baa78e15a4  Readme.txt
< 42bc56a410373112dfddc7985f66524a  Root_fs2.vp
---
> b4df1711c324516e497ce90b66f45de9  readme.txt
> 0d9fd69acfe8b29d616377b057d2fc04  root_fs2.vp
18c18
< 911381d29735fde695647d7388343dd1  UpdateLauncher.exe
---
> babe53dc03c83067a3336f0c888c4ac2  UpdateLauncher.exe

Note: this was all done on Linux under WINE, I don't believe that should make any difference.  Also, it's interesting to note the capitalisation of root_fs2.vp, it seems the patched version is all lowercase while the unpatched version isn't.  That may be a super-simple visual check of whether the patch is installed or not (since IIRC Windows is case-insensitive, but also case-preserving.)

(as for checking the registry, I think I could grab a diff of the WINE registry files, but I'd have to redo the install for that since I didn't find said files until after I'd patched)

[AdmiralRalwood]

Note: this was all done on Linux under WINE, I don't believe that should make any difference.  Also, it's interesting to note the capitalisation of root_fs2.vp, it seems the patched version is all lowercase while the unpatched version isn't.  That may be a super-simple visual check of whether the patch is installed or not (since IIRC Windows is case-insensitive, but also case-preserving.)

In my experience, replacing a capitalized file with a lowercase file with the same name preserves the case of the original file; the fact that it changed case sounds like a peculiarity of WINE, because I just checked my (admittedly GOG.com-installed) folder and the filename is "Root_fs2.vp".

[Yarn]

Yeah, the lowercase r is not a good way to determine whether the patch is installed. It's also important to be mindful of international versions of the game; we don't want to inadvertently change such a version partially into an English version.

I still believe the best method of doing this is to check the MD5 of root_fs2.vp. If it's 42bc56a410373112dfddc7985f66524a, then apply the patch; otherwise, don't. If it's different from the two MD5s shown above, then still don't apply the patch; it's most likely an international version that, if it's not already at version 1.20, will need its own patch.

Niffiwan, would it be OK with you to upload those six files somewhere, both for Goober and as a manual patch? (Remember, Karajorma's patch has cracked EXEs and is missing readme.txt and UpdateLauncher.exe.)

[AdmiralRalwood]

I still believe the best method of doing this is to check the MD5 of root_fs2.vp. If it's 0d9fd69acfe8b29d616377b057d2fc04, then apply the patch; otherwise, don't.

I think you mean 42bc56a410373112dfddc7985f66524a; the other md5 is the 1.2 version.

[Yarn]

I think you mean 42bc56a410373112dfddc7985f66524a; the other md5 is the 1.2 version.

You're absolutely correct; thanks for pointing that out. My post is now fixed.

[niffiwan]

Niffiwan, would it be OK with you to upload those six files somewhere, both for Goober and as a manual patch? (Remember, Karajorma's patch has cracked EXEs and is missing readme.txt and UpdateLauncher.exe.)

Sure, I'll see if I can post that tonight.

edit: and here's a link to the files: http://www.mediafire.com/download/1ko2f3n6v64lko9/fs21x-12.7z

[Yarn]

Could you upload the manual patch to FSMods?

[niffiwan]

Uploaded to FSMods, I guess it's waiting on approval from achtung.

(And seriously, why does the 1st page of google results for "fsmods" only return Farming Simulator Mods )

[jr2]

So, nothing needed to be changed in the registry, correct?

[niffiwan]

Yeah, the installer is just a winzip self-extracting exe, I don't believe there's a way for that to install anything to the registry.

[Yarn]

If you open the installer in 7-zip, you will see the files PATCH.RTP, patchw32.dll, and setup.exe. So, it's definitely possible for the patch to change something in the registry.