Details about the whole approach can be found in the Techcommunity article. But Demetrio describes an approach how to integrate the 16-bit emulator and the Visual Basic 3 16-bit applications into an MSIX package. You have to call the applications from the emulator. The steps are described in the Techcommunity article. The framework can then be used with the emulator to install and run 16-bit programs like Visual Basic 3.0. To do so, the open source 16-bit emulator otya128 – winevdm must be downloaded from GitHub, compiled and installed.Īn artifact in the form of a ready-to-use ZIP archive file otvdm-master -1846.zip (expires in 5 months) can be downloaded from AppVeyor. Luis Henrique Demetrio from Brazil, a Windows Development Advocate in the Microsoft App Consult Team has described a proof of concept in the article Running 16-bit applications on Windows 10 64-bit. The colleagues of now noticed a Techcommunity article, where an alternative way is described. Windows 95 4.6 MB: Restored from snapshot: Windows 3.1 15 MB: Takes 15 seconds to boot: Windows 1.01 0.6 MB: Takes 1 second to boot: MS-DOS 6.22 4.4 MB: With Enhanced Tools, QBasic, vim, games and demos. (16-Bit-Application Visual Basic 3.0 runs in a 64-bit-Windows 10 environment) Windows 98 9.7 MB: Including Minesweeper and Internet Explorer with internet access. And in this VM the 16-bit programs from MS-DOS and Windows 1.0, 2.0, 3.x times could run. The solution: A virtual machine with a 32-bit Windows has to be set up under the 64-bit guest operating system. Under 64-bit Windows, Windows on Windows 16 (WOW16) is missing. Only the 32-bit Windows operating systems contain the Windows NT DOS Virtual Machine (NTVM) (WOW16) – but it may have had to be installed as a feature. Until now, old 16-bit programs from MS-DOS times had to be run under 32-bit Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |