Difference between revisions of "User:Petr-akhlamov/WOW"
(Update the page) |
|||
(13 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | '''Windows on Windows (WOW)''' — is a system component, which enables running apps that | + | '''Windows on Windows (WOW)''' — is a system component, which enables running apps that use legacy 16-bit version of Windows API (Win 16) in 32-bit versions of Windows NT. |
WOW is implemented with the help of NTVDM and win16api stubs. NTVDM is used for running 16-bit code, and win16api stubs thunk legacy 16-bit APIs to their newer 32-bit equivalents. | WOW is implemented with the help of NTVDM and win16api stubs. NTVDM is used for running 16-bit code, and win16api stubs thunk legacy 16-bit APIs to their newer 32-bit equivalents. | ||
Line 5: | Line 5: | ||
Usually, WOW is needed for old 16-bit installers. | Usually, WOW is needed for old 16-bit installers. | ||
− | 29-03-2018 Aleksandar Andrejevic (NTVDM developer) [http://reactos.org/project-news/march-2018-meeting-minutes announced] that he plans to work on WOW. | + | 29-03-2018: Aleksandar Andrejevic (NTVDM developer) [http://reactos.org/project-news/march-2018-meeting-minutes announced] that he plans to work on WOW. |
− | ==Why 16-bit apps work in | + | In May 2019, support was implemented [https://www.winehq.org/announce/4.9 in Wine 4.9], for building 16-bit modules in PE format |
+ | |||
+ | ==Why 16-bit apps work in Wine?== | ||
In the Wine, running of 16-bit apps depends on kernel module ldt16, whereby emulate 16-bit code.[http://wiki.winehq.org/FAQ#16-bit_applications_fail_to_start] | In the Wine, running of 16-bit apps depends on kernel module ldt16, whereby emulate 16-bit code.[http://wiki.winehq.org/FAQ#16-bit_applications_fail_to_start] | ||
Line 17: | Line 19: | ||
Win3mu currently won't run most Windows 3 programs however it does run quite a few games. | Win3mu currently won't run most Windows 3 programs however it does run quite a few games. | ||
+ | </pre> | ||
− | + | Not all apps work and it runs by dragging to app icon. | |
− | + | In 2018, the author opened the source code. It doesn't work in ReactOS since .NET Framework 4.6.1 can't be installed. | |
− | |||
− | |||
*[https://www.toptensoftware.com/win3mu/ Official site] | *[https://www.toptensoftware.com/win3mu/ Official site] | ||
+ | *[https://yadi.sk/d/AVB8-1MNOAnVIQ Download app build] | ||
+ | |||
+ | ===WineVDM=== | ||
+ | ====Latest builds==== | ||
+ | *Go to https://ci.appveyor.com/project/otya128/winevdm/history | ||
+ | *Choose revision | ||
+ | *List JobName, choose Job with GCC | ||
+ | *Go to Artifacts tab | ||
+ | *Download archive file, for example otvdm-cmake-gcc-master-2165.zip | ||
+ | |||
+ | ====Settings==== | ||
+ | Since 0.4.15-dev-g0f05abe, ReactOS automatically opens 16-bit executables with WineVDM if it is present in Program Files\otvdm directory. | ||
+ | *Extract archive file you downloaded | ||
+ | *Copy folder to C:\Program Files | ||
+ | *Rename it to '''otvdm''' | ||
+ | *Go to 16-bit exe-file and just run it. | ||
+ | ====Illustration and games==== | ||
+ | [[File:ROS WOW.png|750px|center]] | ||
+ | *[https://disk.yandex.ru/d/NpZG1zLdzaTR6|Link to ISO with games] | ||
+ | |||
+ | ====Links==== | ||
+ | *[http://github.com/otya128/winevdm Project on Github] | ||
+ | *[https://www.youtube.com/watch?v=bnxSbVksP1g video] | ||
− | == | + | ==Other links== |
*Bugtracker reports: | *Bugtracker reports: | ||
**{{JIRA|8254}} | **{{JIRA|8254}} | ||
Line 33: | Line 57: | ||
*[http://reactos.org/forum/viewtopic.php?f=2&t=15623 16-bit Windows Program Support - Forum topic] | *[http://reactos.org/forum/viewtopic.php?f=2&t=15623 16-bit Windows Program Support - Forum topic] | ||
*[http://www.reactos.org/forum/viewtopic.php?f=22&t=10988 Installing 32-bit programs with 16-bit setup launcher stubs - Forum topic] | *[http://www.reactos.org/forum/viewtopic.php?f=22&t=10988 Installing 32-bit programs with 16-bit setup launcher stubs - Forum topic] | ||
− | *[http://www.wine-staging.com/news/2016-02-10-blog-wine-16bit.html WineStaging - Blog: How do Win 3.1 applications work in Wine?] | + | *[http://reactos.org/forum/viewtopic.php?f=2&t=16897 Will ReactOS native support protected mode 16-bit programs? - Forum topic] |
+ | *[https://web.archive.org/web/20180102112819/http://www.wine-staging.com/news/2016-02-10-blog-wine-16bit.html WineStaging - Blog: How do Win 3.1 applications work in Wine?] |
Latest revision as of 22:24, 24 November 2021
Windows on Windows (WOW) — is a system component, which enables running apps that use legacy 16-bit version of Windows API (Win 16) in 32-bit versions of Windows NT.
WOW is implemented with the help of NTVDM and win16api stubs. NTVDM is used for running 16-bit code, and win16api stubs thunk legacy 16-bit APIs to their newer 32-bit equivalents.
Usually, WOW is needed for old 16-bit installers.
29-03-2018: Aleksandar Andrejevic (NTVDM developer) announced that he plans to work on WOW.
In May 2019, support was implemented in Wine 4.9, for building 16-bit modules in PE format
Contents
Why 16-bit apps work in Wine?
In the Wine, running of 16-bit apps depends on kernel module ldt16, whereby emulate 16-bit code.[1]
Other software
Win3mu
According to the official website:
Win3mu is a Windows 3.0 emulator. It includes an 8086 CPU emulation that loads 16-bit Windows executables and maps API calls onto the modern 32 or 64-bit Windows API. Win3mu currently won't run most Windows 3 programs however it does run quite a few games.
Not all apps work and it runs by dragging to app icon.
In 2018, the author opened the source code. It doesn't work in ReactOS since .NET Framework 4.6.1 can't be installed.
WineVDM
Latest builds
- Go to https://ci.appveyor.com/project/otya128/winevdm/history
- Choose revision
- List JobName, choose Job with GCC
- Go to Artifacts tab
- Download archive file, for example otvdm-cmake-gcc-master-2165.zip
Settings
Since 0.4.15-dev-g0f05abe, ReactOS automatically opens 16-bit executables with WineVDM if it is present in Program Files\otvdm directory.
- Extract archive file you downloaded
- Copy folder to C:\Program Files
- Rename it to otvdm
- Go to 16-bit exe-file and just run it.