1) Although this is a Win32 port, the program itself is not very Windows "aware". It is best run from a shell window (called an MSDOS window on win95/98/Me or a command window on Win2000) where you can give it command line parameters for the input and output files. To get at the command window from Win2000, use Start->Programs->Accessories->Command Prompt.
If you simply double click on the file from Windows Explorer, PISCES will activate, (briefly) display a console screen and then exit.
2) Command line editing is not available in this port.
3) The internal PISCES graphics commands are no-ops in this port. They should be benign to use, but I would avoid them for now. Use the Postmini graphic postprocessor to examine PISCES mesh and solution files Note: I am awaiting approval to allow Postmini to be distributed. If it is not, I will do something to allow rudimentary graphics.
4) Lookup of the PISCES unformatted key file PISC2UKY via a shell environment variable does not work. For now, please place a copy of the unformatted key file in the directory you wish to run PISCES.
This bug has been fixed in release dated 30-Jan-99 or later -- to use, use the command:
SET PISC2UKY=pathname-of-unformatted-keyfile
before running PISCES.
5) If PISCES aborts, it creates a file fort.3 in the current directory with one line of output in it. This is a bug in the code as received from Stanford. (27-Jan-99 This bug has been fixed in release dated 30-Jan-99 or later)
6) On certain Win32 operating systems (e.g. Windows 2000), the directory C:\TEMP may not exist. I stupidly hardcoded this directory name. Pisces will fail to run, giving an error message about not being able to open a particular file in this directory. The workaround is to create this directory. Bug fixed in versions dated 2-Oct-01 or later.