Registered: Jan 2001
Location:
Posts: 42

Folks,

I noticed that there are some Ko free in my EM2 module, I believe it might be possible to access it with some Filemover software.

Has anyone thought / managed to change this 250 Ko memory chip to some XXXX Mo chip. We then would have a EM2/Memory module.

BobRus

Registered: Jun 2000
Location:
Posts: 594

Dave Kessler (of Kopsis) is prob. one of the most knowl. ppl. on a subj. like this, so I hope he takes it on when he gets a moment.
250k is sizeable, but not like the kind of mem. many of us (esp. former EM1 users, who requested this) were hoping would be on-board w/EM2. Maybe w/EM3.
FWIW, did you DL the SW update (that fixes 1 major bug, that allowed a photo to sometimes be recorded w/500k of mem!) from the EM site?
For me, the ability to have SW updates to EM2 of this type (and 1 I think many of us are DYYYYYYYING for: shooting color movies on a b&w Visor) outweighs the poss. use of 250k (about 2.5 "large" photos), though I seriously hear what I believe is your underlying concern: shooting more before you have to upload back to the PC.
ANOTHER UPDATE I'M SURE WE WOULD ALL LOVE, BLOCKS / IDEO, IF YOUR'RE LISTENING (AND THANK YOU FOR THE PREV. UPDATE, BTW), IS TO BE ABLE TO MOVE INDIV. PHOTOS TO AN OFF-LINE MEM. SB (CF, SM, MM, ETC.) W/OUT WORRYING ABOUT A "CORRUPTED DB" NOT GETTING THE PIX BACK TO THE PC. (Anyone ever figure out a work-around?)
TIA.

__________________
"Great Spirits Have Always Encountered Violent Opposition From Mediocre Minds." -- Albert Einstein

Registered: Apr 2000
Location: Oakland, CA USA
Posts: 61

I found a workaround. Use an archiving app like pz or Combiner and keep all the DBs together--this keeps the file-moving software from changing record IDs, which is at the root of the problem. If you have a lot of time to kill, Combiner will also compress.

This solves the problem of multiple sets of images on external memory, but not moving individual images. You also still have to restore/sync/delete each set of images one set at a time.