PDA

View Full Version : TimeLock 2



NewsArchive
07-15-1997, 12:00 AM
Hi!

I'm sure this isn't the right spot to ask this, but I can't seem to find
any support information relating to TimeLock that I go with my
InstallShield. Does anybody know how to contact these guys?

Specifically, I've gotten a few reports like the following:

SHWAREML caused an invalid page fault in
module TL32V20.DLL at 0137:10003493.
Registers:
EAX=000029eb CS=0137 EIP=10003493 EFLGS=00010212
EBX=bff64516 SS=013f ESP=006bf670 EBP=006b0081
ECX=10011622 DS=013f ESI=00000000 FS=24df
EDX=00000031 ES=013f EDI=bff61f5a GS=0000
Bytes at CS:EIP:
89 45 f8 68 71 43 01 10 e8 c0 18 00 00 83 c4 04
Stack dump:
006bf7c8 00008838 006bf814 87c7bf79 bd81b9a2 c2af30b0 8b6da679 a1307077
65af84c3 7dbbaf88 6189c1b1 abc27ba6 7ec7ad86 b138b3b0 7bb174b1 8f656a88

Thanks in advance!


Shawn

NewsArchive
07-16-1997, 12:00 AM
Shawn,

Looking at TimeLock's web site I could not find any support information.
You
may find a way to contact them by going to www.timelock.com.

Dan

Shawn Stumbaugh <sstumbaugh@newamerica.com> wrote in article
<33CBCBFD.68DB@newamerica.com>...
> Hi!
>
> I'm sure this isn't the right spot to ask this, but I can't seem to find
> any support information relating to TimeLock that I go with my
> InstallShield. Does anybody know how to contact these guys?
>
> Specifically, I've gotten a few reports like the following:
>
> SHWAREML caused an invalid page fault in
> module TL32V20.DLL at 0137:10003493.
> Registers:
> EAX=000029eb CS=0137 EIP=10003493 EFLGS=00010212
> EBX=bff64516 SS=013f ESP=006bf670 EBP=006b0081
> ECX=10011622 DS=013f ESI=00000000 FS=24df
> EDX=00000031 ES=013f EDI=bff61f5a GS=0000
> Bytes at CS:EIP:
> 89 45 f8 68 71 43 01 10 e8 c0 18 00 00 83 c4 04
> Stack dump:
> 006bf7c8 00008838 006bf814 87c7bf79 bd81b9a2 c2af30b0 8b6da679 a1307077
> 65af84c3 7dbbaf88 6189c1b1 abc27ba6 7ec7ad86 b138b3b0 7bb174b1 8f656a88
>
> Thanks in advance!
>
>
> Shawn
>

NewsArchive
07-17-1997, 12:00 AM
Hi Dan!

Thanks for the response. Someone forwarded my request to
support@previewsoft.com - now why didn't I think of that;0) Their web
site is a bit uninformative, to say the least.

I did hear back from them and have posted my last response from them
below.

In a nutshell, it appears that their program does not work with Win95
OSR2. I had no idea and released my program last week and started
getting problem reports. Not a good first impression of the product
released and shame on me for not testing.

InstallShield should rethink this relationship and promoting this
program. You can't buy a new Win95 PC without OSR2. TimeLock just
blows up with a GPF. I've sent all pertinent information to them, and
their support person says that it will not be fixed and to wait until
3.0. No release date on this 3.0 version. Today, I can't even get a
message to them - previewsoft.com appears down.

This obviously is not an IS problem, but IS is promoting this product.
Coming from the leading installation software vendor, one could / should
assume that it meets your tough standards for installation and usage
across the popular OS's. Not working on new Win95 PC's is a huge, huge,
huge, problem.

Thanks, and sorry for the rant.


Shawn








Shawn,

>I don't know about Win95 OSR2, but am extremely distressed to hear of
>unfixable problems. Can you be more specific?

Sure. Because TL3 is so close to being released, the TL2 code has
been frozen for all time. All development efforts from here on out
will be focused on TL3 only.


>I will check with the users. Will TL3 fix this problem?

We haven't seen any problems in our testing so far. From what we can
tell, OSR1 and OSR2 behave identically.


>To create the problem, the users are just running the program. It's
>about the 3rd line into the startup routine. Nothing fancy going on. I
>will have to get OS specifics.

In what order are you making the calls to timeLOCK in? It should look
something like the following in your startup code:

x = verifyTimelock();
userState = showMainDialog();
if ((userState == TLOCK_NEW_USER) or (userState == TLOCK_TRIAL_USER))
trialEnvironmentOpen();

Let me know...

Scott




InstallShield Corp. wrote:
>
> Shawn,
>
> Looking at TimeLock's web site I could not find any support information.
> You
> may find a way to contact them by going to www.timelock.com.
>
> Dan
>
> Shawn Stumbaugh <sstumbaugh@newamerica.com> wrote in article
> <33CBCBFD.68DB@newamerica.com>...
> > Hi!
> >
> > I'm sure this isn't the right spot to ask this, but I can't seem to find
> > any support information relating to TimeLock that I go with my
> > InstallShield. Does anybody know how to contact these guys?
> >
> > Specifically, I've gotten a few reports like the following:
> >
> > SHWAREML caused an invalid page fault in
> > module TL32V20.DLL at 0137:10003493.
> > Registers:
> > EAX=000029eb CS=0137 EIP=10003493 EFLGS=00010212
> > EBX=bff64516 SS=013f ESP=006bf670 EBP=006b0081
> > ECX=10011622 DS=013f ESI=00000000 FS=24df
> > EDX=00000031 ES=013f EDI=bff61f5a GS=0000
> > Bytes at CS:EIP:
> > 89 45 f8 68 71 43 01 10 e8 c0 18 00 00 83 c4 04
> > Stack dump:
> > 006bf7c8 00008838 006bf814 87c7bf79 bd81b9a2 c2af30b0 8b6da679 a1307077
> > 65af84c3 7dbbaf88 6189c1b1 abc27ba6 7ec7ad86 b138b3b0 7bb174b1 8f656a88
> >
> > Thanks in advance!
> >
> >
> > Shawn
> >

NewsArchive
12-18-1998, 01:00 AM
InstallShield Software Corporation wrote in message
<367989ef.20085821@news.installshield.com>...
>On Thu, 17 Dec 1998 11:12:30 -0500, "Gary Caspelich" <ppffssm@gate.net>
>wrote:
>>customer to use and Sentinel's customer support is very limited. Every
time
>>we ask them for help, they seem to be holding back on giving information
on
>>their supplied functions and routines.
>
>Gary, look at http://www.previewsoftware.com/ - They used to have a product
>called TimeLock. But it has been renamed.
>
>Stefan Paetow
>InstallShield Software Corp.

Thanks Stefan. This a very good recommendation and I would recommend the
Vbox software to anyone wanting to trial or time lock their software.

-Gary