Chris, Josh,
You both are suggesting permission problems. I'll put
this to our IT folks to check.
Thanks, Pat
>-----Original Message-----
>Pat, just curious if this is your situation: I saw
another report of TIP/XP
>SP2 problems related to domain usage, and the "fix" for
it was discovery of
>the account not having the proper permissions to actually
do the XP
>SP2/Tablet PC Edition 2005 installation. Moving the
permissions up to a
>level to execute the upgrades enabled the full usage.
>
>What apparently results is the account is left in limbo
with no update
>because it doesn't have the permissions to (1) install
the updates and (2)
>what was there before (the native Tablet install) doesn't
exist any more.
>--
>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Pat Ceresia" <pceresia@rogers.com> wrote in message
>news:1e7101c4a88d$18658ce0$a301280a@phx.gbl...
>>I forgot to add in my last update that I ran filemon as
>> per Josh's suggestion and did a search on "tabtip.exe".
I
>> got the following error message:
>> "9:17:54 AM tabtip.exe:672 QUERY INFORMATION
>> C:\WINDOWS\system32\AppProperties FILE NOT FOUND
>> Attributes: Error". Interestingly, this error message
>> appeared when logged into the account in which TIP was
>> working fine. I could not find a listing for tabtip in
the
>> user account where TIP was not working - suggesting that
>> its not even loading.
>> Pat
>>>-----Original Message-----
>>>Well more interesting findings. We thought there may
have
>>>been problems with one of the work user account because
>> of
>>>the "x'd" out services when we ran rsop.msc. It turned
>> out
>>>that the cashed credential for that account had expired.
>>>These were updated. SP2 was uninstalled and reinstalled
>>>and success TIP was now fully functional on the work
>>>account where it had previously been non-responsive. All
>>>was well in the universe until I logged on as an
>>>administrator on the local machine domain.
Unfortunately,
>>>now TIP is non responsive on this account. I checked the
>>>other user account I created on the local machine domain
>>>and TIP was similarly non-responsive there as well. The
>>>obvious first question I would ask is, does anyone have
>>>TIP working properly on multiple user accounts on the
>> same
>>>tablet? Is this question worthy of starting a new
thread?
>>>Cheers, Pat
>
>
>.
>

Wow. who would have thunk XP SP2 could be that complicated.

Some additional information about the Tablet Pen Problem.

1- When XP SP2 was originally installed as Local
Administrator with full rights to the system the Ink
Program only worked under this "Administrator" profile and
none of the other Local or Network accounts seemed to be
updated and therefore the Ink program did not work for the
other profiles.

2- SP2 was then un-installed and re-installed using a
Local user account lets call it "User1" and is part of the
Local Admins group. After XP SP2 was installed using
the "User1" account the Ink program worked just fine for
that user but not for any other Local or Network accounts
including the Local Administrator account.

Based on this information is it possible that the way XP
SP2 is written it is only updating the one profile that is
doing the SP2 install and not any other profiles for the
Inking app. And if so what would it take to replicate the
registry/files settings to all other user profiles defined
on the tablet.


>-----Original Message-----
>Chris, Josh,
> You both are suggesting permission problems. I'll put
>this to our IT folks to check.
>Thanks, Pat
>>-----Original Message-----
>>Pat, just curious if this is your situation: I saw
>another report of TIP/XP
>>SP2 problems related to domain usage, and the "fix" for
>it was discovery of
>>the account not having the proper permissions to
actually
>do the XP
>>SP2/Tablet PC Edition 2005 installation. Moving the
>permissions up to a
>>level to execute the upgrades enabled the full usage.
>>
>>What apparently results is the account is left in limbo
>with no update
>>because it doesn't have the permissions to (1) install
>the updates and (2)
>>what was there before (the native Tablet install)
doesn't
>exist any more.
>>--
>>Chris H.
>>Microsoft Windows MVP/Tablet PC
>>Tablet Creations - http://nicecreations.us/
>>Associate Expert
>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>
>>
>>"Pat Ceresia" <pceresia@rogers.com> wrote in message
>>news:1e7101c4a88d$18658ce0$a301280a@phx.gbl...
>>>I forgot to add in my last update that I ran filemon as
>>> per Josh's suggestion and did a search
on "tabtip.exe".
>I
>>> got the following error message:
>>> "9:17:54 AM tabtip.exe:672 QUERY INFORMATION
>>> C:\WINDOWS\system32\AppProperties FILE NOT FOUND
>>> Attributes: Error". Interestingly, this error message
>>> appeared when logged into the account in which TIP was
>>> working fine. I could not find a listing for tabtip in
>the
>>> user account where TIP was not working - suggesting
that
>>> its not even loading.
>>> Pat
>>>>-----Original Message-----
>>>>Well more interesting findings. We thought there may
>have
>>>>been problems with one of the work user account because
>>> of
>>>>the "x'd" out services when we ran rsop.msc. It turned
>>> out
>>>>that the cashed credential for that account had
expired.
>>>>These were updated. SP2 was uninstalled and reinstalled
>>>>and success TIP was now fully functional on the work
>>>>account where it had previously been non-responsive.
All
>>>>was well in the universe until I logged on as an
>>>>administrator on the local machine domain.
>Unfortunately,
>>>>now TIP is non responsive on this account. I checked
the
>>>>other user account I created on the local machine
domain
>>>>and TIP was similarly non-responsive there as well. The
>>>>obvious first question I would ask is, does anyone have
>>>>TIP working properly on multiple user accounts on the
>>> same
>>>>tablet? Is this question worthy of starting a new
>thread?
>>>>Cheers, Pat
>>
>>
>>.
>>
>.
>

Shouldn't be, but I'm doing some checking for you and will post back.
--
Chris H.
Microsoft Windows MVP/Tablet PC
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


"pthomp7943@rogers.com" <anonymous@discussions.microsoft.com> wrote in
message news:411301c4aae7$642dd8b0$a401280a@phx.gbl...
> Wow. who would have thunk XP SP2 could be that complicated.
>
> Some additional information about the Tablet Pen Problem.
>
> 1- When XP SP2 was originally installed as Local
> Administrator with full rights to the system the Ink
> Program only worked under this "Administrator" profile and
> none of the other Local or Network accounts seemed to be
> updated and therefore the Ink program did not work for the
> other profiles.
>
> 2- SP2 was then un-installed and re-installed using a
> Local user account lets call it "User1" and is part of the
> Local Admins group. After XP SP2 was installed using
> the "User1" account the Ink program worked just fine for
> that user but not for any other Local or Network accounts
> including the Local Administrator account.
>
> Based on this information is it possible that the way XP
> SP2 is written it is only updating the one profile that is
> doing the SP2 install and not any other profiles for the
> Inking app. And if so what would it take to replicate the
> registry/files settings to all other user profiles defined
> on the tablet.
>
>
>>-----Original Message-----
>>Chris, Josh,
>> You both are suggesting permission problems. I'll put
>>this to our IT folks to check.
>>Thanks, Pat
>>>-----Original Message-----
>>>Pat, just curious if this is your situation: I saw
>>another report of TIP/XP
>>>SP2 problems related to domain usage, and the "fix" for
>>it was discovery of
>>>the account not having the proper permissions to
> actually
>>do the XP
>>>SP2/Tablet PC Edition 2005 installation. Moving the
>>permissions up to a
>>>level to execute the upgrades enabled the full usage.
>>>
>>>What apparently results is the account is left in limbo
>>with no update
>>>because it doesn't have the permissions to (1) install
>>the updates and (2)
>>>what was there before (the native Tablet install)
> doesn't
>>exist any more.
>>>--
>>>Chris H.
>>>Microsoft Windows MVP/Tablet PC
>>>Tablet Creations - http://nicecreations.us/
>>>Associate Expert
>>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>>
>>>
>>>"Pat Ceresia" <pceresia@rogers.com> wrote in message
>>>news:1e7101c4a88d$18658ce0$a301280a@phx.gbl.. .
>>>>I forgot to add in my last update that I ran filemon as
>>>> per Josh's suggestion and did a search
> on "tabtip.exe".
>>I
>>>> got the following error message:
>>>> "9:17:54 AM tabtip.exe:672 QUERY INFORMATION
>>>> C:\WINDOWS\system32\AppProperties FILE NOT FOUND
>>>> Attributes: Error". Interestingly, this error message
>>>> appeared when logged into the account in which TIP was
>>>> working fine. I could not find a listing for tabtip in
>>the
>>>> user account where TIP was not working - suggesting
> that
>>>> its not even loading.
>>>> Pat
>>>>>-----Original Message-----
>>>>>Well more interesting findings. We thought there may
>>have
>>>>>been problems with one of the work user account because
>>>> of
>>>>>the "x'd" out services when we ran rsop.msc. It turned
>>>> out
>>>>>that the cashed credential for that account had
> expired.
>>>>>These were updated. SP2 was uninstalled and reinstalled
>>>>>and success TIP was now fully functional on the work
>>>>>account where it had previously been non-responsive.
> All
>>>>>was well in the universe until I logged on as an
>>>>>administrator on the local machine domain.
>>Unfortunately,
>>>>>now TIP is non responsive on this account. I checked
> the
>>>>>other user account I created on the local machine
> domain
>>>>>and TIP was similarly non-responsive there as well. The
>>>>>obvious first question I would ask is, does anyone have
>>>>>TIP working properly on multiple user accounts on the
>>>> same
>>>>>tablet? Is this question worthy of starting a new
>>thread?
>>>>>Cheers, Pat
>>>
>>>
>>>.
>>>
>>.
>>

I have not experienced the problem you describe, so I doubt it's systemic to
SP2.

I updated the eval HP TC1100 to SP2 immediately upon receipt of the unit, as
the local admin account on the machine.

I then joined our domain.

All domain accounts, whether Users or Admins work properly with all
functions.

--
Kevin Eddy




"pthomp7943@rogers.com" <anonymous@discussions.microsoft.com> wrote in
message news:411301c4aae7$642dd8b0$a401280a@phx.gbl...
> Wow. who would have thunk XP SP2 could be that complicated.
>
> Some additional information about the Tablet Pen Problem.
>
> 1- When XP SP2 was originally installed as Local
> Administrator with full rights to the system the Ink
> Program only worked under this "Administrator" profile and
> none of the other Local or Network accounts seemed to be
> updated and therefore the Ink program did not work for the
> other profiles.
>
> 2- SP2 was then un-installed and re-installed using a
> Local user account lets call it "User1" and is part of the
> Local Admins group. After XP SP2 was installed using
> the "User1" account the Ink program worked just fine for
> that user but not for any other Local or Network accounts
> including the Local Administrator account.
>
> Based on this information is it possible that the way XP
> SP2 is written it is only updating the one profile that is
> doing the SP2 install and not any other profiles for the
> Inking app. And if so what would it take to replicate the
> registry/files settings to all other user profiles defined
> on the tablet.
>
>
>>-----Original Message-----
>>Chris, Josh,
>> You both are suggesting permission problems. I'll put
>>this to our IT folks to check.
>>Thanks, Pat
>>>-----Original Message-----
>>>Pat, just curious if this is your situation: I saw
>>another report of TIP/XP
>>>SP2 problems related to domain usage, and the "fix" for
>>it was discovery of
>>>the account not having the proper permissions to
> actually
>>do the XP
>>>SP2/Tablet PC Edition 2005 installation. Moving the
>>permissions up to a
>>>level to execute the upgrades enabled the full usage.
>>>
>>>What apparently results is the account is left in limbo
>>with no update
>>>because it doesn't have the permissions to (1) install
>>the updates and (2)
>>>what was there before (the native Tablet install)
> doesn't
>>exist any more.
>>>--
>>>Chris H.
>>>Microsoft Windows MVP/Tablet PC
>>>Tablet Creations - http://nicecreations.us/
>>>Associate Expert
>>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>>
>>>
>>>"Pat Ceresia" <pceresia@rogers.com> wrote in message
>>>news:1e7101c4a88d$18658ce0$a301280a@phx.gbl.. .
>>>>I forgot to add in my last update that I ran filemon as
>>>> per Josh's suggestion and did a search
> on "tabtip.exe".
>>I
>>>> got the following error message:
>>>> "9:17:54 AM tabtip.exe:672 QUERY INFORMATION
>>>> C:\WINDOWS\system32\AppProperties FILE NOT FOUND
>>>> Attributes: Error". Interestingly, this error message
>>>> appeared when logged into the account in which TIP was
>>>> working fine. I could not find a listing for tabtip in
>>the
>>>> user account where TIP was not working - suggesting
> that
>>>> its not even loading.
>>>> Pat
>>>>>-----Original Message-----
>>>>>Well more interesting findings. We thought there may
>>have
>>>>>been problems with one of the work user account because
>>>> of
>>>>>the "x'd" out services when we ran rsop.msc. It turned
>>>> out
>>>>>that the cashed credential for that account had
> expired.
>>>>>These were updated. SP2 was uninstalled and reinstalled
>>>>>and success TIP was now fully functional on the work
>>>>>account where it had previously been non-responsive.
> All
>>>>>was well in the universe until I logged on as an
>>>>>administrator on the local machine domain.
>>Unfortunately,
>>>>>now TIP is non responsive on this account. I checked
> the
>>>>>other user account I created on the local machine
> domain
>>>>>and TIP was similarly non-responsive there as well. The
>>>>>obvious first question I would ask is, does anyone have
>>>>>TIP working properly on multiple user accounts on the
>>>> same
>>>>>tablet? Is this question worthy of starting a new
>>thread?
>>>>>Cheers, Pat
>>>
>>>
>>>.
>>>
>>.
>>