Docs to go duplicated in Flash and RAM

M

Melondayz101

New member
I'm sure this is answered elsewhere on the forum, so if anyone can recall where I'd appreciate it...

Sometime ago i put in a lot of effort getting Spratting and flashing my t3, and ended up with a fairly stable result...

...and then Documents to Go released their v7.003 (i think) update, which I duely installed, and thought nothing more.

I recently noticed now taht I have 2 copies od DTG, and am wondering what the best way of resolving the issue is?

Comments gratefully recieved.

M
 
Do you use a backup program? I have noticed, even with Spratting that if I don't use a backup program and I move things to my card I get duplicates.
Carol
 
I do back up - using cardbackup, but just to clarify this isn't a duplication of files on the palm and on an SD card, it it duplicate application files, on the palm, in flash and ram.

Doing a search of the forum indicates that i should remove the flash ones (as they are the old apps) and that the apps in flash are the new versions, and that these are being used anyway.

I _should_ just be able to move the new apps into flash (compacting issues aside, nod to PTL)

I found however when i did this last night that i didn't retain full functionality (eg - when you try to mail a DTG file, and in the process change it to a word or excel format, the palm hangs).

Lunch time now - so i'll have another play...
 
martinr

You may want to make sure you "Spratted" ALL of DocsToGo from ROM.

I did the following when I "upgraded" and moved to Flash:

1 - I ran the DocsToGo installation for the new version. BUT DID NOT HOTSYNC.

2 - Went to the C:\Program Files\Palm\"user name"\Install directory

3 - Wrote down the names of all the files DocsToGo was going to install.

4 - Ran Jack Sprat and DELETED all the files that were on my list from step 3. This was to ensure I got all the programs associated with DocsToGo.

5 - Ran HotSync which installed the newest version of DocsToGo in RAM.

6 - Ran Jack Flash and moved as many of the files as possible from RAM to "FLASH"

7 - Have been running DocsToGo this way for months without any problems.

Now, I'm not sure where you "stand" with files from DocsToGo, so I would suggest ...

1 - Run JackSprat (I assume you still have the backup taken earlier) and skip the backup portion.

2 - Search for any DocsToGo files which may still be in "ROM" and delete using Jack Sprat.

3 - Run Jack Flash and delete any DocsToGo files in "FLASH"

4 - Using the Palm "Delete" (From the main menu, Delete Docs to Go.

5 - Run your HotSync which should install the latest version of DocsToGo in RAM. (Presuming you ran the DTG install and DID NOT HOTSYNC)

6 - Run JackFlash and move DocsToGo into "FLASH".

At this point you should have only one copy of DocsToGo (In Flash).

Check to make sure that HotSync completes without error. If it doesn't complete normally, many times the files you are installing are STILL in the "Install" directory on the PC, and the next HotSync will try to install them again, resulting in DTG in Flash AND in RAM (duplicates)

Hope this gives you some idea of where to begin, since I don't know the full state of your T3.

fnagle/Frank
 
Excellent, fnagle! Taught me a couple of things!

Just had the same deal with MobileDB (silent upgrade to 4.1.4).

I wanted to reinstall the desktop, twhich loaded 4.1.4 in RAM. I had 4.1.3 in flash. My plan was just to delete it as I wanted the PC "Syncher;" then noticed there was a slight "change" in version #. Crap.

JF won't allow you to move the flash version to RAM if there's an instance already there.

Deleted handheld/RAM app just installed, then moved "older" flash version to RAM, deleted again including saved prefs entries (full uninstall -from launcher, restored databases later).

Reinstalled "new one" to RAM, and moved it to flash. Restored ALL from CardBackup (good choice!) . . . and all was good (MobileDB didn't "restore," of course because it was in flash when the backup was made . . . where it belongs. Only difference was I made a small "tweak" to MobileDB but that's irrelevant to your problem (boosted dynamic stack request in TealMover before moving to flash, which improves its performance. Doesn't apply to D2G stuff, I'm just being accurate!).

Docs to go is a BEHEMOTH with a lot of "SS10jklxxsh" (I'm making that up, sort of) type files lurking about - and depending on your vrsion of SPRAT it enables you to remove not only docs to go but "other D2G crap" as well. There is SO MUCH stuff that I've thought of going back to TinySheet and foregoing synching spreadhseets at all - but so far haven't done so. Apparently there's a lot of cool new stuff in 7.003 which you'll enjoy; I just question the huge PC/Palm real estate investment considering all these "little files" created. For example:

THERE WILL STILL be one or two small files left behind which will/may be duplicated and I'm too busy now to look for them - but don't worry about it, martinr -- they're small. YOu can't get rid of them or at least you can't if D2G came in ROM with your T3. This is the whole reason I decided to GET JS/JF - the Normal Scenario is when you upgrade you have 2 copies - P1's "built in" 6.002, and your new 7.003!

Fnagle's post will help you - looks like a nightmare, but will go quickly and you should be fine. Just bear in mind from now on that when you UPGRADE, you obviously have to move OUT of flash to RAM, upgrade, move back to flash. Over time this will cause JFlash to "compact" but that's normal and a good thing. It will load the requested app after compaction. That's why I load apps I won't be upgrading (oldies/goodies) first INTO FLASH, SO THAT WHEN THE COMPACTION HAPPENS they're not moved around much or at all. Only the "newer add-ons" are moved, and therefore easily re-installed if necessary due to a "glitch." The only one that ever glitched was Agendus.
 
Thanks Frank and ptl - just in the process of re-installing DTG 7.003 - bit of a pig, but I like the key advice coming out off this:

When upgrading, move the old app to ram, upgrade, then move it back to flash.

SHout if i've got this wrong, as this is what i plan to do in future...
 
OK - solved the duplication problem thanks again- but I still have the same problem with e-mailing files.

If i try to e-mail a DTG format file, and choose to convert it into a .doc or .xls file, the palm hangs. Any thoughts as to what might be wrong?

Ta,

Martin
 
Can't help you with the email thing - sorry.

Yes, that's the procedure for upgrading apps. After moving to RAM, I don't personally do a soft reset but it couldn't hurt. When moving back to Flash, I'd "almost recommend" a soft reset - or the Palm may do that for you (depending on the app). There's a great freeware, 1k in size, called mReset on Freeware Palm; simply tapping on that app gives a soft reset so put it somewhere where you can't hit it by mistake, but get to it quickly.

Also, remember that when you've done it a few times (depending how much free flash you have) JF may compact your flash. At that point you may have a forced soft reset depending what apps were moved to flash, and some apps like SyncBack and AlwaysOn require "resetting." You'll also have to change the layout prefs for "show input area" and perhaps "show graffiti strokes."

Other than that it's pretty "automatic."

One more thing - some apps need to be "unchecked" before moving, like TealScript. JF will give you a screen like "sorry, app is in use and can't be moved;" you can avoid this by thinking ahead and doing it first, but I often forget.
 
Back
Top