First post, by ariqu
- Rank
- Newbie
I've been toying around with WWIV 4.30 under DOSBox 0.72 recently in comparison to Synchronet BBS software for compatibility reasons. Mainly, door games, specifically Legend of the Red Dragon(LORD) and its In-Game-Modules (IGMs) are what have been annoying me. Some of these IGMs and doors are written in Turbo Pascal and have that well-known timing issue (Runtime error 200). Although there are fix programs for this, sometimes they just don't work.
I thought the combination of the environment DOSBox creates for DOS software to run and modem emulation would be the answer to my problems. Plus, I've always thought running authentic BBS software with all of the old file transfer protocol programs and doors at the speed they were probably operating at when they were at their peak would make the experience more enjoyable. However, snags are present.
I want to make it clear, I am not complaining. I'm using DOSBox for a purpose it was not originally intended for, nor currently is. I'm impressed and delighted that it does as much as it does. These are simply my findings and questions about some of the operations of the modem emulation system within DOSBox.
One thing I'm running into that Synchronet appears to have pacified is the modem's carrier detect (CD) status. WWIV uses FOSSIL, and from what I've read, it's supposed to operate via BIOS interrupt 14h. I realize DOSBox does not emulate a complete BIOS, nor do the programs run in it have transparent access to the host's BIOS, not that it would be useful in this case. I assume this is the reason the terminal output from DOSBox contains a warning, "BIOS INT14: Unhandled call AH=C0 DX= 14". Note: there are 2 spaces between '=' and '14'. Upon further testing, I found the AT command '&C0' would set the modem to have a positive CD status absolutely. However, in sending that command, I received another error,"Modem: Unhandled command: &C0".
C0 would appear to be causing the problem I'm experiencing with some door games reporting 'no carrier' when they are called by the BBS as well as some LORD IGMs, and why exiting any IGM results in being dropped back to the BBS instead of to LORD's IGM selector.
The other item I have yet to figure out is why Zmodem protocol downloads suffer from constant CRC errors. When using a native Windows terminal that has a built-in protocol (Mtelnet, Qmodem Pro) or a native DOS terminal (Telix, Procomm) in DOSBox using external protocols (CEXYZ, Ice-Zmodem), The programs report almost constant retries due to CRC mismatches and sync issues. I use the same protocol programs on the BBS as I do in the terminals, so there should be no amount of error due to program incompatibilities. DOSBox doesn't report any errors during this process in its terminal, so I have no idea what is causing this. X and Ymodem protocols do not suffer from this problem.
Other than these 2 issues, DOSBox is becoming more and more fit to be used to emulate an old PC for any purpose, not just games.
So, does anyone have any insight into these issues? Are my suspicions correct regarding C0? What may be causing my Zmodem dysfunction?
Thanks.