HS>HS>There are differences between them.
HS>CB>There are some differences, _but_ the differences are NOT relevant for
HS>CB>a project like this.  They are the same language.  It's the 'frills'
HS>if you actually have something interesting to contribute, then do it, 
on't
HS>tell me these meaningless things. As you gain experience and knowledge and 
a
I'll keep telling you 'meaningless things' until you actually read what
is said.  If you've ever actually used BC30 and TC30 or had porting
experience between multiple compilers, you'd probably understand what
is being said.
HS>soon as you actually get a compiler you will realize that there ARE
HS>differences between the two.
Such as....?  The C language they implement are identical.  All the
other differences (such as Win support, better performance
optimizations, etc.) are totally irrelevant for this program.
HS>ahahahaha, your so stupid.
HS>"should require few to no changes", then why doesn't it compile smoothly 
wit
HS>tc then? And just before you were asking "how do i compile it with tc?".
You didn't listen.  As I've said several times,  it _DOES_ COMPILE
SMOOTHLY. Without any errors or warnings.  The building runs nice and
smooth using the Turbo C 3.0 project file that is provided in the
Wolf3d source.
The problem is that it doesn't run correctly.  And that could be caused
by Turbo C 3.0's known bug in dealing with huge pointers.  It's fairly
well known that TC30 does have a huge pointer bug, and Wolf3D does do
huge memory, but without delving deeply into the source, I can't say
whether the bug is the problem.  It's also true that some people with BC
have had no luck compiling and running it, either.
You don't 'fix' a correctly compiling program that is designed for a
specific memory model by switching it to another memory model.  That's
not fixing it, especially since there is a good chance there is nothing
what so ever wrong with the program itself but a bug in the compiler.
--- QScan/PCB v1.19b / 01-0162
---------------