VOGONS


64bit Vanilla Dosbox?

Topic actions

Reply 20 of 40, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Glad when one turns off autocorrection and has too big thumbs.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 21 of 40, by Tiger433

User metadata
Rank Member
Rank
Member

64bit Dosbox is good, but use of more cores is better, in Ubuntu x64 Dosbox is also 64bit?

W7 "retro" PC: ASUS P8H77-V, Intel i3 3240, 8 GB DDR3 1333, HD6850, 2 x 500 GB HDD
Retro 98SE PC: MSI MS-6511, AMD Athlon XP 2000+, 512 MB RAM, ATI Rage 128, 80GB HDD
My Youtube channel

Reply 22 of 40, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

By default, yes.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 23 of 40, by Serious Callers Only

User metadata
Rank Member
Rank
Member
Tiger433 wrote:

64bit Dosbox is good, but use of more cores is better, in Ubuntu x64 Dosbox is also 64bit?

You can install the 32 bits version by appending :i386 like so:
sudo apt-get install dosbox:i386

That risks uninstalling other things depending on what uses SDL though. So be careful to read the output and cancel if you can't live without something it's trying to install (that has no 32 bits version at least).

Reply 24 of 40, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
Tiger433 wrote:

64bit Dosbox is good, but use of more cores is better

Not necessarily. DOSBox is not multithreaded and there is no reason that can be expected to help speed-wise.

Reply 25 of 40, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie
Tertz wrote:
Darklord42 wrote:

Should we not prepare?

For Windows drop of 32 bit support will not happen during 5 next years, at least. More possible - 10 years.

When Windows drops 32bit support, it will upset a lot of people, especially gamers. Alright, so by then virtual machines might be easier and more convenient to install/set up/use, but Windows gamers won't be pleased that they can't just run Half-Life 1 and 2, the Unreal Tournament games, etc, 'native' in Windows.

Reply 26 of 40, by Darklord42

User metadata
Rank Newbie
Rank
Newbie

No one is worried about windows, they have a long history of backwards compatibility even to the detriment of security. Apple is the main worry, because they have no such qualms (no installed business userbase) so they can drop stuff at the drop of a hat, and there will be some grumbling while we all scramble to make things work again. As dominus said, they haven't done it yet. But I'll bet it's on the horizon.

Reply 27 of 40, by ovvldc

User metadata
Rank Newbie
Rank
Newbie
Kerr Avon wrote:

Alright, so by then virtual machines might be easier and more convenient to install/set up/use, but Windows gamers won't be pleased that they can't just run Half-Life 1 and 2, the Unreal Tournament games, etc, 'native' in Windows.

I could be wrong, but I thought Windows already uses a virtual machine to make XP software work. Windows on Windows is the unimaginative name IIRC. It is all theoretically transparent to the user, but lots of stuff going on under the hood 😉.

Reply 28 of 40, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
ovvldc wrote:

I could be wrong, but I thought Windows already uses a virtual machine to make XP software work. Windows on Windows is the unimaginative name IIRC.

I don't think anyone would call it a virtual machine.
https://en.wikipedia.org/wiki/WoW64

Reply 29 of 40, by Kerr Avon

User metadata
Rank Oldbie
Rank
Oldbie
ovvldc wrote:
Kerr Avon wrote:

Alright, so by then virtual machines might be easier and more convenient to install/set up/use, but Windows gamers won't be pleased that they can't just run Half-Life 1 and 2, the Unreal Tournament games, etc, 'native' in Windows.

I could be wrong, but I thought Windows already uses a virtual machine to make XP software work. Windows on Windows is the unimaginative name IIRC. It is all theoretically transparent to the user, but lots of stuff going on under the hood 😉.

Yes, but that's not an option for all gamers, as the Home Premium version of Windows 7, which is the one installed on many pre-built desktops, and laptops, doesn't support XP mode, as Microsoft want you to pay for a more advanced version of Windows 7, even though to most English speaking people, a product with the word 'premium' in it's name would tend to imply that that product was pretty much the top of the range anyway...

And also Microsoft say "Windows XP Mode was primarily designed to help businesses move from Windows XP to Windows 7. It isn't optimized for graphic-intensive programs such as 3D games, nor is it well suited for programs with hardware requirements such as TV tuners." (my emphasis), source: http://windows.microsoft.com/en-GB/windows7/i … de-in-windows-7

Not that this is too important, as there's a free virtual machine that Windows users, including Home Premium users, can install on their PCs, called VMWare. I've put it on a few PCs a while back to run older software and it worked great, but none of the programs used 3D hardware acceleration, and I don't know if VMWare supports this.

Reply 30 of 40, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

He was referring to WoW https://en.wikipedia.org/wiki/Windows_on_Windows.
The average user isn't aware of this since their software just works (usually).

Virtual PC was a good product back in the day until DOSBox far surpassed it for DOS games and Microsoft butchered it via XP Mode and then discontinued it for HyperV which is tied to the OS.

3D acceleration works in Vmware for Windows 2000 guests and above for D3D9. D3D10 support is in version 12.

How To Ask Questions The Smart Way
Make your games work offline

Reply 36 of 40, by Myg

User metadata
Rank Newbie
Rank
Newbie
DosFreak wrote:

That's for the OS.

Ah yes, that is correct.

There is a youtube video which describes MS's intentions to remove 32bit app support in the seeable future. The same way they removed 16bit app support previously. I cant seem to find the video again so lets just say its a rumour.

Reply 37 of 40, by Falcosoft

User metadata
Rank Oldbie
Rank
Oldbie

The same way they removed 16bit app support previously. I cant seem to find the video again so lets just say its a rumour.

It cannot be 'the same way' since 16-bit support is only missing from 64-bit OS versions (from the beginning). MS never removed 16-bit support form its 32-bit OS versions. So the 'same way' would be if 32 bit support will be missing from future 128-bit OS versions. It can happen 😀

Website, Facebook, Youtube
Falcosoft Soundfont Midi Player + Munt VSTi + BassMidi VSTi
VST Midi Driver Midi Mapper

Reply 38 of 40, by Myg

User metadata
Rank Newbie
Rank
Newbie

This is the closest I could come to any evidence of moves away from native win32 app compat for windows:

https://www.windowscentral.com/understanding- … -os-and-polaris

There are alot of breadcrumbs about the movement of supplanting native with another system or/and locking it into Windows Store apps or some other system.

It shows the movement towards the direction at the least and it might be sooner then later.

Reply 39 of 40, by Falcosoft

User metadata
Rank Oldbie
Rank
Oldbie

This is the closest I could come to any evidence of moves away from native win32 app compat for windows:

Maybe the article was not clear in this respect for you, but it's about a different possibility: namely removing the 'native' Win32/Win64 support. This move would not only affect 32-bit native applications but also 64-bit native Win64 applications. Actually this kind of platform (Windows without native Win32/Win64 support) is almost already exists in the form of Windows 10 S.
In this case the support barrier is not 32-bit vs 64-bit, but applications using the native/legacy Win32 API (notice: the 64-bit version of this legacy API is used also by 64-bit native Win32/64 applications!) and Metro/Modern/WinRT/UWP/Core/Store etc. apps. So on such an OS the 64-bit version of DosBox would not run either since it's also a native/legacy application. In the article's context 'Win32 API' is a generic term. This also includes native 64-bit applications:
https://technet.microsoft.com/en-us/library/bb496995.aspx

Note: The Windows API was formerly called the Win32 API. The name Windows API more accurately reflects its roots in 16-bit Windows and its support on 64-bit Windows. The name Windows API is used in this volume except when comparing 32-bit Windows programming with 64-bit Windows programming. They are then referred to as Win32 and Win64 APIs, respectively.

I think completely removing the whole Win32/64 legacy subsystem without options would be a suicide move by MS. But making some Windows versions without legacy compatibility is not without sense.

Website, Facebook, Youtube
Falcosoft Soundfont Midi Player + Munt VSTi + BassMidi VSTi
VST Midi Driver Midi Mapper