From Newsgroup: alt.bbs.synchronet

Good Day.
Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.
I'm having a few issues that I'm wondering if anyone can assist with.
First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.
I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.
Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).
I migrated the BBS to Server 2003 by simply copying the SBBS directory over. The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.
What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".
Any ideas here?
Thanks in advance.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

Disregard the ERR and the LOGON.LST issue. I forgot that I uppped my account to LEVEL 90 to prevent this door game from being displayed to standard users. I did not have SYSOP logging/statistics turned on.
I'd still be interested in any thoughts on the DoorSource door. Perhaps I need to use REAL modem emulators? (Like NetSerial)?
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

Patched EXEC does not help, either.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Mon Apr 13 2020 04:54 am

From Newsgroup: alt.bbs.synchronet

Good Day.
Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.
I'm having a few issues that I'm wondering if anyone can assist with.
First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.
I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

The Synchronet Virtual UART/FOSSIL driver can also emulate a physical COM Port (UART). The default is to emulate COM1, but that can be changed. Take a look at http://wiki.synchro.net/config:sbbsexec.ini

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).
I migrated the BBS to Server 2003 by simply copying the SBBS directory over. The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.
What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".
Any ideas here?

The errors displayed by the ;ERR sysop command are just the contents of your data/error.log file. You can read that file manually to find out what the errors are.

As for the logon.lst file not getting updated, that could be because you're logging on as a user with quiet-mode enabled or you're logging on as a sysop and you have the sysop excluded from statistics (see setting in SCFG->System->Toggle Options).

digital man

Synchronet "Real Fact" #15:
SBBSecho was introduced (replacing SBBSFIDO) for Synchronet v2 in 1994.
Norco, CA WX: 55.5øF, 89.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

Thanks for the response, DigitalMan. I had seen you post this prior (regarding the Fossil), and have been though all of the settings, adjusted different ways, and am still unable to get this to work.
I'm going to keep trying different workarounds. Something to note; within my code, and command sent to output on the local screen is displayed in the door. Any command to send output via it's library (and via COM), does not display.
I'm going to keep plugging at this.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I've verified the door works direct through COM. I can utilize ESXi's named pipe serial ports to connect WorldGroup to another system running GHOST. The door will execute and traffic will pass. However, since WG/Ghost monitor DCD to determine when the door execution in complete, this doesn't get interpreted over the named pipe - and so Worldgroup sits in the door until either the serial port is disconnected in ESXi, or the (door) system is powered down.
Trying PowerCLI to execute a Serial Port disconnect/reconnect at the virtual machine level to overcome this...but...
Synchronet would be SO much easier!
I'd be happy to pass along the door game if anyone with some know wants to give it a whirl.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Wed Apr 15 2020 02:49 pm

I'd be happy to pass along the door game if anyone with some know wants to give it a whirl.

Sure, upload it here.

Does the program support int14h (FOSSIL)?

If it only supports UART (COM I/O), then you may need to configure the virtual UART driver (sbbsexec.dll) to emulate the specific COM Port you're using (the default is COM1):
http://wiki.synchro.net/config:sbbsexec.ini

digital man

Synchronet/BBS Terminology Definition #21:
DOS = Disk Operating System (as in PC-DOS and MS-DOS)
Norco, CA WX: 76.7øF, 24.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I'll get a ZIP compiled and upload it. Source is QuickBasic 4.5, with DoorSource 4.0 library injected. Unfortunately, there isn't much technical information within DoorSource's documentation to determine how exactly it's trying to communicate. There are parameters to set ADDR/IRQ; and even setting these for a standard COM1 didn't allow it to redirect under Synchronet.
I'll include the DS40 docs in the ZIP as well.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Thursday, April 16, 2020 at 12:10:28 PM UTC-4, brya...@gmail.com wrote:

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I'll get a ZIP compiled and upload it. Source is QuickBasic 4.5, with DoorSource 4.0 library injected. Unfortunately, there isn't much technical information within DoorSource's documentation to determine how exactly it's trying to communicate. There are parameters to set ADDR/IRQ; and even setting these for a standard COM1 didn't allow it to redirect under Synchronet.

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how to attach here...
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Friday, April 17, 2020 at 6:06:44 AM UTC-4, brya...@gmail.com wrote:

On Thursday, April 16, 2020 at 12:10:28 PM UTC-4, brya...@gmail.com wrote:

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I'll get a ZIP compiled and upload it. Source is QuickBasic 4.5, with DoorSource 4.0 library injected. Unfortunately, there isn't much technical information within DoorSource's documentation to determine how exactly it's trying to communicate. There are parameters to set ADDR/IRQ; and even setting these for a standard COM1 didn't allow it to redirect under Synchronet.

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how to attach here...

--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Friday, April 17, 2020 at 6:06:44 AM UTC-4, brya...@gmail.com wrote:

On Thursday, April 16, 2020 at 12:10:28 PM UTC-4, brya...@gmail.com wrote:

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I'll get a ZIP compiled and upload it. Source is QuickBasic 4.5, with DoorSource 4.0 library injected. Unfortunately, there isn't much technical information within DoorSource's documentation to determine how exactly it's trying to communicate. There are parameters to set ADDR/IRQ; and even setting these for a standard COM1 didn't allow it to redirect under Synchronet.

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how to attach here...

I've placed the file on one of my web servers here: http://www.baycountyscanner.org/images/MISCTL.ZIP
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Fri Apr 17 2020 03:06:43

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how
to attach here...

most likely you don't... you should probably send it to DM directly via email... while you're reading a newsgroup, the rest of us are reading the area via QWKnetworking or FTN where file attaches to posts are not copacetic unless they are in private mails ;)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

On Friday, April 17, 2020 at 8:38:22 AM UTC-4, mark lewis wrote:

To: bryandj23
Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Fri Apr 17 2020 03:06:43

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how
to attach here...

most likely you don't... you should probably send it to DM directly via email... while you're reading a newsgroup, the rest of us are reading the area
via QWKnetworking or FTN where file attaches to posts are not copacetic unless
they are in private mails ;)

)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
--- Synchronet 3.18a-Win32 NewsLink 1.112
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

Ahhh...thanks, Mark. Hadn't thought of that angle.

I posted the link to the door above; I tossed it on one of my web servers as I figured that'd be easier. Appreciate the tip!
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Fri Apr 17 2020 03:10 am

From Newsgroup: alt.bbs.synchronet

On Friday, April 17, 2020 at 6:06:44 AM UTC-4, brya...@gmail.com wrote:

On Thursday, April 16, 2020 at 12:10:28 PM UTC-4, brya...@gmail.com wrote:

On Monday, April 13, 2020 at 7:54:08 AM UTC-4, brya...@gmail.com wrote:

Good Day.

Old school BBS sysop here, and I've resurrected my old license of Worldgroup, and am utilizing SBBS for Door games.

I'm having a few issues that I'm wondering if anyone can assist with.

First, I have an old DOS-based Door Game that I personally wrote using QuickBasic 4.5 and DOOR SOURCE libraries (Door Source 4.0). While the door itself executes correctly, SBBS fails to capture any of the communication routines (display text, etc) within the door.

I've tried using Netfoss, but same issue. I can only conclude that Door Source utilizes some sort of hardware-based communication routines on the back end that common Fossil or other redirectors cannot pickup.

Secondly; in debugging my Door, I had to move SBBS from Windows 2000 server to Windows 2003. (Door game would get a division by zero error on 2nd runs in Windows 2000; doesn't occur on 2003).

I migrated the BBS to Server 2003 by simply copying the SBBS directory over.

The only issue I'm having is an error at logon (just saying a critical error occurred, and to check ;ERR). However, my menus have been re-done so that only the game menu is present.

What I have noticed is the C:\SBBS\DATA\LOGON.LST file is not getting updated at logon. I've verified permissions are set to "Everyone - Full Control".

Any ideas here?

Thanks in advance.

I'll get a ZIP compiled and upload it. Source is QuickBasic 4.5, with DoorSource 4.0 library injected. Unfortunately, there isn't much technical information within DoorSource's documentation to determine how exactly it's trying to communicate. There are parameters to set ADDR/IRQ; and even setting these for a standard COM1 didn't allow it to redirect under Synchronet.

I'll include the DS40 docs in the ZIP as well.

Ok. Have the Zip file ready to go. Just trying to figure out how to attach here...

I've placed the file on one of my web servers here: http://www.baycountyscanner.org/images/MISCTL.ZIP

Okay, so I "installed" your door and I/O appears to work fine, though the door game itself didn't really want to work.

First, I created a simple .CFG file (mcsetup.exe didn't seem to work to create one for me, so I just read DS40.DOC and created one with a text editor):

door.sys
My BBS
Mr.
Sysop

This would only work for a single-user configuration since the drop file (door.sys) has to be located in the door's startup directory. There are methods for supporting multiple concurrent users (e.g. creating multiple .CFG files, one for each node and passing the appropriate filename on the MC10.EXE command-line, but that wasn't really relevant to the I/O problem you reported).

Next, I set up the program in SCFG:

Name mc10
Internal Code MC10
Start-up Directory ..\xtrn\mc
Command Line mc10 test.cfg doorsys
Clean-up Command Line
Execution Cost None
Access Requirements
Execution Requirements
Multiple Concurrent Users No
Intercept I/O No
Native Executable No
Use Shell to Execute No
Modify User Data No
Execute on Event No
Pause After Execution No
BBS Drop File Type GAP DOOR.SYS
Place Drop File In Start-Up Directory

Then when running the program, from the BBS, it displays this to the remote user:

= Creating New User File =
= Logging On... =

And then it appears to remote user to just freeze indefinitely.

The game created a file name "DIGI MAN".

Locally, the game displays this: https://1drv.ms/u/s!ApZPvWcrEaRQvNN_2SIEYD_YnEK8hg?e=74f8Uw

And the program then waits for a local keypress before exiting the process and returning control to the remote user.

So yeah, the program didn't really "work", but I/O seemed to work fine. This was tested on 32-bit Windows 7.

digital man

This Is Spinal Tap quote #15:
Review on "Shark Sandwich", merely a two word review: "Shit Sandwich".
Norco, CA WX: 82.7øF, 42.0% humidity, 7 mph NE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

DM:

Thanks for testing it. The fact that you were able to see the "CREATING NEW USER FILE" tells me that the comms are in fact working for you. Those are all sent with the "CALL Send" routine within Door Source.

The errors you saw on the local side seem to indicate the directory structure didn't create. Within your MC folder, the MCINSTAL.EXE should have unzipped RESOURCE.001, 002, etc into subdirectories such as ANSI, PLAYER, WX, INSPECT, etc.

Right after the "Logging On...", the program performs a "SHELL dir$", where dir$ is...aw shit.

I have a hard-coded path in there I was using for testing; I maybe have compiled the wrong code version to send to you.

Either way - the "Creating File" and "Logging on.." that you were able to receive is further/better than where I was able to. I'll try configuring in SCFG as you did, and report back.

Sincerely appreciate your assistance with this. I wrote this in 94; I would have been 16 at the time. The code and routines seriously need some rework.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Thu Apr 23 2020 07:23 pm

From Newsgroup: alt.bbs.synchronet

DM:

Thanks for testing it. The fact that you were able to see the "CREATING NEW USER FILE" tells me that the comms are in fact working for you. Those are all sent with the "CALL Send" routine within Door Source.

The errors you saw on the local side seem to indicate the directory structure didn't create. Within your MC folder, the MCINSTAL.EXE should have unzipped RESOURCE.001, 002, etc into subdirectories such as ANSI, PLAYER, WX, INSPECT, etc.

I got those files, but no sub-directories:

Directory of s:\sbbs\xtrn\mc

04/23/2020 05:47 PM <DIR> .
04/23/2020 04:50 PM <DIR> ..
04/23/2020 05:47 PM 47 DIGI MAN
04/23/2020 05:47 PM 363 DOOR.SYS
04/11/2020 03:11 PM 148,490 DS40.DOC
04/23/2020 05:37 PM 45 JESUJESU
04/12/2020 09:13 PM 141,274 MC10.EXE
04/11/2020 03:40 PM 0 MC10.GGG
12/10/1994 11:15 AM 39,476 MCINSTAL.EXE
04/08/2020 10:10 PM 33,212 MCSETUP.EXE
04/23/2020 05:45 PM 18 path.cfg
02/02/1993 12:34 AM 29,378 PKUNZIP.EXE
04/17/2020 06:01 AM 4,995 README.TXT
12/12/1994 05:55 PM 1,501 RESOURCE.001
12/18/1994 10:44 AM 27,743 RESOURCE.002
12/12/1994 05:55 PM 13,644 RESOURCE.003
12/18/1994 10:44 AM 5,748 RESOURCE.004
12/12/1994 05:55 PM 1,449 RESOURCE.005
04/23/2020 05:40 PM 32 test.cfg

Right after the "Logging On...", the program performs a "SHELL dir$", where dir$ is...aw shit.

I have a hard-coded path in there I was using for testing; I maybe have compiled the wrong code version to send to you.

Either way - the "Creating File" and "Logging on.." that you were able to receive is further/better than where I was able to. I'll try configuring in SCFG as you did, and report back.

Yeah, I figured that was the main point.

Sincerely appreciate your assistance with this. I wrote this in 94; I would have been 16 at the time. The code and routines seriously need some rework.

I know how it is. :-)

digital man

Synchronet/BBS Terminology Definition #54:
PCMS = Programmable Command and Menu Structure (introduced in SBBS v2)
Norco, CA WX: 74.3øF, 47.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

Hi DM. Hope you're having a nice weekend.
Since you still have those RESOURCE.00x files, that indicates that MCINSTAL.EXE was not run to create the necessary directories. No biggie though - your test was exactly what I needed to keep down the troubleshooting road.
I spent some time cleaning up and modifying my code in the game, and finally got back around to trying this out. I reconfigured the door exactly how you have it configured (door in xtrn directory instead of C:\Doors, SCFG set exactly as you have it), and still - only launches locally.
Sidenote: I've had this issue with other doors, and the fix is to configure the door for FOSSIL support; which unfortunately I cannot do with DoorSource.
So, I started changing settings in SBBSEXEC.ini. Pertinent settings here are all default. I did enable debugging, but haven't gone that route yet. So, Virtualize=true, Comport=1. I tried switching virtualize to false; but no change. In fact, my other doors kept working even after changing to false.
I ran process monitor against loading the BBS, and never once did I see a process try to read the SBBSEXEC.ini file. Perhaps I wouldn't see anything here, depending on how it's actually read. Just found it interesting.
SBBSEXEC.dll is 48kb, dated 9/5/2005, 10:31pm. SBBSEXEC.VXD is 27KB, dated 7/20/2001. Perhaps something here?
I may attempt a complete new SBBS install on a new VM. Hmm. Just thought of something.
The image of SBBS that I'm running is a (someone else)-customized version that strips most of the menuing system; as I'm using SBBS as a Doorgame server behind Worldgroup/MBBS. Been quite awhile since I installed it, but I believe it was a "DOOR SERVER" build of SBBS. (Instructions followed were here: http://dmud.thebbs.org/wg/setup.htm).
I also had found the "SBBS-Uart-Patch" and had installed that in an attempt to fix that issue.
Can you think of anything else I may be missing?
Meanwhile, I'll try a fresh SBBS install on another VM and report back.
Thanks again!
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

Update..

So I learned the VXD file is for Win9x installations, not WinNT as I'm running.

Fresh install of 2003 R2, fresh install of latest SBBS 3.17b

"Mission Control" runs fine locally. When launched with DOSXTRN, I get an Overflow error in the DS3 (Doorsource) module. Hmm. New road to look down.

--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Sun Apr 26 2020 04:53 am

From Newsgroup: alt.bbs.synchronet

Hi DM. Hope you're having a nice weekend.
Since you still have those RESOURCE.00x files, that indicates that MCINSTAL.EXE was not run to create the necessary directories.

Yeah, I ran that. And even tried answering both Y and N to the prompt, but no directories were created.

No biggie
though - your test was exactly what I needed to keep down the troubleshooting road.
I spent some time cleaning up and modifying my code in the game, and finally got back around to trying this out. I reconfigured the door exactly how you have it configured (door in xtrn directory instead of C:\Doors, SCFG set exactly as you have it), and still - only launches locally.
Sidenote: I've had this issue with other doors, and the fix is to configure the door for FOSSIL support; which unfortunately I cannot do with DoorSource. So, I started changing settings in SBBSEXEC.ini. Pertinent settings here are all default.

The defaults (e.g. if the sbbsexec.ini file is missing) should normally work just fine. But for what's worth, here's is the sbbsexec.ini file I had in place when I ran your door:

; exec/sbbsexec.ini

loglevel=info

[UART]
Virtualize=true

;[bre]
;YieldInterval=0.05

[dsz|gsz]
YieldInterval=3

[war]
CanDisconnect=false

[war.UART]
Virtualize=true

[sinkem.UART]
virtualize=true

[yt]
YieldInterval=0.01

[fdsz]
loglevel=debug

[lore]
virtualize=false
loglevel=debug

;[cmd.exe.UART]
;virtualize=false

I did enable debugging, but haven't gone
that route yet.

You would need to use a Windows debug log viewer to see the debug output.

So, Virtualize=true, Comport=1. I tried switching
virtualize to false; but no change. In fact, my other doors kept working even after changing to false.

Virtualize is only for the UART feature, so enabling/disabling that function would have no impact on programs that use/work with FOSSIL.

I ran process monitor against loading the BBS, and never once did I see a process try to read the SBBSEXEC.ini file. Perhaps I wouldn't see anything here, depending on how it's actually read. Just found it interesting. SBBSEXEC.dll is 48kb, dated 9/5/2005, 10:31pm.

Yeah, that's pretty old now. The latest build of sbbsexec.dll is from 2011. The copy of that file that matters is the one in your Windows/System32 directory (not the one in sbbs/exec, if there is one) - but only if you're running Windows Vista or later. If you're running pre-Vista Windows, then the copy/version in your sbbs/exec is used. But I would just have it both places and make sure they're in sync.

SBBSEXEC.VXD is 27KB, dated
7/20/2001. Perhaps something here?

VXD's are only used on Windows 9x. So you can safely delete that file now. :-)

I may attempt a complete new SBBS install on a new VM. Hmm. Just thought of something.
The image of SBBS that I'm running is a (someone else)-customized version that strips most of the menuing system; as I'm using SBBS as a Doorgame server behind Worldgroup/MBBS. Been quite awhile since I installed it, but I believe it was a "DOOR SERVER" build of SBBS. (Instructions followed were here: http://dmud.thebbs.org/wg/setup.htm).
I also had found the "SBBS-Uart-Patch" and had installed that in an attempt to fix that issue.

What patch is that? Do you mean the DOSXTRN.EXE?

Can you think of anything else I may be missing?
Meanwhile, I'll try a fresh SBBS install on another VM and report back. Thanks again!

Okay.

digital man

Synchronet "Real Fact" #54:
The Synchronet source code consists of over 500,000 lines of C and C++.
Norco, CA WX: 85.3øF, 34.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

Update v2:

Executing the door via shell, using a batch file to call:

mc10.exe mc.cfg door.sys

Seems to be working for me on 3.l7b! (Still unsure why the overflow via DOSXTRN). Going to try this on the older version.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

Update v3:

Would not work on my install of 3.13a configured the same as on 3.17b.

--Copied DOSXTRN.EXE, SBBSXTRN.DLL and SBBSXTRN.INI from the 3.17b install to the 3.13a install.

The game is now working, with "Use Shell to Execute".

DM: I'll still compare your INI to mine, as it still leaves me curious why your mileage varies.

Thanks again for the help-think I'm finally satisfied. LOL!!
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Sun Apr 26 2020 12:09 pm

From Newsgroup: alt.bbs.synchronet

Update v2:

Executing the door via shell, using a batch file to call:

mc10.exe mc.cfg door.sys

Seems to be working for me on 3.l7b! (Still unsure why the overflow via DOSXTRN). Going to try this on the older version.

Make sure you get/use the latest dosxtrn.exe.

digital man

Synchronet "Real Fact" #96:
Synchronet v3.14a was released in December of 2006 (1 year after v3.13a). Norco, CA WX: 87.2øF, 35.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Door game fight and error at logon
By: bryandj23 to alt.bbs.synchronet on Sun Apr 26 2020 01:22 pm

DM: I'll still compare your INI to mine, as it still leaves me curious why your mileage varies.

I don't think it's the .ini file. It's more likely that I'm running a different version of Windows (i.e. Windows 7). And of course, that ancient v3.13a build of Synchronet could have all kinds of bugs that could cause you issues.

digital man

This Is Spinal Tap quote #23:
David St. Hubbins: I envy us.
Norco, CA WX: 87.2øF, 35.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

From Newsgroup: alt.bbs.synchronet

Agreed; ultimately need to upgrade. I'm a bit concerned with following the upgrade path, given that this is a "customized" build so to speak; but will snapshot the VM prior to each to verify everything's kosher.

--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

bryandj23 wrote to alt.bbs.synchronet <=-

Agreed; ultimately need to upgrade. I'm a bit concerned with
following the upgrade path, given that this is a "customized"
build so to speak; but will snapshot the VM prior to each to
verify everything's kosher.

Agreed about..... what? You didn't quote anything or provide any
context, so nobody knows what you're talking about here.

I realize you're posting from Usenet, but you'll need to try
harder.



... Would you like to wake up from this dream?
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

From Newsgroup: alt.bbs.synchronet

On Sunday, April 26, 2020 at 5:11:44 PM UTC-4, Digital Man wrote:

I don't think it's the .ini file. It's more likely that I'm running a different >version of Windows (i.e. Windows 7). And of course, that ancient v3.13a build of Synchronet could have all kinds of bugs that could cause you issues.

digital man

Agreed. Need to upgrade.
--- Synchronet 3.18a-Win32 NewsLink 1.112
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net