Garmin 195 screen problem

On Thu, 27 Nov 2003 20:23:36 -0600, "John Stricker"
wrote:

Or, perhaps you should just learn how to use it.. 7 machines here running
everything from 98SE, ME, XP home, XP Pro. Almost never have a problem.
Then again, I don't intentionally try to do things to create myself
problems.

First, I am not a booster of MS and I don't even like them and their
ethics, but:

I only have 4 here on a P to P network that run 24 X 7 with the CPUs
staying at nearly 100% utilization.
My wife's system stayed on 98 and then 98 SE for a longggg time before
going to XP Pro. She wouldn't let me change it as it always worked and
she kept hearing horror stories about other people's crashing.

Like you John, I had no problems with ME.

The only problems I've had have been related to line noise,
application conflicts such as Roxio and Nero being unwilling to run on
the same machine and those of my own making.

One of the worst programs for causing problems was "Autocad" as it had
some customized DLLs. I assume they no longer overwrite specific DLLs
with their own customized ones. The way around that, as I recall, was
to put the offending DLL in the root directory for Autocad and copy
the proper DLL back to its own location. Many programs have been
guilty of that.

Oh...and being I do a lot of programming on this one, I had some
problems with earlier versions of Visual Basic setting the creation
date on stock DLLS to the day a program was created. Which, like
Autocad would then overwrite newer DLLs which managed to thoroughly
trash the machine a few times. Never had a problem with C, C++,
Pascal, or Delphi. That is not saying I didn't make some mista... er
add some features that didn't crash the system, but they were at least
recoverable.

I have found NTFS to be much more reliable than FAT16 or 32.


Even my ME box that I use for my internet gateway has been running about 60
days since the last re-boot.

ME was like a lot of people. It was just fussy about who, or what it
chose as friends. At least with XP it warns you about programs it
doesn't like. Welllll... most of them. Get it up and running and it
was reliable, at least for me.


John Stricker

"Ed Wischmeyer" wrote in message
...

and other good windoz stuff.

Ain't no good windoz stuff. All junk. Bah, humbug!

Why is Monopoly Bill worth so much? Figure out how many hours you've
wasted rebooting, reformatting, trying to figure out manuals that didn't
make sense, undoing things that the program did all by itself to "help"

You should try IBM manuals. If you need them you won't understand
them. If you are capable of understanding them, you don't need them.

I will admit that requesting XP to *repair* a network connection is a
dangerous thing to do.

you, trying to get things to work as advertised, fussin' with viruses
and security flaws, etc. Figure out how much your time is worth per

The vast majority of virus infections are due to the lack of knowledge
on the users part and a demand for capabilities that open up the
systems. That they insist on running macros from within office
documents, send out complete VB programs to run databases with Access
tables, and read their news and mail in HTML, is not the fault of MS.
That the apps come with all the goodies turned on could be attributed
to MS, *except* if they weren't the majority of users would be on the
telephone wanting to know why.

hour. Figure out how many millions of people have had the same problems
as you. Multiply those all together to get Monopoly Bill's net worth.

We ran over 1,700 intel systems with Win 98 "on one site". I think we
had something like 7,000 of the things corporate wide. Having to
reboot was not a problem. It was quite a rarity. Many of these
machines ran 24 X 7. That in and by itself should say volumes about
configuration.

How did we manage when MS has such a poor reputation for stability?
We had a set configuration, or rather a set of configurations and
software packages that were tested for compatibility and stability. No
other apps were allowed on the machines. It could easily be worth your
job to change one of those configurations or install a non approved
program. Even approved ones had best be installed by the IS
department.

There is such a vast array of programs/applications available for the
windows environment that it's surprising there aren't more problems.
Many, like the early versions of Autocad have customized DLLs.
Programmers are an independent lot and even though MS tells us to
create our own DLLs if we need something with special functions theirs
still get modified.

yes, there are a great many loop holes in the various incarnations of
their OS and most of them are at least indirectly related to the
attempt to make the system easy for the average user and programmer.
The more complex the system the more likely you will find side effects
such as buffer over run.

The average user does not practice safe computing. The average user
is just barely computer literate under the definition and they
certainly are not "computer savvy". They tend to be of the "it won't
happen to me", "I only open attachments from people I know", and if it
crashes it's the systems fault, type.

According to a recent study about (think it was 38% )of the
population are computer literate. Unless people have changed a lot in
a last few years I think that is probably about 10% high. I taught
intro to computer science at the college level which would be way
above average. The general lack of a grasp of the concepts involved
was surprising for college level students, but at least 90 % of them
did learn how to turn 'em on, insert a disk, run an app, and turn 'em
off which qualifies as societies definition of computer literate.
There were only about 4 or 5 who received an A, out of 195 students.

Most were C and no few were D or worse.
Monopoly Bill hasn't created wealth, he's just transferred it -- like a
crook.


When it comes to business, most are a transfer of wealth from one
person to another, or people to businesses. However, PCs in general
and I do not mean the intel system that was given the copyright (PC),
have advance our quality of life and changes in our way of living (not
all for the best) in so many ways it'd be difficult to name more than
a tiny fraction. So, in that light Monopoly Bill did create a lot of
wealth for a lot of people.

You'll have to fix the return add due to dumb virus checkers, not spam
Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair?)
www.rogerhalstead.com
Bah! Humbug!

Ed "you have to pay me to use microsquish products" Wischmeyer

Or, perhaps you should just learn how to use it.. 7 machines here running
everything from 98SE, ME, XP home, XP Pro. Almost never have a problem.
Then again, I don't intentionally try to do things to create myself
problems.

Coupla comments:
1. I never have problems with the OS or installation or extra software.
Tech support does the first two and I don't attempt the third. I don't
run any MS software at home on a regular basis.
2. My own problems are all with the (*&^ MS applications and help
systems. If (heaven forbid!) we wanted a serious apples to apples :-)
discussion, we could talk about, say, print problems. The other day I
was filling out a form. 8 minutes to do the text, maybe 20 minutes
trying to get the stuff to format properly on the screen (it kept
readjusting itself), and then when that was done, it wouldn't print
right. If it takes a secret decoder ring to disable some unannunciated
mode that is "helping" you, that's bad software design and
documentation. Sometime check out any website on bad human factors in
software design -- 90+% of the examples are Microsoft, not because of
their market dominance, but because they have not established the
requisite culture in their user and developer communities. Also, notice
that it has become a badge of pride to learn how to work around the bugs
and poor design features. (The technical term for figuring out how
things actually work [undocumented] is "hacking.") In fact, this
difficulty-of-use has been institutionalized (brilliant marketing,
actually) in the "Microsoft Certified XXX" programs.
3. At one point, I figured out that lost productivity from using MS apps
ran 5 to 10%, depending. In other words, in a 40 hour week, I would
sometimes spend 10% of my time trying to get the software to work as
advertised. To put that in perspective, the annual cost in lost
productivity was greater than the cost of the hardware, software, and
tech support combined. In some conversations with IT folks, my numbers
were considered low. (Sounds like MS left a lot of money on the table...)
4. In the history of technology, Microsoft is at great risk of earning a
reputation primarily for establishing an international culture of bad
software design and implementation, and training generations of users
that they are too stupid to use computers well. Wouldn't it be great if
MS lived up to its own marketing hype? Unfortunately, the Pandora's box
of incompatibilities and unmaintainabilities has been opened, and not
even MS is rich enough or technically capable enough to close that box.
There may be many responses to this particular comment, and keen readers
would serve themselves well to observe how many of those responses are
dysfunctional or in denial or off topic.

Take away the frivolously flippant attitudes of my previous posts, and
there is entirely too much painful truth there. The tragedy is that
nobody wins -- neither pundits, nor consumers, nor the computing
community at large, nor MS. What lost opportunities. What a shame.

Ed "there's a reason I'm no longer in the computer industry" Wischmeyer

"Roger Halstead" wrote in message
...
On Thu, 27 Nov 2003 20:23:36 -0600, "John Stricker"
wrote:

Or, perhaps you should just learn how to use it.. 7 machines here
running
everything from 98SE, ME, XP home, XP Pro. Almost never have a
problem.
Then again, I don't intentionally try to do things to create
myself
problems.

First, I am not a booster of MS and I don't even like them and
their
ethics, but:


It was the rise in the use of sound cards that gave me a lot of work
re-installing windows, some of the cards would blow resulting in
corrupting the HDD. This was great from my point of view as there was
no data to recover onto floppies or my much used ZIP drive, so it
only required a new card and a clean install; we blamed the client
over his lost data, we did train them in backing up everything.

For some years, CD drives gone bad cause the system to grind to a
halt, thankfully that's not too common now.

My pet hates are, anything a client may use to install any new
applications, games or updated printer drivers etc, floppy drives,
zip drives, cd rom drives and the worst of all that annoying modem
thingy. Provided none of these attachements are on your clients
computer then they cannot do too much damage to their own system
other than formatting the hard drive.

I only have 4 here on a P to P network that run 24 X 7 with the
CPUs
staying at nearly 100% utilization.

I have 7 machines, 4 are working. one is in the lounge with it's own
printer, setup for the wife to use. Three are in my 'office', why so
many for my own use, that's because I split up functions between the
three machines. 1 is used for most of my work, printing, internet, 2
is used for testing all those annoying broken printers people keep
sending me for repair, running my scanner and burning CD's etc, 3 is
em, now just why do I have a third machine connected to my network,
can't think of any good reason, Oh yeh, because it's there.

My wife's system stayed on 98 and then 98 SE for a longggg time
before
going to XP Pro. She wouldn't let me change it as it always worked
and
she kept hearing horror stories about other people's crashing.

My wife did try to use a computer, however, she is still worried
about all the harm you can do to a computer by doing something wrong;
we all know that, well really, what harm can you do to a computer
just writing a letter.

Like you John, I had no problems with ME.


me is a desease that Microsoft created for the PC just to prove they
could do it too.

The only problems I've had have been related to line noise,
application conflicts such as Roxio and Nero being unwilling to run
on
the same machine and those of my own making.


Anything a client can update themselves is the worst application, had
a job on a machine that the client tried to update to IE-6 from ver
5.5 and screwed it up.


--
---
Cheers,
Jonathan Lowe.
/
don't bother me with insignificiant nonsence such as spelling,
I don't care if it spelt properly
/
Sometimes I fly and sometimes I just dream about it.
:-)