DOS ain't dead

After a long time Crazii just posted some update of his SBEMU & VDPMI
https://www.vogons.org/viewtopic.php?p=1418209#p1418209

---
DOS gives me freedom to unlimited HW access.

> After a long time Crazii just posted some update of his SBEMU & VDPMI
> https://www.vogons.org/viewtopic.php?p=1418209#p1418209

Thanks for the info!

Didn't try it yet, but from what I read: (re)implementing a V86 monitor just for SB sound emulation? IMO a bit exaggerated.

---
MS-DOS forever!

> but from what I read: (re)implementing a V86 monitor
> just for SB sound emulation? IMO a bit exaggerated.

I also wonder about it. Isn't QPIEMU interface in JEMM enough?

EDIT: just some quote of Crazii that reveals plans of VDPMI:
I was thinking about a VXD that works on win9x with dsound support, and at the same time, with a possible simple emulation layer of the VMM/VxD API in VDPMI, the same VXD can also work in DOS.
...
Currently VDPMI provides the virtualization of the PIC, the DMA virtualization is still in SBEMU, which should be removed and changed to the VxD API.

---
DOS gives me freedom to unlimited HW access.

> I also wonder about it. Isn't QPIEMU interface in JEMM enough?

Jemm runs v86 code with IOPL 3 - so CLI/STI runs untrapped. Running it with IOPL 0 gives the chance to trap CLI/STI. This may be advantageous, perhaps for demos using the SB's direct mode. But I guess virtually all games require interrupts to be enabled for sound ...

---
MS-DOS forever!

Crazii is doing some new magic in VDPMI with dynamic switching of PVI that helps against some stuttering... https://www.vogons.org/viewtopic.php?p=1426532#p1426532

---
DOS gives me freedom to unlimited HW access.

Just tried it a bit ( 3 games and a few applications ).

Positive:
- it passes my DPMI IRQ routing compliance test
- DOOM and Redneck Rampage work

Negative
- sound in ROTT isn't convincing
- HX Win32 emulation crashes
- even the totally innocent DEBUG.COM causes a reboot with cmd 'q' (Quit)

So it's in alpha stage.

---
MS-DOS forever!

> - even the totally innocent DEBUG.COM causes a reboot with cmd 'q' (Quit)

Did you run DebugD? Does it crash the same way?

---
l

> Did you run DebugD? Does it crash the same way?

Don't know. What is DebugD?

---
MS-DOS forever!

> > Did you run DebugD? Does it crash the same way?
>
> Don't know. What is DebugD?

Debug/X which doesn't hook interrupts 1 and 3, to allow debugging it: https://hg.pushbx.org/ecm/fddebug/file/809a6fbe45b6/MAKEX.BAT#l5

---
l

> > > Did you run DebugD? Does it crash the same way?

Didn't test it, but it crashed in DEBUG.COM at an IRETD ( 32-bit IRET ). That instruction allows to set RF ( resume flag ) when returning to the debuggee. All Debug/X variants use this instruction if a 386+ cpu has been detected.

---
MS-DOS forever!