Subj : Re: C++Builder BCC32.CFG error To : borland.public.cpp.borlandcpp From : "Ed Mulroy [TeamB]" Date : Thu Nov 20 2003 07:17 am With Win98 first edition and second edtion it worked ok for me. Just for drill, here's what I did for Win95, 98 and 98SE. Installed the compiler into the default location, c:\borland\bcc55 Edited the c:\autoexec.bat and added this line at the end of the file path=%PATH%;c:\borland\bcc55\bin Created a file named c:\borland\bcc55\bin\bcc32.cfg The file contained the following two lines -Ic:\borland\bcc55\include -Lc:\borland\bcc55\lib note that the 2nd char on the first line is a capital 'i', not a lower case 'L' and not the digit one Created a file named c:\borland\bcc55\bin\ilink32.cfg The file contained only the second line above, the one which starts with -L The changes to autoexec.bat do not take hold until you restart Windows for Win98 or reboot for Win95. That worked for me on 3 different machines. The only wrinkle I have found is an apparently random glitch in how Win98/Win98SE resolves paths but that glitch is not related to compile time, not related to finding header files. This glitch also happens with other programs so is not something related to the compiler. When that glitch occurs, Windows gives the error that it cannot find ilink32.exe I did not troubleshoot the glitch but just found a quick fix and used it. The fix I used is to put a copy of ilink32.cfg into the directory where I am building the project. Since I use a directory for each project the easiest way I found to do that is to place a copy of ilink32.cfg in the root directory (in C:\) so that it is easy to copy with the command copy c:\ilink32.cfg .. Ed > John P. Streetman wrote in message > news:3FBC9445.1806461@alltel.net... > > i have win98. i think it might be first edition. and using > command line tools from bcb5 version. the downloadable > compiler. though maybe either my path was wrong or > as suggested i didn't have it installed right. it looked > as though it was. thanks for your time. John .