News for hackers. Stuff that matters.
Re:Wine 3.0 Released by makomk on Thursday January 18, 2018 @01:17PM (#16179704)
If I recall correctly, you can still switch the processor to 16-bit mode but virtual 8086 mode is not available from x86-64. So more recent 16-bit Windows applications can be made to work but DOS applications and older 16-bit Windows applications that rely on more legacy DOS-style APIs don't work.
Re:Wine 3.0 Released by JdeBP on Friday January 19, 2018 @02:03PM (#16188768)
The "older 16-bit Windows applications" (actually a misnomer because there isn't this distinction in practice) actually used DPMI, which does not involve v8086 mode.
Re:Wine 3.0 Released by merb on Thursday January 18, 2018 @04:04PM (#16181440)
well which is probably only possible if you don't run on efi only hardware. (no cs/m, which sometimes happens, especially on mac hardware)
Re:Wine 3.0 Released by JdeBP on Friday January 19, 2018 @01:32PM (#16188508)
The actual machine firmware has been irrelevant for v8086 ever since the time of OS/2 2.0 and DOS-Windows 3.1. Both used virtualized machine firmwares to run in the v8086 virtual machines. OS/2's was dealt with by a virtual device driver called VBIOS.SYS, for example.
Re:Wine 3.0 Released by lloeki on Friday January 19, 2018 @08:25AM (#16185990)
This is precisely why DOSBox took a significant performance hit when going from x86 to amd64 back in the day.