/ Register

Fallout 1 not working on Windows 7 x64 (final build 7600)

Discussion in 'Fallout General Modding' started by 5h00n4y, Aug 19, 2009.

Page 1 of 2
  1. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    Hi guys, using Windows 7 Ultimate 64-bit Final 7600 build here, I can't get Fallout to work :(

    I've "installed" the game manually by copying the files and creating the "FALLOUT.CFG" file in the Fallout directory on my partition, with the help of the description found here on NMA:
    Then I copied the files over with the official 1.1 patch, the unofficial 1.2 & 1.3.5 patches, the Restoration Mod and finally patched the exe with the resolution patch.

    Whatever I do, a "Memory Error" window pops up, claiming:
    with only a [OK] button there to press.
    When I click the [OK] button with the "Run as admin" and "XP SP3" compatibility settings chosen, it goes black for a second and returns to Win without other messages, doesn't even want to report this to M$ as a bug or something...
    But, when I use the "normal" settings (without turning those compatibility options on) and press the [OK] button, it goes black and stays that way, and there's no way to get back to win without restarting the PC.

    BTW, the "f1_res_error.log" in my Fallout folder says:
    I know I'm asking for trouble trying such an old game on modern OS, but perhaps I could help to fix it on W7 if anyone would care? Please? ;)
    BTW: I've also tried the game at various "levels of patching", first without any patches it didn't even try to run, then with the 1.1 patch up to the mod - they all give me the same memory mismatch error and go black, so I'm not saying this is the latest mods fault...
     
    5h00n4y, Aug 19, 2009
    #1
  2. BR4ZIL

    BR4ZIL Still Mildly Glowing

    220
    Feb 22, 2008
    hmm, why use manual install? that probably why the game doesnt work, use the normal install on the CD, and try to set compatibility to win 98 or 95, i run XP over here and it only works if i put compatibility with win98

    BTW: FALLOUT IS NOT A OLD GAME
     
    BR4ZIL, Aug 19, 2009
    #2
  3. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    Because I can't run the installer on 64-bit W7.
    Installing manually worked for me in XP, worked for me with Vista... and I didn't even had to set no compatibility mode with the last patches, it just hangs now on W7 :(

    Haha, I didn't mean nothing offensive, I was just comparing it to the release year of W7 ;)
    Hey, I'm an Amiga freak (anyone here from EAB? ;)), I love old games from the 80's you don't have to remind me about the quality of those games mate ;)
     
    5h00n4y, Aug 19, 2009
    #3
  4. BR4ZIL

    BR4ZIL Still Mildly Glowing

    220
    Feb 22, 2008
    oh, i never used a 64-bit OS myself so i dont know much about it, sry :?

    sry if i was rude, i forgot to add a Emoticon to the end of the sentence :P
     
    BR4ZIL, Aug 19, 2009
    #4
  5. TJ07

    TJ07 First time out of the vault

    57
    Apr 25, 2006
    well 13 years is pretty old actually :P, if it was 1996 or was it 97
     
    TJ07, Aug 19, 2009
    #5
  6. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    IIRC, last time I tried to install it the normal way it complained that it's a 16bit app and it can't be run here...
    Fallout2 installer works just fine (IIRC), but I've got all the needed files copied from my original CD onto my HD, and I'm manually installing since years.
    The problem is I didn't play FO1 for a few years (checked it around the time Viśta x64 came out), only FO2 - which works great from XP, Viśta x64 and now on W7 x64 btw.

    No worries... ;)

    So, maybe someone from the TeamX group could help?
     
    5h00n4y, Aug 20, 2009
    #6
  7. Wasteland Ghost

    Wasteland Ghost Still Mildly Glowing

    296
    Sep 20, 2005
    Wow! Never heard about TeamX 1.2 engine version.

    Windows 7 haven't even been released yet, and you already have a problems? ;)

    First. TeamX has nothing to do with the lack of backward compatibility in M$ products. Second. Never install anything, but the game itself, if you experiencing problems and trying to make it work. As I understand, f1_res_error.log is something from the resolution patch? Don't install this patch. Don't install anything, except original Fallout game. Try to run it. Everything OK? Then try to install ONE patch. And so on.
     
    Wasteland Ghost, Aug 21, 2009
    #7
  8. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    Thanks for visiting me thread ;)

    That's what the logs say, I didn't write that... ;)

    Actually, this final version is released for us testers since a couple of weeks now, and that version is the one that is going to released to the public (build 7600). ;)

    I understand that, I don't blame you for anything, but the probability of fixing it is somehow stronger with you guys then mighty M$... ;)
    Could be also NVidia drivers problems, I had some minor glitches in other much "younger" games, but, like M$ - NV doesn't care about old soft... :(

    I did so. Dead.

    Yup.

    Nope, it fails from the beginning, and since patches are usually there to fix things I've assumed they will, and installed them in the correct order AND checked after each and every change. Errors, errors, errors... :(



    PS: Same goes for FO2 - doesn't even start with the original (unpatched) version, but works just great with the final patches + RP mod + highres patch ;)
     
    5h00n4y, Aug 21, 2009
    #8
  9. hakimio

    hakimio It Wandered In From the Wastes

    165
    Feb 27, 2009
    Does the installer and/or the game work in 32bit win7? What are the error messages you get when running the installer? Why not use 32bit version as speed improvement isn't really noticable, it uses less memory and usually there are more/better drivers for 32bit version?
     
    hakimio, Aug 21, 2009
    #9
  10. rogerg2

    rogerg2 First time out of the vault

    31
    Oct 24, 2007
    if I am not mistaken, you cannot run 16-bit applications on a 64-bit Operating System. And I believe that F1 & 2, are both 16-bit software games.
     
    rogerg2, Aug 21, 2009
    #10
  11. Stg Granite

    Stg Granite Look, Ma! Two Heads!

    365
    May 8, 2007
    Exactly.
    F1 only. F2's engine is 32 bit.
     
    Stg Granite, Aug 21, 2009
    #11
  12. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    No idea about the installer, I know the FO1 game works fine in x64 Vista.
    That it's a 16bit app and can't be run in 64bit environment.
    This isn't exactly a thread about "why is this version better then other" so let's just say... because I want to :)
    You are mistaken. ;)
    Only the installer is 16bit, the games both worked fine on x64 Vista and FO2 works on this exact x64 W7 setup.
     
    5h00n4y, Aug 21, 2009
    #12
  13. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    So how the heck did I ran it on Vista 64-bit? :shock:
     
    5h00n4y, Aug 21, 2009
    #13
  14. Stg Granite

    Stg Granite Look, Ma! Two Heads!

    365
    May 8, 2007
    Are you absolutely sure? Weren't you high on something? ;) If that wasn't the case, then, I don't know.

    64 bit OSes can't run 16 bit applications. They don't have compatibility modes for that yet.
     
    Stg Granite, Aug 21, 2009
    #14
  15. hakimio

    hakimio It Wandered In From the Wastes

    165
    Feb 27, 2009
    @5h00n4y
    You must be mistaken.
    MS says 64bit OS doesn't run 16bit apps:
    List of limitations in 64bit windows:
    Code:
    No 16-Bit Code
* No 16-bit code can run, except for recognized InstallShield and Acme installers (these are hard-coded in Wow64 to allow them to work).
* 16-bit Setup bootstraps are not supported.
* 16-bit MS-DOS and Microsoft Windows 3.x utilities will not start. If you attempt to start such a program, you receive a "Program.exe is not a valid Win32 application" error message.
     
    hakimio, Aug 21, 2009
    #15
  16. Timeslip

    Timeslip Water Chip? Been There, Done That
     Modder

    921
    Aug 15, 2007
    There were two version of fallout 1, one for windows and one for dos. The windows one is 32 bit, the other... um, actually I'm not sure. I know sfall doesn't work with it, but it wouldn't work anyway regardless of bittage because it's not directx based. Still, it's probably 16.
     
    Timeslip, Aug 21, 2009
    #16
  17. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    I'm quite sure, it was somewhere around the month Vista came out that I found this site and re-checked both games without any problems.
    You know, with the pre-SP1 Vista you couldn't play more requiring games on it, ROTFL.

    Of course, and they will never have, who cares ;)

    @Timeslip: yup, I believe that's the case, definitely remember reading somewhere about a DOS version of FO1, but I never played it.
     
    5h00n4y, Aug 21, 2009
    #17
  18. 5h00n4y

    5h00n4y First time out of the vault

    36
    Jun 22, 2008
    Exactly, never said I used any 16-bit apps ;)

    Guys, with all due respect, I am aware of the pros and cons of a 64-bit system and I want to use one ;)

    Sure, I could pretty much just install VMware and run FO1 on it on WXP, but maybe, just maybe there is a chance it could be fixed so that I could play it "natively"?
    You know, for the future generations of W7 users :)
     
    5h00n4y, Aug 21, 2009
    #18
  19. Stg Granite

    Stg Granite Look, Ma! Two Heads!

    365
    May 8, 2007
    I don't think you would be able to use VMware to run F1, since F1's win version uses DirectX, which isn't available on VMware. Perhaps I'm wrong?
     
    Stg Granite, Aug 21, 2009
    #19
  20. Timeslip

    Timeslip Water Chip? Been There, Done That
     Modder

    921
    Aug 15, 2007
    Indeed you are. It doesn't try doing anything 3d, and direct draw works perfectly well without hardware support. (So does d3d for that matter, if you install the reference rasterizer and don't mind playing at speeds measured in frames per hour instead of frames per second.)
     
    Timeslip, Aug 21, 2009
    #20
Page 1 of 2