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 :).
Regards,
Mike Badger
At 10:18 AM 6/5/01 -0400, you wrote:
>I'm among the many folks who didn't succeed in providing a
>valid license number for the automatic upgrade procedure.
>I can live with using the eval version and waiting for the
>manually-generated license, though the nag screen is a
>nuisance. But, Netraverse friends, this failure is
>probably even more of a problem for you than it is for us
>out there, since it has to be generating an enormous amount
>of clerical work. Can you fix it?
>
>Paul
>
>
>_______________________________________________
>Win4Lin-users mailing list
>[EMAIL PROTECTED]
>https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
