Results 1 to 9 of 9

Thread: Cannot install any beta patch

  1. #1
    Corporal
    Join Date
    Jun 5 2009
    Location
    Frankfurt/Main, Germany
    Posts
    92

    Cannot install any beta patch

    Hey folks.

    Since it fixes several bugs and so forth, I wanted to install the latest beta patch.
    Unfortunately it wont let me.
    After the packed archive / installer is expanded, it tells me that my "Arma is not installed on this computer or the installation may be damaged".
    This problem occured also with any previous beta patches I tried.

    Now, I know the programm is installed and runs just fine when not trying to install this patch, thus cannot be damaged...

    Before trying a complete reinstall I though I hear you for some suggestions on this matter.
    So, any opinions?

    Thanks for your help

    Regards
    C2D E8500 @ 3,8 GHz // Noctua NH-U12P @ 2*NF-P12 // Asus Maximus II Formula
    8GB OCZ DDR2-9200 Platinum 5-6-6-16 // Zotac GeForce GTX 285 AMP! // Lian Li P50 Black
    Enermax Revolution 85+ 950w PSU // Amilo SL 3260w // X-Fi Xtreme Gamer - Fatal1ty Pro Series

    Win 7/64 from: 250 GB Samsung Sata HDD 5400rpm
    ArmA II from: 2* Seagate 7200.12 1 TB HDD in Raid 0

  2. #2
    What version of Arma 2 do you have? Boxed DVD, Steam, some direct DL site..?

    Also what version of Arma 2 do you have? Yes I know it's the same question, but this time I mean the version number. Isn't English fun? Are you running 1.03?

  3. #3
    Corporal
    Join Date
    Jun 5 2009
    Location
    Frankfurt/Main, Germany
    Posts
    92
    Author of the Thread
    Running 1.03, german version.

    Purchased from gamesplanet.com, downloaded and burned the images on cd/dvd, installed from cd/dvd.

  4. #4
    Hi, I purchased from gamesplanet.com too and have 1 x .exe and 4 x .bin files that i installed from HD + latest official patch ... beta patches working fine for me.

    MfG
    Asus P5Q // Intel Q9550 // 8GB RAM // XFX Nvidia GTS 250 1GB // WIN 7 RC 7100 64Bit // NVIDIA GF 190.62 WHQL

  5. #5
    Corporal
    Join Date
    Jun 5 2009
    Location
    Frankfurt/Main, Germany
    Posts
    92
    Author of the Thread
    Quote Originally Posted by technologickill View Post
    1 x .exe and 4 x .bin files that i installed from HD
    MfG
    Yea, that was it.. 4*bin and 1 exe. Burned them to dvd anyway because at that time i set up my system anew every 3 days and didnt want to have to d/l them every time.

    Now, it'd be nice to know what exactly is checked (which eventually leads the installer to the conclusion something is damaged) right after the extraction of the beta-package.

  6. #6
    Quote Originally Posted by -s!Gm4- View Post
    Now, it'd be nice to know what exactly is checked (which eventually leads the installer to the conclusion something is damaged) right after the extraction of the beta-package.
    I'm guessing it checks the registry for the Arma2 entries. You could check if those are there and look okay.

    Gigabyte Z97-HD3 Motherboard | Intel Core i5 4690k @ 4.5GHz | NVidia GTX 970
    16GB G-Skill Ripjaws 2133MHz RAM | Kingston HyperX SSD | be Quiet! 750W PSU

  7. #7
    Corporal
    Join Date
    Jun 5 2009
    Location
    Frankfurt/Main, Germany
    Posts
    92
    Author of the Thread
    Now, thanks MadDogX. Your suggestion hinted me to the solution, which makes me feel kind of dumb -_-

    My executable was named "arma2.exe" in the explorer.
    In the registry i found that it was named "arma2.exe.exe" in full.
    So messing around with the folder options few days ago - and after that, renaming my exe from crysis64 to arma2.exe - messed things up for me because the file's endings were now hidden (when they were not before...)

    Well, thanks again for your help (cant still believe that i just forgot to check on the names -_-)

    Topic may be closed! (or even better: deleted, to hide/cover my stupidity )

  8. #8
    Quote Originally Posted by -s!Gm4- View Post
    Now, thanks MadDogX.
    No problem.


    Quote Originally Posted by -s!Gm4- View Post
    My executable was named "arma2.exe" in the explorer.
    In the registry i found that it was named "arma2.exe.exe" in full.
    So messing around with the folder options few days ago - and after that, renaming my exe from crysis64 to arma2.exe - messed things up for me because the file's endings were now hidden (when they were not before...)
    Interesting. It's an easy enough mistake to make, which makes me wonder if other people have done the same thing and caused similar problems. Definitely worth remembering this as a possible cause the next time someone posts about being unable to install a patch.
    Last edited by MadDogX; Sep 3 2009 at 13:29.

  9. #9
    Thanks for this, I've got the same problem. Going to try what you said to do MadDogX and we'll see if it works.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •