Nordic XP 32 bit OK
-
Nordic theater v2 works on XP 32 bits.
You cannot use the installer.
But you may change the extension of the source.dat file to be source.7z.
You vill discover it is a 7zip file containing the usual add on Nordic repertory, that you can decompress and install manually.By the way, I still use BMS 4.33 U2 cause the U3 version cannot play on my XP 32 bit (“memory error, address cannot be an instruction…”).
Nordic v2.1, Balkans 4.33 update 3.6, Kurile, Ostsee 3.28.88 theaters work perfectly despite a rather basic configuration : nvidia GTX 750 and Intel Celeron dual core 1620. -
By the way, I still use BMS 4.33 U2 cause the U3 version cannot play on my XP 32 bit (“memory error, address cannot be an instruction…”).
Nordic, Balkans, Kurile, Ostsee theaters work perfectly despite a rather basic configuration : nvidia GTX 750 and Intel Celeron dual core 1620.BMS 4.33.3 dropped XP support,it just doesn’t work. However I’ve had lots of stability issues running the 4.33.2 Rolling Fire campaign under XP 32-bit where XP just get running out of RAM and BMS 4.33.2 would just crash at very random times. BMS 4.32.7 doesn’t have those issues so I’m running that under XP.
-
Thank you for experience sharing.
I suspect some theaters to be no longer XP 32 compatible.
Panama is OK, though not in the same category as Nordic. -
I believe it’s less to do with XP than with 32-bit in general, or rather the ~3.5 GB addressable memory limit of 32-bit operating systems.
They appear to have upped the campaign memory consumption under BMS 4.33.x so when things get really busy early on in the Korea campaign, BMS appears to just run out of memory and crashes. At least that’s what I experienced. -
This sounds interesting, Tazz… almost sure that mine is a noob question, who knows if could this same issue happens with XP 64 bit version too?
As more than sometimes OSs have major hidden bugs in them…With best regards,
-
I have no idea, as my FLCS and TQS won’t work under XP 64 bit
-
I must confess I use a simple T.16000 joystick and my experience as a (sim) fighter pilot goes back to F19 stealth fighter, F15-II, F15-III, F14 Fleet Defender…
I play BMS as a solo tourist viewer in auto mode, nevertheless TEs and campains as well…
You certainly are right in suspecting memory management problems. Other possible causes are bugs, calls to missing apis in XP-32 bit (later implemented in more recent Windows versions) and also configuration dependent overflows that can be avoided by adjusting BMS parameters (for example, number of particles in explosions, there is documentation somewhere…).
My experience with BMS 4.33 U2 on XP-32 bit : some theaters cause an immediate crash or after very few seconds.
On the contrary, “compatible” theaters may run indefinitely. Also : virtual memory must stay system managed by default to allow automatic extension (only limited by disk free space). Also : you may install the AHCI SATA driver from your mainboard cdrom (you have to manually modify registry entries beforehand to do so successfully) to accelerate memory/disk transfers - yes this is possible with XP-32 bit and you get a superfast system.
