Re: NEWS: Nokia tops iPhone and BlackBerry (again), Apple as Nick Clegg

[nospam]

In article <tkcmv5hd9s2082q40pd8veo1hcsooqujqc@4ax.com>, John Navas
<jnspam1@navasgroup.com> wrote:

> >specifically what gets corrupted? how is it out of sync? how did you
> >fix it? you're very light on details, which is not at all surprising.
>
> If you don't known that and how a system crash can cause corruption of
> open output or update files, not to mention the file system itself, then
> you lack the necessary expertise to understand what I'm saying (no
> offense intended).

you're avoiding answering my questions and trying to twist it into
something it isn't. so noted.

of course a system crash can potentially cause problems (it doesn't
always), but that's not the fault of itunes. furthermore, its database
is not as fragile as you imply.

[nospam]

In article <qhimv51dvm17ta3eq48i6u2l2afgnevjoc@4ax.com>, John Navas
<jnspam1@navasgroup.com> wrote:

> >> If you don't known that and how a system crash can cause corruption of
> >> open output or update files, not to mention the file system itself, then
> >> you lack the necessary expertise to understand what I'm saying (no
> >> offense intended).
> >
> >you're avoiding answering my questions and trying to twist it into
> >something it isn't. so noted.
>
> Nothing of the sort. If you're not being disingenuous, then you lack
> the necessary expertise to understand what I'm writing.

i understand it, and it's irrelevant. answer the question.

> >of course a system crash can potentially cause problems (it doesn't
> >always), but that's not the fault of itunes.
>
> Being so fragile is the fault of iTunes.

it's not fragile

> >furthermore, its database
> >is not as fragile as you imply.
>
> It is fragile.

nope. otherwise it would be a common problem. it isn't.