SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : USRX /COMS - and other "stuff"
COMS 0.00130-23.5%Nov 7 11:47 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Jeffery E. Forrest who wrote (2895)5/3/1997 8:21:00 PM
From: Glenn D. Rudolph   of 5244
 
I know this is not the place but I felt is was a good weekend and anything could go:

You are thinking about upgrading? Well, read this story first... Last
year a friend of mine upgraded GirlFriend 6.0 to Wife 1.0. He
immediately discovered that it's a memory hog, leaving very little
system resources for other applications. He has also recently noticed
that Wife 1.0 spawns child processes, which further consume valuable
resources. No mention of this particular phenomena was included in the
product brochure, nor in the documentation, although other users have
informed him that this behaviour is typical, due to the nature of the
application. Not only that, but Wife 1.0 installs itself such that it is
always launched at system initialisation, where it can monitor all other
system activity. He's finding that some applications-such as PokerNight
10.3, BeerBash 2.5, and PubNight 7.0--will no longer run, crashing the
system when selected (even though they always worked fine before). At
installation, Wife 1.0 automatically installs undesired Plug-Ins,
including MotherInLaw 55.8 and BrotherInLaw Beta release. As a
consequence, system performance seems to diminish with each passing day.
Some features he'd like to see in the upcoming Wife 2.0: * A "Don't
remind me again" button. * A minimise button. * An InstallShield feature
that allows him to install Wife 2.0 with the option to uninstall at any
time, without the loss of cache and other system resources. * An option
to run the network driver in promiscuous mode, which would allow the
systems hardware probe feature to see greater use. I myself decided to
avoid all of the headaches associated with Wife 1.0 by sticking with
Girlfriend 2.0. Even here, however, I found many problems. Apparently,
you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must
uninstall Girlfriend 1.0 first. Other users say this is a long-standing
bug that I should have been aware of. Apparently, different versions of
Girlfriend have conflicts over shared use of the I/O port. (You would
think they would have fixed such a stupid bug by now.) To make matters
worse, The uninstall program for Girlfriend 1.0 doesn't work very well,
leaving undesirable traces of the application in the system. Another
annoying problem-all versions of Girlfriend continually pop up annoying
messages about the advantages of upgrading to Wife 1.0. ***** BUG
WARNING ***** Wife 1.0 has an undocumented bug. If you try to install
Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney
files before executing self-de-installation. Then Mistress 1.1 will
refuse to install, claiming insufficient system resources. ***** BUG
WORK-AROUNDS ***** To avoid the above bug, try installing Mistress 1.1
on a different system and never run any file transfer applications (such
as LapLink). Also, beware of similar shareware applications, which have
been known to carry viruses that may affect Wife 1.0. Another solution
is to run Mistress 1.0 via a UseNet provider under an anonymous name.
Here again, beware of viruses, which can accidentally be downloaded from
the UseNet
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext