Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Nathaniel » Fri, 19 Nov 2004 16:46:58



Doesn't work. /sigh/
Thanks for reply though, much appreciated.

Anyone on Team-B have any workaround for this?!?!
 
 
 

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Bob Gonde » Sat, 20 Nov 2004 03:22:26


What version are you using?
Are you compiling from the IDE or the command line?
Try it from the command line.
If it still doesn't work from there, post your commands.

 
 
 

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Nathaniel » Sat, 20 Nov 2004 13:55:03


it works from the command-line, but not from within the IDE. It
hangs I think because of the @response-file. I took the capdos.exe
from my Turbo C++ 4.5 install disk and renamed it to capdos32.exe
and got it to link once, but it started crashing again after that.
If I remove capdos32, it won't link at all because it will just
tell me "TLINK.EXE - CANNOT LOCATE CAPDOS32.EXE".

I am using Borland C++ 5.02. Thanks for your help.
 
 
 

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Nathaniel » Sat, 20 Nov 2004 15:32:34


Okay, I contacted tech support and they sent me to a webpage. Didn't help, but after playing around with the compatibility setting I see that Windows 95/98/Me compatibility allows it to link 16-Bit applications... at the expense of all graphics on every BWCC button in the IDE. Sooo.... I decided to just write an ObjectScript to Generate a Makefile from within the IDE and run my little inserted tool menu item for "Build Via Make" and it works wonderfully.

I can still compile to get any errors in my source code, and you can't debug 16-Bit apps in the IDE anyways (Have TCWin4.5 and BC++3.1/TC++3.0 for that). So I guess I'm happy.

Thanks for all the help guys, I was really frustrated! Grr...
 
 
 

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Goran Berv » Fri, 26 Nov 2004 18:18:19

I don't know if it will be of any help, but I can link DOS app's under XP
without any problems from within IDE and from DOS box without any problems
with BC 5.02, all valid patches applied. I do not have any ".pif" files in
Windows root directory besides _defualt.pif (*) and I have not altered
"config.nt" or "autoexec.nt" files in "Windows\System32" directory. Anyhow,
I have attached all files zipped in "borland.public.attachments" newsgroup
if they will be of any help.

(*) I have no idea what "_default.pif" is for. Looking at it I think I
created it sometime in the past for whatever reason as it starts
"_default.bat" - which is missing. I imagine you don't need it at all but
have no time to investigate. You never know if Bill is around :-)

I suppose you already know that but - you do not have any long names in
Borland C++ install directory and/or in your project, right? And
BTW, Turbo Debuggger (stand alone) shipped with BC 5.02 works just fine with
DOS apps under XP.

goran



help, but after playing around with the compatibility setting I see that
<snip>
 
 
 

Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal

Post by Nathaniel » Fri, 26 Nov 2004 22:21:20

Still won't link. Our autoexec nad config files were identical, i had
played with the other _default file so I replaced it and it still doesn't
link.

Nope, I installed to \bc5 and all my projects are in \projects folder on my
hd, which is valid short filename for directory



Anyhow,
with