1. Forum
  2. DeveloperNet
  3. C++

  • OpenDoors (BBS door development)

    From Nightfox to All on Thu Sep 17 17:14:09 2009
    Today I started experimenting with OpenDoors to write a BBS door program. I was using MS Visual Studio 2008, compiling a Win32 executable.

    I was running into a couple issues.. For one, using od_printf() didn't output anything to my terminal program on the remote side (I only saw the text locally on my BBS machine).

    Second, since I'm compiling for Windows, OpenDoors seems to expect/assume that I'm writing a program with a WinMain function (rather than the standard main function), as in:
    int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpszCmdLine, int nCmdShow)
    For example, I want to use the od_parse_cmd_line() function. There are 2 versions of that function, one which requires the use of a WinMain function (for its lpszCmdLine), and another for use with DOS, which uses argc and argv. The version of that function that uses argc and argv wasn't recognized by the compiler, so I startd writing my door as a Windows app, using a WinMain function.

    Because I was writing it as a Windows app, the app has a GUI, probably provided by OpenDoors. I was closing the door application on my BBS machine, but after checking the task manager, I noticed that the door program was still running. I've seen this before with GUI apps, and usually it means that the GUI window wa closed but the application hasn't exited yet. This even happened with one of the example doors provided for OpenDoors. So what I'd like to know is, if you're writing a Win32 door with OpenDoors, how do you ensure that the program exits when its GUI window on the BBS machine is closed?

    Has anyone run into these issues and solved them?

    Eric
  • From Mercyful Fate to Nightfox on Wed Sep 23 10:37:17 2009
    Re: OpenDoors (BBS door development)
    By: Nightfox to All on Thu Sep 17 2009 17:14:09

    Today I started experimenting with OpenDoors to write a BBS door program. I was using MS Visual Studio 2008, compiling a Win32 executable.

    I was running into a couple issues.. For one, using od_printf() didn't outp anything to my terminal program on the remote side (I only saw the text loca on my BBS machine).

    The windows part uses sockets to communicate with the BBS, usually DOOR32 drop file, so you'll want to make sure you have this part setup as when you compile win32 doors they no longer use the DOOR.SYS etc.. that DOS doors use. I haven't looked at Opendoors in probably 6 or more years though so i'm not much help beyound that.
  • From Nightfox to Mercyful Fate on Sun Sep 27 08:10:41 2009
    Re: OpenDoors (BBS door development)
    By: Nightfox to Mercyful Fate on Wed Sep 23 2009 10:37:17

    The windows part uses sockets to communicate with the BBS, usually DOOR32 file, so you'll want to make sure you have this part setup as when you co win32 doors they no longer use the DOOR.SYS etc.. that DOS doors use. I haven't looked at Opendoors in probably 6 or more years though so i'm not help beyound that.

    Yeah, I was creating the door for DOOR32 support. Thanks for your reply.

    Nightfox
  • From Mercyful Fate to Nightfox on Mon Sep 28 13:16:08 2009
    Re: OpenDoors (BBS door development)
    By: Nightfox to Mercyful Fate on Sun Sep 27 2009 08:10:41

    Re: OpenDoors (BBS door development)
    By: Nightfox to Mercyful Fate on Wed Sep 23 2009 10:37:17

    The windows part uses sockets to communicate with the BBS, usually DOO file, so you'll want to make sure you have this part setup as when you win32 doors they no longer use the DOOR.SYS etc.. that DOS doors use. haven't looked at Opendoors in probably 6 or more years though so i'm help beyound that.

    Yeah, I was creating the door for DOOR32 support. Thanks for your reply.

    I sorta remember that the door32 drop file path was hard coded, you might want to check the source for that.. it was one of those thigns where i was like @#$% when i looked at it along time ago.. so the system might not be finding it.