forums.silverfrost.com

[Kevin]

I am currently using v8.80 in 32bit mode and all is good.
I thought I would try the 64bit compiler. The /64 switch works fine on the ftn95 command but slink64 doesn't do anything. It just returns me back to my command prompt. No Copyright statement, No $.
I have tried on both a Windows 11 and Windows 10 machine, both working fine with FTN95 in 32bit mode and both have the VS2019 integration working fine but nothing with slink64.
Any log files or anything I can try to see what is happening ?
Thanks,
Kevin

[PaulLaidler]

Kevin

The commands for SLINK64 are not always the same as for SLINK. Take a look at the help instructions for SLINK64 and try something very simple first of all.

If you still have problems then post a sample program together with the SLINK64 commands that you are using.

[Kevin]

Paul,
I'm just trying in interactive mode. Literally just typing SLINK64 at the command prompt. This is what I get:

c:\NC\demo>slink64

c:\NC\demo>

and if I search for it I get:

c:\NC\demo>where slink64
C:\Program Files (x86)\Silverfrost\FTN95\Slink64.exe

c:\NC\demo>

So it's not picking up any batch file or another program of the same name.
If I check the details of the file I get:

c:\Program Files (x86)\Silverfrost\FTN95>dir slink64.exe
Volume in drive C is Windows
Volume Serial Number is 3096-8ECB

Directory of c:\Program Files (x86)\Silverfrost\FTN95

19/06/2021 17:48 498,176 Slink64.exe

[PaulLaidler]

Try changing to to Silverfrost folder and typing SLINK64.exe.

[Kevin]

Sorry, should have said that I have already tried that:

c:\Program Files (x86)\Silverfrost\FTN95>SLINK64

c:\Program Files (x86)\Silverfrost\FTN95>

[PaulLaidler]

Kevin

It would be difficult for me to dig out a replacement SLINK64 from July 2021.

Can you re-install or update to a later version?

[JohnCampbell]

Kevin,

Do you have a slink64.bat or some other environment variable alias that could be redirecting ?

Where are you building your program, as you probably don't have adequate rights in c:\Program Files (x86)\Silverfrost\FTN95>

check your install for your PATH settings, MOD_PATH and F95INCLUDE.
You can find all these settings by using
SET > my_settings.txt

[Kevin]

I installed v8.90 and exactly the same issue.
@John:
* I did a dir/s slink64.* from the top-level and only the correct slink64.exe shows up.
* I have tried to run slink64 from various folders, all with full write access
* Don't see why I need those two env. variables but I found fvars.bat in the Silverfrost folder, ran that but still no difference

The Event Viewer, first shows Application Error (Event ID 1000):

Faulting application name: Slink64.exe, version: 3.3.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000001049d
Faulting process id: 0x1690
Faulting application start time: 0x01da5b750d8652da
Faulting application path: C:\Program Files (x86)\Silverfrost\FTN95\Slink64.exe
Faulting module path: unknown
Report Id: a07b1d34-6204-41c6-be9c-324d4265b6ef
Faulting package full name:
Faulting package-relative application ID:

Then it shows Windows Error Reporting (Event ID 1001):

Fault bucket 2073100893512480407, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Slink64.exe
P2: 3.3.0.0
P3: 00000000
P4: StackHash_12e9
P5: 0.0.0.0
P6: 00000000
P7: PCH_69_FROM_unknown+0x0000000000000000
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ae59ea10-697c-401f-96f3-3265d2a3583a.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1776d607-d048-4f94-8cbf-d002d6dea638.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.79b131e3-9a0e-449f-ab2c-8c61110b7a6d.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1f255d4f-73f6-4b0f-8f7b-a5b2afdbdc9e.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.63ec2d9a-f2cf-46fd-a6d1-b86ed7890e74.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Slink64.exe_97a4e9afd6433c94bae2816f4433aca964504fc1_c35ba06b_e42efdef-b5d7-4270-89d6-2c2b2762022a

Analysis symbol:
Rechecking for solution: 0
Report Id: a07b1d34-6204-41c6-be9c-324d4265b6ef
Report Status: 268435456
Hashed bucket: afb9d10f915492e3ecc52247655b3697
Cab Guid: 0

It also creates dump files in c:\users\...\crashdumps with the name Slink64.exe.xxxx.dmp

All very strange!

[JohnCampbell]

this is more than strange !!

can you try other commands, eg
slink64
slink
ftn95 program.f90 /64 /link
set > environment.txt

these should provide some sensible responses.

I have a .bat file to reset environment variables. You could try this

[Kevin]

Yes, as previously mentioned, no problem with slink or the /64 switch on ftn95.
Env. variables can be set ok, but make no difference.

[PaulLaidler]

Kevin

Try using v9.0 which is available to supported users and as the personal edition...

https://silverfrost.com/32/ftn95/ftn95_personal_edition.aspx

[JohnCampbell]

Kevin,

I am puzzled by the reports you are providing. slink64 should give some response ?

Can you type the following command (even copy it into a file zzz.bat)
dir "c:\program files (x86)"\silverfrost\ftn95\*.exe > list_of_files.txt
notepad list_of_files.txt

then post the result from list_of_files.txt

About all I can think is you have overwritten slink64.exe, as if it does not exist, you would get an appropriate response, not nothing !

Alternatively try
dir c:\slink64.* /s > zzz.tce
notepad zzz.tce

I found a copy of Ver 8.80 Slink64 and it reports the
[SLINK64 v3.02, Copyright (c) Silverfrost Ltd. 2015-2021]
$

[Kevin]

John,

That's the whole point - it doesn't make any sense.
My previous posts show that I have done a dir on slink64.exe and it certainly does exist, backed up by the report from Event Viewer as well, but here is a dir of *.exe as requested:

Volume in drive C is Windows
Volume Serial Number is 3096-8ECB

Directory of c:\Program Files (x86)\Silverfrost\FTN95

05/07/2021 16:34 3,072 dbk_link.exe
05/07/2021 16:35 114,688 dbk_link2.exe
05/07/2021 16:35 105,472 dbk_link4.exe
01/02/2020 07:29 50,176 editsvg.exe
24/09/2001 14:55 11,264 fparam.exe
05/07/2021 16:35 2,267,648 ftn95.exe
05/07/2021 16:34 30,720 mk32.exe
18/06/2021 13:57 6,447,616 plato.exe
19/11/2018 15:27 4,520,448 plato32.exe
05/07/2021 16:34 1,221,632 scc.exe
05/07/2021 16:35 82,432 sdbg.exe
22/06/2021 17:42 2,128,384 sdbg64.exe
05/07/2021 16:35 47,616 slim.exe
05/07/2021 16:35 223,232 slink.exe
19/06/2021 17:48 498,176 Slink64.exe
05/07/2021 16:34 1,222,144 src.exe
11/04/2022 11:01 733,410 unins000.exe
05/07/2021 16:35 82,432 wsdbg.exe
18 File(s) 19,790,562 bytes
0 Dir(s) 583,772,434,432 bytes free

and here's the output from the whole C: drive as requested:

Volume in drive C is Windows
Volume Serial Number is 3096-8ECB

Directory of c:\Program Files (x86)\Silverfrost\FTN95

19/06/2021 17:48 498,176 Slink64.exe
1 File(s) 498,176 bytes

Directory of c:\Users\KevinNBradly\AppData\Local\CrashDumps

07/02/2024 12:54 945,170 Slink64.exe.1672.dmp
07/02/2024 15:19 945,170 Slink64.exe.35508.dmp
07/02/2024 12:51 955,994 Slink64.exe.8196.dmp
3 File(s) 2,846,334 bytes

Total Files Listed:
4 File(s) 3,344,510 bytes
0 Dir(s) 583,752,511,488 bytes free

also showing the results from the crash dumps generated the other day.

Tried running as Administrator - no joy
Tried copying slink64.exe elsewhere - no joy
Might try re-booting in Safe Mode - see if that helps!

[JohnCampbell]

Kevin,

I could not identify any problem in your directory list.
The only remaining possibility is conflicting .dll usage.
I certainly get a prompt when using slink64 ??

This is my version 8.80, which looks similar for .exe files.
Are my .dll files similar ? (dir /od *.dll )

[Kevin]

Yes, my DLL list is exactly the same (size and dates).
Interestingly I have v8.70 on another machine and copying the slink64.exe from that machine to this one works as it should.
Which points to the v8.80 install getting corrupt somehow but then I tried v8.90 and that was the same!
Oh well, I'll have to wait until I go up to v9.00 and see if that solves it.
Thanks both for trying to help - it's not urgent as I said before, but just very strange.