And when I look at the message bases they are empty. The files exist but are all 0 bytes except the .jhr file is 1024 bytes. It looks like magicka didn't like the existing files and blanked them out.
Message base files with those three extentions do exist but for some reason magicka blanks them out and creates new (empty) message base
files.
Once magicka has created message bases hpt tosses to them happily.
Something to do with hpt maybe?
I've been seeing this tonight. One thing I notice is that the message
base files hpt creates, basename.jdt, .jdx and .jhr. It doesn't
create basename.jlr but I notice when magicka creates bases it
creates the .jdt, .jdx, .jhr and .jlr files.
Message base files with those three extentions do exist but for some
reason magicka blanks them out and creates new (empty) message base
files.
Once magicka has created message bases hpt tosses to them happily.
Something to do with hpt maybe?
Tossers usally don't create *.jlr files, *.jlr only stores the user's lastread info. Maybe Magicka tries to
open that files, gets an error and thinks it's best to recreate the message base?
Message base files with those three extentions do exist but for some
reason magicka blanks them out and creates new (empty) message base
files.
Magicka should not wipe a message base without permission from the sysop ;).
I think it's unlikely that it is a problem with hpt. Tossers usally
don't create *.jlr files, *.jlr only stores the user's lastread info. Maybe Magicka tries to open that files, gets an error and thinks
it's best to recreate the message base?
More likely something to do with jamlib (which magicka uses). I think I actually remember this from previously.
I'll have a look into it.
I've just pushed a fix to jamlib that should hopefully not fail to opem a jam base with out a jlr file. (and instead create an empty one).
I notice that msged uses a .sql instead of the .jlr to track a persons last read messages. It works but if you carry on with another editor
it won't know where you left off.
.sql is for squish message bases.
Is this a bug in smapi, in msged or intentional?
I wonder if the file has just the wrong name or if it's using a real
Squish .sql file (I don't know if .sql and .jlr are different or the
same structure)
That's possible. I don't know what the contents of the .sql is, it
may just be a wrong extention being used. I'm not really sure.
It could be using sqlite or some other mechanism for last read pointers. For a mail reader with only one user, it could be more practical to use individual message read/unread flags rather than a "last read" pointer.
In which case sqlite might be a good way of doing it.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 57 |
Nodes: | 4 (0 / 4) |
Uptime: | 12:07:49 |
Calls: | 513 |
Files: | 6,922 |
Messages: | 285,897 |