First, this is a program that fiddles with hardware, so Palm won't approve
of it and all of the "don't do this" warnings apply.

Second, the reason I am posting here is that developers know things like
holding the scroll button to prevent reset-enabled programs.

Third, it might destroy your data or worse.  And you DON'T want to use
ecohack in turbo mode.  But if you are on this forum you should know what
you are doing.

I now have a file not listed on my website's index:

http://www.execpc.com/~tz/nowaitz.zip

It is a beta release intended for knowledgable developers, so it is not
configurable.  The final version will be better if I ever release it.  But
since it is an interesting experiment...

This alters three things:

1. It changes the LCD clock like streakhack (unlike streakhack it is NOT a
hack, but does the alteration out of reset and when the icon is clicked -
it doesn't recover from most greyscale programs so you have to click it
manually to get the screen contrast/speed boost back - Note this won't
change as I don't plan on making it a hack).

2. It drops RAM waitstates from 2 to 0.  (Actuall 1 should be safe - the
bit that is for high bus loading; on the V, either there are some caps I
can't see or they have really long traces in the inner layers between pins
1cm apart; The 0ws is because I thought I would live dangerously for the
beta testing). 

3. It drops Flash Waitstates from 1 to 0.

Note that it doesn't alter the system clock so baud rates and event
timings and such will remain the same.  It also does NOT check if you are
running on an old palm.

It runs fine on my Palm V8 (not efig.com, I did it here - one of our
surface mount technician wizards swapped chips).

It also runs fine on my 3x - note that the old LCD does not have the
contrast change with the LCD mod.  (The old LCD is in the 3X because I
wanted my 12MbRAM/4MBflash Palm 3 to have the better screen; If you have 
streaking problems on the 3x, find someone with a 3 and swap screens).

Benchmark returns 161% on both.  An internal benchmark which is CPU
intensive improved to 1:20.  It normally shows 2:13 for the 3, 1:58 for
the 3x, 1:42 1ws flash, 1:36 on the 3 with Ecohack@23Mhz.  [Note: 
Benchmark doesn't run faster from flash].  The only faster configuration
is my Palm 3 running out of 90ns flash@1ws under Ecohack@23Mhz (1:14).

If anyone is interested and has just done a full backup and has a test 3x 
or V, please try it and email me any brief good/bad results.


Reply via email to