MobileRead Forums - View Single Post

grr · 10-04-2008, 11:22 PM

per correction from user: wallcraft, recognition of kindle PID and storage as an additional device is insufficient -- what I really need to do is restore the original PID from the instance of mobireader that was installed on my original hard drive.

Note that the hardware-generated PID hypothesis still seems less likely, or is at least not the ony variable.

As an experiment, I tried running a copy of mobireader in a sandbox, after editing the mobireader.XML file in a naive fashion (eg, replacing each instance of my "new PID" w/ "old PID")

This resulted in the generation of yet another PID (the 3rd) -- I'm assuming that the integrity of the xml file was violated (through some checksum test, or whatever, stored in another file), and thus, mobireader created a new PID for what it thought was a new machine.

If I restored the old, correct xml file and reran a sandboxed instance of reader, it did not create a new PID

By looking at the sandboxed files that were accessed by the sandboxed instance of mobireader, I think i can conclude that the key files are stored somewhere in the files mentioned above:
MBP_global_configuration.mbp
mobibook.mbl
mobireader.xml
sync.xml
MobipocketCache.mbp
...or else in the registry.

I'm a rank amateur when it comes to actual programming, etc -- hoping someone else can contribute something better informed.

Going back to the original issue -- I have a crashed hard drive which I lack an image of (but do have relatively extensive backups of data and settings files for). How do I

1.Restore the original PID as the primary device on my new hard drive install

2.Going forward, back up the original PID so that it can be restored to a hard drive install as the primary PID

For #2, the "definitely works" instance is to image your entire primary drive partition and the partition on which mobireader is installed, if that is a different partition.

I previously wondered if a hacky, but less involved solution might be to create a tiny drive partition that contains just the install of mobi reader, and image/restore that image.

This seems unlikely to be sufficient given the fact that a combo of registry changes and C:\Documents and Settings\USERXXX\Application Data\Mobipocket\ files are needed (again, not sure of registry changes -- I just can't rule it out w/my current lack of sophistication)

However, I wonder if simply copying files in C:\Documents and Settings\USERXXX\Application Data\Mobipocket\ would be sufficient -- this is something I could test more easily (and plan to do next).

10-04-2008, 11:22 PM	#4
grr Member Posts: 20 Karma: 10 Join Date: Aug 2008 Device: Kindle	per correction from user: wallcraft, recognition of kindle PID and storage as an additional device is insufficient -- what I really need to do is restore the original PID from the instance of mobireader that was installed on my original hard drive. Note that the hardware-generated PID hypothesis still seems less likely, or is at least not the ony variable. As an experiment, I tried running a copy of mobireader in a sandbox, after editing the mobireader.XML file in a naive fashion (eg, replacing each instance of my "new PID" w/ "old PID") This resulted in the generation of yet another PID (the 3rd) -- I'm assuming that the integrity of the xml file was violated (through some checksum test, or whatever, stored in another file), and thus, mobireader created a new PID for what it thought was a new machine. If I restored the old, correct xml file and reran a sandboxed instance of reader, it did not create a new PID By looking at the sandboxed files that were accessed by the sandboxed instance of mobireader, I think i can conclude that the key files are stored somewhere in the files mentioned above: MBP_global_configuration.mbp mobibook.mbl mobireader.xml sync.xml MobipocketCache.mbp ...or else in the registry. I'm a rank amateur when it comes to actual programming, etc -- hoping someone else can contribute something better informed. Going back to the original issue -- I have a crashed hard drive which I lack an image of (but do have relatively extensive backups of data and settings files for). How do I 1.Restore the original PID as the primary device on my new hard drive install 2.Going forward, back up the original PID so that it can be restored to a hard drive install as the primary PID For #2, the "definitely works" instance is to image your entire primary drive partition and the partition on which mobireader is installed, if that is a different partition. I previously wondered if a hacky, but less involved solution might be to create a tiny drive partition that contains just the install of mobi reader, and image/restore that image. This seems unlikely to be sufficient given the fact that a combo of registry changes and C:\Documents and Settings\USERXXX\Application Data\Mobipocket\ files are needed (again, not sure of registry changes -- I just can't rule it out w/my current lack of sophistication) However, I wonder if simply copying files in C:\Documents and Settings\USERXXX\Application Data\Mobipocket\ would be sufficient -- this is something I could test more easily (and plan to do next).