That's much easier to determine than you'd think. I've been testing
v-12 in a vmware workstation 7.1.2 setup that I've kept fairly bare. I
haven't even installed firefox or chrome. But it is a fully patched sp3
that started as WinXP sp2. And I've reverted the vm to the point before
this happened. I installed an earlier v-12, maybe build 20 or so a few
weeks ago, then I confirmed that build 29 crapped out with the
registration time-out. Others have also reported that their tcmd v-11
is altered by v-12; I'm not the only one here. Some have said they had
to do a repair installation to get their v-11 working. Others have said
they had to fully remove tcmd.
And then I installed build 30. I have not started this VM a lot in the
last few weeks, either.
SO OTHERS HAVE REPORTED SOMETHING SIMILAR TO WHAT I'M SEEING.
Don't dismiss this as "cannot reproduce it here (nor has anybody else
WRONG! WRONG! WRONG!
On 10/25/2010 07:39 PM, rconn wrote:
> ---Quote (Originally by drrob1)---
> WinXP sp3 32 bit.
> Installed v 12. It said upon installation that it had to update files
> for v 11. I let it do so. Now v12 works as expected but I cannot start
> v11 without it saying I've expired.
> Is this supposed to happen this way?
> ---End Quote---
> No, and I cannot reproduce it here (nor has anybody else reported that). V12 has *no* files in common with v11, and Windows Installer shouldn't be trying to update anything in v11. (There certainly isn't anything in the TCMD install script for that.)
> I'd have to know the exact sequence of TCMD installations you've done in the last few days to make a guess as to what Windows is doing.