Re[3]: Windows Version Dies with GPF
Fri, 27 Jan 1995 18:38:15 -0500

As per Michael's Request: Here is my public apology to Michael included in
the text of the original exchange:


Shouldn't make these replies after having a day like yesterday ;-).

Not totally humor impaired just overstressed ...

My annoyance was more at your cavalier response which amounted to just
rebuild your PC from scratch. As I attempted to explain in my brain
dead mode at the time (also adding to the noise), was that GPF faults
are usually caused by memory overlaps in programs (writing to memory
blocks not malloc'ed to them), memory managers not being setup
correctly so that they attempt to use memory addresses allocated to
hardware, or non-graceful handling of out of memory. This problem is
more than likely caused by the last, because as I said, I can cause
this to happen rather quickly if I bring up another medium sized
program and then enlarge the CUSEEME video window. As soon as I get a
burst of new video data (lots of stuff on the screen changes) I will
(almost) always get a GPF and have to reboot.

I have no beef with your qualifications and for the most part your
answers are very helpful ... maybe you (and I) need to make sure we
don't make replies when to tired to be really helpful.

I debated whether or not to send this on to the whole list, but
decided this was still mostly between you and I and did not really
need to add to the general noise level. Besides, most of this has been
stated in the several follow-ups that were posted to yours and my
initial exchange.

Again, I apologize and will attempt to keep my comments coherent in
the future (and done before midnight ... ;-).

Mark Holm -or-
P.O. Box 1669 Phone (503)626-9700
Beaverton, Oregon 97075-1669 Fax (503)643-3361

______________________________ Reply Separator
Subject: Re[2]: Windows Version Dies with GPF
Author: Michael Sattler <> at ccmail_internet
Date: 1/27/95 3:27 AM

At 23:02 1/26/95, wrote:
> Now that you (the dedicated mac'ite) have had your laugh, the problem
> really exists.

I didn't say it didn't. In fact, the smiley face is there for people like
you, the humor-impaired. I immediately followed with several suggestions
for debugging the problem:

>>Only on your machine :-) Seriously, since you say that you use this
>>machine for nothing else (and you haven't mentioned changing anything
>>recently), my guess is that Windows ate it's antiquated FAT file system. I
>>suggest that you run Norton Utilities to check the file system, use some
>>other software to verify your network connection, and after all that fails
>>to give you joy, re-install (a) CU-SeeMe, (b) your networking software, (c)
>>Windows, as appropriate.

> P.S. Since you seem to have a "LARGE" opinion on how other people
> should be using this list, how come most of the inane comments seem to
> be currently coming from you? Sorry - as you say, every once in a
> while some of us just get annoyed at the rest of you.

I'm not sure what the "LARGE" refers to, and I'm not sure which of my
comments seem inane to you, but I'll be glad to discuss your impressions
off-line. Most of my messages to this list (and my CU-SeeMe web pages) are
intended to help people overcome technical issues in getting CU-SeeMe up
and running.

And to be perfectly clear about my Macintosh dedication: over the last four
years I've professionally installed, configured, used, debugged code on,
and quality-assured code on a great variety of PCs, from IBM ThinkPads to
Cornell Pentiums. I've taken all my experiences and made the informed
choice that for me (and my time) the Macintosh is the more efficient work
platform. I've still put more time in on PCs than most folks, and I can
still help people debug their setups on them.

Michael Sattler <> San Francisco, California |
Digital Jungle Consulting Services |
And so these men of Indostan/ disputed long and loud/ each in his own |
opinion/ exceeding stiff and strong/ though each was partly right/ and |
all were in the wrong! - John Godfrey Saxe |