| View previous topic :: View next topic |
| Author |
Message |
RobBliss
Joined: 14 Jul 2007
Posts: 7
Location: North Carolina, USA
|
 Posted: Sun Oct 14, 2007 5:41 pm Post subject: Problems running FTN95 in Visual Studio 2005 |
 |
|
When set to .NET framework I get the following error message:
"Unable to communicate with FTN95LIB"
When I switch to Win32 Framework, program complies and links, but when I run it (w/ or w/out debug) it opens a cmd window and hangs.
The *.exe runs fine under Plato or an MKS k-shell.
How can I get full VS functionality (either .NET or Win32, don't really care).
Rob Bliss |
|
| Back to top |
|
 |
Andrew
Joined: 09 Sep 2004
Posts: 232
Location: Frankfurt, Germany
|
| Posted: Sun Oct 14, 2007 11:30 pm Post subject: |
|
|
A couple of questions:
Which version of Visual Studio are you using? (oops, saw the title of the thread - VS 2005)
Are you running the latest version of FTN95 and the plugin?
The error related to ftn95lib is one that I have not seen for some time. Can you let me know what the error number is, as I am sure that this message was removed. If you are up to date, can you ensure you only have one copy of the compiler, dbk_link and salflibc.dll on the path.
The other issue with loading Win32 programs is also odd. There is one problem that we know of related to a particular anti-virus program causing problems with DLL relocation (which is solved internally and will be in the next release) but that only affects Win32 programs when debugging. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
