pexy
Član broj: 66983 Poruke: 11 91.191.16.*
|
Evo malo informatickih fora. Ranije sam nasao na jednom sajtu, pa postujem sve zajedno. Nadam se da nije previse.
A computer geek loved a girl who studies computer science.
He sent a letter, saying:
I LOVE YOU MORE THAN MY COMPUTER Believe me it is true ...
You installed the best in me.
Your picture is always in my background.
You clicked my heart gently.
You drive me crazy when I see you.
Your love reset my life and deleted all the sadness in me.
You restored my kindness after I thought it was corrupted.
I'm always connected to you with more than 56 heart beat per second.
You hacked my brain and registered your name in it.
You are the only one that could navigate my feelings and explore my
emotions at the same time.
I feel lost when I try to call you and you are not responding.
I always feel you close to me when I shut down my eyes, or when I open
my windows waiting for you to pass.
You are the only one that can log into my heart and never log out.
I dream of being your only server as long as I live.
You don't have to search for me, cause we are always linked to each
others.
I see your name everywhere, my front page, my homepage and all my
software.
I scanned my life and found that I'm only infected by you.
You are the virus I'd never remove, and why should I do?
Believe me it is true...
I love you more than my CPU!!!!
----------------------------------------------------------------------------------------------------------
GirlFriend Version 1.0
I'm currently running the latest version of GirlFriend and I've been
having some problems lately. I've been running the same version of
DrinkingBuddies 1.0 forever as my primary application, and all the
GirlFriend releases I've tried have always conflicted with it.
I hear that DrinkingBuddies won't crash if GirlFriend is run in
background mode and the sound is turned off. But I'm embarrassed to
say I can't find the switch to turn the sound off. I just run them
separately, and it works okay.
GirlFriend also seems to have a problem co-existing with my Golf
program, often trying to abort Golf with some sort of timing
incompatibility.
I probably should have stayed with GirlFriend 1.0, but I thought I
might see better performance from GirlFriend 2.0. After months of
conflicts and other problems, I consulted a friend who has had
experience with GirlFriend 2.0. He said I probably didn't have
enough cache to run GirlFriend 2.0, and eventually it would require
a Token Ring to run properly. He was right--as soon as I purged my
cache, it uninstalled itself.
Shortly after that, I installed GirlFriend 3.0 beta. All the bugs
were supposed to be gone, but the first time I used it, it gave me
a virus anyway. I had to clean out my whole system and shut down
for a while.
I very cautiously upgraded to GirlFriend 4.0. This time I used a
SCSI probe first and also installed a virus protection program. It
worked okay for a while until I discovered that GirlFriend 1.0 was
still in my system. I tried running GirlFriend 1.0 again with
GirlFriend 4.0 still installed, but GirlFriend 4.0 has a feature I
didn't know about that automatically senses the presence of any
other version of GirlFriend and communicates with it in some
way, which results in the immediate removal of both versions.
The version I have now works pretty well, but there are still some
problems. Like all versions of GirlFriend, it is written in some
obscure language I can't understand, much less reprogram. Frankly I
think there is too much attention paid to the look and feel rather
than the desired functionality. Also, to get the best connections
with your hardware, you usually have to use gold-plated contacts.
And I've never liked how GirlFriend is totally "object-oriented."
A year ago, a friend of mine upgraded his version of GirlFriend to
GirlFriendPlus 1.0, which is a Terminate and Stay Resident version
of GirlFriend. He discovered that GirlFriendPlus 1.0 expires
within a year if you don't upgrade to Fiancee 1.0. So he did, but
soon after that, he had to upgrade to Wife 1.0, which he describes
as a huge resource hog. It has taken up all his space, so he can't
load anything else. One of the primary reasons he decided to go
with Wife 1.0 was because it came bundled with FreeSexPlus.
Well, it turns out the resource allocation module of Wife 1.0
sometimes prohibits access to FreeSexPlus, particularly the new
Plug-Ins he wanted to try. On top of that, Wife 1.0 must be
running on a well warmed-up system before he can do anything.
Although he did not ask for it, Wife 1.0 came with MotherInLaw 1.0
which has an automatic pop-up feature he can't turn-off.
I told him to try installing Mistress 1.0, but he said he heard if
you try to run it without first uninstalling Wife 1.0, Wife 1.0
will delete MSMoney files before doing the uninstall itself. Then
Mistress 1.0 won't install anyway because of insufficient resources.
I suppose the moral of the story is: know your system's hardware,
it's software requirements and compatibilities and be real careful
about what software you install and when and how you upgrade.
-----------------------------------------------------------------------------------------------------------------------------------
If Microsoft Bought McDonalds
Super Size 'upgrades' would be mandatory, if customers wanted to actually
use the food to its fullest potential.
We'd all have to buy new cars to use the McMicrosoft Drive-Thru.
Upon hearing about a new burger about to be launched by Netscape King,
McMicrosoft would 'preannounce' *their* new burger, even though its secret
sauce is still in alpha.
They'd steal recipes from Apple's employee cafeteria!
Once a customer eats McMicrosoft food, trying to remove all traces of it
from the digestive tract proves impossible.
--------------------------------------------------------------------------------------------------------------
If Restaurants Functioned Like MICROSOFT
Patron: Waiter!
Waiter: Hi, my name is Bill, and I'll be your Support Waiter.
What seems to be the problem?
Patron: There's a fly in my soup!
Waiter: Try again, maybe the fly won't be there this time.
Patron: No, it's still there.
Waiter: Maybe it's the way you're using the soup;
try eating it with a fork instead.
Patron: Even when I use the fork, the fly is still there.
Waiter: Maybe the soup is incompatible with the bowl;
what kind of bowl are you using?
Patron: A SOUP bowl!
Waiter: Hmmm, that should work. Maybe it's a configuration
problem; how was the bowl set up?
Patron: You brought it to me on a saucer; what has that to
do with the fly in my soup?!
Waiter: Can you remember everything you did before you
noticed the fly in your soup?
Patron: I sat down and ordered the Soup of the Day!
Waiter: Have you considered upgrading to the latest Soup
of the Day?
Patron: You have more than one Soup of the Day each day??
Waiter: Yes, the Soup of the Day is changed every hour.
Patron: Well, what is the Soup of the Day now?
Waiter: The current Soup of the Day is tomato.
Patron: Fine. Bring me the tomato soup, and the check.
I'm running late now.
Waiter leaves and returns with another bowl of soup and
the check
Waiter: Here you are, Sir. The soup and your check.
Patron: This is potato soup.
Waiter: Yes, the tomato soup wasn't ready yet.
Patron: Well, I'm so hungry now, I'll eat anything.
Waiter leaves.
Patron: Waiter! There's a gnat in my soup!
The check:
Soup of the Day . ........... . . . $5.00
Upgrade to newer Soup of the Day. . . $2.50
Access to support . . . . . . . . . . $10.00
--------------------------------------------------------------------------------------------
Top 25 Explanations by Programmers When Their Programs Don't Work
1. Strange...
2. I've never heard about that.
3. It did work yesterday.
4. Well, the program needs some fixing.
5. How is this possible?
6. The machine seems to be broken.
7. Has the operating system been updated?
8. The user has made an error again.
9. There is something wrong in your test data.
10. I have not touched that module!
11. Yes yes, it will be ready in time.
12. You must have the wrong executable.
13. Oh, it's just a feature.
14. I'm almost ready.
15. Of course, I just have to do these small fixes.
16. It will be done in no time at all.
17. It's just some unlucky coincidense.
18. I can't test everything!
19. THIS can't do THAT.
20. Didn't I fix it already?
21. It's already there, but it has not been tested.
22. It works, but it's not been tested.
23. Somebody must have changed my code.
24. There must be a virus in the application software.
25. Even though it does not work, how does it feel?
|