Category : BBS Programs+Doors
Archive   : TONSMOD.ZIP
Filename : ELRIC43A.MOD
49/50: Elric43: Fix
Name: Lord Elric #1 @18251
Date: Tue Jun 26 01:00:22 1990
I worked on that a bit more, and still seem to find that is the ONLY problem
with WWIV and Turbo C++, however, it has come to my attention that under
certain circumstances, it still will not compile correctly. To rectify this, I
have rewritten the mod, which now basically says to replace every occurance of
_VideoInt(); with "geninterrupt(0x10)".
Elric
50/50: elric43...new version
Name: Lord Elric #1 @18251
Date: Tue Jun 26 01:00:40 1990
Elric 43
How to Compile WWIV under Turbo C++
To say this is a trivial mod doesn't even begin to describe it. The
problem comes from Wayne Bell using a non-standard unofficial function
to do things. In short, the _VideoInt function. All it does is generate
interrupt 10. But, apparently under Turbo C++, they changed its behavior
somewhat.
To make things easy on you, heres all you have to do.
/** this step is indeed a form step, much like a form letter **/
From DOS, in your dir where you keep your source....
PKZIP SOURCE *.c *.h
If you already have a source zip file, then
PKZIP -f source *.c *.h
This way you have a copy of everything before you screw it up with a bad mod.
If you decide to take the mod out, it's as easy as
PKUNZIP -x source
and hit Y to overwrite any files you changed.
/** we now resume our regularly scheduled mod with step 2.... **/
2. Previously I just redefined _VideoInt() in Vardec, however, I found this
would not work in some cases...so, you really ought to do this the hard way.
Basically, everywhere you see the line
_VideoInt();
replace it with
geninterrupt(0x10);
The following files have _VideoInt(); in it, for your reference.
COM.C (1 time)
CONIO.C (18 times)
EXTERN.C (1 time)
RETURN.C: (18 times)
But just to be sure, you might type
grep -i "_VideoInt();" *.c
and see which files are listed.
3. End of mod. Re-compile.
The only other thing I found in the stock 4.11 source code was a call in
conio.c, which was
topscreen(0);
which should be
topscreen();
You might want to check for that. But since that would not compile under
Turbo C 2.0 either, I will assume that has already been fixed in your source
code.
/** hey, it's the form info file **/
As usual, I take no responsibility for hard drive crashes, death in the
family, or end of the world as we know it resulting from this mod.
It's your fault if you didn't back up the files before you made the mod.
It's your fault if you don't back up your ENTIRE hard drive AT LEAST once
a month.
It works on my system with Turbo C 2.0, WWIV 4.1, V20/8088, 640K/640EMS,
Dos 3.3.
If you use this, the only payment I ask is that you send me a note through
WWIVLink to 1@18251 saying you are using it...not too much to ask is it?
-------------------------------------------------------------------------------
Strawberry Macaw #1 @3502
Sat Jun 30 00:17:18 1990
RE: More from ELRIC on getting WWIV and TCC+ to work:
I just successfully compiled WWIV with Turbo C++ and I thought I'd confirm the
fact that Lord Elric's mod works. I tried compiling it without any changes
first, and although it compiles okay, it locks up immediatedly when you run
it. I had to do three things to get it to compile properly:
1. Write a new BBS.PRJ file in the new Turbo C++ format.
2. Disable the "function should return a value" warning (or tolerate the
warnings)
3. Add the line, "#define _VideoInt(); geninterrupt(0x10); to the end of
VARDEC.H per Lord Elric's post.
I also disabled "Debug info in OBJs" to reduce the file size by over 100k. I'm
running the Turbo C++ compiled BBS right now, and so far nothing has gone
wrong...gone wrong...gone wrong...gone wrong...gone wrong...gone wrong...gone
From the Parrot Jungle, host of the Civil Liberties Debate Forum
and the new Brain Teaser Sub (math & logic puzzles).
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/