Mike Badger wrote:
> Can we fix it? Well almost. Part of the problem we have with
> the verification is in the way data was stored with some of the
> early 2.0 licenses. We've had a few registration methods, and
> as a result, we have a couple different ways our data was stored.
>
> A few problems were discovered during the testing, and another
> found shortly after it was made available (but not public). Those
> instances should have been fixed. I believe there are still some
> other cases out there, which are failing.
>
> I haven't had a chance to look at the total number of pending
> requests, but it's on my list to double check today and make
> sure ample resources are devoted from an already stretched
> staff :).
That's exactly the point. This glitch is more of a problem for
Netraverse than it is for the rest of us, for whom it's so far still
at the nuisance level.
Here's a practical suggestion. If the volume of update requests
has reduced to a trickle, then you probably shouldn't worry; the
remaining ones can be handled manually, and improvements to the
autmatic updating procedure will merely generate duplicates of
requests already in the queue. But if they're still coming in fast
and furious, the problem needs fixing in order to relieve your
"already stretched staff".
Paul
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
