WebUpdate clashing with GReg?

Hi All,

I have spoken with Friedrich and he has not had any other feedback to
this effect so could I ask anyone who uses GReg for their copy
protection to try an app that has been registered using GReg and then
try a WebUpdate and tell me if the app then requires being unlocked
again. More importantly if this is the behaviour can you determine a
workaround. By the way in my testing I didn't have to actually require
or find an update it was merely the action of running wupdate.exe.

Best Regards,
Geoff Spillane
Data Down Under

On 23 Jun 2005 09:17:49 -0400, Geoff Spillane wrote:

> ould I ask anyone who uses GReg for their copy
> protection to try an app that has been registered using GReg and then
> try a WebUpdate and tell me if the app then requires being unlocked
> again

It shouldnt require re-registration unless the app "G-reg name" has been
changed, or new modules have been added.
--

Mark

Hi Mark,

That's the peculiar thing. I set up an app with GReg, applied an
unlock code, ran the app doing everything other than "check for
updates", closed app, all ok, opened app and this time clicked on
"check for updates" which just runs the default wupdate.exe, it
reported that I had the latest version, which was correct then I can
do whatever else I like with the app until I close the app then during
the close the GReg window pops up with rubbish information (like no
expiry date), then when I restart the app the GReg window again pops
up with most information missing, the App name correct, the default
UNREGISTERED COPY as registered user and a negative number in the
Expiry date code equivalent to the original number of days allowed for
the trial prior to needing to register with an unlock code. Could you
quickly try this for me?

Best Regards,
Geoff

On 23 Jun 2005 20:35:34 -0400, Geoff Spillane wrote:

> Could you
> quickly try this for me?

Well, I could, except I dont have any working SB5 installs that have
anything to do with G-reg apps:)

I cant for the life of me figure out why a web update would cause that,
unless it is tinkering with the g-reg ini. Id check that first. Set it to
read only and try your update and see if it still breaks it.
--

Mark

We are not using webupdate in our app yet, but we have to re-register our
G-Reg protected app every time we install updates on Windows 98 and ME
machines - the system ID changes. On Windows 2000 and XP we don't get this
problem. We have had this problem ever since we started using SB5 for update
distribution, but have never considered it would be anything to do with
SetupBuilder. This is a totally new version of our app with very major
changes so we assumed it was something in our code somewhere. We even
regressed our G-Reg template to the version we were using when everything
last worked properly, but the system ID still changes after updates.

Maybe this is not related to your problem at all, but it might be of
interest.

Jeff

Hi Jeff,

With regard to my problem Mark put my on the right track. It turned
out that I had inadvertantly used the same ini name for my web-update
as I had for the GReg and that was what was causing the clash. I
changed the ini name and everything was fine. I haven't tested on Win
98 but I will do and let you know if I have the same problem that you
are experiencing.

Best Regards,
Geoff Spillane
Data Down Under