× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: PROGMAN GPF in Client Access Enh. for Win 3.1
  • From: DAsmussen <DAsmussen@xxxxxxx>
  • Date: Sun, 22 Mar 1998 16:16:52 EST

Chris,

In a message dated 98-03-21 04:07:28 EST, you write:

<<snip>>
> I can vouch for that, Dean! Sure must be surprising coming from me, eh?
>  
>  I remember a Win 3.1 machine that experienced ZERO problems month after
>  month. Not even ONE moments intervention required. I should point out,
>  though, that this wonderful stability came about only after many days of
>  frustration before I discovered the key to the setup. Also, the stability
>  of the whole platform can go right out the window (no pun intended) if
>  tampered with by someone who doesn't understand the requirements of a
>  Windows machine.
>  
>  After months of uninterrupted stability, an operator screwed up by
>  changing the settings. He turned the power switch to ON. Big mistake, but
>  I corrected the setting and the machine was again no trouble.
>  
>  I understand that the same setting works well for the stability of Windows
>  95 and NT machines. 

Well, despite the sarcasm of the previous note, I agree with you as well Chris
(man, anybody checked the temperature in Hades lately ;-)?).  I think that
about a quarter of Windows problems originate from our not having time to
"mess with" the settings and get them running right in the first place.  I
think another quarter comes from poorly written software -- I can count on
AmiPro and Visio to crash the 3.1, Win '95, NT/Workstation, and OS/2 (client
site) machines without fail if I handle too many or too large objects with
them, despite a plethora of memory on all.   Another quarter comes from
installing software packages that load DLL's and TSR's without asking, or
telling you where they put them.  The final quarter comes from installing
hardware that claims to be compatible, but really isn't unless you have
"Service Pack X" installed.

There are just _TOO_ many darned variables, and _NOBODY_ has time to learn all
of them.  If Micro$oft wants to rule the universe, then they had better start
supplying registered users with the latest patches for their various releases
-- without having to be asked.  Just today, I went to the MS web site to get
some NT patches that I need for my new printer.  Unfortunately, the file that
the cover page said I needed _WASN'T_ on the FTP page it sent me to!  Is
_this_ any way to run a railroad?

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"It's Deja Vu all over again..." -- Yogi Berra
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.