At 01:00 PM 6/5/01 -0400, you wrote:
>First let me say that I am very pleased with the Win4Lin-3.0 release.
Thank you.
>I am also one who could NOT online update/register. But it is MY fault. After
>several attempts at online update I was copying my 2.0 license.txt, word for
>word, when I noticed that my "ZIP code" in my license was not correct. A quick
>check of my member info showed that there I had entered it correctly. My
>fault.
The only part of the license.txt you need to copy is the portion after the
LIC_ID=
line.
Here is an example of a v2.0.x license.txt, with some fields removed to
protect the innocent.
PRODUCT="Win4Lin-2.0-upgrade"
LICENSE=upgr
LIC_ID=012345 (this is not a valid value )
LIC_TYPE="single"
LIC_VER="5.1.1-00"
SESSIONS=1
CUSTOMER_NAME="Mike Badger"
ETC, ETC, ETC.
So if I were to try and use this license.txt information to get my upgrade
to 3.0, the only thing I would
need to enter in the form is 012345. If the automated approach fails to
verify this number, then it
would be appropriate to copy the entire license.txt into the available
comments box and submit it for
manual verfication.
Regards,
Mike
>Something to maybe to into for others with problems.
>
>BTW: When I try to 'log off' I am sent back to the member log off screen.. But
>that is probably my fault too. <smile>
>
>From: Mike Badger
>Sent: Tue, 05 Jun 2001 12:01:55 -0400
>To: [EMAIL PROTECTED]
>Subject: Re: [Win4Lin-users] License numbers for upgrade
>
> > 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
> >
>
>--
>David Boles
>[EMAIL PROTECTED]
>My GnuPG Key ID: 78A3ADB0
>
>_______________________________________________
>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
