forums.silverfrost.com

[Erik]

I want to move my FTN95 program development from a 32 bit PC to a 64 bit. The program compiles apparently without problems, but SLINK crashes. Is this the general pattern, and is there a remedy?

[Wilfried Linder]

Erik,

I'm working with FTN95 under Win7/64 since about two years without any problems. For linking I use simple text files containing those objects I want to link. Example:

"c:\program files (x86)\silverfrost\ftn95\slink" modules.txt (command line or within a batch file)

together with the file modules.txt which looks like

lo c:\...\*.obj
lo c:\...\*.dll
...
file c:\...\my_programme.exe

Maybe this helps? Or can you tell us the error message from slink?

Regards - Wilfried

[jalih]

[LitusSaxonicum]

Erik,

What version of FTN95 are you using? When I used 4.90, SLINK crashed in Windows 7. Later versions (e.g. 6.10) are fine - I don't know when things changed, it isn't in the change log on the support page.

Eddie

[Erik]

The lastest version of FTN95 I have tried is v5.30, so it may be too old to work in Win7/64?

The error message is as follows:

Runtime error from program:c:\ftn95sf\slink.exe
Access Violation
The instruction at address 004196c8 attempted to read from location 04e8f20c

00419426 loadDll(<ptr>char,int) [+02a2]

004028ed loadObject(<ptr>char) [+0291]

004259d9 loadCatenatedObject(<ptr>char) [+02ac]

00402c17 loadNamedObjectFile(<ptr>char) [+0143]

00420708 findDLL(<ptr>char) [+01b0]

004208d0 loadStandardDLLs(void) [+01b2]

0040766a parcelUpExe(void) [+0857]

004081d9 processFileCommand(<ptr>char,int) [+023d]


eax=04e92c6b ebx=04e925f4 ecx=04e9191c
edx=00000000 esi=000005dc edi=04e8f208
ebp=0370ea68 esp=0370e9b4 IOPL=1
ds=002b es=002b fs=0053
gs=002b cs=0023 ss=002b
flgs=00010203 [CA OP NZ SN DN NV]

004196c8 mov esi,[edi+0x4]
004196cb mov [ebp-0x7c],esi
004196ce push 0xf0f0f0f0

[Wilfried Linder]

Hmm... my (older) version is 5.50 from 27th of February 2010, this works properly.

Regards - Wilfried

[LitusSaxonicum]

Erik,

My suggestion is to download the Personal Edition and try that. If it works, then the SLINK problem is because your version is too old. If it doesn't work, then there is something odd about your machine's configuration.

This isn't Silverfrost's fault - Microsoft make changes, and if your version wasn't tried out in Win 7 (especially 64-bit) then incompatiblities do arise.

There have been a lot of useful corrections and updates since 5.30.

The good news is that if you compile and link on (say) an XP machine, the executables will run - probably.

Eddie