news | articles | reviews | software | modules | accessories | discussion | faq | mobile | store
VisorCentral.com >> Discussion >> Visor Related >> How To / Troubleshooting
16MB Flash

Post a New Thread | Post A Reply

  Last Thread   Next Thread
Author
Topic: 16MB Flash    
goldrazi
Member

Registered: Mar 2001
Location:
Posts: 1

Angry

Please help,[visor neophyte]

I bought the 16MB flash module because I needed more memory capability, but I can not use the software that I bought the module for. I wanted space to carry such programs as 'the 5 minute clinical consult' [3MB], and Lexidrugs [4MB] etc, but transfering these programs onto the module leads to 'fatal exception error' and I have to reset my Handspring. I have also noticed the although the doc files can work from the module, jfile and hanDBase files will again crash if one tries to use them from the module.

How can I use the files that I want to? How will I know what software is compatible with the module?

goldrazi is offline Old Post 03-19-2001 09:19 PM
Click Here to See the Profile for goldrazi Edit/Delete Message Reply w/Quote
MarkEagle
VisorCentral Staff

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

Any database that needs to be written to cannot be stored on a Flash module. There are even some static databases that won't run either.

You can try contacting the developers of the various apps to see if they support running from a Flash module.

__________________




    God bless America, my home sweet home...

MarkEagle is offline Old Post 03-19-2001 10:21 PM
Click Here to See the Profile for MarkEagle Edit/Delete Message Reply w/Quote
lynnallen00
Member

Registered: Mar 2001
Location: NYC
Posts: 17

Question

I also need more memory for those 3 + 4mb programs to which I plan to add some text. The company says that the databases can be stored in the 8 or 16mb module and the added notes kept in the vdx RAM. Question: will the memplug work better, equally or more awkwardly for this purpose? Thanks to anyone who can help.

__________________
'Make everything as simple as possible but not simpler'--Albert Einstein

lynnallen00 is offline Old Post 03-28-2001 12:56 AM
Click Here to See the Profile for lynnallen00 Edit/Delete Message Reply w/Quote
BHansen
Member

Registered: Mar 2000
Location: Cape Elizabeth, ME USA
Posts: 73

16MB Flash

Store LexiDrugs (76K), DIpersonalDB(1K), and notesLexi (1K), 5MCC (77K), 5MCCpersonalDB (1K), K2K3Medication (10K), and notes 5MCC (1K) in Internal.

Store LexiDrugsDB (2442K) and 5MCC2000 (2704K) in Module.

JFile and HanDBase Readers also both need to live in the Internal Memory.

Like iSilo, the texts can live in Memory, but one needs to have the Readers on Internal so the "binoculars" can look over the wall into the Memory Module, where the texts can be read.

You can't reach over the wall with your hand to turn the pages or interact with any text.

Happiness, Yes?

Bruce, The PDA P.A.

BHansen is offline Old Post 03-28-2001 11:22 PM
Click Here to See the Profile for BHansen Edit/Delete Message Reply w/Quote
joelforman
Member

Registered: Dec 1999
Location: New York, NY, USA
Posts: 60

Smile Things that can run off the 8mb flash module

I am a pediatrician and keep lots of stuff on my 8mb flash module (Ver 1.0 which I updated to ver 1.1) with no problems. I have had the module for a year now and am constantly moving things on and off as well. I had problems early on until I learned a few general rules:

1) Most .prc files (apps) can run fine off the module. I usually check th async computing list of flash compatibility first, but if the app I am looking for is not there I will generally go ahead and try. (http://www.asynccomputing.com/flashram/)

2) Many .pdb files can live on the module as long as they are read only and the app doesn't try to modify the data in any way. For instance, Vindigo is NOT flash-compatible. It modifies itself with every hotsync. The Epoctrates .prc file IS compatible, but the data IS NOT (it is modified with every hot sync.

3) NEVER try to move any of those little .pdb file created by various apps to the module. These often contain registration information, bookmarks, notes, and other data that changes with every time you open data with the related app. These are usually only a few kb anyway and don't save much RAM.

4) Always run new apps and DBs out of RAM first before moving to flash. Enter registration codes while in RAM before moving things to Flash.


The following is a list of the files that I have on my module that work fine:

Medically related:

Handheldmed reader (.prc)(112k)
AAP Red Book 2000 (.pdb) read with handheldmed reader (1104k)
I leave in RAM these little files: AxHist DB (1k), EZReader (1k), Reader Annotations (1k), Reader Bookmarks(1k).

Lexidrug .prc 66k
Lexidrug database .pdb 2459k!!
I leave all the other little files in RAM.
UnitConv .prc 17k
Growth (Peds Growth charts) 77k
4tmed 29k
JfilePro 98k (I have lots of patient tracking, call tracking , and reference databases customized.
TealInfo 49k
Imm db 18k
NHLBI Asthma guidelines 51k
Epocrates .prc 144k
(The various versions of MobileLink/Autoupdate don't seem to like Flash)
Medcalc 163k

Others:

iSilo 81k plus tons of customized isilo and doc format documents all fully flash compatible. The flash compatibility is the main reason I went with iSilo ages ago.

Homeloan, Autobase, Tetris, Fireviewer, X-man, Address+, Beampro, Currency, Avantgo (app only 240k), BigClock, BeamBox, DateMate, Datebook4, dbscan, Todoplus, Memoplus, Holiday Planner, SuperUtility, Jshopper, Account manager, Peanut Reader and databases (now PalmReader), subhunt.

I use 7.5mb of both my flash and RAM. I will be looking for a unit with 16mb RAM or more as a replacement in the future.

Hope this is helpful.

Joel

joelforman is offline Old Post 04-02-2001 06:53 PM
Click Here to See the Profile for joelforman Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 07:51 PM. Post New Thread    Post A Reply
  Last Thread   Next Thread
[ Show a Printable Version | Email This Page to Someone! | Receive updates to this thread ]

Forum Jump:

Powered by: vBulletin Version 2.3.4
Copyright ©2000, 2001, Jelsoft Enterprises Limited.