🚀 go-pugleaf

I've noticed this bug in Windis several times and thought 'I'm back-level: it 
must be fixed in the current', but I'm now running 3.1 and it still isn't 
fixed. It's fairly small but very annoying when I hit it.

We keep our newsbase on a shared (Novell) network drive so that anyone can read 
news. But because the ACTIVE, SUSPEND and HISTORY.SNW files are kept open by 
SNews, only one person can read at a time. Not only that, but you can't unbatch 
while someone is reading news.

All this is fine, but the problems come when Windis exits and tries to unbatch. 
It tries to open the active file, fails, puts up a dialog box saying 'Cannot 
Open Active File', ***and then removes the batch anyway even though it has 
not unbatched it***. Result: lost news.

We're using Windis 3.1 in Win95. Any chance of a fix (or a peep at the source 
so I can fix it myself?)

-- 
Alistair Bell, Brown's Operating System Services, London. Disclaimers as usual.
alistair@browns.co.uk (home: alistair@ichthya.demon.co.uk)

#include <random.quote>