-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BBS Door "Dungeon Master" can't find configfile #212
Comments
Should now be fixed. |
Also this software is full of a famous |
Wow, that was super quick! Apologies re: dmmodule.dat, didn't realize. I appreciate the speedy turnaround here, thanks! |
Please note that recently I also |
Confirmed this fix works and the game runs perfectly. Thanks! Unbelievable speed/turnaround. Please let me know if there's some way I can donate to this project as I use it a ton for my DOS BBS doorgames. Re: runtime 200 bug, yeah, sorry, forgot to mention that as well when I initially reported the bug. I'm just very used to patching these by now it's almost a reflex lol. As far as remote mode doors, very cool. I'll definitely give this a whirl. Thanks for the note. |
Interesting because you said
This is an interesting question.
I mean, that should be done in a more There was such an attempt: |
Can you link your patreon here? |
Hmm, actually to give you a link, Note: saying that I am the only donor, needs |
I don't see a way to subscribe donations to you just yet, no.
I don't have thousands of €$ but I'd be happy to chip in a little every month.
DOSBox-X is okay, but DOSBox is still very focused on games. And the FS redirector is only implemented for the internal DOS there I believe, unlike dosemu's MFS which works with any compatible DOS kernel. |
I've got a notification that my page is
Thanks! :)
I personally think dosbox-staging has
I hope to bring in more features, like a |
Picked from the commit at dosemu2/fdpp@fe1c4dc The referenced issue is at dosemu2/fdpp#212 The patch was applied using unix2dos on the patch file then `patch -p1 --binary` with the patch file as stdin. Original commit Metadata: From: Stas Sergeev <stsp@users.sourceforge.net> Date: Wed, 1 Feb 2023 13:01:55 +0500 Subject: [PATCH] truename: fix array overrun [fixes #212] src[-2] was peeking into a random memory location. It seems entire truename() is written by some morons... :( Its completely unreadable and full of bugs.
Picked from the commit at dosemu2/fdpp@fe1c4dc The referenced issue is at dosemu2/fdpp#212 The patch was applied using unix2dos on the patch file then `patch -p1 --binary` with the patch file as stdin. The original used a new define for the maximum path length. As there is no difference to our current SFTMAX define I changed this hunk to retain the SFTMAX use. Original commit Metadata: From: Stas Sergeev <stsp@users.sourceforge.net> Date: Wed, 1 Feb 2023 13:01:55 +0500 Subject: [PATCH] truename: fix array overrun [fixes #212] src[-2] was peeking into a random memory location. It seems entire truename() is written by some morons... :( Its completely unreadable and full of bugs.
Picked from the commit at dosemu2/fdpp@fe1c4dc The referenced issue is at dosemu2/fdpp#212 The patch was applied using unix2dos on the patch file then `patch -p1 --binary` with the patch file as stdin. The original used a new define for the maximum path length. As there is no difference to our current SFTMAX define I changed this hunk to retain the SFTMAX use. This fixes a bug when eg function 3Dh receives a buffer that starts with ".\" but the byte in memory before this buffer happens to be also a dot. I ran into this problem semi-randomly during building EDR-DOS with the most recent WarpLink build. If WarpLink was placed somewhat low in the Low Memory Area then one of its function 3Dh calls would happen to have a dot before the pathname buffer. (I had to load lCDebug using the last fit strategy then enter TSR mode, to catch the bug without the presence of the debugger working around the occurrence of the bug.) Original commit Metadata: From: Stas Sergeev <stsp@users.sourceforge.net> Date: Wed, 1 Feb 2023 13:01:55 +0500 Subject: [PATCH] truename: fix array overrun [fixes #212] src[-2] was peeking into a random memory location. It seems entire truename() is written by some morons... :( Its completely unreadable and full of bugs.
Picked from the commit at dosemu2/fdpp@fe1c4dc The referenced issue is at dosemu2/fdpp#212 The patch was applied using unix2dos on the patch file then `patch -p1 --binary` with the patch file as stdin. The original used a new define for the maximum path length. As there is no difference to our current SFTMAX define I changed this hunk to retain the SFTMAX use. This fixes a bug when eg function 3Dh receives a buffer that starts with ".\" but the byte in memory before this buffer happens to be also a dot. I ran into this problem semi-randomly during building EDR-DOS with the most recent WarpLink build. If WarpLink was placed somewhat low in the Low Memory Area then one of its function 3Dh calls would happen to have a dot before the pathname buffer. (I had to load lCDebug using the last fit strategy then enter TSR mode, to catch the bug without the presence of the debugger working around the occurrence of the bug.) Original commit Metadata: From: Stas Sergeev <stsp@users.sourceforge.net> Date: Wed, 1 Feb 2023 13:01:55 +0500 Subject: [PATCH] truename: fix array overrun [fixes #212] src[-2] was peeking into a random memory location. It seems entire truename() is written by some morons... :( Its completely unreadable and full of bugs.
Describe the bug
When trying to run a BBS Doorgame called "Dungeon Master", the main gamefile cannot find the configfile specified during the setup portion. I have confirmed this works as expected in dosbox and a DOS VM.
To Reproduce
Download Dungeon Master - https://www.johndaileysoftware.com/download?method=1&terms=220DM - and run the installer. Once the installer has completed, run 'dm.exe /LOCAL' and get an error that it cannot find "DEFAULT.CFG" - which is in .\config\ - also note that this will work when trying to use another means (i.e., dosbox) to run the game.
Attach program/game binaries or provide an URL
https://www.johndaileysoftware.com/download?method=1&terms=220DM
Attach the log
A regression?
I believe this worked as expected in dosemu1.
Additional info
Using dosemu-freedos, /etc/dosemu/dosemu.conf is as follows:
The text was updated successfully, but these errors were encountered: