Hi, Sorry in advance for too many details, but in case anybody cares ....
On Sun, Nov 11, 2012 at 11:16 AM, Mateusz Viste <mate...@viste-family.net> wrote: > > You could give a try with the new version of FDNPKG (v0.91, released a > few minutes ago) - I don't think it will change much, but one never know... I doubt it. I'm pretty sure most problems (not counting the VBox tmpfile issue) are due to buggy sound driver code. > About the vbox/dosemu issues with smmu.exe - emulation is never perfect, > and FreeDOS being a niche system, I fear that we'll have to live with > the fact that some software isn't running as well on emulated > environnements as it is on physical machines :) I've (vaguely) narrowed down the sound problem, at least. But I'm not sure of the best way to "properly" handle it (recompile, binary patch, workaround, additional readme, etc). SMMU isn't very verbose when it crashes under DOSEMU due to its own signal handlers, hence "Segmentation Violation" [sic] isn't very descriptive. I pity my own weak skills for not knowing how the heck to fix that right now. I ended up reverting to his fork of MBF "with fixes" and recompiling with debug info. Then GDB showed the crash in something about "translate soundfont", and commenting that out seemed to work okay. Dunno why DOSEMU would autodetect as AWE32 (assuming I understood correctly). Fiddling with some env. vars. didn't help. Unfortunately, not much config tweaking in menus nor (generated) manually with smmu.cfg seemed to help. (Actually, smmu.cfg seemingly won't even get made until successful start.) And like I said, even "-nosound" now [in my existing build in public .ZIP] won't work under DOSEMU, it just crashes with reg dump (SIGSEGV). But recompiling (even if I was convinced of the proper way, which I'm not yet) is clunky and bad for anybody having already downloaded. I wanted to see if (by rare chance) I could "fix" this without that hassle. I didn't think I'd need it (and forgot anyways), but putting allegro.cfg (from included SOURCE\FREEDOOM\ALLEG312.ZIP) in the same dir as .EXE does make it start up correctly. Then and only then does the in-game sound menu let me [correctly] disable (MIDI?) "music", so then at next startup it does actually play sfx (shotgun effects, etc). Otherwise, with allegro.cfg found it's totally silent (and without even that it crashes / won't start!). Well, kinda annoying, and who knows if that's the same quirk that I saw in Eternity 3.29 or whatever. Too bad I'm one of the last (only?) guys still interested in a DOS port of Doom (and using "2x old" Allegro, double whammy). Who knows, similar to Wolf4SDL, maybe SDL + ReactOS MSVCRT.DLL lets one of the Win32 versions work better under HX (RT + GUI), but I somewhat doubt it (esp. without having tried). I should probably start a thread on news://comp.os.msdos.djgpp , but it's such a ghost town sometimes. :-( P.S. I have not been in contact with anyone related to Doom at all, but a quick search did surprisingly find a very very recent interview with SMMU's main coder, if anyone is interested: http://doomnexus.drdteam.org/Stuff/doomster/DU_Fraggle.html ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
