Hi, I just noticed some odd behavior with DDMsgReader. I usually read my messages via QWK, and just logged in locally to check messages. My
message pointers when reading messages with DDMsgReader were set to #1
in all areas.
I tried using the menu option to reset menu pointers, then reset them to today at 00:00, I still get #1 as the new message pointer in all areas
when using DDMsgReader, but get the normal high message pointers when
using the defaults.
Hi, I just noticed some odd behavior with DDMsgReader. I usually read my messages via QWK, and just logged in locally to check messages. My message pointers when reading messages with DDMsgReader were set to #1 in all areas.
I tried using the menu option to reset menu pointers, then reset them to today at 00:00, I still get #1 as the new message pointer in all areas when using DDMsgReader, but get the normal high message pointers when using the defaults.
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 286 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 15:21:11 |
| Calls: | 2,436 |
| Calls today: | 1 |
| Files: | 5,283 |
| D/L today: |
30 files (11,124K bytes) |
| Messages: | 443,107 |