Hi Greg,

 GH>       I'm not sure if this is a bug, or a case of not RTFM, but:
 GH> if I start to read a message packet that
 GH> has not been indexed, and then
 GH> press (n)ext message, QWKRR goes off and
 GH> indexes the rest of the mail packet.

It is in the manual and it both is and isn't a bug.

*any* of the browse modes (including selecting a specific conference)
relys upon the packet being indexed. Until this is done it has no idea
whether there are any more messages that matches your chosen browse
mode, so it will keep indexing until it comes to a disk error
signifying the last message.

There is NO way around this so it's not really a bug.

 GH> This ok, but sometimes,
 GH> especially if I'M in a hurry, I don't
 GH> need to index 1000+ messages, only enough
 GH> so I can browse the first few
 GH> echoes (usually Commodore ones!).
 GH> I  guess I can still limit the indexing
 GH> by typing in a message number,
 GH> and QWKRR will index up to it.
 GH> And ideas?

Nope.  My only idea was what you just suggested to limit the indexing.

Cheers
Rod

___ QWKRR128 V4.21 [R]

--- EzyQwk V1.10b0