Re: [Freedos-user] dosbox-x update available
> NTVDM Compatibility and quality problems aside, WinNT+'s NTVDM only supports (subset of) DOS programs designed for the standard IBM PC with limited hardware configurations. On the other hand, DOSBox(-X) goes way beyond this, for example, allowing to emulate another full DOS-based PC, running different types of DOS programs and DOS-based Windows. You can for example emulate a PCjr, Amstrad, or NEC PC-98 system, and run programs designed for them, which are simply not possible with NTVDM. This is similar to that running DOSBox-X in DOS itself - you can emulate a DOS system very different from the host DOS and run programs designed for that DOS system. NTVDM is rather basic in such functionalities when compared with dedicated DOS emulators like DOSBox(-X). Wengier On Wednesday, August 17, 2022 at 12:26:51 p.m. EDT, Wengier W via Freedos-user wrote: > The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. > The reason the NT one isn't very good is the reason that NT was a successful > product: because it isolates apps from the hardware, making it more reliable > and allowing SMP and things. The root reason is that WinNT is not DOS based, so it tried to emulate DOS in some way. However, as you also agree that the NTVDM has apparent compatibility problems, so many people sought for better solutions and DOSBox(-X) emerged at the time which worked better for their purposes. I really wonder why you were "puzzled" about such solutions. Many people simply needed a better DOS emulator rather than the emulation that NTVDM provided. > That is nothing to do with the VDM. There was definitely something to do with the VDM, that Microsoft was never interested in seriously working on NTVDM in the (32-bit) XP+ era. For example, XP's NTVDM only provided Sound Blaster 2.0 emulation for sound support. We know how terrible the sound was in SB 2.0 (compared with later sound cards), but Microsoft never provided better sound card emulation in their NTVDM, say SB Pro or SB 16 emulation. People who wanted better emulations had to use 3rd-party products anyway. If Microsoft was more serious in supporting NTVDM, they would certainly provide a better quality solution for NTVDM, such as adapting SB Pro/16 emulation and/or trying to fix the full-screen mode issue in Vista+. However, it was clear that no new functionalities were added to NTVDM by Microsoft since XP, but only reduced functionalities, even if it was well-known that NTVDM had many problems. > It's part of the hardware design and MS has little influence over that. The apparent thing is that Microsoft had no interest in keeping DOS/Windows 3.x support at all in their new products. If they were interested, they could definitely try to develop 64-bit NTVDM for 64-bit Windows releases (similar to NTVDMx64). But as mentioned above, Microsoft had no desire to improve NTVDM even in their 32-bit Windows releases, so it is understandable that they would not have desire to ever work on 64-bit NTVDM for their 64-bit Windows releases. MS had full control over this. Wengier On Wednesday, August 17, 2022 at 06:00:16 a.m. EDT, Liam Proven wrote: On Wed, 17 Aug 2022 at 01:34, Wengier W via Freedos-user wrote: > > The apparent problems are the compatibility and quality. There are huge > differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's > NTVDM. Well, yes. The Win9x DOS prompt is real DOS running on a real DOS kernel which can access hardware. The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. The reason the NT one isn't very good is the reason that NT was a successful product: because it isolates apps from the hardware, making it more reliable and allowing SMP and things. This is akin to complaining that a motorcycle is a bad bicycle because this big heavy engine slows you down. The engine is the point of the exercise. If you don't use the engine then yes it gets in the way. > Even OS/2's MVDM did a much better job than XP's NTVDM in emulating DOS. Yes, it did. But I bought and ran OS/2. Running Fractint for DOS in an OS/2 DOS box, and then picking one of Fractint's extended screen modes, reliable crashed OS/2. It let apps hit the hardware. More compatible, but less stable. You can have one thing or the other. Not both, unless you time-travel 20Y forwards and emulate the entire computer in software. That's very inefficient and that itself offends my sense of elegance. :-) > The NTVDM only got worse with (32-bit) Windows Vista or 7 -- things such as > the full-screen mode were removed from its NTVDM as well. That is nothing to do with the VDM. That is because PCs were all getting 3D cards. Microsoft's devs (and Linux's devs) had no idea what to do with them. Apple's devs were smarter and worked out how to use a 3D accelerator to speed up a windowing desktop: what you do is, you render all the window contents as textures, and then you hand those textures to
Re: [Freedos-user] dosbox-x update available
> The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. > The reason the NT one isn't very good is the reason that NT was a successful > product: because it isolates apps from the hardware, making it more reliable > and allowing SMP and things. The root reason is that WinNT is not DOS based, so it tried to emulate DOS in some way. However, as you also agree that the NTVDM has apparent compatibility problems, so many people sought for better solutions and DOSBox(-X) emerged at the time which worked better for their purposes. I really wonder why you were "puzzled" about such solutions. Many people simply needed a better DOS emulator rather than the emulation that NTVDM provided. > That is nothing to do with the VDM. There was definitely something to do with the VDM, that Microsoft was never interested in seriously working on NTVDM in the (32-bit) XP+ era. For example, XP's NTVDM only provided Sound Blaster 2.0 emulation for sound support. We know how terrible the sound was in SB 2.0 (compared with later sound cards), but Microsoft never provided better sound card emulation in their NTVDM, say SB Pro or SB 16 emulation. People who wanted better emulations had to use 3rd-party products anyway. If Microsoft was more serious in supporting NTVDM, they would certainly provide a better quality solution for NTVDM, such as adapting SB Pro/16 emulation and/or trying to fix the full-screen mode issue in Vista+. However, it was clear that no new functionalities were added to NTVDM by Microsoft since XP, but only reduced functionalities, even if it was well-known that NTVDM had many problems. > It's part of the hardware design and MS has little influence over that. The apparent thing is that Microsoft had no interest in keeping DOS/Windows 3.x support at all in their new products. If they were interested, they could definitely try to develop 64-bit NTVDM for 64-bit Windows releases (similar to NTVDMx64). But as mentioned above, Microsoft had no desire to improve NTVDM even in their 32-bit Windows releases, so it is understandable that they would not have desire to ever work on 64-bit NTVDM for their 64-bit Windows releases. MS had full control over this. Wengier On Wednesday, August 17, 2022 at 06:00:16 a.m. EDT, Liam Proven wrote: On Wed, 17 Aug 2022 at 01:34, Wengier W via Freedos-user wrote: > > The apparent problems are the compatibility and quality. There are huge > differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's > NTVDM. Well, yes. The Win9x DOS prompt is real DOS running on a real DOS kernel which can access hardware. The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. The reason the NT one isn't very good is the reason that NT was a successful product: because it isolates apps from the hardware, making it more reliable and allowing SMP and things. This is akin to complaining that a motorcycle is a bad bicycle because this big heavy engine slows you down. The engine is the point of the exercise. If you don't use the engine then yes it gets in the way. > Even OS/2's MVDM did a much better job than XP's NTVDM in emulating DOS. Yes, it did. But I bought and ran OS/2. Running Fractint for DOS in an OS/2 DOS box, and then picking one of Fractint's extended screen modes, reliable crashed OS/2. It let apps hit the hardware. More compatible, but less stable. You can have one thing or the other. Not both, unless you time-travel 20Y forwards and emulate the entire computer in software. That's very inefficient and that itself offends my sense of elegance. :-) > The NTVDM only got worse with (32-bit) Windows Vista or 7 -- things such as >the full-screen mode were removed from its NTVDM as well. That is nothing to do with the VDM. That is because PCs were all getting 3D cards. Microsoft's devs (and Linux's devs) had no idea what to do with them. Apple's devs were smarter and worked out how to use a 3D accelerator to speed up a windowing desktop: what you do is, you render all the window contents as textures, and then you hand those textures to the 3D accelerator and ask it to render those textures onto flat rectangles on the screen. It's called display compositing, and Apple's implementation is called Quartz Extreme. Microsoft copied it in Vista. The display is a composited 3D scene rendered by the GPU. No frame buffer any more, and no way to switch between full-screen and window any more. Linux did the same, first with Compiz (AFAICR). But in Linux, the GUI is in a separate process from the kernel, so you can still switch back to text mode. Windows can't, because in NT4, Microsoft foolishly moved the GDI, the Graphics Device Interface, into the kernel. After NT4 the kernel is running in graphics mode all the time, and it was only about a decade later that MS realised this was a bad idea and started trying to disentangle them again.
Re: [Freedos-user] dosbox-x update available
Hello, On Wed, 17 Aug 2022 at 12:00, Liam Proven wrote: > On Wed, 17 Aug 2022 at 01:34, Wengier W via Freedos-user > wrote: > > > > The apparent problems are the compatibility and quality. There are huge > differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's > NTVDM. > > Well, yes. The Win9x DOS prompt is real DOS running on a real DOS > kernel which can access hardware. > Not actually. It may access the VxD virtual devices that do the real hardware access in 32-bit, and are able to coordinate "multiple DOSes" acceeding the same hardware (including "Windows", that is running in DOS VM0). > The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. > > The reason the NT one isn't very good is the reason that NT was a > successful product: because it isolates apps from the hardware, making > it more reliable and allowing SMP and things. > Actually translating BIOS and DOS calls to an OS that is not on the DOS line, therefore doing not as good as VMM32.VXD (aka DOS386.EXE in previous versions) and all its VxDs did in Windows 9X. > Win64 drops 16-bit support. DOS is a 16-bit OS. It went along with > 16-bit Windows support, no more and no less. > I think this is more realistically the real problem (not the graphics). After all, we could still manage with DOS in a box, even if you can't switch to full screen. Aitor ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
>> The apparent problems are the compatibility and quality. There are huge >> differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's >> NTVDM. > Well, yes. The Win9x DOS prompt is real DOS running on a real DOS > kernel which can access hardware. Well, no. The Win9x DOS prompt is protected mode DOS running on a protected mode DOS kernel that allows your program to access hardware as if it were in real mode. thats no the same. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
On Wed, 17 Aug 2022 at 01:34, Wengier W via Freedos-user wrote: > > The apparent problems are the compatibility and quality. There are huge > differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's > NTVDM. Well, yes. The Win9x DOS prompt is real DOS running on a real DOS kernel which can access hardware. The 32-bit WinNT one can't: it's a sort of VM, containing a DOS emulator. The reason the NT one isn't very good is the reason that NT was a successful product: because it isolates apps from the hardware, making it more reliable and allowing SMP and things. This is akin to complaining that a motorcycle is a bad bicycle because this big heavy engine slows you down. The engine is the point of the exercise. If you don't use the engine then yes it gets in the way. > Even OS/2's MVDM did a much better job than XP's NTVDM in emulating DOS. Yes, it did. But I bought and ran OS/2. Running Fractint for DOS in an OS/2 DOS box, and then picking one of Fractint's extended screen modes, reliable crashed OS/2. It let apps hit the hardware. More compatible, but less stable. You can have one thing or the other. Not both, unless you time-travel 20Y forwards and emulate the entire computer in software. That's very inefficient and that itself offends my sense of elegance. :-) > The NTVDM only got worse with (32-bit) Windows Vista or 7 -- things such as > the full-screen mode were removed from its NTVDM as well. That is nothing to do with the VDM. That is because PCs were all getting 3D cards. Microsoft's devs (and Linux's devs) had no idea what to do with them. Apple's devs were smarter and worked out how to use a 3D accelerator to speed up a windowing desktop: what you do is, you render all the window contents as textures, and then you hand those textures to the 3D accelerator and ask it to render those textures onto flat rectangles on the screen. It's called display compositing, and Apple's implementation is called Quartz Extreme. Microsoft copied it in Vista. The display is a composited 3D scene rendered by the GPU. No frame buffer any more, and no way to switch between full-screen and window any more. Linux did the same, first with Compiz (AFAICR). But in Linux, the GUI is in a separate process from the kernel, so you can still switch back to text mode. Windows can't, because in NT4, Microsoft foolishly moved the GDI, the Graphics Device Interface, into the kernel. After NT4 the kernel is running in graphics mode all the time, and it was only about a decade later that MS realised this was a bad idea and started trying to disentangle them again. https://www.zdnet.com/article/microsoft-confirms-minwin-is-in-windows-7-after-all/ It only applies to server versions and it's only partial. > Meanwhile, 64-bit Windows XP (or higher) never had NTVDM in the first place. On x86, 64-bit Windows runs in x86-64 mode. x86-64 does not have VM86 any more. It has been removed. https://en.wikipedia.org/wiki/Virtual_8086_mode#64-bit_and_VMX_support Basically you have to run a full VM, or emulate it. > Clearly, Microsoft was trying to gradually eliminate the existence of DOS > from its Windows releases. It is not "clear" at all. It's part of the hardware design and MS has little influence over that. Remember, x86-64 is not even an Intel design: it is from AMD. Win64 drops 16-bit support. DOS is a 16-bit OS. It went along with 16-bit Windows support, no more and no less. -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hello, > I am puzzled: I mean, XP can run DOS programs directly, without assistance, can't it? The apparent problems are the compatibility and quality. There are huge differences between Windows 9x's MS-DOS prompt and (32-bit) Windows XP's NTVDM. Even OS/2's MVDM did a much better job than XP's NTVDM in emulating DOS. The NTVDM only got worse with (32-bit) Windows Vista or 7 -- things such as the full-screen mode were removed from its NTVDM as well. Meanwhile, 64-bit Windows XP (or higher) never had NTVDM in the first place. Clearly, Microsoft was trying to gradually eliminate the existence of DOS from its Windows releases. DOSBox(-X) emerged around this time exactly to solve such problems (and also for other platforms). Wengier On Tuesday, August 16, 2022 at 05:05:51 a.m. EDT, Liam Proven wrote: On Tue, 16 Aug 2022 at 07:13, Wengier W via Freedos-user wrote: > > DOSBox-X's Windows XP support has been there for a long time, which will > benefit those who use it (original DOSBox also supports it). I think the > pixel-perfect mode patch which you implemented still works too, so that those > who use Windows XP (or higher) can enjoy it as well. (Please, if you can, bottom post on mailing lists. It makes threads *much* easier to follow.) I am puzzled: I mean, XP can run DOS programs directly, without assistance, can't it? -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
On Tue, 16 Aug 2022 13:15:32 +0200 Aitor Santamaría wrote: > Yes, on 32-bit versions of Windows (and I think this applies to > Windws > Vista/7 at least), there used to be the NTVDM that can run DOS > programs fairly well. > I used to test FD-KEYB there quite a lot, as in case it locks the > console, you don't need to restart. Many DOS programs don't work with MS NTVDM. It is in typical microsoft fashion a bare minimum implementation. Just enough to not anger business users too much. It seems even ReactOS' NTVDM implementation has better compatibility with DOS programs. I think it implements some BIOS interfaces that MS' implementation doesn't. However DOSBox(-X) is light years ahead in compatibility even though it's not some kind of hypervisor like NTVDM. So definitely a great thing for some people that it runs in XP. -- WWW: https://metalpunks.info GPG: C90CAB7122AC1231 pgptM4PdIU1U4.pgp Description: OpenPGP digital signature ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hello. On Tue, 16 Aug 2022 at 11:05, Liam Proven wrote: > I am puzzled: I mean, XP can run DOS programs directly, without > assistance, can't it? > > Yes, on 32-bit versions of Windows (and I think this applies to Windws Vista/7 at least), there used to be the NTVDM that can run DOS programs fairly well. I used to test FD-KEYB there quite a lot, as in case it locks the console, you don't need to restart. Aitor ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
On Tue, 16 Aug 2022 at 07:13, Wengier W via Freedos-user wrote: > > DOSBox-X's Windows XP support has been there for a long time, which will > benefit those who use it (original DOSBox also supports it). I think the > pixel-perfect mode patch which you implemented still works too, so that those > who use Windows XP (or higher) can enjoy it as well. (Please, if you can, bottom post on mailing lists. It makes threads *much* easier to follow.) I am puzzled: I mean, XP can run DOS programs directly, without assistance, can't it? -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hi Anton, DOSBox-X's Windows XP support has been there for a long time, which will benefit those who use it (original DOSBox also supports it). I think the pixel-perfect mode patch which you implemented still works too, so that those who use Windows XP (or higher) can enjoy it as well. Wengier On Aug 13, 2022, at 9:32 PM, Anton Shepelev wrote: Wengier Wu: Yes, most 32-bit Windows builds of DOSBox-X can run on Windows XP. DOSBox-X also has DOS builds for running in DOS itself (so that you can emulate a different DOS system for example). As happy user of Windows XP, and am very glad that you keep support of this last sane version Windows. I hope the pixel-perfect mode that I implemented still works, in spite of the difficulties I had in reconciling it with the GUI configurator. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Wengier Wu: > Yes, most 32-bit Windows builds of DOSBox-X can run on > Windows XP. DOSBox-X also has DOS builds for running in > DOS itself (so that you can emulate a different DOS system > for example). As happy user of Windows XP, and am very glad that you keep support of this last sane version Windows. I hope the pixel-perfect mode that I implemented still works, in spite of the difficulties I had in reconciling it with the GUI configurator. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Tanks all for answer Il gio 4 ago 2022, 20:23 Wengier Wu via Freedos-user < freedos-user@lists.sourceforge.net> ha scritto: > Hi Gabriele, > > Yes, most 32-bit Windows builds of DOSBox-X can run on Windows XP. > DOSBox-X also has DOS builds for running in DOS itself (so that you can > emulate a different DOS system for example). The most recent version of > DOSBox-X is now 0.84.2 / 2022.08.0, which (among other things) added > network functionality on the DOS side. A packet driver is needed IF network > functionality (such as IPX and Modem support) is desired. > > Wengier > > On Aug 4, 2022, at 10:38 AM, Gabriele Barbone wrote: > > > Hi dosbox-x can run on Windows XP SP3? I have a old pc > > Il ven 8 lug 2022, 15:10 Eric Auer ha scritto: > >> >> Forwarding from BTTR - the release notes are indeed worth reading :-) >> After CandyMan found a problem with NDN (Necromancer's Dos Navigator), >> Wengier provided an updated https://dosbox-x.com/devel-build.html >> yesterday. The original announcement from BTTR is: >> >> >> >> DOSBox-X 0.84.1 released! >> >> posted by Wengier, 01.07.2022, 22:11 >> >> DOSBox-X 0.84.1 has now been officially released! Designing to be a >> cross-platform DOS emulator, it is the goal of DOSBox-X to support >> different types of DOS software and implement accurate emulation, >> accurate enough to help make new DOS developments possible with >> confidence the program will run properly on actual DOS systems. >> >> DOSBox-X provides official DOS versions in addition to other platforms. >> Several accessory files (such as fonts and languages) have been added to >> the DOS package in this release, and support for TTF output has also >> been improved in the DOS version. You can download the DOSBox-X 0.84.1 >> DOS package from the DOSBox-X project homepage: >> >> https://dosbox-x.com/ >> >> There are a number of improvements in this latest version, and you can >> find the release notes for this version (containing the change history) >> here: >> >> * https://dosbox-x.com/release-0.84.1.html >> >> The DOS package is self-contained so that you can simply unzip the file >> and type DOSBOX-X to run in DOS. It is confirmed to work in DOS, and >> read the included README.TXT file for more information. >> >> >> >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hi, On Thu, Aug 4, 2022 at 9:38 AM Gabriele Barbone wrote: > > Hi dosbox-x can run on Windows XP SP3? I have a old pc Not sure, I think?? they still provide XP-compatible versions alongside newer Windows versions. BUT! It does run atop FreeDOS with the included HX files. ;-) (quoting the website): "If you need Windows XP support, you can use either the 32-bit Visual Studio builds or the 32-bit MinGW low-end builds (but not the standard MinGW builds). You may also want to use one of the MinGW builds if you encounter specific problem(s) with the Visual Studio builds (such as floating point precision issues)." "Yes, DOSBox-X can officially run on DOS systems as well ... The HX-DOS package allows you to run DOSBox-X in a real DOS system (MS-DOS 5.0+ or compatible) with the help of the freely-available HX DOS Extender, which is already included in the recent DOS release packages." ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hi Gabriele, Yes, most 32-bit Windows builds of DOSBox-X can run on Windows XP. DOSBox-X also has DOS builds for running in DOS itself (so that you can emulate a different DOS system for example). The most recent version of DOSBox-X is now 0.84.2 / 2022.08.0, which (among other things) added network functionality on the DOS side. A packet driver is needed IF network functionality (such as IPX and Modem support) is desired. Wengier > On Aug 4, 2022, at 10:38 AM, Gabriele Barbone wrote: > > Hi dosbox-x can run on Windows XP SP3? I have a old pc > > Il ven 8 lug 2022, 15:10 Eric Auer ha scritto: >> >> Forwarding from BTTR - the release notes are indeed worth reading :-) >> After CandyMan found a problem with NDN (Necromancer's Dos Navigator), >> Wengier provided an updated https://dosbox-x.com/devel-build.html >> yesterday. The original announcement from BTTR is: >> >> >> >> DOSBox-X 0.84.1 released! >> >> posted by Wengier, 01.07.2022, 22:11 >> >> DOSBox-X 0.84.1 has now been officially released! Designing to be a >> cross-platform DOS emulator, it is the goal of DOSBox-X to support >> different types of DOS software and implement accurate emulation, >> accurate enough to help make new DOS developments possible with >> confidence the program will run properly on actual DOS systems. >> >> DOSBox-X provides official DOS versions in addition to other platforms. >> Several accessory files (such as fonts and languages) have been added to >> the DOS package in this release, and support for TTF output has also >> been improved in the DOS version. You can download the DOSBox-X 0.84.1 >> DOS package from the DOSBox-X project homepage: >> >> https://dosbox-x.com/ >> >> There are a number of improvements in this latest version, and you can >> find the release notes for this version (containing the change history) >> here: >> >> * https://dosbox-x.com/release-0.84.1.html >> >> The DOS package is self-contained so that you can simply unzip the file >> and type DOSBOX-X to run in DOS. It is confirmed to work in DOS, and >> read the included README.TXT file for more information. >> >> >> >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dosbox-x update available
Hi dosbox-x can run on Windows XP SP3? I have a old pc Il ven 8 lug 2022, 15:10 Eric Auer ha scritto: > > Forwarding from BTTR - the release notes are indeed worth reading :-) > After CandyMan found a problem with NDN (Necromancer's Dos Navigator), > Wengier provided an updated https://dosbox-x.com/devel-build.html > yesterday. The original announcement from BTTR is: > > > > DOSBox-X 0.84.1 released! > > posted by Wengier, 01.07.2022, 22:11 > > DOSBox-X 0.84.1 has now been officially released! Designing to be a > cross-platform DOS emulator, it is the goal of DOSBox-X to support > different types of DOS software and implement accurate emulation, > accurate enough to help make new DOS developments possible with > confidence the program will run properly on actual DOS systems. > > DOSBox-X provides official DOS versions in addition to other platforms. > Several accessory files (such as fonts and languages) have been added to > the DOS package in this release, and support for TTF output has also > been improved in the DOS version. You can download the DOSBox-X 0.84.1 > DOS package from the DOSBox-X project homepage: > > https://dosbox-x.com/ > > There are a number of improvements in this latest version, and you can > find the release notes for this version (containing the change history) > here: > > * https://dosbox-x.com/release-0.84.1.html > > The DOS package is self-contained so that you can simply unzip the file > and type DOSBOX-X to run in DOS. It is confirmed to work in DOS, and > read the included README.TXT file for more information. > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
