![]() |
#91 |
Nameless Being
|
blah blah
If you have MS Front Page 2003
Open "add/remove programs", select "MS Front Page 2003" and click "change" button. Now chose "Add or Remove Features" and click next , there expand "Office Shared Features" and click on "Microsoft Handwriting Component" and select "Not available" and click "update". If that's no help then expand in the same tree "Alternative User Input" and do the same for "Handwriting" option. I can't now remember which is one of that two guilty because I have them both uninstalled. After this there is no more that WISPTIS.EXE and MS installer. |
![]() |
![]() |
#92 |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Oct 2004
|
What if I don't have Frontpage? Which I don't? I have MS Office 2003.. Word, Excel, Powerpoint, Outlook, all installed.. but I don't need FrontPage so it's not installed. Any other way/
|
![]() |
![]() |
Advert | |
|
![]() |
#93 |
Fully Converged
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 18,166
Karma: 14021202
Join Date: Oct 2002
Location: Switzerland
Device: Too many to count here.
|
MoeRL, try what the previous poster said with your Office installation. See if you can also find the Handwriting Component and try to disable it.
I am sure one of the registry methods mentioned earlier in this thread works, but using the method described here just before would be the "cleaner" solution. |
![]() |
![]() |
![]() |
#94 |
Nameless Being
|
9999 GDI Objects
Yeah, this stupid process (Wisptis.exe) is using up 9999 GDI objects and is preventing me from opening any other programs.
MS really needs to work on preventing resource leaks... In the meantime, I'm going to uninstall the Journal Viewer... |
![]() |
![]() |
#95 | |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Oct 2004
|
I thought just a tad further and thought I'd give you this:
http://support.microsoft.com/default...roduct=off2003 ![]() Whoa.. check it: Quote:
![]() Last edited by MoeRL; 12-11-2004 at 01:08 AM. |
|
![]() |
![]() |
Advert | |
|
![]() |
#96 |
Nameless Being
|
![]()
I just wanted to say thanks for the script. Worked well on my XP Pro OS and solved the annoying problem WISPTIS caused with my tablet.
|
![]() |
![]() |
#97 |
Nameless Being
|
How to get rid of it easily!
Sorry but this solution does NOT work.
|
![]() |
![]() |
#98 |
Nameless Being
|
I FOUND IT RUNNING AFTER I INSTALLED MSN 7 BETA,AND I HAVEN'T NOTICED IT BEFORE.
HOW SHOULD IT UNISTALLED IN THIS CASE? I JUST SEARCH IT AND GET ONE .PF FILE DELETED. |
![]() |
![]() |
#99 |
Nameless Being
|
![]()
This is for all you guys who first checks the end of the thread: here's a summmary referring the best posts.
- First of all this problem applies to all NT versions as well, like Windows 2000 and Windows 2000 Pro - Every type of solution possible is posted at least twice, and often discussed endlessly - As usual in a long thread(98 posts/7 pages before me!) some people don't bother to read it through anymore, in stead they add their own 'unique' solution. Post #85/page 6 is a hilarious example: he really thinks he's the first with that solution, while in reality, the very same solution is described in posts #21/page 2(!) and #38/page 3... Still, the arguments for this solution put forward in post #85/page 6 are excellent. Read them and ponder. 1. Solution type 1: *RECOMMENDED* Represented by post #85/page 6, which has an excellent summary of the arguments for this kind of solution. Post #53/page 4 also points out what so many seem to forget: that there might actually be situations where you need to load he wisptis.exe, even on a non-tablet pc because it interacts with the mouse as well... (see post #1/Page 1!), and with this solution it's done in a breeze. 2. Solution type 2: A good alternative, effectively the same as solution type 1 The general idea is to keep the wisptis.exe from loading without messing with uninstalls/registry hacks, which is exactly what solution type 1 does(read post #85/page 6 if you don't understand why this is the best approach). However there are countless other ways of achieving that, and this solution type is probably a more widely useful approach: the zero bite file in solution type 1 did after all require some specialized know-how. Represented by posts #50/page 4(splendid thinking), #80/page 6(a bit messy though). I'm sure that many of you can come up with a couple of more ways, but PLEASE, don't add them here! We all get the hang of it... 3. Solution type 3: The DIY-home carpentry solutions including all kinds of uninstalls/registry hacks If you don't get by now why this is *NOT* the recommended way to go, I'm not gonna try and stop you. You just go right ahead and try whatever fits your personal taste. Though I do suspect that you really have to much time to kill(like me writing this post - phew ![]() Conclusion ---------- This thread was viewed over 90'000 times by thread #82/page 6, and now it's exactly 115,687... Even if people surely will keep reading it, I hope you all agree that what we DON'T need is more of these 'great job' comments or DIY-home carpentry solutions, like endless registry key references (they never have, and never will, always be exactly the same for all versions of Windows - OR Office - go figure if U really think that's the way to go when you're advising EVERYONE to do it your way when there ARE controlled ways of fixing this problem - I KNOW it worked for you, but that does NOT mean that it's a great idea to post it here...). ![]() PS. There are also a couple of nice tips about tools in this post, but I'm not gonna spoil all your fun finding it yourselves ![]() plug-ins that come with Acrobat Reader 6 - so you dont have do downgrade... DS. So, in hopes that this is - the last - post regarding how to actually fix THIS problem... Bye, bye |
![]() |
![]() |
#100 |
Nameless Being
|
![]()
This works on win2k. Edit to fit your Windows directory structure. Save to "Disable-Enable wisptis.exe.vbs". Pls note U must first create the zero byte file (wisptis.exe.zero)
'Disable-Enable wisptis.exe '-------------------------------------------------------------------------------- ' Written by ProgrammerDude '-------------------------------------------------------------------------------- subject ="Pen input device" pdir ="C:\winnt\system32\" pgm ="wisptis.exe" Set fso = CreateObject("Scripting.FileSystemObject") If Not fso.FileExists(pdir +pgm +".disabled") Then Set file = fso.GetFile(pdir +pgm) file.Name = pgm +".disabled" Set file = fso.GetFile(pdir +pgm +".zero") file.Name = pgm MsgBox subject +" has been disabled." _ , vbExclamation +vbSystemModal, " " +subject +" has been disabled" Else On Error Resume Next Set file = fso.GetFile(pdir +pgm) file.Name = pgm +".zero" On Error Goto 0 Set file = fso.GetFile(pdir +pgm +".disabled") file.Name = pgm MsgBox subject +" is enabled." _ , vbInformation +vbSystemModal, " " +subject +" is enabled" End If |
![]() |
![]() |
#101 |
Junior Member
![]() Posts: 1
Karma: 10
Join Date: Jun 2010
Device: Xperia X10
|
You know, for the past year or two I've tried in vain to find out what's been slowing my PC down more and more as time goes on. I was starting to think memory chips were failing, or my HDDs were failing. Or maybe that McAfee SecurityCenter was working overtime.
After many times of looking in the Task Manager to check the usual culprits, things like mcshield.exe would only report high CPU hog-rates at sporadic intervals. Same with everything else. Whilst getting a "low on virtual memory" report for the hundredth time in a month, with hardly anything running, and checking on Task Manager today, I noticed this pesky WISPTIS.EXE showing "00" in the CPU% column, but always hovering one or two items above the tasks showing an actual number. At first I did a search on the net just to see what it was (in case it was spyware), not because I thought it was hogging resources. After finding this thread, I thought perhaps this might have been the cause of my sluggish performance after all. I ran the "unreg.cmd" file and, although I haven't checked to see if it will get reinstalled by anything, I noticed an IMMEDIATE improvement. Whilst the unreg was happening, my HDD was accessing like crazy, like it has done for so long for apparently no reason. After running it, no more, and everything is responding like lightning. So at first glance it would appear this process is indeed very destructive to a Windows PC's performance. I just hope it stays this way! Thanks to the guys who found out how to get rid of this crud. |
![]() |
![]() |
![]() |
#102 |
Junior Member
![]() Posts: 1
Karma: 10
Join Date: Aug 2012
Device: none
|
Here's more complete way to get rid of this hidden feature of Office 2003: from command line, run this:
Code:
msiexec /i {90110409-6000-11D3-8CFE-0150048383C9} REMOVE=Excel_WISPFiles,Word_WISPFiles,PPTNonBootFiles,WISPFiles,XDOCSNonBootFiles,WISPHidden |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Where do I get Zip.exe? | Tony_A20 | ePub | 24 | 01-26-2015 08:23 PM |
Focus annoyance | edbro | Calibre | 2 | 10-05-2010 06:07 PM |
Major annoyance with iBooks app | HarryT | Apple Devices | 23 | 07-22-2010 03:11 PM |
doc2fb.exe | KoopaOne | Workshop | 2 | 02-10-2010 01:44 PM |
A possible reason for E-ink flash annoyance? | stxopher | Which one should I buy? | 6 | 12-15-2006 04:28 PM |