Only one way to fix it forever!
bobbyjohn wrote:
Only one way to fix it forever!
That's my friend Bazz. He also has another hammer near his smart ass TV! Back in the day his Bronica fell to the hammer.
Thank you!
Thirty-five years of experience condensed into 11 indisputable facts!
Coming from an IT guy,
10. The number one cause of computer problems is the user.
Laramie wrote:
Coming from an IT guy,
10. The number one cause of computer problems is the user.
I had techs who used the code ID10T, to denote certain users in trouble logs. True then, true now.
pendennis wrote:
I had techs who used the code ID10T, to denote certain users in trouble logs. True then, true now.
Haha - I forgot about that one!
Laramie wrote:
Coming from an IT guy,
10. The number one cause of computer problems is the user.
That must come from an IT guy as nobody would think so.
pendennis wrote:
I had techs who used the code ID10T, to denote certain users in trouble logs. True then, true now.
My strangest support problem was with dBase for DOS running under early Windows.
One database was getting screwed up, apparently "loosing data".
I
finally (did take a while) figured that someone was "cut-n-pasting" data from another Windows application into a text field in the data base screen (user) interface program. The problem was that dBase was taking the CTL-V paste command as an input character, NOT pasting the contents of the buffer. This caused dBase to put an EOF marker (End Of File) in the database. The data actually remained, it was just not accessible past the EOF marker.
I removed the EOF marker (manually edited the field), and all was well again.
Who (at the time) knew......
john451
Loc: Lady's Island, SC/Columbia, SC
The most important thing I learned in my 38 years of programming is that the computer always does what you've told it to do.
If you want to reply, then
register here. Registration is free and your account is created instantly, so you can post right away.