I installed Galactic Dynasty 2 in Mystic on WIN7 32 bit. When the door loads it starts with the first ansi screen and says to "Hit any Key" When I hit any key nothing happens the games just locks up and i have to disconnect from the BBS.

Below is my .bat file and Menu command:

@echo off
C:
cd \mystic\doors\gdynasty2
GalacticDynasty2.exe c:\mystic\temp%1\door32.sys


Menu Command:
(D3) Exec DOOR32 program c:\mystic\netfoss\nf.bat /N%3 /H%0 c:\mystic\doors\gdynasty2\gdynasty2.bat %N

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)

I installed Galactic Dynasty 2 in Mystic on WIN7 32 bit. When the door loads it starts with the first ansi screen and says to "Hit any Key"
When I hit any key nothing happens the games just locks up and i have
to disconnect from the BBS.

Are you seeing the ANSI screen on the terminal (remote) side or just the BBS side? It shouldn't be possible for the remote to see the game at all with it configured as it is currently.

Menu Command:
(D3) Exec DOOR32 program c:\mystic\netfoss\nf.bat /N%3 /H%0 c:\mystic\doors\gdynasty2\gdynasty2.bat %N

You won't need to use NetFoss for games that use a DOOR32.SYS drop file. NetFoss acts as a shim between the network socket the user is connected to and older doors which need to communicate via a FOSSIL driver. NetFoss lets the door 'think' it is communicating over a serial connection. DOOR32.SYS doors communicate directly via the network socket.

@echo off
C:
cd \mystic\doors\gdynasty2
GalacticDynasty2.exe c:\mystic\temp%1\door32.sys

You also should call DOOR32.SYS doors directly unless there is a specific reason not to. Using a batch file sometimes interferes with socket inheritance even though it shouldn't. Almost all DOOR32.SYS doors will automatically change to the program's directory so the batch file isn't needed. Try having the menu call the game directly using the menu data:

c:\mystic\doors\gdynasty2\GalacticDynasty2.exe c:\mystic\temp%N\door32.sys


--- MultiMail/Win v0.52
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

You also should call DOOR32.SYS doors directly unless there is a
specific reason not to.

You will need a batch file on mystic. Synchronet can set the working
directory (so it's not needed there) but mystic doesn't.

You won't need to use NetFoss for games that use a DOOR32.SYS drop
file.

This is almost certainly the cause.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.24-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

c:\mystic\doors\gdynasty2\GalacticDynasty2.exe
c:\mystic\temp%N\door32.sys

That seemed to do the trick. I didn't know there was no need to use NetFoss for Door32.

But I still used the Batch file.

@echo off
c:
cd \mystic\doors\gdynasty2
GalacticDynasty.exe %1

and Menu Command:
c:\mystic\doors\gdynasaty2\gdynasty2.bat c:\mystic\temp%1\door32.sys

The more Install doors the more I realize no 2 doors are the same

Thanks Wall E.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)

Hey Wall E. are you having problems logging into Lunatics? Let me Know?

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)