Author |
Message |
Topic: Source code not displaying during SDBG |
bstott
Replies: 3
Views: 6779
|
Forum: Support Posted: Fri May 30, 2025 10:41 pm Subject: Source code still not showing in SDBG with FTN95 v 9.1 |
Thanks for the reply. My Windows 11 version is indeed 24H2. So I have just bought the upgrade to FTN95 v 9.1. However, after deinstalling my former FTN95 version 8.7 and installing 9.1, the problem ... |
Topic: Source code not displaying during SDBG |
bstott
Replies: 3
Views: 6779
|
Forum: Support Posted: Fri May 30, 2025 6:35 pm Subject: Source code not displaying during SDBG |
I have used FTN95 and SDBG for many years without issues. I have just reinstalled Windows 11 Home and all my apps, including FTN95 v 8.7, on my present PC - something I have done several times before ... |
Topic: Statements that execute in debug mode only |
bstott
Replies: 3
Views: 34163
|
Forum: Support Posted: Fri Feb 28, 2025 6:28 pm Subject: |
Many thanks. That works well, but it seems to require that the specific F90 file in my multi-file project containing the test must itself be compiled (or not) in debug mode. You mentioned other ways ... |
Topic: Statements that execute in debug mode only |
bstott
Replies: 3
Views: 34163
|
Forum: Support Posted: Thu Feb 27, 2025 1:44 am Subject: Statements that execute in debug mode only |
I use FTN95 Win-32 with SDBG. I'm sure this has been brought up before, but I now need a way to branch the execution path depending on whether the code was compiled in release or debug modes. Some c ... |
Topic: SDBG Font sizes |
bstott
Replies: 1
Views: 4404
|
Forum: Support Posted: Wed Sep 07, 2022 9:17 pm Subject: SDBG Font sizes |
I have just replaced my old monitors with higher resolution ones, and have adjusted the Windows 10 display settings accordingly. But now the text fonts in all the Win32 Debugger (SDBG) subwindows hav ... |
Topic: Calling a FTN95 DLL from C# |
bstott
Replies: 3
Views: 6813
|
Forum: Support Posted: Fri May 21, 2010 11:07 pm Subject: |
Hi Robert. Both my Visual Studio C# Express 2008 and my colleague's full Visual Studio 2008 have SP1. |
Topic: Calling a FTN95 DLL from C# |
bstott
Replies: 3
Views: 6813
|
Forum: Support Posted: Tue May 18, 2010 11:41 pm Subject: Calling a FTN95 DLL from C# |
I am using Visual Studio Express 2008 for C# and am trying to call a FTN95 DLL from C#.
The FTN95 help section �Net platform/.NET programming/Calling Fortran from other .NET languages� seems to say ... |
Topic: FTN95/SDBG under 64-bit Vista |
bstott
Replies: 5
Views: 14367
|
Forum: General Posted: Sun Aug 17, 2008 4:31 pm Subject: |
Thanks Andrew. One thing I can report is that I tried FTN95 on my wife's Vista 32 machine and everything, including SDBG, worked fine. |
Topic: FTN95/SDBG under 64-bit Vista |
bstott
Replies: 5
Views: 14367
|
Forum: General Posted: Sat Aug 16, 2008 11:51 pm Subject: |
Right now I would just settle for being able to run the existing SDBG on a Windows Vista x64 OS, which is supposed to handle 32-bit apps. But SDBG always fails with the message "Salford run-tim ... |
Topic: FTN95/SDBG under 64-bit Vista |
bstott
Replies: 5
Views: 14367
|
Forum: General Posted: Fri Aug 15, 2008 8:13 pm Subject: FTN95/SDBG under 64-bit Vista |
I just got 64-bit Windows Vista, which is supposed to be friendly to 32-bit apps. In fact, every one of my 32-bit apps migrated nicely to it, including FTN95 (versions 4.9 and 5.21), run in console m ... |
Topic: SDBG under Vista 64 |
bstott
Replies: 0
Views: 4292
|
Forum: Support Posted: Sun Aug 10, 2008 12:15 am Subject: SDBG under Vista 64 |
I have just "upgraded" from XP to Vista 64 (Intel Core 2 Quad) and my existing 32-bit application programs (office, editors, etc) have migrated quite nicely. In the case of FTN95, the insta ... |
Topic: side by side SDBG |
bstott
Replies: 1
Views: 4644
|
Forum: Support Posted: Sun Apr 06, 2008 9:47 pm Subject: side by side SDBG |
I use FTN95 4.9.0 under Windows XP, and I have dual monitors (as supported by standard Windows). I write programs that run in an application window produced by Clearwin or Winteracter.
In either ... |
|