forums.silverfrost.com

[offthechart]

I am finally going to Windows10 from Windows7. (Don't laugh). I currently run FTN95 from a Command prompt on W7. Will I still be able to create a Command Prompt in W10 or how is a Fortran program run on W10? Excuse my ignorance, but is Silverfrost downloaded in W10 without problems? Thanks.

[PaulLaidler]

You should be able to use the same approach on Windows 10.

[LitusSaxonicum]

Do beware with Windows 10, especially the 64-bit version, on a lowly computer., because there may not be enough RAM to work properly.

My junk heap, or should I say collection of old computers, includes several laptops. One, that still runs Win 7 32-bit has 1Gb RAM, and Windows 7 occupies half of it. Unfortunately, it's rather heavy, and unsuited for travel, but FTN95 runs fine on it, and so do all my apps.. The 4Gb RAM machine went a bit flaky after overheating in its bag after being switched on at Gatwick by security and not switched off properly. I then 'upgraded' to the later model in the same range with only 2Gb which was fine for some years but Win 10 64 bit has now decided it wants 1.9Gb and so is now unusable. (The last 2 upgraded automatically from Win 7 and Win 8 respectively, but to Win 10 64-bit). So I'm back to the 4Gb machine while I work out what to do next.

As far as Win 10 goes, FTN95 works just fine, provided that there is free RAM - my problem is with MS Office that won't run now on the 2Gb machine. My desktop with oodles more RAM works fine.

No matter how superior Plato is, I still use the freeware programmer's File Editor PFE32 as I'm habituated to it. It has its own DOS box. Win 10 has several choices including 'Power Shell'.

IN short, FTN95 is fine with Win 10, but upgrading an inferior old machine from Win 7 32-bit to Win 10 64-bit may not prove all that successful.

Eddie

[offthechart]

Thanks for the replies! I am planning on getting a new computer with at least 16Gb RAM. My main concern was the 'methodology' of running Fortran on Win10 64-bit. My current setup is W7-64 with 8Gb. Remarkably fast considering I originally started with IBM mainframes many, many years ago writing engineering software. Now it is just for fun. (Want to know how much farther a home run travels in Denver vs Miami?)

[LitusSaxonicum]

John,

In some ways you are right, but in others wrong, I�m afraid.

Not that I need 64-bit Windows, but I suspect that 64-bit programs wouldn�t run under Win 7, at least, not satisfactorily. I get the impression that Win 7 64-bit was a rara avis anyway.

Your advice about Office 2013 is great if all you need to do is to create and exchange bits of printed paper with some e mails thrown in. What you should realise is that there are later forms of MS documents that Office 2013 cannot read. Also, documents created with mismatched early versions of Office formats do not open and display properly, for example, misplacing graphic content. Part of the reason for this is how page sizes are calculated, for example, with US letter paper not being the same size on a European-configured Windows/Office combo as a US version, which was hell if preparing a �camera-ready� paper for a US conference. Something to do with dpi, probably.

Software continuously evolves to annoy the user. For example, my CorelDRAW won�t open early version files, nor files from a version later than the one I�m using. MS Office can be the same, and certainly it no longer supports opening WordPerfect files, WordStar was abandoned long before that. Quattro Pro (Yep, still exists) won�t open or run early version files, and Excel doesn�t want to know � it used to when it was playing �catch-up�).

And as for those poor blighters afflicted with .NET and Visual Studio � well, that�s a continual process of catching up.

Eddie

[LitusSaxonicum]

John,

Pot calling Kettle black methinks over the 2003/2013 typo!

As to "avoided like the plague", then name one. You can compound it by programs that disappear.

I'll PM my view of Powerpoint.

Eddie