Comments for ilink32 Version 5.66 Update for C++ Customers

re: ilink32 Version 5.66 Update for C Customers

2005-04-10T01:32:33-07:00

me too :(

ilink32 Version 5.66 Update for C Customers

2005-03-01T03:28:07-08:00

I follow the link and found nothing.:-(. Then I read your opinions about this update and I'm happy. I solve this error by another way. I create new project and move all units to it. If you see inside .bpr file to and sections you found difference between those two projects. BCB 6.0 add many not required libraries and this cause ilink32 error. I just copy those two sections from new project to old.(You need to close all files before copying, do copy in another text editor and load project again).

ilink32 Version 5.66 Update for C Customers

2005-02-01T02:26:04-08:00

where is link to download ilink32 v. 5.66 Update for command-line tools?

ilink32 Version 5.66 Update for C Customers

2004-12-11T05:56:59-08:00

super !!!

ilink32 Version 5.66 Update for C Customers

2004-12-04T16:49:15-08:00

I downloaded the fix as suggested but only found the fileilink32.exe and no ilink32.dll file. I replaced the oldfile with the new one but the linker continues to crash on me.

re: ilink32 Version 5.66 Update for C Customers

2004-11-08T20:07:26-08:00

Borland gave up and rolled over long ago. The Borland that we have loved and supported for so long is unfortunately no more!

ilink32 Version 5.66 Update for C Customers

2004-11-08T20:05:09-08:00

Unfortunately linker still crashes with the very informative message "Fatal Access Violation. Link Terminated". This is rather a weak and disappointing effort by Borland.

ilink32 Version 5.66 Update for C Customers

2004-10-01T07:07:59-07:00

I have got the impression to better live without it. I have survived a lot of unpredictable crashes using it. But now it has been enough.

ilink32 Version 5.66 Update for C Customers

2004-09-26T02:03:05-07:00

All Borland linkers suck. On numerous occasions I have had to shut down the system, and build 270 files from scratch. On at least two occasions I had to reinstall the entire compiler and various third party components. Why it sucks? Because Borland does not know everything there is to know about APIs and Windows. And support? Forget about it. They are too busy to congratulate themselves on their lousy job and portray themselves as the best guy on the block. Best solution: .NET platform; no more incompatibility problem.

ilink32 Version 5.66 Update for C Customers

2004-09-03T00:24:51-07:00

How can you rate this paper with 5 stars if nothing is said about what is fixed?Luigi