Linux and readline

[Fairlight]

Y'all catch dis heeyah?  Kenneth Brody been jivin' 'bout like:
> 
> Obviously, your applications were dependent on a bug in previous releases, 
> which they have now fixed, thereby causing your apps to crash as they should 
> have been doing all along.  :-)

I know what you're talking about.  Like when they couldn't fix bugs in
'doze because it would break Office, which took advantage of some bugs.
But...

Then they're multi-generational bugs.  FRAPS is dying.  I've used that
since Win2000, and SnagIt also started dying this morning after a sequence
of restores.  I'm now back to fully patched, but still encountering issues.

But...I can start the applications after they've crashed, and they stay up
and working.

It -appears- that it's related to the end of the boot-time startup
sequence...or perhaps the order in which something is loaded.  It's also
affecting basically the last 5-6 applications in my boot sequence, but not
earlier ones.  Something odd is going on here.  I can't even blame it on
.NET, as not all the apps in question use it.  Same with networking, same
with audio, same with video, same with using IE or ie.dll.  Between them
all, -none- of these programs have any consistent link, other than they're
part of my boot sequence.  I do have 19 non-networking (ie., not LAN or
Wireless LAN) systray icons.  :)  And only the last 5-6 are getting slammed
in some way now.

I plan on trying MS support in a while. *sigh* They -will- put out, and
they -will- put out for free.  They made this mess, they -will- fix it on
-their- dime.  My system was operating 100% within normal parameters before
their blinkin' patches yesterday.

mark->
-- 
"I'm not subtle. I'm not pretty, and I'll piss off a lot of people along
the way. But I'll get the job done" --Captain Matthew Gideon, "Crusade"