Can I Install a Clip Art That Will Run With My 64 Bit

I wrote this post as a proof of concept and as a best effort to make a sixteen-bit awarding run on Windows 10 64-bit.

It will be demonstrated how to use a third-part open source framework called otya128 – winevdm, how to employ MSIX, UWP Execution Allonym and Packaging Support Framework.

Delight notice that Microsoft recommends using virtualization or 32-bit machines to run 16-flake applications.

This post is simply a proof of concept and for informational and training purposes just and are provided "every bit is" without warranty of any kind, whether limited or unsaid.

As 64-fleck operating system does not have back up for the Windows NT DOS Virtual Car (NTVM) system component, the outset step is to download the 16-scrap emulator chosen otya128 – winevdm that is open source and available on GitHub:

https://github.com/otya128/winevdm

Yous can clone the repository and build yourself or download the build antiquity from the AppVeyor repository  https://ci.appveyor.com/project/otya128/winevdm/history

If y'all opt to download the app from the AppVeyor repository, you need to choose what build yous desire:

Select the job:

And finally click on artifacts to download the artifact file:

Now, all you must do is to extract the files to a folder of your preference. I will excerpt the files in the following folder of the root of my C bulldoze:

           C:\otvdm-master-1846        

If you attempt to run the Visual Basic 3 installer (setup.exe), you will receive the post-obit message telling that the awarding cannot run, since information technology is a 16-scrap application and that the NTVDM is non bachelor.

Nosotros need to run the otvdm.exe passing equally argument the awarding that nosotros want to launch, in our case, the setup.exe of Visual Bones three.0:

          C:\otvdm-primary-1846\otvdm.exe "C:\VB\VB.EXE"        

Notice that now the Visual Basic 3.0 16-bit installer has been successfully launched:

Nosotros can proceed with the installation:

The default destination folder is C:\VB:

At that place are no registry keys, and all the files will be copied to the C:\VB directory:

Done!!!! Visual Basic is successfully installed:

Click on Run Visual Bones 3.0 to launch VB3 on Windows x 64-bit:

Notice that despite of Visual Bones 3 is available on Start menu, you can't directly launch the app from there, as the app is 16-fleck:

In that case you need to run the following command:

          C:\otvdm-primary-1846\otvdm.exe "C:\VB\VB.EXE"        

Permit's run into how MSIX can simplify the awarding deployment by keeping together the sixteen-bit emulator and VB3 awarding in a single MSIX installation file. The installation volition be reduced to a single click action that will install the App in less than 10 seconds.

At the same time MSIX volition provide a better user experience, allowing users or other apps to phone call the application executable, in this case, VB.EXE without having to specify the otvdm emulator. This is possible, because once packaged, the App volition be admission to the UWP manifest that allows united states of america to create an execution alias.

The commencement footstep is to download and install the MSIX Packaging Tool, that is free and available on Microsoft Store, to allow usa to package our App:

https://www.microsoft.com/store/productId/9N5LW3JBCXKF

Before launching the MSIX Packaging Tool, move the emulator and VB folders to another folder, like C:\setup\:

This step is demand, as MSIX Packaging Tool (MPT) will monitor the changes made on the computer environment. And then, as nosotros already take VB3 installed and we don't want to install it again, I will just copy these two folders to their last destinations at the moment that the MPT will be monitoring the modifications.

In one case installed, open the MSIX Packaging Tool and click on Awarding bundle to create a new package for the application:

The MSIX Packaging Tool will monitor the changes fabricated on the environment. To perform the packaging, it is possible to use a virtual machine or the physical car itself to install the application.

The best scenario is to employ a virtual machine assuasive you lot to reproduce the same procedure if necessary. It is important that the auto used to install the awarding does non contain the applications and their previously installed components.

Choose the desired scenario and click the Next button:

In this step, the tool will verify that the MSIX Packaging Tool Driver is installed and will disable Windows Update to decrease the number of changes to the operating arrangement:

Click on the Adjacent button.

Only MSIX packages signed with a valid document can exist installed on Windows ten machines.

You can create a self-signed document for testing purposes, using the following PowerShell command:

          office CreateCertificate($proper noun, $path) {      Prepare-Location Cert:\LocalMachine\My          New-SelfSignedCertificate -Blazon Custom -Subject "CN=$name" -KeyUsage DigitalSignature -FriendlyName $name -CertStoreLocation "Cert:\LocalMachine\My"      $cert = Get-ChildItem "Cert:\LocalMachine\My" | Where Subject -eq "CN=$proper name"      $pwd = ConvertTo-SecureString -Cord DefineTheCertificatePasswordHere@2020 -Forcefulness -AsPlainText       Consign-PfxCertificate -cert $cert.Thumbprint -FilePath "$path.pfx" -Countersign $pwd          Export-Certificate -Cert $cert -FilePath "$path.cer"           Move-Particular -Path $cert.PSPath -Destination "Cert:\LocalMachine\TrustedPeople"   }  CreateCertificate "luisdem" "cert"                  

To execute the control, open PowerShell_ISE.exe and press F5. The control creates the test document and copies it to the Trusted People binder.

Information technology is important to notice that this test document should only exist used to corroborate the application in a test environs. To distribute the application.

Now, that nosotros accept a document, nosotros tin can inform the certificate to have the final MSIX package file automatically signed. It is not necessary to provide the installer file, every bit the tool monitors all changes fabricated to the operating system.

Click on the Next button.

In this step, it is necessary to provide information such as the proper noun of the bundle, the description that volition exist displayed to the user during installation, the name of the supplier (must be the same as the document) and the version number. Fill in the requested information:

Click on the Next button.

Is in this step that we demand to install the application.

Every bit nosotros already accept the VB3 installed, this is the moment to moving back the emulator and VB3 folders to the drive C root:

Click on the Next push button only later on completing the awarding installation and all settings.

On the next screen it is necessary to define which applications volition be visible in the start menu.

Equally VB3 is a xvi-bit application that depends on the 16-bit emulator, select only the otvdm.exe, as follows:

Find that is non possible to provide the arguments for the otvdm.exe, i.east.,C:\VB\VB.EXE. For now, we can ignore the arguments every bit nosotros are ready that later.

Follows the expected effect and then far:

Click on the Next button.

The following screen is displayed at the end of the installation and asks for confirmation if the monitoring can be ended:

Click the Next button, every bit the application does not install any services:

At this signal, it is necessary to inform where the packet volition be generated, also as information technology is possible to edit the package before saving it.

Click on the Bundle editor push button to check the package structure, equally follows:

Click on Open file to check how the manifest was generated:

It is possible to edit the manifest information, such every bit processor compages, application clarification, minimum supported version of Windows ten and others.

Modify the ProcessorArchitecture to "x86", the DisplayName and Description attributes to "Microsoft Visual Basic 3.0":

Notice that the Executable attribute doesn't take the C:\otvdm-master-1846 path, but instead it has the value VFS\AppVPackageDrive\otvdm-principal-1846. The AppVPackageDrive is the folder within the package that corresponds to the drive C root. The application will look for the file on C:\otvdm-principal-1846 simply information technology will be redirected to the binder inside the package (VFS\AppVPackageDrive\otvdm-master-1846).

The only problem hither, is that is no possible to pass arguments in this manifest file. So, we volition need to use Packet Back up Framework (PSF) to ready that.

For now, just change the Executable value path to "PsfLauncher32.exe" that is part of the PSF.

We volition now create an execution alias to let launching the awarding by typing or calling the VB.EXE control from anywhere. To practice this, add the post-obit lines merely below the line </uap:VisualElements>:

          <Extensions>         <uap3:Extension Category="windows.appExecutionAlias"                          Executable="PsfLauncher32.exe"                         EntryPoint="Windows.FullTrustApplication">           <uap3:AppExecutionAlias>             <desktop:ExecutionAlias Alias="VB.EXE" />           </uap3:AppExecutionAlias>         </uap3:Extension>  </Extensions>        

Follows how the manifest file must be defined:

Relieve and close the manifest (Notepad file) to unblock the MSIX Packaging Tool editor screen.

Click on Package files and check if all the files and directories listed are used by the application.

Remove unnecessary files or directories to reduce the packet size:

Information technology is at this stride that we demand to add together the Package Support Framework files, to allow the PsfLauncher32.exe calling the emulator passing the arguments.

To keep, download the PSF files (PSFBinaries.zip) available on GitHub:

Releases · microsoft/MSIX-PackageSupportFramework (github.com)

And excerpt the contents to a folder of your preference. I volition extract to C:\PSF:

In the same folder, create a config.json file with the post-obit content:

          {    "applications": [     {       "id": "OTVDM",       "executable": "VFS/AppVPackageDrive/otvdm-master-1846/otvdmw.exe",       "arguments": "AppVPackageDrive/VB/VB.EXE",       "workingDirectory": "VFS"     }   ] }        

The id corresponds to the Awarding Id divers in the application manifest, the executable contains the emulator path inside the package and the arguments the VB3 path inside the bundle.

Switch back to MSIX Packaging Tool. In the Parcel file tab, right click on Package folder and click on

Add file from the context bill of fare:

Add all the files that finish with 32 and the config.json files to the projection:

Click on the Create button to generate the package and inform where the file should exist generated.

The following screen will display where the MSIX file was generated likewise every bit the log file:

Double-click the package to install the application:

You can now launch the application directly from Showtime menu or typing vb.exe in a prompt command:

This solution is compatible with MSIX App Attach for Windows Virtual Desktop on-premises or on Microsoft Azure.

I hope you like information technology!!!

castillosirstion66.blogspot.com

Source: https://techcommunity.microsoft.com/t5/windows-dev-appconsult/running-16-bit-applications-on-windows-10-64-bit/ba-p/1671418

Share this post