This is possible, because once packaged, the App will be access to the UWP manifest that allows us to create an execution alias. The installation will be reduced to a single click action that will install the App in less than 10 seconds.Īt the same time MSIX will provide a better user experience, allowing users or other apps to call the application executable, in this case, VB.EXE without having to specify the otvdm emulator. Let’s see how MSIXcan simplify the application deployment by keeping together the 16-bit emulator and VB3 application in a single MSIX installation file. Improving the app distribution and providing a better user experience through MSIX In that case you need to run the following command: Notice that despite of Visual Basic 3 is available on Start menu, you can’t directly launch the app from there, as the app is 16-bit: There are no registry keys, and all the files will be copied to the C:\VB directory:ĭone!!!! Visual Basic is successfully installed:Ĭlick on Run Visual Basic 3.0 to launch VB3 on Windows 10 64-bit: Notice that now the Visual Basic 3.0 16-bit installer has been successfully launched: We need to run the otvdm.exe passing as argument the application that we want to launch, in our case, the setup.exe of Visual Basic 3.0:Ĭ:\otvdm-master-1846\otvdm.exe "C:\VB\VB.EXE" If you try to run the Visual Basic 3 installer (setup.exe), you will receive the following message telling that the application cannot run, since it is a 16-bit application and that the NTVDM is not available. Installing Microsoft Visual Basic 3.0 IDE on Windows 10 64-bit
I will extract the files in the following folder of the root of my C drive: Now, all you must do is to extract the files to a folder of your preference. If you opt to download the app from the AppVeyor repository, you need to choose what build you want:Īnd finally click on artifacts to download the artifact file: You can clone the repository and build yourself or download the build artifact from the AppVeyor repository This post is only a proof of concept and for informational and training purposes only and are provided "as is" without warranty of any kind, whether express or implied.Īs 64-bit operating system does not have support for the Windows NT DOS Virtual Machine (NTVM) system component, the first step is to download the 16-bit emulator called otya128 – winevdm that is open source and available on GitHub: Please notice that Microsoft recommends using virtualization or 32-bit machines to run 16-bit applications. It will be demonstrated how to use a third-part open source framework called otya128 – winevdm, how to use MSIX, UWP Execution Alias and Packaging Support Framework. I wrote this post as a proof of concept and as a best effort to make a 16-bit application run on Windows 10 64-bit.
0 kommentar(er)
