> Of course you can't un-ring a bell, and all 100 > participants in the experiment continued to blame me > for the experiment's failure. >
Hey! I was there when you turned it off. Except I am the one who said you did it on purpose! Yeah, that's the ticket! You did it to get more revenue for fixing what you had broken. Okay, I confess, I was not there. But Seriously, could you not see a civilian contractor doing just that? heh-heh.. So, this is how runors get started, eh? Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michael Madigan > Sent: Thursday, July 19, 2007 4:53 PM > To: [EMAIL PROTECTED] > Subject: RE: Slow load of runtimes > > > I remember a large battlefield simulator experiment > crashing in our lab with one of the rack servers > turning off. > > My chair was directly in front of the server, so > someone started a rumor that I had shut the server off > by carelessly backing up into a server's power switch. > > Of course on further inspection, and trying to > duplicate the failure, you couldn't push the chair > into the button to get it to turn off, no matter how > you tried, since the button was recessed into the > chassis. > > Of course you can't un-ring a bell, and all 100 > participants in the experiment continued to blame me > for the experiment's failure. > > My point is that you should always follow up a fix > with an EMAIL explaining the cause and the remedy, > otherwise they will continue to believe it was your > software that didn't work. > > > --- "Graham Brown (CompSYS)" <[EMAIL PROTECTED]> > wrote: > > > It was only the machines down one side of the > > building which was the weird > > thing. > > > > I had the "network guru" hovering over me asking > > "why is *your* software not > > working?" over and over. It obviously took him a > > while to agree to down the > > networks on a hunch but once he saw what was > > happening with his boss stood > > behind him his attitude completely changed. While > > not actually apologising > > to me it was good fun watching him squirm his way > > out. > > > > happy days. > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Behalf Of mrgmhale > > Sent: 19 July 2007 14:00 > > To: [email protected] > > Subject: RE: Slow load of runtimes > > > > > > Wow, I thought only I had run across that kind of > > loopback on a LAN <g>... > > In the case where I saw it, the entire network went > > down immediately after > > some folks began to migrate cables to a new set of > > switches. I got the call > > after everything crashed. I asked what they had > > changed just before it all > > crashed. "Nothing, we just started moving cables > > from the old hubs to the > > new switches, then it all stopped working. We think > > we have a bad switch > > out here." I had then double check to make certain > > they did not have two or > > more cables uplinking to any "child switches". Sure > > enough, there was a > > duplicate uplink. They unplugged the offending > > cable the "new, broken > > switch" was suddenly fixed <g>... > > > > Gil > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of > > Graham Brown (CompSYS) > > > Sent: Thursday, July 19, 2007 5:40 AM > > > To: [EMAIL PROTECTED] > > > Subject: RE: Slow load of runtimes > > > > > > > > > Hi > > > > > > I had a site a couple of months back which was > > doing the same. Exe was > > > local, runtimes also local vfp data on network and > > still running slow. > > > > > > Switched off every machine and server and still 14 > > ports lit on the > > > switches. > > > Turned out to be cabling with the 5 network > > switches in that they > > > had switch > > > A connected to switch B which was connected back > > to switch A and so on (14 > > > times!) > > > > > > No I didn't believe anyone could be so stupid > > either having spent hours > > > checking the application over!! > > > > > > I'd recommend if it is a small network isolating > > it to the one machine. > > > > > > Cheers > > > Graham > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > > Behalf Of Michael Hawksworth > > > Sent: 19 July 2007 08:24 > > > To: [email protected] > > > Subject: RE: Slow load of runtimes > > > > > > > > > AV, DNS lookup issues or Your app is causing > > memory paging when it is open > > > with the 42K spreadsheets, word documents and > > sundry other programs that > > > obviously don't effect performance! (early XP > > desktops only had 256MB > > > memory) > > > > > > If this is using SQL server check that your ODBC > > does have a reference to > > > the server otherwise it has to go find a suitable > > system > > > (30s-2mins delay). > > > > > > Degrag the drive (run checkdsk first) > > > > > > It is usually one of the above. > > > > > > Regards > > > Michael Hawksworth > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > [mailto:profoxtech- > > > > [EMAIL PROTECTED] On Behalf Of MB Software > > Solutions > > > > Sent: 18 July 2007 20:28 > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: Slow load of runtimes > > > > > > > > Allen wrote: > > > > > I have seen this on sites where the program is > > loaded from a server. > > > > Its > > > > > painfull. > > > > > Allen > > > > > > > > > > > > > Yes, I've seen what you've seen too. However, I > > run my apps > > > > local...not > > > > from the server location. > > > > > > > > -- > > > > Michael J. Babcock, MCP > > > > MB Software Solutions, LLC > > > > http://mbsoftwaresolutions.com > > > > http://fabmate.com > > > > "Work smarter, not harder, with MBSS custom > > software solutions!" > > > > > > > > > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
