Registered: Feb 2001
Location:
Posts: 32

PiBackup/PiMove bug!

Please be aware that these program doesn't make exactly copy of your databases. They don't save uniqueID for each record in the PDB Header.
Here is the format of record entry :
typedef struct {
LocalID localChunkID; // local chunkID of a record
UInt8 attributes; // record attributes;
UInt8 uniqueID[3]; // unique ID of record; should
// not be 0 for a legal record.
} RecordEntryType;
And PI's programms are using the simple counter for uniqueID then some programms like AvantGo, UltrasoftMoney are using it for own information like category. I'm sure that many other programms are using this field, so they may may lost information too.
I don't know why this bug is not fixed yet, but it's really showstoper.

Registered: Dec 2000
Location:
Posts: 52

Re: PiBackup/PiMove bug!

quote:

---

Originally posted by ssas
Please be aware that these program doesn't make exactly copy of your databases. They don't save uniqueID for each record in the PDB Header.

---

Registered: Dec 2000
Location:
Posts: 5

I have had a problem with corrupted Address DBs after performing PiBackup and PiMover operations. I have not noticed any problems with other files. Using BackupBuddy, a USB reader/writer, and numberous backup/restore operations, I have noticed the following:

1. The problem occurs when the file is moved from RAM to the smartmedia. If I copy the file from the PC to the smartmedia using the USB adapter, then from the smartmedia to Visor memory, the DB is good. Copying the file from RAM to smartmedia and back to RAM results in a corrupted DB.

2. The problem occurs on the 8177/8178 record boundary. 8177 records or less do not have corrupted DBs following backup/restore. But a DB with 8178 records or more gets corrupted during this sequence. I have one private record and am not sure if/how this affects this boundary.

3. I don't think this is related to other applications on my Visor. I have performed a hard reset of the Visor then installed the file using the USB adapter and a move from smartmedia to RAM. The file was good. Then subsequent mover or backup/restore operations (with no other applications loaded) resulted in a corrupted DB.

4. I have not had this problem with my HandSpring backup module.


I have attached a picture of what the Address list looks like when the application is first entered. If any record is tapped on, a fatal exception occurs. No hard reset is required to recover from this.

PI was very responsive when I first brought up this problem, but apparently were not able to duplicate the problem. They did request my DB to help in duplicating the problem, but I did not provide it since it has proprietary information from my Employer. Maybe someone else with large databases has seen this problem and can provide a sample DB to PI.

I have been very satisfied with my adapter and have a workaround for this problem, but I wanted people aware of this problem since I have seen other posts stating how reliable the PiBackup and PiMover applications are. Those with large Address DBs might want to run a few tests to reassure themselves their backup works fine for them.

Attachment: p6180754.jpg
This has been downloaded 70 time(s).

Registered: Oct 1999
Location: Mineola, NY USA
Posts: 161

Deleted

__________________
-Michael-

Registered: Oct 1999
Location: Mineola, NY USA
Posts: 161

Since doing a full restore with PiBack up I have been getting the error message "Unique ID Not Found" frequently following a change of path and a scan in PiDirect. When that occurs I have to tap the on screen reset button several times. It's an annoyance, but minor and does not affect performance or any data as I can determine. Certainly does not detract from the tons (make that megabytes) of books, programs, maps and things that I can now store and access on my Prism using PiDirect.

I informed PIT about the problem. They are studying it and informed me that expect to have a fix within a week or two.

__________________
-Michael-

Registered: Feb 2001
Location:
Posts: 32

quote:

---

Originally posted by Tom Pruitt


1. The problem occurs when the file is moved from RAM to the smartmedia. If I copy the file from the PC to the smartmedia using the USB adapter, then from the smartmedia to Visor memory, the DB is good. Copying the file from RAM to smartmedia and back to RAM results in a corrupted DB.

---

Attachment: log.jpg
This has been downloaded 66 time(s).

Registered: Dec 2000
Location: June 10, 2001 San Clemente Pier , CA
Posts: 211

OK, so today I did a restore from my memplug.

VERY unsuccessful. Nothing but '#8017 file size not found' errors. I'm reporting these to memplug developers but thought I would let my visor buddies in on my trials/tribulations. My Prism was unusable, unresetable.

Gotta love that HS backup mod. Even if it is 3 days old.

BTW, the reason for the restore initially was because SplashPhoto crashed and went into 'reset loop' after being moved back from the memplug to Prism. Which BTW, was necessitated by a crash while trying to run SplashPhoto directly from memplug with piDirect like their website says it can.

Not thrilled with the memplug yet. And, it's slooooooooow. Still am holding out hope though. You know, you spend $100, you keep trying. But if I hadn't bought the memplug yet.... I would probably be holding off for a while still.

__________________
"I cannot live without books." Thomas Jefferson