Does dosemu2 Support sound through pipewire and adlib emulation?
I would rather see a serious maintetner who has the experience take the task and work with the current maintetners of the unreal SDK. Their patches, code tweaks, and fixes etc⊠are highly stable and add a host of improvements to the game and extra game modules developers make for maps. They actually have permission from Epic to use Epics private source codes for porting the SDK for Windows and Linux.
I tried porting surreal engine a few months back. Compiling was easy, but Haiku is very strict about code quality and surreal engine is very lax mainly being windows and Linux based. Not only that, but surreal engine only supports the old unreal99 code, not the new code maintained by the current SDK maintetners,. It lacks support for but only a few maps, and other UI/Bot elements are not 100% working correctly.
While it would be fun to test and play with, given all the info I just mentioned above, thatâs a big nope for me.![]()
I havenât tested sound tbh, from the dependencies it has itâs very likely it uses SDL2 to handle sound.
@ablyss Code quality wouldnât stop a third-party app like that from getting into the repo usually, however, if the engine is unfinished as you describe then itâs not good enough for most people so yeah, not much sense in porting it yet.
The recipe for Wine 11.8 has landed in Haikuports proper now, so it can be tested by anybody whoâs on a development version of Haiku and has Haikuporter set up. The recipe cannot be used on Beta 5 apparently. (The same applies for dosemu2 too btw)
Just a note for future Wine nerds:
- Migrate Wine 11.x port from OpenSound (OSS) to Haikuâs MediaKit.
its in depot : package opensound
where is the package for wine in the depot? if its removed then where can i find wine now
Everything should work in Wineâs own D3D implementation (on Linux), unless youâre hitting a bug. DXVK is primarily about performance.
For sure remnant from the ashes without dxvk hangs entire the wine and does not work without dxvk
Iâm on latest available - Haiku x86_64, hrev59893. I upgraded recently. Re-enabled Haikuports, and seen new wine packages among available upgrades
îČ ïŹ user î°î° ~ î°î° ï 12:20 î°î° ï î° pkgman update
100% repochecksum-1 [65 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (BeSly Software Solutions)...done.
100% repochecksum-1 [65 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (FatElk_64)...done.
100% repochecksum-1 [65 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (Haiku)...done.
100% repochecksum-1 [64 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (HaikuPorts)...done.
100% repochecksum-1 [65 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (KapiX's Depot)...done.
100% repochecksum-1 [71 bĂĄjt]
EllenĆrzĆkĂłd Ă©rvĂ©nyesĂtĂ©se a tĂĄrolĂłhoz (LOTE)...done.
The following changes will be made:
in system:
upgrade package qt6_base-6.10.3-2 to 6.10.3-3 from repository HaikuPorts
upgrade package gtk3-3.24.52-1 to 3.24.52-2 from repository HaikuPorts
upgrade package gtk4-4.23.2-1 to 4.23.2-2 from repository HaikuPorts
install package wine-11.8-1 from repository HaikuPorts
upgrade package kio6-6.28.0-1 to 6.28.0-2 from repository HaikuPorts
upgrade package gcr-3.41.1-5 to 3.41.1-6 from repository HaikuPorts
uninstall package wine_bin-7.9-2
Continue? [yes/no] (yes) :
100% qt6_base-6.10.3-3-x86_64.hpkg [18,33 MiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/qt6_base-6.10.3-3-x86_64.hpkg...done.
100% gtk3-3.24.52-2-x86_64.hpkg [14,39 MiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/gtk3-3.24.52-2-x86_64.hpkg...done.
100% gtk4-4.23.2-2-x86_64.hpkg [24,85 MiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/gtk4-4.23.2-2-x86_64.hpkg...done.
100% wine-11.8-1-x86_64.hpkg [343,85 MiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/wine-11.8-1-x86_64.hpkg...done.
100% kio6-6.28.0-2-x86_64.hpkg [5,80 MiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/kio6-6.28.0-2-x86_64.hpkg...done.
100% gcr-3.41.1-6-x86_64.hpkg [899,58 KiB]
Validating checksum for https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/gcr-3.41.1-6-x86_64.hpkg...done.
[system] Applying changes ...
[system] Changes applied. Old activation state backed up in "state_2026-07-23_12:15:04"
[system] Cleaning up ...
[system] Done.
[system] 533 old state(s) can be cleaned up. Use "pkgman cleanup" to remove them.
îČ ïŹ user î°î° ~ î°î° ï 13:21 î°î° ï î°
Installed them, and probe again my favourite test executable
îČ ïŹ user î°î° ~ î°î° ï 13:21 î°î° ï î° /boot/system/bin/wine64 /SANDSK256GO/OtherS/DoQ/DL/stresszoldo.exe
bash: /boot/system/bin/wine64: No such file or directory
îČ ïŹ user î°î° ~ î°î° ï 13:22 î°î° ï î° find /boot/system/bin -name win*
/boot/system/bin/winpr-makecert
/boot/system/bin/winpr-hash
/boot/system/bin/winicontoppm
/boot/system/bin/winicontopam
/boot/system/bin/wineserver
/boot/system/bin/winepath
/boot/system/bin/winemine
/boot/system/bin/winemaker
/boot/system/bin/winegcc
/boot/system/bin/wineg++
/boot/system/bin/winefile
/boot/system/bin/winedump
/boot/system/bin/winedbg
/boot/system/bin/winecpp
/boot/system/bin/wineconsole
/boot/system/bin/winecfg
/boot/system/bin/winebuild
/boot/system/bin/wineboot
/boot/system/bin/wine
îČ ïŹ user î°î° ~ î°î° ï 13:23 î°î° ï î° /boot/system/bin/wine /SANDSK256GO/OtherS/DoQ/DL/stresszoldo.exe
002c:fixme:file:get_device_info device info not properly supported on this platform
002c:fixme:ntdll:create_logical_proc_info stub
002c:fixme:ntdll:init_logical_proc_info Failed to get logical processor information, status 0xc0000002.
002c:err:winediag:getaddrinfo Failed to resolve your host name IP
0034:fixme:file:get_device_info device info not properly supported on this platform
003c:fixme:file:get_device_info device info not properly supported on this platform
0040:fixme:thread:set_native_thread_name not implemented on this platform
0048:fixme:file:get_device_info device info not properly supported on this platform
0058:fixme:thread:set_native_thread_name not implemented on this platform
006c:fixme:file:get_device_info device info not properly supported on this platform
0078:fixme:thread:set_native_thread_name not implemented on this platform
0084:fixme:file:get_device_info device info not properly supported on this platform
0090:fixme:thread:set_native_thread_name not implemented on this platform
009c:fixme:file:get_device_info device info not properly supported on this platform
00a8:fixme:thread:set_native_thread_name not implemented on this platform
00c4:fixme:file:get_device_info device info not properly supported on this platform
00cc:fixme:file:get_device_info device info not properly supported on this platform
00ac:err:setupapi:do_file_copyW Unsupported style(s) 0x10
00d4:fixme:file:get_device_info device info not properly supported on this platform
wl_ips_client_connected
display: 0xce74baae00
client: 0xce74babcc0
00cc:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
00cc:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
00cc:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
00cc:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
wl_ips_client_connected
display: 0x8145b93e00
client: 0x8145b94cc0
00d4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
00d4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
00d4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
00d4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
00f4:fixme:file:get_device_info device info not properly supported on this platform
0104:fixme:thread:set_native_thread_name not implemented on this platform
0108:fixme:thread:set_native_thread_name not implemented on this platform
0120:fixme:file:get_device_info device info not properly supported on this platform
0130:fixme:thread:set_native_thread_name not implemented on this platform
wl_ips_client_connected
display: 0xd427531e00
client: 0xd427532cc0
wl_ips_client_connected
display: 0xcc7e646e00
client: 0xcc7e647d80
002c:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
002c:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
002c:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
002c:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
00c4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
00c4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
00c4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
00c4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
0160:fixme:file:get_device_info device info not properly supported on this platform
wl_ips_client_connected
display: 0x95eed45e00
client: 0x95eed46cc0
00f4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
00f4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
00f4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
00f4:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
016c:fixme:thread:set_native_thread_name not implemented on this platform
wl_ips_client_connected
display: 0x54d1af22a0
client: 0x54d1f57cc0
0160:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
0160:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
0160:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
0160:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
0160:fixme:file:NtLockFile I/O completion on lock not implemented yet
0160:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0160:fixme:ntdll:create_logical_proc_info stub
0160:fixme:ntdll:init_logical_proc_info Failed to get logical processor information, status 0xc0000002.
0180:fixme:file:get_device_info device info not properly supported on this platform
wl_ips_client_connected
display: 0xd5c297ce00
client: 0xd5c297dcc0
0180:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
0180:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
0180:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
0180:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
0180:err:waylanddrv:wayland_pointer_update_constraint This function requires zwp_pointer_constraints_v1
0180:fixme:win:NtUserActivateKeyboardLayout Aliased keyboard layout not yet implemented
0180:fixme:urlmon:InternetBindInfo_GetBindString not supported string type 20
018c:fixme:thread:set_native_thread_name not implemented on this platform
0180:fixme:urlmon:HttpProtocol_on_error Not handling error 997
0180:fixme:win:NtUserActivateKeyboardLayout Aliased keyboard layout not yet implemented
0180:fixme:win:NtUserActivateKeyboardLayout Aliased keyboard layout not yet implemented
0024:err:environ:run_wineboot boot event wait timed out
0024:fixme:file:get_device_info device info not properly supported on this platform
0198:fixme:file:get_device_info device info not properly supported on this platform
No LDT support on this platform
AlkalmazĂĄs nem indult el, vagy nincs alkalmazĂĄsi jog hozzĂĄrendelve a fĂĄjlhoz.
ShellExecuteEx hiba: BelsĆ hiba.
îČ ïŹ user î°î° ~ î°î° ï 13:29 î°î° ï î° 0180:fixme:win:NtUserActivateKeyboardLayout Aliased keyboard layout not yet implemented
0180:fixme:win:NtUserActivateKeyboardLayout Aliased keyboard layout not yet implemented
01a8:fixme:file:get_device_info device info not properly supported on this platform
wl_ips_client_connected
display: 0x8124501e00
client: 0x8124502cc0
01a8:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_pointer_constraints_v1 (pointer locking/confining won't work)
01a8:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwp_relative_pointer_manager_v1 (relative motion won't work)
01a8:err:waylanddrv:wayland_process_init Wayland compositor doesn't support optional zwlr_data_control_manager_v1 (clipboard functionality will be limited)
01a8:err:waylanddrv:wayland_process_init Wayland compositor doesn't support xdg_toplevel_icon_manager_v1 (window icons will not be supported)
No LDT support on this platform
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
00a4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c00000e5
002c:err:setupapi:SetupDiInstallDevice Failed to start service L"winebth" for device L"ROOT\\WINE\\WINEBTH", error 1359.
002c:err:setupapi:SetupDiInstallDevice Failed to control service L"winebth" for device L"ROOT\\WINE\\WINEBTH", error 1062.
002c:err:virtual:try_map_free_area mmap() error Bad address, range 0x7fffff400000-0x7ffffffe2000, unix_prot 0x3.
wineserver: server/object.c:548:release_object: obj->refcount
Abort
îČ ïŹ user î°î° ~ î°î° ï 13:39 î°î° ï î°
Seems what worked under Linux Mint, from a BFS formatted drive .. still needs some further software to work on Haiku that smoothly as well âŠ
That means the Buildmasters got updated and recipes got re-triggered, wine couldnât be built on beta5-based buildmasters.
The same is true for dosemu, which just received a package today as well.
Wine on Haiku needs a lot of work to even come close to what Wine can do on Linux, at the moment itâs just a toy for testing, treat it as such.
Too bad 11.8 is already oldâŠ

