0148 0000 0148 0000
if i've done my math properly, these both point to your last and
highest read message numbers in that area as being 328...
Correct ... but this still does not change anything with my original problem that the unread flag is not reset when I read a mail in goated ;)
problem that the unread flag is not reset when I read a mail in goated ;)if i've done my math properly, these both point to your last andCorrect ... but this still does not change anything with my original
highest read message numbers in that area as being 328...
if i've done my math properly, these both point to your last and
highest read message numbers in that area as being 328...
Correct ... but this still does not change anything with myuser, which run goated can write in JLR file?
original problem that the unread flag is not reset when I read a
mail in goated ;)
Correct ... but this still does not change anything with my original
problem that the unread flag is not reset when I read a mail in
goated ;)
user, which run goated can write in JLR file?
the problem seems to be that when RM reads a message addressed to him,
it should be marked as received... when he switches to the other
reader using the same message base files, that same message is not
marked received...
i have not asked RM if this is seen only when going
from goated to golded or if he sees the problem when reading with
golded first and then goated...
the problem seems to be that when RM reads a message addressed to him,
it should be marked as received... when he switches to the other
reader using the same message base files, that same message is not
marked received...
Correct ... except all messages not only those addressed to me.
i have not asked RM if this is seen only when going from goated to
golded or if he sees the problem when reading with golded first and
then goated...
Unread messages are marked in a different color in the message lister.
Goated does not have a message lister, so I do not know if it would
show them as unread.
On 2019 Apr 07 09:56:38, you wrote to me:
the problem seems to be that when RM reads a message addressed
to him, it should be marked as received... when he switches to
the other reader using the same message base files, that same
message is not marked received...
Correct ... except all messages not only those addressed to me.OH! then they are not ""marked received""... that's with the received attribute bit in the message header and only if the name matches the user's name... i got confused with your use of the phrase "marked received" or "marked read"... messages aren't marked read or received
in general...
right... so the problem does appear to be something with the last/high read pointers
seems to have been done properly... i'm assuming that you do only have
328 (or whatever that number was) messages in the area in question?
now i'm curious about that JLR data again and which of the two
programs was the last one used which would have written those counters
to the file...
Let me rephrase.
1 READ
2 READ <- LASTREAD POINTER
3 UNREAD
4 UNREAD
If I read them in golded all will be marked read,
1 READ
2 READ
3 UNREAD
4 UNREAD <- LASTREAD POINTER
So the unread pointer is updated, but the messages in the JAM base are not marked as read. (and show up in a different color, as golded sees them as unread)
right... so the problem does appear to be something with the
last/high read pointers
No, the lastread pointer is updated correctly.
seems to have been done properly... i'm assuming that you do only
have 328 (or whatever that number was) messages in the area in
question? now i'm curious about that JLR data again and which of the
two programs was the last one used which would have written those
counters to the file...
The JLR file is fine.
do you have another JAM capable local sysop reader you can use to
access your JAM bases with? does it show the same problem as GoldED?
if you do have one, it would point more toward where the problem is... maybe try TimED or MsgED?
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 765 |
Nodes: | 10 (1 / 9) |
Uptime: | 63:01:48 |
Calls: | 10,570 |
Files: | 185,893 |
Messages: | 1,675,011 |