\input texinfo @c
@setfilename INSTALL.win32.info
@include topdocs/defs.texi
@settitle INSTALL.win32
@node Top, , , (dir)

@chapter INSTALL.win32 - how to install GNU Solfege @value{SOLFEGEVERSION} on MS Windows

Installing Solfege @value{SOLFEGEVERSION} on MS Windows is almost as simple as on
Debian GNU/Linux:

@itemize @bullet
@item Download the file solfege-win32-@value{SOLFEGEVERSION}.exe
available through the website as @uref{http://www.solfege.org}.
@item Run the file by double-clicking on it.
@item Accept all default values, and the program is installed
in a few seconds.
@item You can start the program from the Start Menu, 
select Programs/GNU Solfege.
@end itemize

@section Uninstall the program.
To uninstall the program, use the
'Uninstall GNU Solfege' menu entry on the Start Menu.
Do not delete the files directly.

@section Upgrading
Please uninstall older versions of Solfege before installing this
new version. The installer is not very smart, and might get confused.

@section Trouble?
It is possible that the file @file{\home\solfegerc@value{SOLFEGESHORTVERSION}}
is corrupted by a bug in the program. If you have strange problems,
you can try to delete the file and rerun the program.

If you still have problems, you should check if there is a newer
release available. And if so, test that release to see if the 
bug has been fixed. If not, you can email you can email your questions to
@email{solfege-devel@@lists.sourceforge.net}. Remember to tell
what version of Solfege you are running. Do @emph{not} email
the author of Solfege directly, because when emailing the list,
other people than me get the chance to help. 

@section Developers
*** This section is under construction. Missing and wrong urls and
version numbers and plain lies follows: ***

This section will be filled with info for developers that has to
use MS Windows while programming.

There are some stuff you need to have installed:
@itemize @bullet
@item Python 2.1 (http://www.python.org/2.1). Version 2.0 will not work.
@item py2exe
@item NSI installer
@item http://hans.breuer.org/dia/gtk+-bin-2001-05-12.zip
@item http://hans.breuer.org/ports/pygtk-2000-11-26.zip
@item iconv.zip from hans.breuer.org
@end itemize

At the moment, building the installer is done this way:

@itemize @bullet
@item On Linux: from the source dir: @command{make export-to-dos}
@item Copy the newly create directory @file{../solfege-export-to-dos}
  to your windows partion.
@item Reboot to some version of Windows
@item Edit runpy2exe.bat so that PYTHONPATH points to where
pygtk is installed.
@item Windows: run the runpy2exe.bat
@item Right click on installer.nsi and select "Compile NSI"
@end itemize

Hopefully, I or someone else will figure out how to build the sound
module on windows instead of cross-compiling it from linux. Then it will be
possible to do the whole build of the windows installer on windows.

Newer or older versions of gtk and pygtk might work, but
don't come screaming for help if they break. (But please
do if the above urls disappear.)
If you have gimp installed, you can probably drop
gtk+-bin-2000-08-26.zip. But I am not sure, since I
don't want to download gimp for ms-windows just to test this.


You start the program by executing the @file{solfege.bat} file.
Notice that you probably must edit @file{solfege.bat} and set the
@env{PATH} variable to point to where you have the python interpreter
installed.

Sometimes windows can have trouble finding/loading some
of the gtk.dll's, it usually works if you try to start the
program a few times more.

@section Sound

The first port to MS Windows had to call an external midiplayer
program to play the music, but thanks to Joe Lee, Solfege now
talks directly to the soundcard, just like on linux. Using
@file{midiplayer.exe} is still possible, but talking directly
to the soundcard is now the default. (@file{midiplayer.exe} will
disappear in a later version if nobody needs it.)

Please let me know if you have any problems with this new sound
code, and especially if using @file{midiplayer.exe} works and
winsynth fails.


