Ryan Underwood wrote:
The idea was to be able to file bugs against a particular application under a particular DOSEMU version
I think that can be helpfull. But as the bottleneck of a dosemu development process is unfortunately elsewhere, I wouldn't assign the prio to that your project higher than to your adlib server:)
It should function similarly to the WINE application compatibility database.
Just wondering, is/was that possible to reuse their (or other) code rather than writing your own?
whether or not it works with any of the other emulators (FreeBSD doscmd, DosBox, Bochs, etc)
Actually testing against NT or 2000 dos box is the most important. Bochs and doscmd are out of comparision.
PS: I think there will be problems with your adlib server as a separate process to mix the sound with dosemu's SB digital output in real-time. The adlib server must do a frequent small transferrs together with taking care about keeping the OSS's buffers partially filled to avoid underruns. At the same time dosemu's DMA will write a large blocks and very infrequently. When the block from DMA arrives, there is already a data from an adlib server in a real card's DMA buffers, and there is no possibility to mix so lately (unless the hardware permits). So I beleive the DMA and Adlib sounds will always interrupt each other, unless they are coordinated and using an internal mixing (not per your design). Is there a planned solution for that? Or is there something in ALSA that can help with the real-time mixing even under that hostile conditions? dmix?
- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
