Don Simons wrote:
> David Allsopp wrote:
> > [email protected] wrote:
> > > Dirk--
> > >
> > > It's nice to see some PMX activity!
> > >
> > > Could you post the input file so I can play with it?
> > >
> > > Also, I'm thinking about your PMX macro suggestion, but don't hold
> > > your breath...since I got a machine with 64-bit windows, my trusty
> > > visual fortran compiler won't install; I need to use gfortran, and
> > > its debugger sucks.
> >
> > Precisely which Visual Fortran compiler? Can you not install by first
> > changing the compatibility settings for the installer?
> >
> > Alternatively, if you have your old Windows CD/DVD, install Virtual
> > Box (www.virtualbox.org) and run it from a Virtual Box - shared
> > folders/host- only-networking make doing this much less painful than you
> > might think.
> >
> > HTH,
> >
> >
> > David
> 
> According to the CD, it's DIGITAL Visual Fortran Version 5.0, ca. 1997.

A quick look online suggests that Digital Visual Fortran is "maintained" by 
Intel these days: 
https://software.intel.com/en-us/fortran-compilers#pid-31448-97, though it's 
not free, unsurprisingly!

> I don't think they even had invented 64-bit PCs then,

They were released in 1961, at least for supercomputers! Practically, by the 
time your 1997 compiler was released, 64-bit workstations were quite common, 
inasmuch as PCs were common, (UltraSPARC, etc.). But we digress 
(http://en.wikipedia.org/wiki/64-bit_computing for those who, like me, like 
digressions!)

> and there certainly aren't any obvious settings I could change to fix this.

It sounds like it probably won't work, but I was referring to right-clicking 
the installer program (e.g. SETUP.EXE on the CD) from Explorer and choosing 
Properties then from the Compatibility tab ticking "Run this program in 
compatibility mode for" and picking something suitable (presumably Windows XP 
SP3).

Incidentally, as long as the compiler doesn't have any 16-bit (i.e. Windows 
3.x) parts - which isn't guaranteed in something released in 1997, the 64-bit 
architecture won't be the problem, it'll be the version of Windows (7 or 8.1, I 
assume?). 32-bit programs run pretty much without issue on 64-bit Windows - but 
16-bit doesn't work at all because Microsoft, quite reasonably, chose not to 
allow 16-bit programs in 64-bit Windows.

> I will try the
> other suggestion though. I'm not familiar with Virtual Box, and would be a
> bit concerned about virus protection issues.

If you're only going to use it for Visual Fortran, then there's no need to 
connect it directly to the Internet. Virtual Box allows you to create a "host 
only network" so that your computer can connect to the virtual box, but not 
allow the guest to access the Internet.

> I know that's a big issue if you install a virtual Windows XP on a Windows 7
> box, where you'd need to install anti-virus on the virtual machine to be 
> protected.
> To be honest I do have a (somewhat cumbersome) workaround...I can still
> fire up an old XP laptop (and make sure it doesn't connect to the web,
> since the antivirus S/W on it has long expired). It's a tradeoff whether
> that's more of a hassle than using gfortran and foregoing the debugging
> facilities.

Doing this would be largely equivalent (but slower) to running the Virtual Box 
without the network being attached.

I of course basically applaud your trying to avoid using Windows XP, naturally! 
Alternatively, if you can bear it, you can probably achieve increased safety by 
using Windows '95 or '98 in Virtual Box as I imagine there is no 
viruses/malware at all which is targeting it these days!! :o)


David

-------------------------------
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to 
http://tug.org/mailman/listinfo/tex-music

Reply via email to