That's what we do … but we still have occasional Fatal errors. We have tried setting it the compatibility mode to XP sp2 , changed perms to full control for all users , etc.

Have you folks found out anymore info from Sirsi that might help?

Say, anyone know how Vista's stock is doing these days?

Sadly, the demise of support in *all* areas outside the continental United States should be taken with increasing alarm by all US-centric customers. Those with a longer memory than most of the new Vista and SirsiDynix executives know that the strength of the customer base was even more formidable, informatitve, and even more enjoyable, with a healthy and cooperative international and globalized customer base.

Long live Dynix. Long live Horizon. Cheers, Dave! — q

Unfortunately, the UK office has already made it clear that their primary focus is Symphony and that they are unable/unwilling to provide any sizeable development resources for non-Unicorn/Symphony customers.

I think it's also fair to say that the Horizon customers, via the various European User Groups, have raised their concerns on many occasions and there has been little or no progress (in fact, an earlier initial decision to provide localised versions of 7.4.2 for Europe appears to have been reversed by senior SD management prior to the conference in Southampton).

I would welcome the opportunity to raise my concerns again, but sadly the company seems unwilling to send any of its staff to the meetings of our local regional user group. Contact with our Account Manager (who appears to be far too overstretched with accounts) is minimal. From memory, our contract with the company stipulates that our Account Manager must have quarterly meetings with us, but that hasn't happened since Vista EP took over the company.

In the meantime, I would gladly settle for a version of Horizon that is compatible with Windows XP SP3 and Windows Vista, and a version of HIP that I don't have to hide behind Apache mod_security to keep it from behind hacked. At the conference in May, we were led to believe that this would happen, but (to the best of my knowledge) there has been no further communication from the company. If progress on these issues is being made, why are customers being kept in the dark? Small wonder that many of the emails that I've received in the last couple of days from fellow customers have included the word "abandoned".

Despite the wish of the company for their Dynix/Horizon customers to move to Symphony at the earliest opportunity, for many of us, this simply isn't feasible in the short term.

I fully appreciate the ratio of customers on customised/localised versions is small (at least compared to the large US customer base), but the revenue stream from the annual maintenance of those customers will still be sizeable figure. A clear indication that some of that revenue will be used to provide bugfixes to customers who are unable to use the core US release and who are unable to move to Symphony straight away would be, I believe, most warmly received.

For those who are running local variations we have requested that individuals contact their local account manager or Help Desk to discuss their particular concerns. In the case of customers requiring specific fixes, we have been able to backport many into their current release. Others have indicated an interest to move to Symphony.

We would encourage any customer who has specific concerns to contact their local office.

Regarding the security issues, we are working to see how we can best resolve these issues for you and I will communicate these options to you by November 15, 2008.

Given that Chesham (to the best of my knowledge) has yet to formally inform their customer base about the recent change in management at SDI, I would have been amazed (and pleasantly surprised) if I had heard anything.

On a slightly different subject, is anyone planning to go to the PTFS event in London on 13th November?

The regional variartions in the code were explained to me last year by a former employee of the company. From what I gather these are less than straightforward 'lumps' of code which can't be patched into existing UK installations; hence why we're heading for LMS purgatory.

The recent "20 reasons to migrate to Symphony" post on the Mailing List, says it all really.

If Symphony is the answer, could someone please repeat the question?