Subj : Re: Borland C++ 5.02 - Unable to Build DOS Programs - CAPDOS32 Fatal To : borland.public.cpp.borlandcpp From : Nathaniel L. Walker Date : Thu Nov 25 2004 07:21 am 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 "Goran Bervar" wrote in message news:41a5a375$1@newsgroups.borland.com... > 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 > > "Nathaniel L. Walker" wrote in message > news:419da192$1@newsgroups.borland.com... > > > > 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 > > > .