Looks Like Total Uninstall is Going Shareware

  • Thread starter Thread starter BobbytheBrain
  • Start date Start date
(e-mail address removed) wrote in
KHaled,

What version of Windows are you running?

Regards,
Eric

Win2K, SP4.

--
KHaled

e-mail: khaledihREMOVEUPPERCASELETTERS at fusemail dot net
(correcting antispam crap..)
please start your subject line with the string "==NG=="
 
omega wrote:
[snip]
As to limitations with current/last freeware incarnation of TUN. One of
those is that there is a limit on how much it can handle for a particular
log to perform an install. When I've used TUN on VB prog installs which
bundle some excess amount of OCXs, then writing many hundreds of keys to
HKCR, then TUN cannot cope, and crashes during trying to use if for the
uninstall. I have to do a very tedious workaround of running the uninstall
in pieces, marking ignore on different groups of keys in turn, to keep
things under the ceiling for how much TUN can process per each round of
uninstall.
[snip]

Hi omega, long time no see. If you uncheck Options|Uninstaller|Log
"warnings" and "successful actions", I think the uninstall will be
successful. Martau knows as I've contacted him about a year ago about
this.

Regards,

Inspire ([email protected]) / Spacey Spade

ps. When you disappeared, I decided to take a different alias on acf,
but now you're back!
 
Spacey Spade said:
Hi omega, long time no see. If you uncheck Options|Uninstaller|Log
"warnings" and "successful actions", I think the uninstall will be
successful. Martau knows as I've contacted him about a year ago about
this.

I just tested. Ran through about five of the problem .tun files that I'd
set aside. (I needed to turned off all logging checkboxes for testing on
those. This since the original entries relating to those installs no longer
existed in my registry, so it wasn't only successful action logging that
I needed to suppress, but the "not exist, fail" lines, too.)

This seemed to make a real difference. I was now able to run those .tun
through files through all the way, without first going through the tedious
workaround of unchecking different sections to reduce per-round processing
size.

Thank you for the excellent tip! =)

By the way, it did not make a difference on one of the problem .tun files
I'd tried just now. It was one where it turns out I'd misidentified the
problem, thinking this one a matter of too many reg entries to process --
when instead it was the other item which makes TUN crash during an attempted
uninstall. Funky chars in the reg keys, ones that TUN doesn't like. It's
from an installation of $Textpad. Some of the values there are not even any
kind of normal ansi. They show as garbage, little squares, when try to view
as text. Replace0 = ''

A long time ago, I'd made occasional attempt to take note on the type of
funked-up reg entries which made TUN stumble, but soon ended up not
bothering to expend the effort. Instead just removing any entries that
look to be giving it a problem, on a per-se basis, (deleting manually via
registry editor), and not taking notes.

I don't recall much really legit during the occasions. I don't know the
story exactly with $Textpad's problem, but other times, it was pretty
obvious that it was dumb slop on the part of some programmer. Using
question marks as part of key names, or forward slashes, or weirdo chars
from don't know where, maybe extended high ascii set, or maybe it was mars.

Slop like the example below, stupidly using the special forward slash to
name a settings key, it not merely makes TUN stumble, but it annoys the
heck out of me to have to even witness it:

[HKCU\Software\VB and VBA Program Settings\Notepad And 1/2\Settings]

.. . . . .
Regards,

Inspire ([email protected]) / Spacey Spade

ps. When you disappeared, I decided to take a different alias on acf,
but now you're back!

I caught all acf articles from the year, including during the period when
not had time to engage in netnews, just that my reading was sometimes months
behind realtime. And my attention was caught by the Inspire posts, since
those were on subjects that much interest me, from a perspective I share
with you, and it was immediately clear that it was you speaking. :) Are
you back to hang a while? Or are we only having a weekend rendez-vous?
 
[edit]
(I needed to turned off all logging checkboxes for testing on those.

Oops. I'd not read your instructions precisely. :( Uncheck these two
logging boxes: "warnings" and "successful actions." That really works
well. Thanks again, Spacey.

.. . .
on a per-se basis, (deleting manually

That was supposed to read "on a per-see basis" (ie, each time seen).

The spellcheck wizard got me again (think I was better off when I had the
firm practice of keeping it out of the picture).
 
dadiOH said:
What size *.tun seems to be the limit for you? I have one for NASA's
Worldwind that is 2,439 KB and TotalUninstall handles that OK.

A .tun file might be very large when it includes a lot of entries for files.
Where I have noted problems, it always seemed to concern registry entries.

The smallest problem .tun file that I was able to dig out, it is only 47k.
All of that is regkeys. Tun text export of this one comes out at 660 lines.

On that .tun file, I've now tried the workaround which was given to me by
Spacey Spade. Turning off the options of logging warnings and successful
actions. That made significant difference: the whole process now completed
smoothly, TUN not crashing.

I have one extra large .tun file sitting there, too. It's 147k. Every bit
of it is registry entries. It was a result from one day having launched
a copy of winword 97 from my removable drive. A program that is not formally
installed on my computer. Totally MSO character... To even take one step
into the door, that wrote, and changed, a massive landslide of entries. I'm
not going to test that one with the new trick just now, though. As I'd need
to do it on temp copy of registry only, as running the undo file for that
would restore entries to my registry that were from a couple of years ago,
many no longer wanted.
 
Back
Top