Which Windows version are you using?
-
I’m using windows 7 x64.
Nikos. -
Microsoft never got the memo that I was running on an actual computer and not a smart phone or a tablet so Win 8 was never in the cards for me. Win 7 all the way.
-
Win 7 x64
Sword
-
win7 and xp dual install. BMS run better on win7.
I just got a 8.1 laptop. Fastest bootup/shut down time in windows history. It runs office98. I think the smart phone UI applies to touch screens and pads. As for the full screen start menu and apps, I didn’t use the start menu in previous win. I plan to load 8.1 on my desktop.
-
Hi gents,
I’d like to get an overview about the Windows versions which you gents are using to run BMS.
For those still running XP or Vista, please choose whether upgrading to Win7 or higher is an option for you or not.
Thanks!
Dunc.Hey Dunc,
It sounds like you need to “self ban” yourself again being “terribly tired” and get some sleep! :razz:
See my sig for windows version my friend.
-
Win 8.1 64bit. I have no problems running BMS so far.
-
Windows 7 all the way baby….I think it a great OS.
-
Windows 8.1 - 64-bit
-
Windows 7 Home Premium 64bit
-
Windows 7 Home Premium 64bit for BMS
(And I will never touch 8, or higher.)Anything else: GNU/Linux Linux Mint 17-KDE-64 (atm).
-
Windows 8/64 Bit maxed out, runs awesome and smooth.
-
Win 7 Home Premium 32 bits
-
Win 7 HP 64bit for gaming.
For all the other things Fedora/Xubuntu/Linux Mint -
Win 7 x64 Ultimate, runs very smooth
-
Windows XP SP3
-
Dunc, why ask? Related to release builds? Note subsystem 5.01 can be forced with any VS version (with editbin or otherwise), as well as static CRT usage so XP non-broken.
-
Win 7 Home Premium 32 Bit
-
Note subsystem 5.01 can be forced with any VS version (with editbin or otherwise), as well as static CRT usage so XP non-broken.
…only if you choose NOT to make use of new APIs which are available only from Vista and up. Let alone migrating away from DX9… See every link which has a blue background in the following table:
http://linuxtesting.org/compatibility/Windows_SDK_5.0_to_Windows_SDK_6.0/x86/abi_compat_report.htmlWe WANT to make use of some of the new stuff eventually. Hence we WILL break the compatibility with XP eventually. It’s not a question of “if”, only a question of “when”.
Oh, and to calm you down: it’s not relevant for 4.33!
-
Saw most. Other by names can’t be even remotely relevant: ODBC, DHCP(v6), codec api, hardware video decoding.
As for those that could be considered possibly relevant for the project - why consider Windows-only APIs?
While e.g. SSL a pain to begin with, there’s more gain for the programmer adding new feature to be familiar with a portable API, to avoid MSFT poorly designed APIs, bug-for-bug compatibility till hell freezes over, and other reasons that you know of.There are valid reasons for fringe workloads to use, say, overlapped IO and not methods typical across whole desktop ecosystem. Are there any in this case though?
Note implication of DX9 -> DX10+ migration being at least not discounted completely in the future Make sense. Linux guerrillas deep in the country now have a partly-working DX10/11 impl though, but i digress.
Good for all, except them poor sods who have to implement, then QA 4.33 and whatever comes next. That’s a curse really, never get to fly any, jump in pit, takeoff, then see some bug or a glitch. Abort the flight.
-
The world must be easy to understand if you can only see black or white…