From: Jochen Buchholz Spam User Newsgroups: comp.os.msdos.djgpp Subject: djgpp and Windows NT - headerfile and XXXXXXXX.XXX filename problem Date: Thu, 22 Jul 1999 02:30:31 +0200 Organization: Uni Dortmund Message-ID: <37966627.5BF87288@sx2.HRZ.Uni-Dortmund.DE> NNTP-Posting-Host: dial-143167.hrz.uni-dortmund.de Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------FA831520E14A0412BB81D96E" X-Trace: nx6.HRZ.Uni-Dortmund.DE 932603423 454 129.217.143.167 (22 Jul 1999 00:30:23 GMT) X-Complaints-To: news AT hrz DOT uni-dortmund DOT de NNTP-Posting-Date: 22 Jul 1999 00:30:23 GMT X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en Lines: 73 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com --------------FA831520E14A0412BB81D96E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The first thing that I have to say is, I hate Mirco$oftt. OK, I'am an Unix guru and be dammed to export my, under Unix, very fine running program to Mirco$oft. My first decision was djgpp, and I installed him to Windows NT. After testing an Hello World and other simple programs, I put the sources of my programm to the NT machine to test it also. But I got always a message that gcc could not find any header files. Then I tested it at home under my Windows 95 system with djgpp and everything works fine. Next day I archived my programm executeable with all ini files and transfer it to th NT workstation. I start it there and I got an Message that my program cant open an inifile with name IN_BSP_KAP.TXT - under Windows 95 it has no problems to open it?!?!?? The second action of the program is, if somehing with the inifile is wrong, to write an errorfile with name "dd-calc-err.txt", but under NT it has the name "dd_calc_.txt"!! Whats wrong? I can generate files like "halihalloblablabla.txt" by hand under NT. Is it possible that the Win95 executeable want's to have a filenames with XXXXXXXX.XXX notation under Windows NT? thanks in advance Jochen I try to see it from a funny side and this picture help me a little bit ;-) http://metalab.unc.edu/Dave/Dr-Fun/html/Dr-Fun/df9507/df950713.jpg -- __ ______ _____ Jochen Buchholz __ / // __ // ___/\ http://www.rimnet.de/~buchholz / /_/ // /_/ // __/\\/ su0473 AT sx2 DOT HRZ DOT Uni-Dortmund DOT DE /_____//_____//____/\ Tel: +49-172-9585956 --------------FA831520E14A0412BB81D96E Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit The first thing that I have to say is, I hate Mirco$oftt. OK, I'am an Unix guru and be dammed to export my, under Unix,  very fine running program to Mirco$oft. My first decision was djgpp, and I installed him to Windows NT. After testing an Hello World and other simple programs, I put the sources of my programm to the NT machine to test it also. But I got always a message that gcc could not find any header files. Then I tested it at home under my Windows 95 system with djgpp and everything works fine. Next day I archived my programm executeable with all ini files and transfer it to th NT workstation. I start it there and I got an Message that my program cant open an inifile with name  IN_BSP_KAP.TXT - under Windows 95 it has no problems to open it?!?!?? The second action of the program is, if somehing with the inifile is wrong, to write an errorfile with name "dd-calc-err.txt", but under NT it has the name "dd_calc_.txt"!! Whats wrong? I can generate files like "halihalloblablabla.txt"  by hand under NT. Is it possible that the Win95 executeable want's to have a filenames with XXXXXXXX.XXX notation under Windows NT?

thanks in advance

    Jochen

I try to see it from a funny side and this picture help me a little bit ;-) http://metalab.unc.edu/Dave/Dr-Fun/html/Dr-Fun/df9507/df950713.jpg 

-- 
       __ ______ _____        Jochen Buchholz
  __  / // __  // ___/\       http://www.rimnet.de/~buchholz 
 / /_/ // /_/ // __/\\/       su0473 AT sx2 DOT HRZ DOT Uni-Dortmund DOT DE
/_____//_____//____/\         Tel:   +49-172-9585956
  --------------FA831520E14A0412BB81D96E--