Archived 2013-12-08
This page has been archived and some links may not work correctly anymore. No updates of this page will be done anymore.

Contents of this page:


Introduction:

I have been asked in several personal emails to explain my backup mechanism in detail. I´ll do it here now:

In general, my setup does the following every night:
Checks if everything is ready to make a backup:

  • checks the data bases on C:\_dat\*.?db (appointment book, phone book, notes)
  • checks the main battery voltage

If everything is okay, it makes a backup of drive C:\, creates a zip file in A:\BACKUP_C which contains the whole C: drive.
The backup is discarded if the target disk is full during the process.

Notifies me using an entry in the appointment book every morning if the backup succeeded or not, and if not, why not. It can be unsuccessful due to one of the following reasons:

  • insufficient battery power
  • insufficient disk space on the A: drive
  • a currupt database (appointments, contacts, notes)

I do a rotational backup with 2 backups existing at one time, every second day every backup is overwritten by its new version. I call these backups "a.zip" and "b.zip". So, if no error occurs, I should have two backups everytime. One which is not older than 24h and one which is not older than 48h.

The mechanism can easily be extended to make more than two rotational backups. If you have plenty of room on A: for several backups, I recommend to make more backups.

In addition I strongly recommend to backup the A: drive (probably a flash or compact flash card) to another target, such as a desktop computer, and burn it on CD-RW from time to time.

In order to make this backup procedure work reliably, I recommend that you take care to save all your work every evening, and it is good to close system manager applications (MEMO, notes, phone book, appointment book etc). A system macro will do that automatically for you if you don´t do it, but you could have forgot to save something important, and this could cause problems.

Setup:

Now in detail:

Needed programs:

  • pkzip
  • voltchck (checks battery voltage, by J. Korthof)
  • dbcheck (checks data bases, by Curtis Cameron)
  • and, if you like to see the daily greeting of the appointment book, you need greet.zip by Andreas Garzotto

All these utilities should be installed somewhere your path variable points to.

1. Create the file backup.bat somewhere where it can be found by the "path". It is assumed that you want to backup the whole C: to A:\BACKUP_C\
See my backup.bat below. If source and/or target differ, modify all relevant path information in the backup.bat and in the system macro F9 described below.
And create the directory a:\backup_c on your flash card.

2. Create two system macros (and save them! Otherwise you will lose them if you lose all you other data and have to restore the backup ;-)). I call these macros F10 and F9 (as they are called on my palmtop). You may call them whatever you like.

  • F10: Closes all system manager applications and goes back to the System Manager Topcard (and makes sure a MEMO document is saved if MEMO asks if it should save)
    {Filer}{Filer}{More}{Menu}{Enter}l{Enter}{More}{Menu}{Enter}l
    On my German palmtop, the macro is
    {Datei-Manager}{Datei-Manager}{Mehr}{Menü}{Enter}a{Enter}J{Mehr}{Menü}{Enter}a

     

  • F9: Manages the notification: Opens MEMO, loads a:\backup_c\report.txt (adjust path if necessary!), marks the reporting line (shift-cursor-down), copies to clipboard, exits MEMO, launches appointment book, makes sure the appointments window is open (F9), jumps to today (F5, F4), creates a new appointment (F2), pastes the clipboard as title, sets the start to 8am (adjust if you prefer another time), sets the stop time to 8.01am (adjust...), disables notification (take care you enter the space after the two tabs!), 5*tab to the weekly and monthly view and disable both (spaces!), save with F10 and exit appointment book:
    {Memo}{F9}a:\backup_c\report.txt{Enter}{Shift+Down}{Copy}
    {Menu}q{Appt}{F9}{F5}{F4}{F2}{Paste}{Tab}8{Tab}8.01
    {Tab}{Tab} {Tab}{Tab}{Tab}{Tab}{Tab} {Tab} {F10}{Menu}q

    The German version is:
    {Memo}{F9}a:\backup_c\report.txt{Enter}{Ums+Ab}{Kopie}
    {Menü}e{KAL}{F9}{F5}{F4}{F2}{Einfg}{Tab}8{Tab}8.01
    {Tab}{Tab} {Tab}{Tab}{Tab}{Tab}{Tab} {Tab} {F10}{Menü}e

3. Create 3 appointments in the appointment book early in the morning when you don't expect to use your palmtop, for example at around 2am. Preserve the time differences I used. Increase the time difference between the second and the third appointment, if your backup takes longer than about 10 minutes for a backup (e.g. if you have a huge C: drive to back up or a single speed palmtop. Maybe consider increasing the battery voltage limit in backup.bat!).

  • 2:00am:||10
    (calls system macro 10)
  • 2:01am: |c:\batch\backup.bat a |
    (calls backup.bat with parameter a (so it creates a.zip) (replace path by your custom path) and reserves all available memory for that backup.bat)
  • 2:15am: ||9
    (calls system macro 9)

Set for all these appointments:
Stop time: 1 minute after start time,
Location: Q
Notification: activated, 0 minutes,
no weekly and monthly view.

Set for the 1st and 3rd one: Repetition: daily until 1.1.2020
Set for the second: Repetition: every second day (daily, cycle=2 days) until 1.1.2020

Here you can see how it looks in my appointment book. You can even see a notification that the backup was successful at 8am.

4. Copy the second appointment (2:01) and paste it into the day after the one you created the other appointments in, and change its title to |c:\batch\backup.bat b | (apply the change to all occurrencies of this appointment, when you are asked).
Take care all other settings match the settings of the original appointment. Go a few days ahead and see if the repititions are set correctly. You should now have three appointments every day, and the one which calls backup.bat should have a and b as parameters, alternating.

Here you can change the behaviour of the rotational backup. You can create as much different "backup.bat" calling appointments as you like, giving parameters with different names. So you can set 5 different appointments with "backup.bat a", "backup.bat b", "backup.bat c" and so on. Or 10 or 20. Just be sure you have one of them each day and you have enough disk space available on the target drive.
Of course you can also create the appointments weekly instead of daily, this may be better if you don´t use your palmtop very often.

BTW: You can also call backup.bat from the command line, if you want to make a manual backup e.g. when you plan to take apart the palmtop or install some new dangerous software ;-). Just call "backup m" and you will do a manual backup, called m.zip. You will see the report, which you usually see in the appointment book at 8am, at the end of the manual backup.

5. Either disable the daily greeting of the appointment book (menu "options") or modify the time it is shown each day with Andreas Garzotto's greetime.com from the greet.zip package mentioned above. The greeting has to be shown AFTER the notify macro is executed, e.g. I could call greetime 0500 in order to let appointment book show my daily greeting not before 5am, so it doesn´t interfere with the backup routine and even shows its report when popping up.

Have fun and take care of your data!

@echo off
REM backup.bat by Daniel Hertrich
REM http://www.hermocom.com/knowledgebase/hplx/backuplx

echo ERROR CREATING REPORT.TXT > a:\backup_c\report.txt
a:
REM Change 2.40 to 2.30 if you use Alkalines. 2.40 is good for
REM Rechargeable batteries
a:\bin\voltchck.exe 2.40
if errorlevel 1 goto power

REM =============================================
REM You can put other nightly jobs in here, too!
REM =============================================

dbcheck c:\_dat\*.?db > a:\dbcheck.log
if errorlevel 2 goto dberror

REM now create today's backup, first with a temporary name
a:\bin\pkzip -rp -es -whs -Jhrs a:\backup_c\%1_temp.zip c:\*.*
if errorlevel 14 goto space

REM delete old version of backup
del a:\backup_c\%1.zip > nul

a:
cd \backup_c

REM rename today's backup to %1.zip
ren %1_temp.zip %1.zip
echo Backup %1 was successful > a:\backup_c\report.txt
goto end

:dberror
echo Backup %1 FAILED (see a:\dbcheck.log) > a:\backup_c\report.txt
goto end

:power
echo Backup %1 FAILED (battery) > a:\backup_c\report.txt
goto end

:space
echo Backup %1 FAILED (disk space) > a:\backup_c\report.txt
goto end

:end
REM print report to screen
type a:\backup_c\report.txt

And here you can see the contents of my C: drive (about 4MB currently) on the left side zipped to the a.zip and b.zip in a:\backup_c on the right side, the file report.txt is also shown


Restoring a backup:

If you ever get in trouble with your C: drive you now have a fairly up-to-date backup on your flash card. But what to do to get it back onto C:?

Here is a suggestion how to handle fast data recovery:

Everytime I boot my palmtop with the flash card inserted (and that is usually the case) it looks on the flash card for a config.sys and if it exists, it takes this one instead of the d:\config.sys or the c:\config.sys. And if it takes a:\config.sys, it also takes a:\autoexec.bat if it exists.

Now I have a line in my a:\autoexec.bat which verifies if the C: drive is intact by looking for a specific file which is always there if the drive is intact:

if not exist c:\bin\spd31.exe goto c_deleted

label c_deleted leads to my "catastrophe handling routine", which is very simple:

:c_deleted
echo c:\bin\spd31.exe is missing. The RAM drive seems to be deleted.
echo In order to restore the latest backup, please enter on C:\>
echo unzip -d -o a:\backup\[lastbackup].zip
path a:\bin
c:
cd\
dir a:\backup_c
goto end

So this simply tells me what to do in such a case and sets the path to a:\bin, where unzip.exe is located and it shows the contents of a:\backup_c, so I can see what the name of the latest backup is. For example, if the following is shown:

 Volume in drive A is 96M-CARD
 Directory of A:\BACKUP_C

.            (DIR)     07-19-01  10:13a
..           (DIR)     07-19-01  10:13a
A        ZIP   2035650 09-03-01   2:06a
B        ZIP   2051668 09-04-01   2:06a
REPORT   TXT        26 09-04-01   2:06a
        5 file(s)    4087344 bytes
                     7411712 bytes free

I know that b.zip is the latest backup, so I have to use

C:\> unzip -d -o a:\backup_c\b.zip

to restore my C: drive.

Please make sure unzip.exe (or pkunzip.exe) is available on your flash card, otherwise you would have a big problem. pkunzip uses the same switches as unzip, so the command line would be

C:\> pkunzip -d -o a:\backup_c\[lastbackup].zip

The switch "-d" creates all needed directories, "-o" overwrites without prompting. Sometimes I have to set the settings in the config utility of system manager anew after a backup restore (time, date, owner, time / date format...). And appointment book (and alarm clock, if you have and use it) has to be started once in order to make the next alarms work.

Use manual backup to clone a RAM drive:

By the way: This technique is ideal for cloning RAM drives of palmtops:

If you wish to copy a RAM drive 1:1 from one palmtop to another, simply put the flash card into the original one, type

C:\> backup z

Put the flash card into the one which shall get the RAM drive contents of the first palmtop, initialize its RAM drive if necessary, reboot the palmtop with this flash card and type

C:\> unzip -d -o a:\backup_c\z.zip

This works of course only if the second palmtop has enough space available on its RAM drive.

A much more improved technique using PIM/PE for logging and reporting and optimized for large (upgraded) RAM drives:

I have recently upgraded my internal RAM drive to 32 MB and I switched entirely from the built-in appointment book to PIM/PE (by Andreas Garzotto). Hence my need to modify and improve the nightly backup technique.

See below my new "nightly.bat" which is still invoked by the built-in appointment book, but now without any parameter, everything regarding rotational backup is done entirely from within the batch file ("if exist ....zip move ....zip ....zip").

Download links to all needed utilities are directly in the batch file below.

@echo off
REM %1: nobackup OR onlybackup OR everything
REM nobackup: Only runs "other nightly jobs"
REM onlybackup: overrides "other nightly jobs"
REM everything: executes "other nightly jobs" AND backups.

REM %2: all (only if %1 given!) - overrides AC and battery voltage
REM detections and backups everything, regardless of the voltage.

REM Needs:
REM setit, echot, timestmp, voltchck, pkzip, dbcheck

if not "%1" == "everything" goto normal
if not "%2" == "all" goto normal

setit lf
echo ATTENTION: Light Sleep Mode deactivated during nightly runs!

:normal

set f=n
if not "%f%"=="n" goto NOENV

timestmp  >> c:\_dat\pim\data\backup.pim
echot "Starting nightly.bat" >> c:\_dat\pim\data\backup.pim

if "%1"=="nobackup" goto OTHER

if "%2"=="all" goto pow1ok

voltchck 4.00
if errorlevel 1 goto noAC

:pow1ok

if "%1"=="onlybackup" goto NOOTHER

echot "AC connected. Doing everything." >> c:\_dat\pim\data\backup.pim

:OTHER

REM ============= OTHER NIGHTLY JOBS: ==============

echot "Start pdb2x.bat"  >> c:\_dat\pim\data\backup.pim
call c:\batch\pdb2x.bat nightly
REM (called with %1 = nightly, so pdb2x knows that it has been invoked automatically!)
echot "Done  pdb2x.bat"  >> c:\_dat\pim\data\backup.pim

echot "Start find -r"  >> c:\_dat\pim\data\backup.pim
find -r
echot "Done  find -r"  >> c:\_dat\pim\data\backup.pim

REM =========== END OTHER NIGHTLY JOBS =============

if "%1"=="nobackup" goto nobackup

:NOOTHER

REM FROM HERE EVERYTHING IS BACKUP-RELATED!

:BACK1

:zip1
echot "Zipping C:\\PROGRAMS" >> c:\_dat\pim\data\backup.pim
if exist a:\backup_c\c_progr.zip del a:\backup_c\c_progr.zip
pkzip -rp -ex -whs -Jhrs a:\backup_c\c_progr.zip c:\programs\*.*
if errorlevel 14 goto NOSPC1

REM SHIFTING!!
if exist a:\backup_c\2_c_pr.zip del a:\backup_c\2_c_pr.zip
if exist a:\backup_c\1_c_pr.zip move a:\backup_c\1_c_pr.zip a:\backup_c\2_c_pr.zip
if exist a:\backup_c\0_c_pr.zip move a:\backup_c\0_c_pr.zip a:\backup_c\1_c_pr.zip
move a:\backup_c\c_progr.zip a:\backup_c\0_c_pr.zip
goto BACK2

:NOSPC1
echot "NO SPACE (1) on A for c:\\programs backup!" >> c:\_dat\pim\data\backup.pim
set f=y

:noAC

:BACK2

if "%2"=="all" goto pow2ok

voltchck 2.40
if errorlevel 1 goto nopow2
goto pow2ok

:nopow2
echot "POWER TEST (2) UNSUCCESSFUL. No Backup of c:\\*.* and f:\\*.*." >> c:\_dat\pim\data\backup.pim
set f=y
goto FINISH

:pow2ok
echot "Batteries sufficient for C: backup w/o programs." >> c:\_dat\pim\data\backup.pim
echot "Checking DBs in C:\\_dat\\*.?db" >> c:\_dat\pim\data\backup.pim

dbcheck c:\_dat\*.?db > a:\backup_c\dbcheck.log
echot "Done. Result See a:\\backup_c\\dbcheck.log"  >> c:\_dat\pim\data\backup.pim
if errorlevel 2 goto dberr2
echot "Databases okay." >> c:\_dat\pim\data\backup.pim
goto zip2

:dberr2
echot "DB(s) (2) FAULTY. See A:\\dbcheck.LOG ! No backup of C:\\*.* this time!" >> c:\_dat\pim\data\backup.pim
set f=y
goto BACK3

:zip2
echot "Zipping C:\\*.*" >> c:\_dat\pim\data\backup.pim
if exist a:\backup_c\c.zip del a:\backup_c\c.zip
pkzip -rp -ex -whs -Jhrs -x@a:\backup_c\omit2.pkz a:\backup_c\c.zip c:\*.*
if errorlevel 14 goto nospc2

REM SHIFTING!
if exist a:\backup_c\2_c.zip del a:\backup_c\2_c.zip
if exist a:\backup_c\1_c.zip move a:\backup_c\1_c.zip a:\backup_c\2_c.zip
if exist a:\backup_c\0_c.zip move a:\backup_c\0_c.zip a:\backup_c\1_c.zip
move a:\backup_c\c.zip a:\backup_c\0_c.zip

goto BACK3

:nospc2
echot "NO SPACE (2) on A for c:\\*.* backup!" >> c:\_dat\pim\data\backup.pim
set f=y



:BACK3

if "%2"=="all" goto pow3ok

voltchck 2.40
if errorlevel 1 goto nopow3

:pow3ok
echot "Batteries still good. Doing F:\\*.* Backup." >> c:\_dat\pim\data\backup.pim

:zip3
echot "Zipping F:\\*.*" >> c:\_dat\pim\data\backup.pim
if exist a:\backup_c\f.zip del a:\backup_c\f.zip
pkzip -rp -ex -whs -Jhrs a:\backup_c\f.zip f:\*.*
if errorlevel 14 goto nospc3

REM SHIFTING!!
if exist a:\backup_c\2_f.zip del a:\backup_c\2_f.zip
if exist a:\backup_c\1_f.zip move a:\backup_c\1_f.zip a:\backup_c\2_f.zip
if exist a:\backup_c\0_f.zip move a:\backup_c\0_f.zip a:\backup_c\1_f.zip
move a:\backup_c\f.zip a:\backup_c\0_f.zip

goto FINISH


:nospc3
echot "NO SPACE (3) on A for f:\\*.* backup! >> c:\_dat\pim\data\backup.pim
set f=y
goto FINISH

:nopow3
echot "POWER TEST (3) unsuccessful. No F:\\*.* backup." >> c:\_dat\pim\data\backup.pim
set f=y
goto FINISH

:nobackup
echo Nobackup. No backup created (noly manually), END.
goto FINISH

:FINISH
timestmp >> c:\_dat\pim\data\cur.pim
if "%f%"=="n" echot "Backup successful!" >> c:\_dat\pim\data\cur.pim
if "%f%"=="y" echot "BACKUP FAILURE! See backup.pim" >> c:\_dat\pim\data\cur.pim
echo. >> c:\_dat\pim\data\cur.pim
goto end

:NOENV
echo NO ENVIRONMENT SPACE AVAILABLE!
echot "NO ENVIRONMENT SPACE AVAILABLE!" >> c:\_dat\pim\data\backup.pim
echot "BACKUP FAILED! NO ENVIRONMENT SPACE AVAILABLE!" >> c:\_dat\pim\data\cur.pim

:end
setit lo

How it works (in words):

Usually I plug in the AC adapter before I go to sleep. Sometimes not.
I want to let nightly.bat do all its jobs if AC is plugged in (they take about half an hour), if AC is not plugged in, I want nightly.bat to leave alone backing up c:\programs entirely (since there are programs only, which don´t change too often anyway.
And if AC is not plugged in, I want nightly.bat to do the most important thing first, then all the others, and before every new action it checks the battery voltage. If the battery voltage has droppen below 2.40 volts, I want nightly.bat to finish its job instantly.

Also I want to be able to give parameters to nightly.bat in case I call it manually to control its behaviour (bypass voltage checks for example).
And the report is now created very detailled with time stamps (using my self-made utility "echot") and written into "backup.pim" for PIM/PE instead of a single line written into the appointment book.

Here is the "English translation" of nightly.bat:

IF %1 is not "everything" goto "NORMAL"
IF %2 is not "all"        goto "NORMAL"

Deactivate light sleep mode (using setit)

:NORMAL

set environment variable "f" to "n" (is later used to indicate bakup failures)
check if "f" is really "n", otherwise goto NOENV

Create a time stamp in backup.pim
and write "starting nightly.bat" to backup.pim

IF %1 is "nobackup" goto OTHER (no backup, only "other nightly jobs")
IF %2 is "all" goto POW1OK (bypass first power check)

Volt check for 4.00 volts (only "true" if AC is plugged in, see voltchck documentation)
If not true goto NOAC (no adapter plugged in)

:POW1OK
IF %1 is "onlybackup" goto NOOTHER (i.e. override "other nightly jobs")
write "AC connected. Doing everything" to backup.pim

:OTHER
...
here are all the other things which I want to be done nightly,
i.e. pdb2x, reindexing FIND/LX etc.

IF %1 is "nobackup" goto NOBACKUP

:NOOTHER
(from here everything is backup-related)

REM ================= Backup 1 ====================
:BACK1  (backup no 1)
:ZIP1
PKZIP C:\PROGRAMS
if PKZIP ends with errorlevel 14 (not enough space) goto SPC1

For rotational backup: Delete last one in the queue,
shift existing ones one place forward
and put new ZIP file at the end.
goto BACK2


:SPC1
set variable "f" to "y" (to indicate a failure)
and write failure to backup.pim

REM ================= Backup 2 ====================
:NOAC
:BACK2  (backup no 2)
IF %2 is "all" goto POW2OK (bypass 2nd power check)
Volt check for 2.40 volts
IF power OK goto POW2OK,
ELSE goto NOPOW2

:NOPOW2
write failure to backup.pim
set environment variale "f" to "y" to indicate failure
goto FINISH

:POW2OK
write to backup.pim that power is OK in 2nd test
checking data bases (using dbcheck)
IF a data base is not OK, goto DBERR2
ELSE write "databases Okay" to backup.pim
goto ZIP2

:DBERR2
write "database faulty" to backup.pim
set "f" to "n" to indicate failure
goto BACK3

:ZIP2
Doing 2nd backup:
PKZIP C:\*.* (without C:\PROGRAMS)
if PKZIP ends with errorlevel 14 (not enough space) goto NOSPC2

For rotational backup: Delete last one in the queue,
shift existing ones one place forward
and put new ZIP file at the end.
goto BACK3

:NOSPC2
write "no space" to backup.pim
set "f" to "y" to indicate failure

REM ================= Backup 3 ====================
:BACK3
IF %1 is "all" goto POW3OK (bypass 3rd power check)

Volt check for 2.4 volts
IF power OK goto POW3OK,
ELSE goto NOPOW3

:POW3OK
write to backup.pim that power is OK in 3rd test

:ZIP3
PKZIP F:\*.* (the small RAM drive, which contains drivers, but doesn´t change often)
if PKZIP ends with errorlevel 14 (not enough space) goto NOSPC3

For rotational backup: Delete last one in the queue,
shift existing ones one place forward
and put new ZIP file at the end.
goto FINISH

:NOSPC3
write "no space" to backup.pim
set "f" to "y" to indicate failure
goto FINISH

:NOPOW3
write "no power" to backup.pim
set "f" to "y" to indicate failure
goto FINISH

:NOBACKUP
ECHO "doing no backup (only manually). END!
goto FINISH

write timestamp to cur.pim
if "f" is "n" write "backup successful" to cur.pim
if "f" is "y" write "backup FAIULURE, see backup.pim" to cur.pim
goto END

:NOENV
ECHO "NO ENVIRONMENT SPACE AVAILABLE"
write "backup failed, no environment space available" to backup.pim and cur.pim

:END
enable lightsleep mode (with setit)

Special thanks to Konstantin v. Witzleben for testing the whole setup, Tony Hutchins for translating the Macros from German to English and Avi Meshar for the basic idea for the way of creating the notification in the appointment book!

Archived 2013-12-08
This page has been archived and some links may not work correctly anymore. No updates of this page will be done anymore.

How to repair a HP 100LX, 200LX or 1000CX Palmtop

Contents of this page:


See also: Tutorial: Disassembly of a 200LX 


Introduction / where to let the palmtop repair:

This page is intended to give you advice if your HP Palmtop is broken.

If you want to let your palmtop repair professionally, you have two options: 

  • Thaddeus computing in USA repairs palmtops for a flat rate, regardless of the defect. They have excellent service and turnaround time, you even get warranty on the repaired device. They also buy used units.

  • Another option for you is to use my repair service. Please contact me to get an individual offer. It helps, if you describe the defect as detailed as possibile in your first email, ideally providing photos or a video showing the symptoms of the defect

In case you decide it is not worth to repair the palmtop anymore, please do not throw it away. It certainly contains valuable spare parts. In that case, please submit an offer for me to buy this machine.

 

If you need advice how to repair a palmtop yourself, read on:

Of course I cannot cover every imaginable defect, so I´ll describe the most common problems and the problems I´ve had myself. Since HP discontinued the 200LX palmtop, it becomes more and more important to repair broken units, because it will be difficult to find used units in good shape. 

For some of the repairs, you should be familiar with opening the palmtop´s case and taking it apart. For some repairs you even have to take the screen out of its shell. So if you have doubts, rather ask a friend who is able to do this quite complicated job for you.
Warning: You can take almost the entire palmtop apart, you´ll get it back together if you know how you took it apart. But there are a two exceptions:

The right hinge and the screen:
1. The right hinge: Don´t ever take the right hinge apart! Don´t remove the metal ring that holds the hinge together! You probably won´t be able to reassemble it, and that would result in a nearly unusable palmtop! If you want to remove the screen, you can do it leaving the hinge intact. Remove the four Torx-6 screws and carefully bend the screen part of the case apart and take the screen out of it. The screen is only lying in there, no additoinal screws, and the electric contacts are only pressed onto the screen by the two case screws on the left side which you have already removed.

2. the screen itself: If you have taken the screen out of the case, the only thing you can do is to separate the electronics board from the LCD by bending the little metal latches away from the circuit board. But don't ever remove the flat cable that goes from the electronics board of the screen to the LCD glass! That would let the screen die forever! Additionally, it is very difficult to get both screen halves back together; it is a matter of 1/10th mm! SO rather avoid that.

 

What you will need when doing your first repair job, is advice about opening the palmtop. I have written an article about the process of dismantling the palmtop. There is another source for advice for this:
This email address is being protected from spambots. You need JavaScript enabled to view it. wrote a page with instructions guiding you through the process of opening the palmtop and even doing hardware upgrades. Click here to read these instructions.

 

Let's now talk about the actual repairs:

 

Broken latch:



The latch which holds the case closed if you put down the screen lid gets easily broken. What breaks is not the latch itself, but very thin plastic springs that are responsible for the latch to flip into its original position after you pressed it to open the lid.

It is nearly hopeless to try to glue the spring back to the latch. It will break again sooner or later.
But there are some ways which enable the latch to work again.

1. Use a piece of a rubber band and sqeeze it into the gap under the latch. Maybe cut ittle triangles out of the rubber band, so that it is not so strong.

2. The solution I chose: A drop of silicone, which is actually used to make tight the gap between your bathtub and the wall, will do the job very nicely. You can use a screw driver to work the silicone into the gap under the latch, Just be sure to wipe away any silicone that remained outside. Let it become hard 12 hours with the latch fixed with adhesive tape or something like that, and voila: You have a working latch again.

3. Also a small piece of foam rubber (abt. 13mm * 8mm and abt. 1-2mm thick) can do the job very effectively. I have one palmtop repaired this way, too. Looks not as ugly as the above solutions and works very well.

 

The hinge crack:


Sometimes the case right above the right hinge of the palmtop breaks due to the strain if you open and close the palmtop frequently. This type of defect is typical for the HP 200LX and appears quite often. It is usually called the "hinge crack". The hinge crack is forced by a hinge that's too tight (See next item!)

 

Some people simply wait until the crack is wide enough and then put a little(!) drop of superglue or epoxy glue into the crack. That seems to work if you use very good glue.
However, the chance that this fix breakes again is big. There are other approaches, Alan Striegel used a small metal plate to reinforce the hinge, his results are shown on his home page. I have also tried this approach and so far I can tell it seems to be very reliable:

 

 

A nice 100LX user, Thomas Mahoney Jr., provided the method he used to successfully repair his hinge crack:

After using 2-part epoxy to reglue my broken hinge halves, I test fit the spring to make sure it was going to fit. Use an X-acto knife to smooth out the epoxy that may have entered the inner hinge area. CUT the hinge spring to about 75% of its usual length with a pair of diagonal cutters, so that you do not need a lot of force to compress the black ring onto the plastic hinge halves. Once all of the hinge pieces are in the correct order and in the hole, I used 2-part epoxy to glue the black ring onto the repaired hinge. The epoxy also acted as a "rubbing" dampener, that is, it makes it harder for the display to flop/fall down since the friction of the epoxy in the area of the right hinge against the hinge tube. The epoxy on the outer hinge also makes it harder for the hinge cap to come off and tightly grips the hinge assembly. Once the epoxy is dried, you may have to use an X-acto knife to cut away undesired epoxy that may be blocking the hinge tube from going back into position and/or cut epoxy away from the outer hinge so the hinge cap can slide on. I had to cut the hinge cap open slightly in order to make it slide onto the hinge. The hinge works good. I actually needed a drop of lubricant to loosen it up slightly after this repair.
Thanks for the dismantling guide. It's great!
Have a great day,

Tom

The hinge is too tight or too loose

If either the hinge is too tight (danger of hinge crack) or too loose (screen falls slowly back while you are working), you may be able to fix that (it does not always work!):
Remove the cap from the right hinge (only the right hinge contains the mechanics). You can do that by carefully prying it off with the nails of your two thumbs while the screen lid is opened with an angle of 90 degrees to the keyboard.


What you see then is a metal shaft in the center and plastic parts around it. The hinge consists of a spring which presses a little plastic cone onto a metal ring (which is on the side you cannot see because it's in the tube). The black plastic you can see directly around the metal pin is the back side of the spring with its plastic anchor. Now you have to adjust the friction of the cone to loose / tighten the hinge. You can do that by using very little amounts of either a lubricant (to loose) or Isopropanol alcohol (to tighten the hinge). Use only a very little drop of the lubricant and work the hinge a few times by opening and closing the lid. Of Isopropyl Alcohol you can use larger volumes. I suggest to use a syringe to apply the lubricant or alcohol.

Caution: Some people reported problems with some lubricants which seem to attack the plastic material! WD-40, for example, must never been used! And remember: Don't ever take apart the right hinge, except you know exactly what you're doing!

 

The screen: Missing pixels and other problems (and: Doublespeed upgrade!)

If you don´t see anything on the screen, as if the batteries were dead, but you know they aren´t, it is most probably not a screen problem. It may be a software problem. Take out all batteries, press the On key for a few seconds, then let the palmtop alone for 24 hours (so all electricity can vanish). Then put the batteries into the palmtop again and see if it works now. If now, it may be an electrical problem.

 

If the screen shows weird characters on boot-up or if the screen contents are shifted by about two columns to the right and the two left columns show flickering nonsense, the screen is not defective, but your palmtop is double-speed upgraded! To make things look well again you need a driver. If the double-speed upgrade has been installed by Times2Tech, use the driver by Mack Baggette. The following picture shows a typical double-speed-without-driver screen:

 

 

It can sometimes be much worse, so that even the characters are not readable anymore.

 

To be sure you have a double-speed upgraded palmtop, you can also enter the self-test mode of the palmtop (only if the screen is readable, otherwise you cannot read the self-test output!) using Esc-On to switch it on instead of just On. Then do the "Timers" test. If the test is not successful, the palmtop is upgraded. (Warning: Never do the RAM-Card test if a flash card is in the slot, this test is only for SRAM cards and can destroy other cards!)

 

If you look through the backup battery tray, you may see if a double-speed crystal is installed. If on the silver cylindrical component behind the tray is written 158 CP52, it is an original single speed palmtop, if you see F31.673, the palmtop has been double-speed upgraded:

 

 

If you see nothing written on the crystal, you either have to open the palmtop to read the crystal model number, or run the built-in timer self-test: Press Esc-On to switch the palmtop on, and if you can read the screen well, go to Timers test and press enter to execute it. If it fails (output: time bad), probably a double-speed upgrade is installed. If you cannot read the screen at all due to strange characters, you can be quite sure that a double-speed crystal is installed. Load the above mentioned driver and the screen will be readable again.

 

If lines or blocks of the screen are missing, flickering or black, or if the whole screen is black or white, there may be a defect.

 

There are various typical scenarios which I try to describe here. It heavily depends on the symptoms where you will most probably find the problem: 

If the whole screen turns black or white, flickers wholly or block-wise, or something like that:

Maybe only the contacts between the screen cable and the screen itself are loose: Switch the palmtop on so that you see a picture which lets you see problem and press on the area marked in the picture below.


Does that fix the problem temporarily? If yes, you should pry off the screen cover on which is written "200LX" and so on and then fasten the two Torx-6 screws on the left side of the screen. If the screw fastening is not enough, you can probably use a few layers of paper to make the pressure contacts under the screws stronger. If these contacts aren´t the problem, maybe the cable which connects the screen to the motherboard is damaged or not properly attached to the motherboard connector.

If you have missing pixel lines (rows or columns), but if only every second column in a certain area is missing

(e.g. as you can see on the picture below) this is most probably caused by IC contact problems. Since all the mechanical stress when opening and closing the LX is only applied on the right side (because only the right hinge contains the relevant mechanics), mostly contacts on the right side are affected, and these are responsible for the columns of the right part of the screen.

A failure of that kind can look like this (type "On" and the slash "/" to invert the screen, so it becomes obvious which lines are missing):

 I was able to fix such a screen durably by resoldering the pin rows of some of the SMD ICs on the screen´s circuit board which have become loose.

The following pictures show a removed screen module with the ICs on the back. There is no way to tell without tests which of the pin rows may be loose. You have to try that by connecting the screen to a motherboard and pressing gently onto some ICs and their contacts or using a small screw driver to short-circuit the contacts one-by-one carefully while you observe the screen. Please note that you should use real SMD soldering equipment (a soldering iron blowing hot air), otherwise you need an extremely sharp soldering tip and a very calm hand.

 

 Here you can see the principle how the ICs are wired on the other side of the circuit board (so you can understand which columns depend on which IC contacts):

 

 However, if you have a screen which looks like this on the back:

 

You are out of luck, because these kind of screen has the ICs on the other side of the PCB and if that wasn´t bad enough, these ICs are fully covered and don´t have any legs which can be resoldered. But on the other hand, these screens are probably much less prone to this kind of failure. Another problem may be a too loose pressure of the screen glass to the conductive rubber band which connects the circuit board contacts to the contacts between the screen glas layers. But that happens only rarely. This can be fixed, too, but I only recommend that if you have good fine-mechanical skills and if this screen is not your only one - you could damage it forever with the following procedure:

There are metal latches which press both screen parts together. A pair of such latches is marked on the following picture: 

You can first try to fasten these latches in the area where pixel columns are missing. If that doesn´t help, you have to separate the two parts of the screen and clean the contacts of circuit board, rubber band and the glass contacts carefully with alcohol and then reassemble it. The reassembling is tricky, because you have to place the both parts horizontally exactly as they were before you separated them, otherwise the contacts of circuit board and screen do not fit. Although the metal frame helps with that, you cannot rely entirely on that frame.

First, bend the metal latches straight so that they don´t press the parts together anymore. Take care the you do not break one of the latches. 

Now you can remove the entire metal frame in which the two parts are embedded and pressed together.

Don´t separate the LCD from the circuit board yet, but apply some markings on the rubber bands and on the side of the circuit board, so you can later adjust them horizontally 100% precisely again.

 

Then carefully seperate the two parts, but note that they are still connected by a conducting adhesive tape on one side, this is for the horizontal lines and cannot be removed, otherwise you damage the screen permanently and make it totally unusable! Also make sure the white rubber bands remain on the LCD glass. This makes it way easier to reassemble the screen later. The following pictures show an opened screen:

Screen with metal frame still mounted:


 Screen with removed metal frame: You see the white conducting rubber bands on the long sides and the yellow conducting adhesive tape on the short side.


 Seperated screen parts: Do never remove the yellow conducting adhesive tape (actually a ribbon) on the short side and be very careful with it! Do not apply any force to it! 


Now you can carefully clean the thousands of contacts on the circuit board and on the rubber band. Lift the rubber band only in these areas from the screen glas, where columns are missing, and clean the contacts there, too. Then reattach the rubber band to the glass and reassemble the whole screen. Take care you adjust the two parts horizontally exactly the same way they were adjusted to each other before, otherwise you will not get a valid picture, if you will get one at all! Many missing columns in a pattern which looks like an interference pattern can be the result.

Be sure to bend the metal latches again so that the two parts are pressed together with appropriate force.

 

If a block of consecutive rows or a single row is missing:

This can be caused either by bad IC soldering contacts, or (which is the worse case) by a defective ribbon cable - the yellow one on the right short side, which connects the LCD glass body to the circuit board of the screen module.

First try to find loose IC contacts, as described above. If that is not successful, take the screen module apart as described above, prepare a flat iron (highest heat level), put a bunch of paper strips under the contact row of the LCD on the right, where the yellow ribbon cable connects, to support the LCD glass mechanically, then press the flat iron gently onto the ribbon cable, moving it slightly, to melt the plastic and glue a little. After a few seconds, remove the flat iron and let the screen get cold again. I was able to fix some screens using this method. But it is risky, if you apply too much heat to the ribbon cable, it may be damaged permamently. In case this didn´t fix the problem, try the same on the contacts on the other side of the ribbon cable (on the circuit board).

 

 

Some or all keys of the keyboard don´t react anymore

Most likely the pressure contacts which connect the keyboard to the motherboard are not pressed strongly enough against the motherboard. These contacts are placed in the area under the menu key, the right shift key, the zero key and the dot key. Try to press the two parts of the palmtop´s shell together in that area and see if that fixes the problem.
If it only fixes it temporarily, you should try to fasten the screw under the plus key (from the bottom of the palmtop).

If that also doesn´t help, it may be necessary to clean the keyboard contacts to reduce resistance between the two contact counterparts. For that, you´ll have to open the palmtop. Click here to read how to do that. Be very careful when cleaning the keyboard foil contacts with alcohol or any other solvent. The contacts are build by a thin graphite layer, which is easily rubbed off using solvents. Clean them only once, and with only slight pressure with a soft tissue and some alcohol. Don´t worry about the black stuff rubbed of the contacts: It´s probably no dirt, but the graphite itself. So do not rub until no black stuff is rubbed off anymore!

The contacts on the motherboard can be cleaned as usual, using isopropyl alcohol and a tissue. These contacts are made of copper, so they cannot be rubbed off using a tissue.

 

Other case cracks

The hinge crack is by far the most common crack which appears on the case of the LX. However, there are a few more positions which the case breaks easily at. For example the little plastic "bridge" on the back between the battery cover and the keyboard part of the lower case shell:

 

 

I have no idea how this can be fixed the best way. I would try to take the shell apart, put epoxy glue into this crack, wrap it with adhesive tape until the glue is hard, remove the adhesive tape and then reassemble the palmtop.

Archived 2013-12-08
This page has been archived and some links may not work correctly anymore. No updates of this page will be done anymore.

Tutorial: Build an LED light for the Palmtop

Contents of this page:


 

What is the LED light?

 

The LED light is a device that illuminates the screen of your HP Palmtop 100LX, 200LX, OmniGo 700LX or 1000CX.
It gets its power from the palmtop´s serial port, so no external power source is needed.
You simply plug the LED light into the serial port, load the Software ´LIGHTON´ (by Stefan Peichl), and you can switch the LED light on and off using the hotkey Fn-L (or any other hotkey).

 

Since the backlight upgrade project by Thaddeus Computing has been cancelled due to technical problems, such an LED light is in my opinion the most comfortable solution if you need to read the screen of your palmtop in bad lighting conditions or even in total darkness.
UPDATE: I have taken over the backlight project in 2002 and continued the great work the people of Thaddeus computing have done, so now there is a backlight upgrade available for the 100LX, 200LX and 1000CX. If you prefer backlight instead of a LED light, please click here!

 

If you bought an LED light from me (so don´t have to build you own one), please jump directly to the usage instructions!

 


This picture shows my LED light in action: This picture was taken in nearly total darkness. As you can see, the screen is perfectly readable and even the keyboard is a little bit illuminated!

 

First a note about the electronics: You may wonder why no current limiting resistor is needed. The reason is, that the RS232 port driver chip in the palmtop contains already current limiting resistors for each line, which are needed to protect the port from all kinds of short circuits. The RS232 specification says that an RS232 serial port has to stand short circuits for an unlimited time. If you insert an additional resistor for safety here, you will drop the current so much that the light will not be bright enough anymore to be useful. The 6.8 mcd, which the LEDs should produce, are only reached at a current of about 20mA. Here we have a current of only about 10 mA, so the LEDs are not as bright as they could be anyway. So don´t worry about the serial port - it will probably be safe, even without an additonal resistor. I use my LED light every evening for several years now, without any sign of a damage to the palmtop.
However, I do not guarantee that it is totally safe. Damage may occur to your palmtop, I will not be responsible!

 

Also, all LEDs are different, even if it comes from the same manufacturer, has the same part number and so on. So you may notice a slight difference in brightness or colour temperature of the two LEDs of the LED light. This effect is enforced by the fact that the LEDs are not driven at their nominal current, but at a much lower current.

 


 

Building Instructions

 

What you need:

  • 2 white LEDs. I used Wustlich WU-7-750 SWC. Specs: 5mm white, GaInN, viewing angle 20 degrees, 6200 mcd at I=20mA. Available from Segor Electronics. Other kinds of LEDs may also work, but only white or blue ones. Red, orange or yellow LED light is not reflected well enough by the reflective layer of the screen. Also in the meantime there might be LEDs on the market with better suitable characteristics. A wider angle would be preferable, for example.
  • A connector for the serial port. For example part number 739251 from Conrad ElektronikClick here to see pictureIt is a 2*20 pin connector, which has to be cut to 2*5 pin. The connector of a notebook 2,5" IDE hard drive also has the correct hole spacing, but it doesn´t have the pins on the back, so it cannot be easily soldered to the circuit board.

The following items can probably be found in any electronics store:

  • a 1cm * 2cm piece of circuit board, both sides copper-coated, 2mm thick
  • 23 cm of stiff copper wire 1,2mm diameter, Segor order number: K4030-12501.
  • 25 cm of flexible insulated wire
  • 20 cm of heat shrink tubing 2.4mm diameter
  • 3 cm of heat shrink tubing 12-14mm diameter
  • 2 cm of heat shrink tubing abt. 5mm diameter
  • hot melt glue
  • a soldering iron
  • a rotary grinder or something similar to remove some of the copper of the circuit board. Of course if you have the tools, you can also etch the circuit board according to the plan below.

 

Here is a step-by-step guide to build the LED light:

    • Cut off a 2*5 pin piece of the connector, which fits into the serial port of the palmtop.

 

 

    • Use a rotary grinder or an adequate tool to build the needed copper circuits on the board. On the bottom side, no pin has to be connected to anywhere. They must all be insulated from each other. On the top side, pins 3 and 5 are used: Pin 3 is +Vcc for the LEDs and should go to the big copper plate with the holes, where later the stiff copper wire is soldered into, pin 5 is ground and should be connected to the second, flexible wire. Also drill the two holes into the circuit board. They should have a diameter of 1.3 or 1.4mm and the hole next to the connector side of the board should be at least 9 mm away from the connector side.

 

      If you have the equipment, you can of course etch the circuit board according to the diagram below, but you should not use the graphic as the template, because the lines may be too thin to make a good insulation gap.

 

    • Then solder the connector to the circuit board. Take care not to procude short-circuits!

 

 

    • Bend the stiff wire using pliers the following way:

 

 

    • Stick the stiff wire through the holes of the circtuit board and then bend the tail of the stiff wire around the edge of the board, so that it has a firm hold, even without soldering.

 

 

    • Now solder the stiff wire to the large copper plate. Use much soldering tin.

 

 

    • Solder one end of the flexible wire to Pin 5 of the connector.

 

 

    • Test, if the light works: Plug it carefully into the serial port of the palmtop, do a

serctl /w

          to enable the port, then take an LED and connect it with the short leg to the stiff wire, the long leg to the flexible wire. The LED should shine brightly.

 

 

    • Push the 20cm 2.4mm heat shrink tubing over the two wires and shrink it.

 

 

    • Carefully apply hot melt glue to the bottom and top side of the circuit board, so that it gets a little more voluminous, and so that everything is fixed (esp. the flexible wire). Let the glue get cold. You could also use Epoxy glue here, but that one gets so hard that corrections, if necessary, are difficult. If you use hot melt glue, you don´t have to take care that it doesn´t look ugly, because that kind of glue will be melted again when heating the tubing later and adapt itself "automatically" to the tubing.

 

 

    • Prepare the 3cm 12-14mm heat shrink tubing: use a small screw driver to prick a little hole from the inside to the outside of the tubing, exactly where the LED light arm will pierce it.

 

 

    • Bend the LED light arm directly above the board 90 degrees towards the connector. Be careful to not break the stiff wire!

 

 

    • Prick the arm with its wires from inside through the hole of the large tubing and slip it over the circuit board. Bend the arm up again (carefully!) and shrink the tubing. Begin at the connector side, so hot melt glue getting liqid again cannot pour from inside and fill the contact holes of the connector. This could destroy the connector! Do no apply too much heat here, otherwise the hole in the tubing can be teared open too much. Cut off hot melt glue which poured from the back of the LED light grip with a hot knife. Also cut off tubing which may be in front of the connetor holes.

 

 

Now it should look like this:

 

 

    • Take the two LEDs, bend their legs as the first picture shows (carefully! Don´t break the legs!) and twist the corresponding legs together (short led with short leg, long leg with long leg).

 

 

    • Shorten the LED legs. Cut them off so they get the same length, see picture:

 

 

    • Shove the 2cm 5mm tubing over the LED light arm and cut the two wires to an equal length, so that they are abt. 1cm longer than than the tubing which they are in:

 

 

    • Solder the LED leg which is made from the two originally short legs to the stiff wire and the leg which was long before to the flexible one. If you don´t know the right direction, simply plug the light into the palmtop and try it out by applying the LED legs to the wires manually.

 

 

    • Wrap a piece of paper around the legs to prevent future short-circuits.

 

 

    • Shove the 2cm 5mm tubing over the soldering points, apply a spot of hot melt glue onto the top where the legs come out to stabilize the legs and shrink the tubing.

 

That´s it!

 

 


 

Usage instructions

 

Software:

There is a little program (a TSR) written by Stefan Peichl especially for the LED light, called LIGHTON, which lets you simply switch the LED light on and off by using the hotkey Fn-L. Download this program from the S.U.P.E.R. site, unzip the archive, place the file lighton.com somewhere on your C: drive (for example in c:\bin) and add a line to your autoexec.bat:
c:\bin\lighton.com
Then reboot your palmtop. (You may need the COM file from the LIGHTON2 package. Try which one you need: Go into DOS mode and press Fn-L (if no LIGHTON TSR is loaded). If a pound symbol is created, LIGHTON is okay. If just a lowercase L is created, you need LIGHTON2, which has the hotkey changed to Alt-L, instead of the original hotkey Fn-L)
After the reboot, you should hear a beep sound everytime you press Fn-L or Alt-L.

Unpacking

If you received your LED light by mail, I probably have folded it up and put it into a music cassette box (picture shows box with two LED lights). If not, omit the following step.

 

 

Remove all adhesive tape carefully (or rip it open with a sharp knife for example) and unpack the folded LED light.
The first thing you should do is to remove the three kinks by bending them into the opposite direction, so that your LED light is straight.

 

 

Caution: Don´t bend the LED light too much. The stiff wire used inside the light is a copper wire which will break if you bend it too much or often. So be careful!

 

Adjusting the LEDs

Now plug your LED light into the serial port of the palmtop and switch the palmtop on. Does the light work? Try to press Fn-L or Alt-L a few times, you should switch the light on and off by that. If not, you either installed lighton incorrectly or you have another TSR loaded which keeps the serial port deactivated (like Buddy, for example).

 

Well, your LED light illuminates the ceiling now. That´s nice, but not what you bought the LED light for. Darken the room and see how bright the LEDs are! They may indeed illuminate your entire room a bit.

 

Now the most tricky part begins: You now have to adjust the LEDs so that they illuminate the screen in an optimal way (i.e. as evenly as possible). A few rules-of-thumb:

 

    • The LEDs must point from a similar direction than your eyes look, otherwise you will get only odd effects due to the light reflection and polarizing properties of the screen.
    • The distance of the LEDs to the screen must be at least 8-10cm, because the LEDs have a viewing angle of only 20 degrees.

 

First, bend the whole thing so that the LEDs point onto the screen in a way I just described. It should look as on the pictures:

 

 

Always take care you don´t press the contacts of the LEDs together, you could cause a short-circuit, which wouldn´t damage anything electrically, but you would wonder why the LEDs don´t shine and you would risk mechanical damage of the LED legs.

 

 

Now you have to fine-tune the LEDs´ positions. Be careful! First, adjust the angle between the LEDs in a way that one LED illuminates the right part of the screen and the other one illuminates the left part. Then bend the whole LED head again to finish the adjustment.

 

It will take a while until you will get used to the reflections of the LED light which you will always see on the screen. Maybe you even find a position where the reflections disappear without too much light loss. Simply try around!

 

 

This is a badly adjusted LED light:

 

 

And this is how it should be:

 

 

These pictures show only the center light dots of the LEDs, but the surrounding light will be fully sufficient to make the screen readable even in total darkness. And as a side effect, the keyboard will be well visible!

 

Have fun!

 


 

 

DISCLAIMER:
I'm not responsible for physical or other damages to your devices. The descriptions I made may contain errors which could cause serious damage of your palmtop or your peripherial devices. What you build here is a device directly connected to the motherboard of your palmtop. If you damaged the motherboard, it would become really expensive for you!

Archived 2013-12-08
This page has been archived and some links may not work correctly anymore. No updates of this page will be done anymore.

HP OmniGo 100 / 120 - Technical Information

Contents of this page:

Introduction

The HP OmniGo 100 is a totally different kind of palmtop than the 100LX, 200LX, 1000CX and even the OmniGo 700LX: It is GUI based, can be controlled by pen input or keyboard, but it lacks that great versatility of the other models, because it cannot be run in a real DOS mode. There is software which lets you run some DOS programs on the OG100, but this is very limited. The normal operation mode of the OG100 is GEOS, with its Graffitti handwriting recognition, which works surprisingly well.

This is describing text from http://www.thocp.net/hardware/hp_omnigo100.htm:

The HP OmniGo 100 handheld organizer includes a host of financial- and business-productivity functions designed to eliminate the need for multiple reference tools. In addition to incorporating the industry-standard HP 12C financial calculator, the new product´s personal information-management features include the following:

  • pen-navigation and keyboard-input capabilities - to accommodate user-interface preference;
  • a jotter application - to allow customers to capture information on the go and organize it later;
  • a Graffiti handwriting system - for easy-to-learn handwriting recognition; drawing capabilities - to enable the user to scribble quick notes and design maps and pictures;
  • HP financial-analysis tools and spreadsheet capabilities - for computing cash flow and loan payments, currency conversions, business calculations, percentages and margins;
  • a notepad feature - to input notes and organize thoughts via keyboard and pen entry;
  • appointment, address and telephone books - to give users a central repository for access to important personal appointments, activities and contact information;
  • database capabilities - for personalized list management; and
  • worldtime feature - for locating cities around the world and obtaining current time and city information.

I have not heard of any hardware upgrades which are available for the OmniGo 100/120.

Pictures

These are pictures of the internals of the OmniGo 100:

Usage of PCMCIA SRAM / Flash / CF storage cards

Although all documentations and FAQs say that the OmniGo 100 does only work with SRAM cards, and not with Flash or Compact Flash, I had success using a Sandisk 192MB Compact Flash card with my Omnigo 100. It worked instantly without any problem. If you want to put new programs for the OG100 on a card so that they can directly be used, you should let GEOS first prepare the card. Then you can put *.GEO files from the program packages into the \geoworks\world directory, put the card into the OG100, reboot the OG100, and the programs are available from the main menu screen.

Interesting external links

http://nenya.ms.mff.cuni.cz/~gergic/ogo_page/omnigo.html

http://www.mgroeber.de/omnigo.htm
http://www.salbrook.woodwind.org/ogo
http://www.scc.net/~jonco/omnigo
http://www.ulrich-cordes.de/omnigo/german/omnigo.htm

Do you like to support me?

Dear fellow Palmtopper!

If you like, you may reward me for the work I put into this website with a donation.

 

For a donation in US$:

For a donation in €:

Your donation, even if it's just a single USD, will help me to:

  • finance the server that hosts the site
  • justify time I spend with maintaining the site and do not spend with earning money otherwise (wife is watching! ;D)
  • just continue to be motivated :)

Since my company "hermocom" does not exist for many years anymore, I am now spending my spare time and private money for all of this. Thank you very much! 🙂

Yours truly,
Daniel Hertrich