PocketFrotz Rev 0.4b  2/7/04
1. Re-Compiled to work with Pocket PC 2003.


PocketFrotz Rev 0.3b  7/24/01
1.  Fixed(?) a bug where the application would crash intermittently.
      if this happens, and you see a cryptic message such as "OnDraw" or "OnChar", if
      you could forward this info to blj29@home.com it would be appreciated.

2. Removed install program.  Received a ton of complaints that it did not work.  So it's     back to manual for the short term.
    To install, simply copy the appropriate exe (ARM, MIPS, SH3) to your device  	      and run it.  Does not require any additional files.  (Other than the story files)


PocketFrotz Rev 0.2b
1. Added an install program.

PocketFrotz Rev 0.1b
The code/executables are provided "AS IS".  
This project is simply an update to the FROTZCE port by IAN Dean.  A few features have been added, but for the most part, this is simply an attempt to get Frotz running on my IPAQ.

CURRENT ISSUES
1) THERE IS CURRENTLY NO INSTALL PROGRAM.  You must copy the appropriate executable(ARM,MIPS,SH3) for your device directly.  
2) This program is BETA!!!!!   Use it at your own risk.  Backup your data before using this application.


New Feature for Rev 0.1b
1) Should now run on PocketPC platform.  Tested on IPAQ.
2) Added a compass to main screen to allow for single tap movement.
3) Added a macro menu to allow for custom commands.  i.e. "frotz "  "up"  etc..  (max of ten now)
4) Fixed issue with save dialog that would not allow user to specify a filename.
5) Renamed Pocketfrotz so as not to be confused with FrotzCE (which should probably run on PocketPC with mips or SH3)

You can do what you like with this source code except to use it (or anything derived from it) for any kind of commercial gain. Stefan Jokisch, the Frotz author owns the rights to the Frotz 'C' source code and his conditions can be found within the documentation of his code.

If you distribute anything developed from this source code, you must distribute the source code from it too. 

Any bugs/comments can be sent to blj29@comcast.net.  No guarantee that I'll fix them, but I'm currently still working on this so I might.

Please no comments about my piss-poor programming style.  I'm a hardware engineer, not a software engineer.

Enjoy,

William H. Johnson
Rumson, NJ
blj29@comcast.net


******* README FROM FROTZCE by IAN DEAN


The FroztCE source is provided 'as is'. Please do not ask me questions about this source code as I am currently not continuing development of FrotzCE. The source is commented, but is probably not how I would implement FrotzCE if I was to do it with the Win32 and WinCE knowledge that I have now. Documentation of the original Frotz code is found in the 'Frotz' subdirectory. This is all the documentation that there is for the FrotzCE code, so if you're not up to scratch with your WinCE C++ programming, you're probably not going to be able to make much use of this source...

There are two seperate projects contained within this archive. FrotzCE.dsw is the project workspace file for Windows CE 1.0 and must be used with Visual C++ 5.0 and the CE 1.0 Toolkit. FrotzCE2.dsw is the project workspace file for Windows CE 2.0 and later and must be used with Visual C++ 6.0 and the CE 2.0 Toolkit.

FrotzCE is a Windows CE port of Frotz, a portable Z-Machine emulator. The Frotz 'C' code handles all of the emulation, and relies on an operating system layer to be implemented for screen, keyboard and file I/O. Where possible I have stuck to this model. The original untouched Frotz source code resides in the 'Frotz' sub-directory. Where I've had to change some Frotz source files, I've moved these files up into the FrotzCE source directory. The original unmodified files remain in the 'Frotz' subdirectory for comparison, but are not used in the FrotzCE project.

You can do what you like with this source code except to use it (or anything derived from it) for any kind of commercial gain. Stefan Jokisch, the Frotz author owns the rights to the Frotz 'C' source code and his conditions can be found within the documentation of his code.

If you distribute anything developed from this source code, you must distribute the source code from it too. I'd also appreciate it if you mentioned myself and Stefan Jokisch in the documentation as we both have spent a lot of time developing this code (especially Stefan Jokisch)...

Thanks and Good Luck!

Ian Dean