Derek,
If Jamey could code the bootldr to backup the RAM to CF first (and offer to
restore it later), that might be the best solution. I spoke with Compaq
support folks yesterday, and although they recognize the problem (even for a
Windows CE user, without the linux factor), they have no solution for it at
this time. According to Compaq, there isn't sufficient API support to do a
pure backup, and the process of restoring the database entries makes them
appear new. The bootldr, on the other hand, should able to make a perfect
binary backup, and restore it later.
As I maintained to Mary, this issue impacts linux dual boot. Allowing that
process to be as smooth and painless as possible should be the emphasis of
any solution devised. If it has some benefit beyond facilitating dual boot,
that's serendipitous.
--- Noel
-----Original Message-----
From: Derek Glidden
If there were a way to "dd" the RAM to a device or file once Linux got
booted (as part of the boot process maybe even?) and then have the
ability to restore it when you want to reboot to WindowsCE, that would
help get around the issues and make dual booting a much less painful
procedure since you'd automatically have a valid backup of your WinCE
memory as part of the dual-boot process. Jumping back and forth would
be easy if Linux carried the whole burden of doing the RAM backup.
(And show up WindowsCE as inappropriate for this format device. And
show how cool Linux is at dealing with WinCE's shortcomings. :)
But I'm not going to hold my breath. I'd rather see more and improved
functionality under Linux than trying to fix something broken about CE.
I wouldn't be surprised if the "CFBackup" behaviour were intentional as
a way of deterring people from toying around with alternative OS's on
their WindowsCE-based handhelds. If they know they're in for an hour or
so of fixing conflicts when they try to CFRestore, they're less likely
to want to go that way to begin with if there is data on their handheld
that's even vaguely useful to them.
(It's been an issue for me; my Palm died and I haven't been able to
afford to replace it, so I had to start using my iPAQ as an actual PDA.
I haven't been able to do as much experimenting with Linux as I'd like,
because I actually use the thing with some regularity now, as much as I
don't care for it, for calendaring and contacts. The failure of
CFBackup to actually do what it says it's doing is a crock and a
hassle.)
On Tue, 2002-04-16 at 13:00, Noel J. Bergman wrote:
> Mary,
>
> It MIGHT be a Compaq problem if the CF Restore is causing it. I don't
know
> the answer to that question. No, the "always replace the item on my
device"
> setting does not do what you think; it is useful only when there is a
> CONFLICT (i.e., both the PC and PDA copies have been updated).
>
> As for the linux-centric nature of the list, this topic comes up because
of
> how people are being told to dual boot with Windows CE and linux.
>
> --- Noel
>
> -----Original Message-----
> From: Deck, Mary
>
> Not a Compaq problem, since it's ActiveSync -- talk to Microsoft (if you
> think they'll listen).
>
> And I think you can get around that by changing the "conflict resolution"
> option under tools/options/rules to "always replace the item on my device"
> (and then you probably want to change it back after initial sync). I
don't
> know what happens with deleted items.
>
> But, as this is a Linux-centric list, I'm sure there are better places to
> address this......
>
> -- Mary
>
> -----Original Message-----
> From: Noel J. Bergman
>
> > WinCE thinks it's messed up and clears it (so you loose
> > everything you had stored there, do a Ram2CF backup first)
>
> One problem ... using Compaq's included CF Backup tool, after you restore,
> ActiveSync thinks that EVERYTHING is out of sync. WORSE, it thinks that
all
> of the PIM content on the iPAQ is NEWER than the content on the desktop.
>
> Each time I have to restore, it takes me a good hour to "fix" the
> corruption.
>
> Since RAM to CF is the recommended method, do we have a friendlier
(better)
> tool to advise people to use? Is Compaq even aware of the problem?
>
> --- Noel
Received on Wed Apr 17 14:14:03 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:44:46 EDT