Does anyone have Thunder Cat V3.30 BBS door game from TopSoft working on their BBS? I got it from the BBSFiles.com collection on most BBS files section. I am having a hard time getting it run. I loved playing this game. It was my first BBS door on my RBBS system in 1990. I get the editor to run in Dos but tcat.exe cannot open the .ctl file no matter which way I configure it. Any help would be appreciated.
Re: Thunder cat V3.30 BBS door game help
By: Rixter to All on Sat Oct 12 2024 10:36 pm
I have Thunder Cat installed and working on my BBS. I don't think I had to do anything special for it though.
Nightfox
--- SBBSecho 3.20-Linux
* Origin: Digital Distortion: digdist.synchro.net (21:1/137)
Re: Thunder cat V3.30 BBS door game help
By: Rixter to All on Sat Oct 12 2024 10:36 pm
I have Thunder Cat installed and working on my BBS. I don't think I had to do anything special for it though.
Nightfox
--- SBBSecho 3.20-Linux
* Origin: Digital Distortion: digdist.synchro.net (21:1/137)
I am getting the error message: error in module gapqbdr error #6 but I have no idea what error 6 is?
I was getting gapqbdr error #5 error. I had C:\mystic\temp1 in the first line of the .cfg file. I changed that to C:\mystic\temp1\door.sys and then I get the message "Cannot read Door.sys" . Maybe it's looking for the older version of door.sys.
I also can't get it running in my BBS. Says it can't read the Door.sys file.the sample that is given in the documentation mentions tcat.cfg which should be t-cat.cfg or something like t-cat%#.cfg or t-cat1.cfg or t-cat2.cfg depending on how many nodes you run. I was thinking it needed an older door format myself. I am getting help from Chris Johnson from CJ's Place BBS. It ran for him the first time around. I have found a sprinkling of others saying there are getting GAPQBDR Error #6. I cannot find a reference to what #6 even is. A real mystery! Thanks for trying if I find a solution I will share.
I was getting gapqbdr error #5 error. I had C:\mystic\temp1 in the first line of the .cfg file. I changed that to C:\mystic\temp1\door.sys and then I get the message "Cannot read Door.sys" . Maybe it's looking for the older version of door.sys.
|02-=|10Cozmo|02=-
... A .GIF is worth a thousand .TXT.
--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: Lunatics Unleashed (21:3/135)
In my configuration file, I just specify the directory where door.sys
is, but not include door.sys itself.
the sample that is given in the documentation mentions tcat.cfg which should be t-cat.cfg or something like t-cat%#.cfg or t-cat1.cfg or t-cat2.cfg depending on how many nodes you run. I was thinking it needed an older door format myself. I am getting help from Chris Johnson from CJ's Place BBS. It ran for him the first time around. I have found a sprinkling of others saying there are getting GAPQBDR Error #6. I cannot find a reference to what #6 even is. A real mystery! Thanks for trying
if I find a solution I will share.
In my configuration file, I just specify the directory where door.sys
is, but not include door.sys itself.
I tried both ways. If I don't have Door.sys in the path I get the GAPQBDR Error #5 error. When I put Door.sys in it says cannot read Door.sys. So I don't know whats going on there but I can't get it to wok no matter what i try.
What OS/environment are you running it in? I'm running mine with
dosemu2 on Linux.
What OS/environment are you running it in? I'm running mine with
dosemu2 on Linux.
Windows 7 - 32 bit. Also tried Dosbox without out any luck.
I am getting the error message: error in module gapqbdr error #6 but I have no idea what error 6 is?
I was getting gapqbdr error #5 error. I had C:\mystic\temp1 in the first line of the .cfg file. I changed that to C:\mystic\temp1\door.sys and then I get the message "Cannot read Door.sys".
Re: Re: Thunder cat V3.30 BBS door game help
By: Cozmo to Rixter on Sun Oct 13 2024 11:23 am
The path without the filename is the correct setting.
This door kit is picky about the dropfiles it reads. In the case of Mystic's DOOR.SYS file, line 14 (User password) being blank is causing the error #5. Anything at all on that line will suffice to get rid of the error. Then you'll start getting runtime error #6.
Line #46 gets "32768" written to it by default. This line gets read into a 16-bit signed integer with a maximum positive value of 32767. Anything over that results in a runtime error.
There's a utility called CVTDOOR that can be used to manipulate these two lines. Use the utility to add anything to line 14 and set line 46 to any smaller number. By changing these two lines I was able to get the Mystic generated DOOR.SYS file to work.
--- SBBSecho 3.14-Win32
* Origin: The Fool's Quarter, fqbbs.synchro.net (21:1/149)
The path without the filename is the correct setting.
This door kit is picky about the dropfiles it reads. In the case of Mystic's DOOR.SYS file, line 14 (User password) being blank is causing
the error #5. Anything at all on that line will suffice to get rid of
the error. Then you'll start getting runtime error #6.
Line #46 gets "32768" written to it by default. This line gets read
into a 16-bit signed integer with a maximum positive value of 32767. Anything over that results in a runtime error.
There's a utility called CVTDOOR that can be used to manipulate these two lines. Use the utility to add anything to line 14 and set line 46 to any smaller number. By changing these two lines I was able to get the Mystic generated DOOR.SYS file to work.
problem fixed. it was in the door.sys file. I used a ruler and went down all 52 lines of the door sys file based on door.sys on the synchronet wiki which shows what each line is for and valid ranges for some of them. In my case it was line 42 out of range for Tcat v3.30 42 is time credit in
| Sysop: | Gary Ailes |
|---|---|
| Location: | Pittsburgh, PA |
| Users: | 132 |
| Nodes: | 5 (0 / 5) |
| Uptime: | 124:37:21 |
| Calls: | 733 |
| Files: | 2,171 |
| Messages: | 81,555 |