I'm having problems with a game that seems to defy all attempts for me to get it to detect ANSI.

It actually wants to communicate through COM1:. I setup a virtual serial port connection with socat and two tty devices. It was giving me "lost carrier" when running but I worked with the dosemu2 author and now got past that issue.

The software appears to be sending ^[6n to get the cursor position and using that to determine if ANSI is present. Of course, since it's sending out the serial port, it isn't getting a response.

I'm not sure how I would go about telling sbbs that anything out of the serial port should to go the tcp/ip connection. I thought that Synchronet was supposed to deal with taking the com trafic and shuffling to the user's tcp/ip connection.

Am I misunderstanding? Can someone maybe shed some light on the issue? This is the first time I've had a door act in this manner.

The game is zwordz if anyone is interested...and already comes with a few challenges in itself.

Oh, there's a /FD options to make it use the fossil driver.

Right now, open to suggestions.

Thanks,

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: How Synchronet interacts with DOSEMU?
By: nelgin to All on Wed Jul 24 2024 07:29 pm

I'm having problems with a game that seems to defy all attempts for me to get it to detect ANSI.

It actually wants to communicate through COM1:. I setup a virtual serial port connection with socat and two tty devices. It was giving me "lost carrier" when running but I worked with the dosemu2 author and now got past that issue.

The software appears to be sending ^[6n to get the cursor position and using that to determine if ANSI is present. Of course, since it's sending out the serial port, it isn't getting a response.

Most doors (especially those developed using a door development kit) read BBS drop files (e.g. door.sys) to determine the terminal type (e.g. ANSI or not). I'd certaily look/hope for such a option with this door.

I'm not sure how I would go about telling sbbs that anything out of the serial port should to go the tcp/ip connection. I thought that Synchronet was supposed to deal with taking the com trafic and shuffling to the user's tcp/ip connection.

Synchronet for Windows does include a virtual UART driver for that purpose (only for 16-bit DOS programs), but nothing like that for Synchornet for *nix.

Am I misunderstanding? Can someone maybe shed some light on the issue? This is the first time I've had a door act in this manner.

The game is zwordz if anyone is interested...and already comes with a few challenges in itself.

Oh, there's a /FD options to make it use the fossil driver.

And when you use that option, it still writes to a UART?

Right now, open to suggestions.

dosemu does the interception of DOS program I/O in your case, so unless this is a native/32-bit door, that's where you'd need to look I suppose.
--
digital man (rob)

Steven Wright quote #10:
The early bird may get the worm, but the second mouse gets the cheese.
Norco, CA WX: 91.3øF, 35.0% humidity, 9 mph SW wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: How Synchronet interacts with DOSEMU?
By: Digital Man to nelgin on Wed Jul 24 2024 17:49:54

Most doors (especially those developed using a door development kit) read BBS drop files (e.g. door.sys) to determine the terminal type (e.g. ANSI or not). I'd certaily look/hope for such a option with this door.

It does support door.sys but where do I find the terminal type in it? Assuming this is an old game and only supports the original 31 lines?

I'm not sure how I would go about telling sbbs that anything out of the serial port should to go the tcp/ip connection. I thought that Synchronet was supposed to deal with taking the com trafic and shuffling to the user's tcp/ip connection.

Synchronet for Windows does include a virtual UART driver for that purpose (only for 16-bit DOS programs), but nothing like that for Synchornet for *nix.

Could there be something for Linux in SBBS to do this? I guess it would need some sort of virtual com driver in sbbs to take the com1 output and route it elsewhere?

Oh, there's a /FD options to make it use the fossil driver.

And when you use that option, it still writes to a UART?

Yes. It seems to.

dosemu does the interception of DOS program I/O in your case, so unless this is a native/32-bit door, that's where you'd need to look I suppose.

No, this is a 16 bit DOS program running on DOSEMU so ...I dunno.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: How Synchronet interacts with DOSEMU?
By: nelgin to Digital Man on Thu Jul 25 2024 12:03 am

Re: How Synchronet interacts with DOSEMU?
By: Digital Man to nelgin on Wed Jul 24 2024 17:49:54

Most doors (especially those developed using a door development kit) read BBS drop files (e.g. door.sys) to determine the terminal type (e.g. ANSI or not). I'd certaily look/hope for such a option with this door.

It does support door.sys but where do I find the terminal type in it? Assuming this is an old game and only supports the original 31 lines?

Line 20 of door.sys = GR when the user's terminal supports color and ANSI "graphics" (CP437 characters).

I'm not sure how I would go about telling sbbs that anything out of the serial port should to go the tcp/ip connection. I thought that Synchronet was supposed to deal with taking the com trafic and shuffling to the user's tcp/ip connection.

Synchronet for Windows does include a virtual UART driver for that purpose (only for 16-bit DOS programs), but nothing like that for Synchornet for *nix.

Could there be something for Linux in SBBS to do this? I guess it would need some sort of virtual com driver in sbbs to take the com1 output and route it elsewhere?

This is a DOS program? It would require something else... like what dosemu does already.

Oh, there's a /FD options to make it use the fossil driver.

And when you use that option, it still writes to a UART?

Yes. It seems to.

That sounds like a bug then.

dosemu does the interception of DOS program I/O in your case, so unless this is a native/32-bit door, that's where you'd need to look I suppose.

No, this is a 16 bit DOS program running on DOSEMU so ...I dunno.

Right, so in that case dosemu is the thing that would need to do any UART redirection to stdio (which SBBS then redirection to socket I/O).
--
digital man (rob)

Sling Blade quote #14:
Karl Childers: Some folks call it a sling blade, I call it a kaiser blade. Norco, CA WX: 73.3øF, 63.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: How Synchronet interacts with DOSEMU?
By: Digital Man to nelgin on Thu Jul 25 2024 01:31:37

Line 20 of door.sys = GR when the user's terminal supports color and ANSI "graphics" (CP437 characters).

Ah ok. Not immediately obvious but makes sense.

Right, so in that case dosemu is the thing that would need to do any UART redirection to stdio (which SBBS then redirection to socket I/O).

I think we're getting to the bottom of it. Thanks.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: How Synchronet interacts with DOSEMU?
By: Digital Man to nelgin on Thu Jul 25 2024 01:31:37

I got it working, thank you again.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: How Synchronet interacts with DOSEMU?
By: nelgin to Digital Man on Thu Jul 25 2024 12:00 pm

I got it working, thank you again.

Care to share how?
--
digital man (rob)

Breaking Bad quote #31:
Feels like one of those cones put on dogs so they don't lick their own balls. Norco, CA WX: 62.9øF, 82.0% humidity, 0 mph NNW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: How Synchronet interacts with DOSEMU?
By: Digital Man to nelgin on Sun Jul 28 2024 03:34:02

I got it working, thank you again.

Care to share how?

I fixed a typo :)

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com