Jim Nagel <
jimne...@abbeypress.co.uk> wrote:
> I have often wished that the R-Comp website should include a list of
> all products showing latest versions. That would make it easy to
> check whether I am missing an update before bothering Andrew about it.
> Perhaps link to a copy of the History file for each app for details of
> whether the update is major or minor.
Andrew at R-Comp has clarified the position as follows:
> The problem with that is remembering to maintain this causes problems
> - if the website info becomes out of sync with reality, people then
> won't even *ask* (ie. worse than now)! We issue release info about
> updates on comp.sys.acorn.announce, and to magazine/website editors,
> which are the primary methods of dispersing info.
>
> PlingStore also lists current version numbers. If users do *not* have
> PlingStore installed yet, they should do. It's free, and provides a
> valuable resource/service. Please see
http://www.plingstore.org.uk/
>
> To cover the main topic, all updates are emailed out to relevant users
> as a matter of course.
>
> However, in the case of UniPrint, after 4 years of availability, I
> haven't sent 4.05 out because it is likely to create a support
> nightmare of users struggling to upgrade when their existing
> installations work just fine. UniPrint is one of our most
> support-heavy products, and I am quite fearful of users breaking
> working setups with largely unnecessary updates. Add to this that
> several ISPs block our UniPrint emails altogether (ie. users won't
> even receive the text) as there's a blanket ban on .exe files, even
> inside zip archives! (Notably Virgin / NTL suffer this, but I suspect
> Sky and possibly other gmail- resellers may be affected). As such,
> emailing UniPrint upgrades is a non-trivial task.
>
> All other products (eg. SafeStore2, MusicMan2, Messenger Pro 7,
> NetFetch 3.5 etc) continue to receive regular free updates via email.
The moral of the story is: PLEASE for heavens' sake report problems to
R-Comp. I might be already working on a fix, I might have produced a fix but
for the reason given above not it hasn't been distributed universally, or we
may simply not know the problem exists (especially if none of you reports
it).