It is a ....Visual Basic 5 program.
OCX terror-storm. Eleven OCX's it shoved into the system
directory! Plus a few more of those in its directory, that
accounted for the majority of the =>1600+ registry
entries<= the install added.
Even just a few OCX's for an app and you get a ton of stuff
snaked through the classes root key, with their clsid,
interface, typelib entries... very messy and ugly IMO. And
this prog has more damned ocx's than I've had to witness in
a long time.
The install also did this thing similar to what I
unfortunately do see routinely, but dislike each time.
Changed a whole bunch of registry entries to mark
everything down from vb6 to vb5. In this case, though,
particularly high number: more than 80 keys it changed
down.
That large set of changes must have been why TUN crashed
every time I tried to use it to uninstall this thing.
(Finally I just reverted to the copy of the registry I'd
saved before running the install.)
And this is without even going into all the extra files and
regentries that MSI always tries to add. The OCX hell
especially, and changing all the vb file reg values, then
adding MSI to the offense, I give this app a D- at best as
far as character, lack of respect for people's computers.
Graphics features? Who knows. I did run it twice. Crashed
my machine. Very quick - my resources monitor wasn't able
to warn me in time. So I tried running it after a fresh
reboot, where my startup values are in the high 90s. Just
launching it then, without even a file loaded, that shot me
down to 34/34/46. Woah! Ok, I only have 192mb RAM & use
w98, but what's this thing take? I mean, what if one has a
few big image edits going on?
I'll leave this prog for the rest of you. I'm going to go
interact with a few dignified, gentle Borland programs to
console me after the ordeal.