windows 2.1.50 install

[Paul Kienzle]

I've put an octave-2.1.50-inst.exe up on octave-forge.

I've tested it a little and the results are not promising.

One machine could not run gnuplot 3.8i. (An AMD machine.
Anyone know how gnuplot 3.8i shipped with previous 
octave-forge builds was compiled?)

Another machine could not run rxvt (missing libX11??).

A couple more machines I didn't have sufficient privileges
to plug the cygwin keys into the registry.  (Are there
environment variables we can use when we can't get at the
registry?)

The post-install script, install_octave.sh, assumes cmd
rather than command for dos commands.  Unfortunately,
this can kill the script, which causes other problems
because the oct-file links don't get fixed up.

Rebuilding yourself will be a bit of a challenge as you
will need to apply the patches I've sent previously to
this list.  You should be able to reconstruct a set of
build directories from an installed system by copying
<install>/opt/octave to /opt/octave, copying 
<install>/bin to /opt/octave-support, and moving the
octave supplied binaries from /opt/octave-support to
<install>/opt/octave/bin.  That way you can grab the
latest octave-forge and experiment with the install
scripts.

Let me know if it works for you, and tell me which systems
it doesn't work for.  Better yet, send me patches ;-)

Paul Kienzle
address@hidden