Page 1 of 1

Win XP fatal RichText eidt and SQL crashes

Posted: Tue Feb 25, 2014 1:20 pm
by aule
I have sent a debug log on these crashes

The DB is now unusable ... but thereappears to be no log of kept of my changes since the last backup

A simple encrypted zip of notes not yet in a valid backup seems such a simple solution. This is merely Utf-8 text with almost no formatting ... no cross-links between notes ... no quoting notes within other notes. Nothing nightmarish that I can see. Not even categories as distinct from 'tags' and 'sections' (yes, a category is not a class nor a tagged group or "bag" ). If there were logical groupings of tags as "filters", I could see an excuse for bugs when a filter vanishes .. as with quoted notes when a note is deleted. But barring such features, I cannot see what precludes prevention of data loss between backups.

We have used something like this in the Smalltalk programming environment since before '80 - we can always see our changes and reconstruct an invalid image. Because everythign we type is our work. Loss of work is not acceptable. Perid.

One instance of the loss of an hour's worth of my work costs me more than the price of this s/w ... which may now drive me back to MS OneNote - reluctantly, but these sorts of bugs in an odd-numbered release are difficult to view as other than beta-test by users - which I do not find acceptable as a model for payware. Open-source freeware - fine. Caveat emptor, as ever.

Very vexed user.

Re: Win XP fatal RichText eidt and SQL crashes

Posted: Wed Feb 26, 2014 6:41 am
by CintaNotes Developer
I'm sorry for all the frustration.
With the sheer number of different possible OS versions and configurations it is not possible to test all imaginable conditions. We do our best, but sometimes bugs may slip through.

You database may very well be fixable, if you would trust me to fix it.

I didn't quite understand what you were saying about the encrypted zip of notes. CintaNotes doesn't make any encrypted zip of notes.

Helpful would be also to understand when exactly did the problem occur, and what were your action just prior to it, what exactly did error messages say.

We're currently investigating the log files, as soon as I have more information I'll post it here.