![borland c for windows 8.1 borland c for windows 8.1](https://blog.longbowsoftware.com/wp-content/uploads/2017/08/Updated-the-Borland-Root-path-300x209.jpg)
- #BORLAND C FOR WINDOWS 8.1 MANUALS#
- #BORLAND C FOR WINDOWS 8.1 64 BIT#
- #BORLAND C FOR WINDOWS 8.1 UPDATE#
Thanks Microsoft! But there is a solution.ĭelphi 7 still works.
![borland c for windows 8.1 borland c for windows 8.1](https://4.bp.blogspot.com/-kFpdAsqhehU/U94sgpZMAUI/AAAAAAAAAjk/Mljd-HAQbIQ/s1600/2014-08-03_193445.jpg)
#BORLAND C FOR WINDOWS 8.1 UPDATE#
They are missing an older version of the dotNET framework which was there in Windows 8 but vanished in the update process. I hope this helps others to fix that problem, but I wrote this post mostly to find this information later if I need it again. For many older products, original owners and licensing are impossible to verify.
#BORLAND C FOR WINDOWS 8.1 MANUALS#
(The actual build script is a bit more involved because it allows to call several different Delphi versions depending on an environment variable.)Īfter this change the build script worked again. The following old software development tools are in stock and for sale by EMS Professional Software.Unless otherwise specified, each product includes ONLY original manuals and media in usable condition. SET PATH=%FrameworkDir%%FrameworkVersion% %FrameworkSDKDir% %OldPath% SET FrameworkDir=%SystemRoot%\Microsoft.NET\Framework\ I changed my build script to work around this issue:.I didn’t really like that approach either so I went for option 3. So another option to fix the problem is to change the FrameworkDir to point to …\Framework\ rather than …\Framework64\. I guess this was fixed in later versions. The Delphi 2007 installer is probably using some outdated method to find the dotNET framework, which works only on 32 bit Windows. I found that for some reason the rsvars.bat script contained the FrameworkDir=C:\Windows\Microsoft.NET\Framework64\įollowed PATH=%FrameworkDir%%FrameworkVersion% %FrameworkSDKDir% %PATH%.
#BORLAND C FOR WINDOWS 8.1 64 BIT#
I didn’t like that approach because the build process is 32 bit, so why should it involve the 64 bit dotNET framework at all?