Re: How I overcame Error 1321 and got a new MSI--Thanks Mary!

From: Chad Harris (ddram32_nospam_at_yahoo.com)
Date: 06/06/04 

Date: Sun, 6 Jun 2004 17:47:43 -0400

Mary--

I finally got it in and without the @@@###$$%%%%% Redmond wisptis.exe and
your links pushed me to keep trying.

1) I blew off Norton.
2) I used a Beta RC1 MSI 3.0 installer.
3) I got a 1911 error that gave me the chance to say no to wisptis and I got
my Office back.

Here's what I take away from this. I installed MOS 2003 two or three times
and paid no attention to Norton but from now on I'll always shut it down
during Office and major installations or installations that are having
problems getting in that I can detect. The MSI or Windows Installer has
always had problems, and if you're encountering stubborn set up errors like
this one, anything you can do to repair or get a new installer may get the
job done.

BTW--Whisptis.exe is not the only illconceived .exe to completely escape
Beta testing. And I can appreciate that wisptis although not needed by 99+%
of Office users may not be causing problems, but when it is keeping you from
installing Office because you got rid of it that takes on a whole new
dimension. Note this by Sam Gentile (experienced engineer, .net developer
and author on .net since it's inception on his blog:

Outlook 2003 Causing CRSS.EXE to go spastic!

http://samgentile.com/blog/archive/2004/01/15/11186.aspx

I have been spending so much time trying to get Office in the last few days,
that I was pretty burned out but when you stuck with it I decided to give it
one more try. I know set up problems aren't that interesting to people
unless it's their own and installers aren't by a long shot the most
satisfying part of Office or Windows obviously, but when you need them they
become important. It's not near as much fun as clip art can be, but without
Office you aren't using Office clip art. So thanks for sticking with it and
stretching to get some good resources that I still want to learn about.
Obviously Install Shield had a way to log installs (and that made me think
of Verbose logging as well) and in the right hands that could produce the
info you need I imagine.

Here's what it did and I have my MSO 2003 back working well. Whether MSFT
knows how to get in their BCM remains to be seen. I think they have the
developers for that add-in hidden better than WMD in/out of Iraq. I still
am going to pursue the answers to my questions but one in a sense did get
answered.

1) I decided since every single experienced Office user, MVPs and MSFT
Office people are unanimous in saying that Norton can definitely interfere
with Office installations in particular to nuke Norton off my computer.
2) I decided maybe I needed some new blood in my installer. Because, and I
don't know and want to find out how experienced Office set up people would
describe this but my errors may have indicated components of the MSI itself
were missing, or that .dlls that the installer writes to or calls on or
invokes including the many C:\config.msi.rbf numbered files invoked in the
errors were missing. I had mentioned to you and I've seen the concept
batted in XP newsgroups, that maybe I could download the MSI
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CEBBACD8-C094-4255-B702-DE3BB768148F

but if I remember correctly, you can update for 95, 98, ME or what people
call the MSFT Wintendo OS's, but XP contains the correct installer--2.0
and XP SP2 contains the Betas I believe of 3.0 and I suppose they will
dovetail MSI 3.0 for the XP SP2 RTM.

This is the quote on the link above. I was thinking that you might be able
to find the download for Windows Installer 2.0 and refresh the files.
That's also what I attempted to do when I ran System File Checker last night
and it didn't help. I was trying desparately to fix the installer or give
the installer any of the C:\Config.msi files it needed that were damaged or
missing by running SFC.

"Windows XP contains Windows Installer 2.0 and therefore can't be installed
or upgraded by this redistributable."

*So that raises the question how does one fix MSI 2.0 in Windows XP if they
need to to install whatever Office included?* So I decided to use and I'm
not discussing it I'm just saying I used it the Beta MSI 3.0 crossing my
fingers it would help me. I knew it might complicate things but I could
always blow it off. I plan to put that question on the XP Customize group
because I may be able to draw an answer there or if there is an XP setup
group or an MSDN group where I can get it answered so much the better.

3) Then I ran MOS 2003 set up. I got this error and this is one of my
favorite error experiences. I betcha the GUID referenced is the GUID for
the Tablet PC ink component, the little CPU gobbler that MSFT Office
developers have so generously shoved down the throat of anyone who installs
MSFT Office whether they plan to touch a tablet PC or not. And it's not
that I don't think tablets will be a definite part of many verticals,
schools, and companies and have lots of potential, its just that MSFT has no
business sticking a little used file that can cause serious CPU freezes for
such a little utilized purpose when they could make it optional. And after
all, since both wisptis.exe can "freak" your CPU as well as

 In connection with the 1911 error below I got what is my favorite dialogue
box of the year. Doyawanna retry or doyawanna ignore? And it was there
that I found my holy grail that I'd been looking for--how to install MOS
2003 and surgically blow off the infamous trouble maker wisptis.exe. I hit
IGNORE and the installation zoomed right on without it and installed
successfully.

Product: Microsoft Office Professional Edition 2003 -- Error 1911. Setup
cannot register type library for file C:\WINDOWS\System32\WISPTIS.EXE.
Contact Microsoft Product Support Services (PSS) for assistance. For
information about how to contact PSS, see
G:\FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10R.CHM.

Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature
'HandWritingFiles' failed during request for component
'{E6BFD503-3A35-4B78-BAB5-9570EDDEF81C}'

Product: Microsoft Office Professional Edition 2003 -- Installation
operation completed successfully. Product: Microsoft Office Professional
Edition 2003 -- Configuration completed successfully.

So thanks very much for the help Mary. I hate the time these MSFT Windows
and Office problems can take, but putting things together and solving them
is a sweet feeling--and you hope you're a little bit better able to handle
the next similar one because it's just around the corner.

Chad Harris

____________________________________________________________________________
______________________

"Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
news:O9B4S2$SEHA.1472@TK2MSFTNGP09.phx.gbl...
> Mary--
>
> I want to thank you again. I got a chance to look at your site, and I
truly
> appreciate the high quality of help that MS MVPs and others unselfishly
> offer on the Office/Outlook groups day after day that allows you to get a
> lot of valuable links and between the lines help/ learning to supplement
> books.
>
> As to evidence of which app installed wisptis, I suppose you'd have to
set
> view to show the criteria for origin, date, or notice when you're doing
it,
> or associate a download date from your downloads file if you save the
> download setups, zips, .exes, ect in a downloads folder. I just know
Office
> 2003 sure wants to install it and stalls when it can't because the
progress
> bar freezes with wisptis front and center and then I get all the
> config.msi.rbf error messages.
>
> Is there any way in the world to get into setup with some custom tool from
> the Resource kit or somewhere else and surgically/selectively remove
wisptis
> which is the prime cause for my 1321 setup snag?
>
> I want to ask this *first* because it hasn't been answered yet. Is there
> any way to be able to surgically single out Wisptis and keep it off the
list
> of things setup is trying to get in? I tried last night to open up a
> custom install with a tool for the resource kit because I couldn't do it
> from the default setup with a custom install Probably not, but if that
were
> possible, if I could get into the guts of setup with some tool and nuke
> wisptis, then I'd be able to get Office back in. I even wonder what tricks
I
> could play with this setup if I knew more dos--if I could get at the
wisptis
> file through the command prompt and keep it the ___ out of setup that way.
>
> I don't know how you tell which of the 3 apps--the MSFT Journal Viewer,
> Adobe Reader 6, or Office 03 installs wisptis--except by date of the
install
> if you configure the view to show that or can find it in your downloads
> folder since almost everybody has Adobe Reader although maybe not 6, I do
> have the Journal Viewer entry on the WICleanUP, but I don't know what
> uninstalling it would do to help this problem now.
>
> I want to be clear about a couple things so you know what I've tried;
that
> I'm glad to try anything you suggest, and that I appreciate your time and
> effort. I search KBs pretty regularly, and the KB 231243 for the 1321
> error (that was I found within seconds of setup balking) offered one
thing
> and that was to check a registry key value--my original post was long so
you
> might not have seen it but I had that value as zero so it didn't offer me
> any setting that I didn't already have.
>
> As far as Office plug-ins and Norton AV or System Works, I don't see any
> Office plugs ins or even the same configuration with my version of Norton
as
> the help describes, but that's no surprise that has happened before.
> Norton Help references looking in the "left pain under other" of the
options
> window for Office plug ins. There is no "other," and there is no "left
> pain." and I've drilled options and don't see any mention of Office plug
ins
> on anything you can click. I don't see anything under web tools listed
at
> all. I'll be glad to uninstall Norton if I can get it to uninstall
> cleanly--often a tricky proposition once you've had an SP2 build on your
> machine because Seattle and Capertuino California are apparently not
> speaking to one another and SP2 users are going to really enjoy the
result
> of that. No mention of that fact in the 300 million dollar ad
campasomeone
> is hatching for SP2 next month.
>
> I checked for quotes in the setup.ini file MST section and found no quotes
> and very little there per the KB 818239. I'm chewing on Install Shield
doc
> Q107388 now. I don't understand their reference to patching strategy
unless
> they mean some MSI patch. All Office 2003's are gone with it. The
document
> on patching strategy makes me wonder if any update or patch for install
> shield from their library would help me. I also wondered if I could
> redownload the MSI and refresh files and it would do any good.
>
> I thought of trying Safe Mode but the MSI installer may not get loaded in
> Safe Mode. I saw
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;823816&Product=off2003
> and wondered if the "setup.ini wizard" mentioned could help me if there
were
> one and there doesn't seem to be or at least they want to say if you use
it
> for 2003 since it's for Office XP and there are problems, don't look to
us.
>
> When I was working with the gentleman from *MSFT, he wanted to use the
> Windows Installer Cleanup Utility but we couldn't *simply because* there
was
> no listing for MOS 2003 in it, so we couldn't select what wasn't there.
> One thing I'd like to ask, is it not uncommon when someone has uninstalled
> something let's say Office Systems 2003 or another version, that if there
> are components to "clean up" that you'd still see an entry for Office 2003
> after you uninstalled it? Because if that's not the case then once you
> uninstalled you can't use that utility. If you uninstalled Office and you
> don't see it, does that imply there aren't remnants for it to clean?
>
> So the MSFT office specialist had a list of registry keys including GUIDs
> and also all the Office folders he wanted to nuke, and nuke we did so
> hopefully we could get it meticulously off. Office was working fine, I
> just couldn't install BCM so the MSFT Office specialist wanted a clean
> slate so he insisted that I uninstall Office. And any of us understand
> that--files could be corrupt; registry strings or orphans could be a
problem
> and I agreed with that logic and uninstalled it. I didn't count on the
so
> not needed WISPTIS for tablet PCs would come back to bite me. Again I
love
> MSFT Office developer logic--less than .05% of people using Office even
have
> a tablet PC since it has so much evolving to do compared to a loaded
quality
> notebook with the newest features as far as a dollar choice, and it
gobbles
> CPU sometimes considerable CPU, so let's make it mandatory to install it.
>
____________________________________________________________________________
> ____________________________________________
>
>
> *My Lack of MSFT Support Rant and View Hex Error Messages Do Nothing for
the
> User to Solve a Problem in Real Time so why offer them to the User?*
>
>
> I was also running SP2 at the time as a Beta tester, and even though I had
> tried to associate BCM before with SP2 uninstalled and going back to SP1,
> they wanted to work with SP2 off. I don't believe that SP2 is the problem
> with associating that desktop SQL MSDE with Outlook. I think it has more
to
> do with the fact that it's the first .net add in MSFT has had and they
> pushed it out unfinished with a lot of problems as a fairly buggy Beta but
> they called it RTM. No big precedent there--it happens with all their
> software to degrees and certainly happens with the Windows OS and Office
and
> will be the case with Longhorn and Blackcomb. So here is this company
who
> is going to spend $300 million dollars to promote XP SP2 because they want
> way more than 250 million legitimate copies sold--if SP2 is radically
> different someone wake me up because I've read everything MSFT has written
> on it. It baby sits and reminds people to use a firewall and update
viral
> definitions some of whom are much more concerned about the latest Kazaa
lite
> fileshare. That's why some of the best and brightest universities in the
US
> become viral infected every single day.
>
> My point here is that this company that I like is going to spend this huge
> amount of money promoting SP2--but they are telling me that they don't
think
> an Office component out of a $500 box of Office is compatible with what
they
> are feverishely trying to get on every OEM computer and the OEM companies
> are perenially like somoene who is thirsty in the desert--they want
moisture
> and they aren't particularlly worried about whether the water is safe or
> not. Anything that even hints of a new OS wrinkle the OEMs always push
for.
> You don't have to be a NYT, WSJ, IBD afficianado to get that. I think one
> add campaign I won't see from whoever handles the promotion is
"Watchout!!!!
> Don't buy Office because SP2 won't work with one of the CD's in Office Pro
> or Office Enterprise edition. We are recalling Office because of SP2.
> SP2 isn't the problem with BCM, but it's a good excuse for Convergys to
say
> we don't support a Beta when they don't know anything about the Office
> add-in BCM and they don't.
>
> But once SP2 releases to manufacture with the major problem that it's not
> compatible with Norton Internet Security or Norton System Works, and RC1
is
> public now being promoted on TechNet's site as a download, so I am
> perfectly OK in saying that using Norton will evoke screens that say it's
> not compatible with SP2 builds (all of them). It must be further than I
> thought from Redmond Washington to Cupertino California and I suppose MSFT
> is not allowed to use Live Meeting or even Net Meeting that's still in XP
by
> putting "conf" in the run box, or a cell phone, or email out of Redmond to
> communicate with Symantec Enterprise/Norton Home and Small Business users
to
> iron out the kinks. It won't be the first time. And I know for a fact
> they've heard from plenty of people using SP2 on this.
>
> At this time I want to point out how much help the all hex all the time
> error messages are for the consumer or even the Sys Ad maven. Few people
> have the tools and training to interpret these hex errors, so they are
zero
> help to most of us. The site .oca.microsoft.com the so-called crash
> analysis site is completely and utterly worthless--I've played with it for
> three years and never seen it yield anything but that there's no solution
> for any given error at this time. What they're thinking with it I don't
> know. I have heard people from Redmond speak of real time practical
error
> help about the time Longhorn every births, but Longhorn ain't no short
term
> solution and it's a different vision depending on what side of the bead
Mr.
> Allchin wakes up on. Right now helpful error messages are in the
primitive
> stages. Many of the KBs have little or no help and I've read a few
> thousand, and many are superficial brushes by the subject like the single
> one on the 1321 error with its reference to one registry key.
>
> _____________________________________________________
>
>
> *I mean MSFT because I want to be clear that Convergys can't and doesn't
> support BCM. Its employees doesn't know anything about BCM and by and
> large the phone support for MSFT is from Convergys employees, many of whom
> want to keep it an NSA secret that they work for Convergys. I'd be hiding
> as well if I were Convergys. They have a compelling reason to hide and
MSFT
> has a compelling reason to hide that they farm support out to them.
>
> So I persisted in asking for help from MSFT. Call me silly. I believed
> the Redmond company that makes and develops and writes code for the
product
> and sells it at quite a profit and lives quite well because of these sales
> should actually support the product. Likewise the Convergys support route
> knows next to nothing about Office setup problems as well but they call
> themselves "set up specialists" much like a degree mill where you can buy
a
> Ph.D. in whatever field over the web in seconds and call yourself Dr.
Bozo.
>
> Chad Harris
>
>
____________________________________________________________________________
> ___________________________________________
>
>
>
> "Mary Sauer" <laserdog@mycolumbus.rr.com> wrote in message
> news:%23PrQAX7SEHA.644@tk2msftngp13.phx.gbl...
> > Hi Chad,
> > Have you tried cleaning up the Installer?
> > Description of the Windows Installer CleanUp Utility
> >
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301&Product=off2003
> >
> > There is a knowledge base article that may relate.
> > Office 2003 Install May Fail When You Use a Transform File
> >
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;818239&Product=off2003
> >
> > When you open Norton, near the top is the options button, this is where
> you disable
> > office plug-ins. In my opinion Norton should be disabled altogether
before
> you
> > install.
> >
> > Installshield has some documents too
> > ERRDOC: Windows Installer Error 1321
> > http://support.installshield.com/kb/view.asp?articleid=Q107388
> >
> > I have wisptis on my computer, it was installed when I installed Office.
I
> also have
> > Adobe 6, but doing a search on my computer does not have show evidences
of
> it being
> > part of Adobe.
> >
> > Have you setup a log?
> > How to use an Office 2003 Setup log file to troubleshoot Setup problems
> > http://support.microsoft.com/default.aspx?kbid=826511
> >
> > Yours is a rare error... if you ever get it worked out let me know. I
wish
> I could be
> > more help. Hopefully someone will jump in here and solve it for you.
> >
> > --
> > Mary Sauer MS MVP
> > http://office.microsoft.com/
> > http://www.mvps.org/msauer/
> > news://msnews.microsoft.com
> > "Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
> > news:%23q8Xtc4SEHA.1768@TK2MSFTNGP10.phx.gbl...
> > > Hi Mary--Thanks for taking a swing at this. I'm really greatful for
any
> > > help. Knocking out annoying Wisptis probably took config.msi files
> that
> > > it needs and now setup wants to stuff it back in. Wisptis is
explained
> > > below. It's installed by MOS 2003, the Journal viewer, and Adobe
> Acrobat
> > > Reader 6.0 from what I can see from googling it. I have Adobe 6 also.
> > > Wisptis was uninstalled. I should have tried tip to get rid of it,
and
> I
> > > should have thought of it it's so basic, but I didn't see it when I
> went
> > > after it--but this method just below might have still given me the
> install
> > > problem if it disabled or got rid of those config.msi files.
> > >
> > > An easier way to do it is to right click on the file
> > > C:\windows\system32\wisptis.exe, click Properties, go to the security
> tab
> > > and remove all permissions except An easier way to do it is to right
> click
> > > on the file C:\windows\system32\wisptis.exe, click Properties, go to
the
> > > security tab and remove all permissions except for Read
> permissions.You'll
> > > never see it run again.
> > >
> > > *Where do you mean to go to "options" and disable Office plug-ins?*
> What do
> > > you think of trying to get back files that setup wants for its never
> needed
> > > turkey wisptis (unless you are using a paritcular tablet component)
> using
> > > System File Checker? At least running SFC rarely causes any
problems.
> > > Also do you think there is any way to download any tool for the
resource
> kit
> > > that will let me do a detailed enough or selective enough custom
install
> to
> > > single out wisptis and keep it from installing? My reasoning there is
> if I
> > > can keep wisptis from knocking on the door with the setup, the setup
> will
> > > move on to completion.
> > >
> > > *I'm going to try what you suggested as soon as I can clear up the
> answer to
> > > where you mean by Options to disable plug-ins.*
> > >
> > > I also wondered if by running System File Checker, I could get back
any
> > > config.MSI files would help, but setup is balking everytime on getting
> > > wisptis in by saying it doesn't have access to certain different
> numbered
> > > config.msi files.
> > >
> > > ******** This all started out with my wanting to associate BCM with
> Outlook
> > > and now I can't get Office in. I'm ready to try setup with script
> > > blocking disabled, but I'm not following where "in options" I can
> disable
> > > Office Plug-ins. Options on the Norton interface? IE Internet
Options?
> I
> > > couldn't find any Office Plug-Ins. ********
> > >
> > > I can't do any kind of repair from Maintainance Mode of course,
because
> > > Office is not installed. I saw the KB--it's no help. Like a lot of
> KBs
> > > it has a helpful sounding title with very little of substance inside.
> The
> > > problem with a 1321 setup error is all kinds of things can cause it.
I
> need
> > > to explain to you what wisptis.exe is and how it came about.
> > >
> > > Every time I try to run set up, it almost gets through and the the bar
> stops
> > > with good old wisptis.exe on the box. I put the wispis info below so
> you
> > > could browse it. I didn't want to distract from telling you at the
top
> what
> > > I think happened. I got a removal tool from one of the sites below
for
> > > wiptis. I can see it as an .rar file in my downloads file. Also after
> > > rereading the desciption I don't know if some reg key could have been
> > > modified by wisptis to make reinstall of Office hard. Now when I
try
> the
> > > setup, it runs to close to completion, then the progress bar stops
with
> the
> > > label "installing wisptis.exe" * I think when I ran the removal tool
> > > (successfully) to get rid of wisptis it also took out some some of the
> > > config.msi files that good ole wiptis wants to install. 99.999999% of
> > > people running Office don't use a tablet. The development teams and
> product
> > > managers for Office could have put it on a MSFT downloads site with
> links
> > > from the MSFT Office site. I'd love to see whoever got the great idea
> to
> > > explain what they were thinking when they wove it into Office 2003.
Now
> I
> > > understand why I hear over and over and over that Redmond developers
are
> > > completely on a planet of their own, and often not even making great
> contact
> > > with the Product managers and their teams.
> > >
> > > I was asked by a MSFT Office specialist to meticulously uninstall
Office
> > > which was working just fine. One thing that spooked people and I
can't
> > > explain is that for a transient period of time, I was getting an
Outlook
> > > 2000 splash screen on opening Office 2003 but after that I was getting
> the
> > > normal Outlook splash screen. OL was working just fine; I just
couldn't
> get
> > > BCM associated with it after trying every thing I could think of. I
had
> > > Office XP, and then when I got MOS 2003 I let setup uninstall it. I
> mean
> > > of course uninstalling and reinstalling MOS 2003 would be no big
> deal--but I
> > > had gotten a lot of extras from the MSFT site and others that were
nifty
> and
> > > I hated going after them again. Here's some context for wisptis? Do
you
> > > have it showing up in processes on any of your MOS 2003 machines?
> > >
> > >
> > > *What Wisptis is--among other things, certainly not needed in
Micorosft
> > > Office--it should have been an optional download.* I have long ago
> given up
> > > on trying to figure out the answer to "What were they thinkiing?" when
> it
> > > comes to developers or Product Teams on the Redmond campus. "Let's
put
> in a
> > > pen data collection component for Tablet PC whether anyone has a
tablet
> or
> > > not. It'll serve as a great memory hog with excellent potential to
> freeze
> > > computers and send CPU to 100%!!! But let's not tell anyone this can
> > > happen. Let them be surprised."
> > >
> > >
> >
>
http://216.239.57.104/search?q=cache:2U612r2ecOgJ:www.hyperboard.co.uk/index.php%3Fshowtopic%3D2517+wisptis.exe&hl=en
> > >
> > >
> > > Wisptis.exe (\Windows\System32) This executable runs as a system
> > > service that provides pen-data collection for other components of the
> > > SDK. When a component needs to interact with the pen (for example, to
> > > collect ink or to detect gestures), this executable is spawned as a
> > > service to communicate directly with the input device. On a Tablet PC,
> > > Wisptis.exe interacts with the digitizer, whereas on a desktop it
> > > interacts with the mouse as well. The executable’s name is an acronym
> > > that references an outdated internal name for the team that developed
it
> > > (Windows Ink Services Platform Tablet Input Subsystem).
> >
>
> --------------------------------------------------------------------------
> --
> > > ----
> > >
> > > Well I don't have a Tablet PC and I certainly don't want an
unnecessary
> > > process eating up my memory resources.
> > >
> > > You cannot get rid of wisptis.exe by renaming or deleting it: Windows
> File
> > > Protection would cause it to reinstall the next time you run Adobe
> Acrobat.
> > >
> > > There is even a rumor about a bug in wisptis.exe itself whereby it
keeps
> > > part of the current user registry hive locked, preventing updates and
> > > eventually resulting in a corruption of the registry hive (which as
> reported
> > > leads to a "Userenv event 1517" on logging off or shutting down).
> > >
> > > Others reported GDI leaks and CPU hogging. I haven't noticed the
latter
> but
> > > can confirm that at one point, the number of open GDI handles by
> wisptis.exe
> > > was above 1000, which is unacceptable.
> > >
> > > So by and large it seems wisptis.exe can make a thorough nuisance of
> itself.
> > >
> > > To uninstall wisptis and Microsoft's Tablet PC Components on your PC,
> you
> > > must delete the following registry entries:
> > >
> > > HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}
> > > HKEY_CLASSES_ROOT\AppID\wisptis.EXE
> > > HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}
> > > HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}
> > > HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}
> > > HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}
> > > HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}
> > > HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}
> > > HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}
> > > HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}
> > > HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}
> > > HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}
> > > HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}
> > > HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}
> > > HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}
> > > HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}
> > > HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}
> > > HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}
> > > HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}
> > > HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}
> > > HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}
> > > HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}
> > > HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}
> > > HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}
> > > HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}
> > > HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}
> > > HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}
> > > HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}
> > > HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}
> > > HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}
> > > HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}
> > > HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}
> > >
> > > HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550
E1F4488DBD2A1578ACF8B
> > > HKEY_CLASSES_ROOT\Installer\Features\7040110900063
> > > D11C8EF10054038389C\WISPFiles
> > > HKEY_CLASSES_ROOT\Installer\Features\7040110900063
> > > D11C8EF10054038389C\WISPHidden
> > >
> > > HKEY_CLASSES_ROOT\TpcCom.* (all of them)
> > >
> > > HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}
> > > HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}
> > > HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}
> > > HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}
> > >
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62
> > > 580BE1
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52D
> > > E68CA4
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CD
> > > E3BF4D
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA
> > > 34E827
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038
> > > 389C\Featu res\WISPFiles
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
> > >
>
entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038
> > > 389C\Featu res\WISPHidden
> > >
> > > Now you can also safely delete \Windows\System32\Wisptis.exe. Make
sure
> the
> > > process is not running; otherwise kill it before deletion.
> > >
> > > Fully tested on an up-to-date Windows XP SP1.
> > > Wisptis is a Tablet PC platform component that someone on the Office
> > > development team decided to load as far as I can tell with Office
2003,
> even
> > > though 99.9% of Office users don't have a Tablet interacting with
their
> PC.
> > > It could have been made available on the Office site, the Windows
Mobile
> > > site, and the MS Tablet site, but no--they made it a mandatory install
> as
> > > far as I can tell. Most people tell me it's listed in processes when
> they
> > > install Office 2003, but some have said they don't see it. It takes
up
> CPU,
> > > and when it's not in the system 32 folder it can be a virus or Trojan
> like
> > > so many normal processes exploited by them, and it's very difficult if
> not
> > > impossible to keep it from starting up. So I ran a toolfrom one of
> these
> > > sites to uninstall it and I think deleted a few reg keys associated
with
> it.
> > > Now I think I'm paying the price.
> > >
> > > I got the removal tool which did the job or the removal tool and the
> > > sequence of steps from one of these sites:
> > >
> > >
> >
>
http://www.boredguru.com/modules/downloads/visit.php?lid=4http://www.boredguru.com/modules/downloads/visit.php?lid=4
> > >
> > >
> >
>
http://216.239.51.104/search?q=cache:vOsMzLAdVhYJ:www.boredguru.com/modules/newbb/viewtopic.php%3Ftopic_id%3D193%26forum%3D24+wisptis.exe+&hl=en
> > >
> > > http://www.aswinnen.be/modules.php?name=News&file=article&sid=53
> > >
> > >
> >
>
http://216.239.51.104/search?q=cache:ilR8VawdrRgJ:www.aswinnen.be/modules.php%3Fname%3DNews%26file%3Darticle%26sid%
> > >
> > > Couillon Inc. has fixed the issues with the WISPTIS.EXE process.
You'll
> see
> > > your non-tablet PC freaking when this process is running, and you'll
> have
> > > this process running if you have Microsoft Journal Viewer or Adobe
> > > Acrobat/Reader 6.0 or MS Office System 2003 installed
> > >
> > > Of course this fix is available through our Downloads section.
> > >
> > > Enjoy It!
> > >
> > > UPDATE: We've re-released the fix with some minor improvements...
> > >
> > > You can download it over here
> > > 3D53+wisptis.exe&hl=en
> > >
> > > Thanks,
> > >
> > > Chad Harris
> > >
> > > ____________________________________________________________________
> > > "Mary Sauer" <laserdog@mycolumbus.rr.com> wrote in message
> > > news:%23bPhNH0SEHA.2408@tk2msftngp13.phx.gbl...
> > > > Do you have Norton? Disable "Script Blocking" and in options,
disable
> > > Office Plug-ins
> > > > before you install.
> > > > This document is for 2000 but it addresses your issue
> > > > Various Error Messages When MSI File Creates and Modifies Files and
> > > Registry Keys
> > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;232143
> > > >
> > > > http://www.appdeploy.com/faq/msi_errors/detail.asp?id=84
> > > >
> > > > What is WISPTIS.exe? It is “Microsoft Tablet PC Platform Component”.
> > > >
> > > >
> > > > --
> > > > Mary Sauer MS MVP
> > > > http://office.microsoft.com/
> > > > http://www.mvps.org/msauer/
> > > > news://msnews.microsoft.com
> > > > "Chad Harris" <ddram32_nospam@yahoo.com> wrote in message
> > > > news:uN0LrzxSEHA.3944@tk2msftngp13.phx.gbl...
> > > > > One main question I have is can you custom install office to the
> point
> > > of
> > > > > keeping one file or folder from installing which is my snag?
> > > > > Are there any 2003 resource kit tools that will help you do this?
> Will
> > > > > using Office 2003 Editions Resource Kit
> > > > > Ork.exe
> > > > >
> > > > > or
> > > > >
> > > > > Office 2003 Setup.exe (Enhanced Version)
> > > > > EntSetup.exe 2/24/04 Approximate file size: 210 KB
> > > > > A self-extracting executable (EXE) file that contains
> Office
> > > > > 2003 Setup version 11.0.6176.0. For more information about the
> benefits
> > > of
> > > > > this enhanced version, see New Setup.exe Fine Tunes Local Caching.
> > > > >
> > > > >
> > > > > help me keep from installing wisptis.exe?
> > > > >
> > > > >
> > > > > I posted this in the setup forum but from what I can tell the
Setup
>
> > > group
> > > > > has *no one responding to setup problems.* It does have
> > > miscellaneous
> > > > > Office problems posted there that could be posted here where
people
> who
> > > are
> > > > > regulars here with help help with non-setup problems over there.
> > > > >
> > > > > Every time I try setp, with of course AV off and even with an
> "msconfig
> > > > > clean boot, I get a 1321 setup error. Is it possible to custom
> > > install
> > > > > and tweak to the file level to leave out wisptis.exe, and is it
> possible
> > > to
> > > > > install in Safe Mode or do you lose the MSI in Safe Mode or
> something
> > > else
> > > > > needed to run the Office setup? I have tried naming these 3 files
> to"
> > > > > .old":
> > > > > C:\Config.MSI file
> > > > > Mapi32.dll
> > > > > MAPI.dll
> > > > >
> > > > > *Every time I try setp, with of course AV off and even with an
> msconfig
> > > > > clean boot, I get the setup error with a diffent numbered
> C:\Config.MSI
> > > > > file number. Is it possible to custom install and tweak to the
file
> > > level
> > > > > to leave out wisptis.exe, and is it possible to install in Safe
Mode
> or
> > > do
> > > > > you lose the MSI in Safe Mode or something else needed to run the
> Office
> > > > > setup?*
> > > > >
> > > > > MOS 2003 Pro install setup error on Win XP Pro SP1. I was
having
> > > trouble
> > > > > getting the BCM add-in to associate with OL 2003. I was asked to
> > > uninstall
> > > > > BCM and MOS 2003 Pro and then to reinstall MOS 2003. MOS 2003 was
> > > working
> > > > > fine. With support help from MSFT Office specialist (not
Convergys)
> we
> > > > > meticulously deleted the appropriate reg keys and files. We were
> going
> > > to
> > > > > use the Windows Installer Cleanup Utility, but it didn't list MOS
> 2003
> > > so we
> > > > > did it manually.
> > > > >
> > > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
> > > > > I am getting the following setup errors and setup stops when
trying
> to
> > > > > install wisptis.exe. Wisptis.exe is unfortunately installed with
> MOS
> > > and it
> > > > > works with tablet PC. If you don't have a tablet, it stubbornly
> starts
> > > and
> > > > > helps itself to CPU. Just ending it as a process or trying to use
> > > msconfig
> > > > > won't stop it. A CPU gobbler that far and away most of the
> population
> > > > > dosn't need as a gift from the MOS developers and product team
with
> > > every
> > > > > Office installation is ridiculous, but someone at Redmond made
that
> > > call.
> > > > > These two links context how to get rid of it and I used one of
these
> > > tools.
> > > > > They work and wisptis.exe disappears from your procdesses. Now I
> think
> > > this
> > > > > is causing me problems on the reinstall.
> > > > >
> > > > > I took steps here to uninstall wisptis.exe and use the wisptis
tool:
> > > > >
> > > > > http://www.longhorn.be/modules.php?name=Downloads&d_op=MostPopular
> > > > >
> > > > >
> > >
> http://www.boredguru.com/modules/newbb/viewtopic.php?topic_id=193&forum=24
> > > > >
> > > > >
> > > > >
> > > > > I'm getting this Error: Error 1321: Setup cannot modify the file
> > > > > C:\Config.MSI 3a5322.rbf. Verify that the file exists (it doesn't)
> in
> > > your
> > > > > system and that you have sufficient permission to update it.
Should
> I
> > > > > search for this to download it? Could it possibly have been
> eliminated
> > > iin
> > > > > getting rid of the wisptis.exe annoyance?
> > > > >
> > > > > File Extension Details for RBF: Roll Back File Backup of existing
> file
> > > > > stored in hidden CONFIG.MSI directory.
> > > > >
> > > > > http://filext.com/detaillist.php?extdetail=RBF (3rd entry down)
> > > > >
> > > > > KB that superficially references setup problem by referring to one
> > > registry
> > > > > value:
> > > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;232143
> > > > >
> > > > > This KB deals with the error in Office XP and recommends checking
a
> > > registry
> > > > > value here. My value is correct and conforms with this solution:
> > > > >
> > > > > HKEY_Local_Machine/Software/Microsoft/Windows
> NT/CurrentVersion/Winlogon
> > > > > 1.. In the right pane, right-click AllocateCDRoms, and then
click
> > > Modify.
> > > > > 2.. In the Value data box, type 0 (zero), and then click OK.
> > > > >
> > > > > 3.. Would appreciate if anyone has suggestions as to how to
> overcome
> > > this
> > > > > setup error.
> > > > >
> > > > > TIA,
> > > > >
> > > > > Chad Harris
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>