software products to the 29 handheld devices (Visor Prisms and Pros)
in our project. The purpose of the project is to have specialty pdas (i.e.
a visor for pediatrics, a visor for surgery, etc.) with content specific to
that specialty. It has taken a great deal of time to load the various
software packages/e-books to the various devices. Some of the pdas
have 5-6 e-books on them.
I was most recently involved in an e-book project,
Academic Libraries Take An E-Look at E-books, evaluated by Tom Peters, CIC, which utilized the
RCA REB 1100 in one college classroom, and the Franklin ebookman in another. The nasty device war
with e-book reading devices seemed to be leading to the use of common pda platforms for e-book
readers in the Palm OS and Windows CE.
From this experience in loading various e-books/software products, there is now a definite reading
software going on. There are e-books using the isilo reader, the Handheldmed reader, the
Franklin reader software, and the Palm OS e-book reader. On any one device, there could
be up to 4-5 reading software programs needed to read the e-books downloaded on the device.
Where will this end? Will there always be a war of some kind be it either device, or reading
software? Handstory looks to solve some of this,
but certainly doesn't seem to provide the answer for everything. I think this will be confusing
for users, not to mention the nightmares of not only having to register and keep up the
software product/e-book itself, but all of the reader software packages too.
Anyone else experiencing these problems, let me know. It would be interesting
to discuss solutions, if there are any, or possibilites for this handheld headache.
This service is brought to you by
News Is Free