Sort of. Maybe it does work for 99% of the people out there. I know
nothing of that. And yes, my toes are sensitive to things such as this. If
I lose my op sys it takes me months to get it back to the condition I had
before its destruction. You may not believe me but I assure you that is the
Michael A Chase wrote:
> I'm having trouble understanding how setup.exe became the source of all
> evil in the universe. You had one BSOD months ago which may or may not
> have been caused by setup.exe and as a result you are unwilling to try
> another version of it ever again.
>
> A client le
At 01:51 PM 4/20/2002, George Hester wrote:
>Sort of. Maybe it does work for 99% of the people out there. I know
>nothing of that. And yes, my toes are sensitive to things such as this. If
>I lose my op sys it takes me months to get it back to the condition I had
>before its destruction. You
George Hester wrote:
> The information I have garnered here has helped to maybe stick my toes in
> the fire again. I will wait a while and see if there is any good soul that
> can explain the procedures for a manual setup. And if that is pie in the sky
> then at that point I will decide if walk
ROTFLMAO
George Hester was the one who wanted all this stuff -- and I just got
four (count 'em, FOUR) "Message not delivered, virus/sensitive content
found" bounce messages from HIS account. Apparently, George's email
account is paranoid about ".README" files .zip files, in addition to
p
Charles Wilson wrote:
> ROTFLMAO
>
> George Hester was the one who wanted all this stuff -- and I just got
> four (count 'em, FOUR) "Message not delivered, virus/sensitive content
> found" bounce messages from HIS account. Apparently, George's email
> account is paranoid about ".README"
On Sat, 20 Apr 2002 17:39:15 -0400 Charles Wilson <[EMAIL PROTECTED]> wrote:
> ROTFLMAO
>
> George Hester was the one who wanted all this stuff -- and I just got
> four (count 'em, FOUR) "Message not delivered, virus/sensitive content
> found" bounce messages from HIS account. Apparently,
On Sat, Apr 20, 2002 at 01:51:36PM -0400, George Hester wrote:
>Sort of. Maybe it does work for 99% of the people out there. I know
>nothing of that. And yes, my toes are sensitive to things such as this. If
>I lose my op sys it takes me months to get it back to the condition I had
>before its
> -Original Message-
> From: Charles Wilson [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 21, 2002 4:14 AM
> (*) has anybody ported GnuPG to cygwin? Would you mind supporting it
> and adding it to the cygwin dist?
If someone has ported it to mingw, that would be even better
On Sun, Apr 21, 2002 at 08:40:52AM +1000, Robert Collins wrote:
>> -Original Message-
>> From: Charles Wilson [mailto:[EMAIL PROTECTED]]
>> Sent: Sunday, April 21, 2002 4:14 AM
>
>> (*) has anybody ported GnuPG to cygwin? Would you mind supporting it
>> and adding it to the cygwin dist?
Christopher Faylor wrote on Saturday, April 20, 2002 11:38 PM:
> ... You might also want to invest in
> something like Norton Systemworks which has diagnostic tools that may
> help narrow down what's wrong with your system.
Hmm. Recently we had an NT system which was frequently BSOD'ing
(not Cy
It ain't me man wha!
--
George Hester
_
"Charles Wilson" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Charles Wilson wrote:
>
> > ROTFLMAO
> >
> > George Hester was the one who wanted all this stuff -- and I just got
>
It wasn't setup that BSOD'd the op sys it was rebooting after the setup.
Jeeze! And please if you want to give me the old "screw you" that doesn't
help any. You may think my op sys is hanging on by it's IDE cable and if so
that's your call. I cannot believe you suggested installing a Norton
pro
> It wasn't setup that BSOD'd the op sys it was rebooting after the setup.
> Jeeze! And please if you want to give me the old "screw you" that doesn't
> help any. You may think my op sys is hanging on by it's IDE cable and if so
> that's your call. I cannot believe you suggested installing a
On Sun, Apr 21, 2002 at 01:48:12PM +0100, Cliff Hones wrote:
>>It wasn't setup that BSOD'd the op sys it was rebooting after the
>>setup. Jeeze! And please if you want to give me the old "screw you"
>>that doesn't help any. You may think my op sys is hanging on by it's
>>IDE cable and if so that
cgf worte:
> ...
> I appreciate your (Cliff) letting people know about your experiences
> with Norton on XP. ...
Actually it was with NT4SP6. And I can't be sure that it was a
bug in the Symantic/Norton code, as the system had been 'repaired'
and the Norton s/w was rather old. But it does illus
Got you. I don't recall if a reboot was necessary. All I remember was that
the Cygwin installation didn't work. I then rebooted hoping then it would
work. It didn't I BSOD'd. Now that was in Windows 2000 Professional which
is doing very well now thank you. I was going to put Cygwin in Window
Have mercy upon me please.OK I'll come clean. This was so long ago (18 mos)
that I don't really remember what exactly happened. But I do know that it
didn't work. I have the old Cygwin CD package which I bought from Cygwin.
I took the one I downloaded and installed from Redhat and removed it.
FWIW, All I think any one really needs here is to be certain that you have done and
checked every possibility (that
you can) out your self before bringing it up on the list. Check mailing list
archives, etc.
Once it is clear that you have checked every possibiliity (there are a lot of
On Sat, Apr 20, 2002 at 02:51:45AM -0400, George Hester wrote:
>Suggestion. Let's consider a Manual Install Direction for us weenies
>that lost a few toes trying to install this software in the past.
You're making things way too hard for yourself. Just run setup.exe
and select "Install" rather
> -Original Message-
> From: George Hester [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 20, 2002 4:52 PM
> To: [EMAIL PROTECTED]
> Subject: I am not going to let Cygwin BSOD my Windows 2000 Server
Consider this: A BSOD is equivalent to a unix kernel panic - usermode
software shou
Do you have all your toes?
--
George Hester
_
"Christopher Faylor" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> On Sat, Apr 20, 2002 at 02:51:45AM -0400, George Hester wrote:
> >Suggestion. Let's consider a Manual Install Dir
On Sat, 20 Apr 2002 02:51:45 -0400 George Hester <[EMAIL PROTECTED]> wrote:
> I realize that at one time setup.exe might not have been all that it was
> thought to be. And that now it may be better. But once burned many
> people
> do not jump back in the flames. Well I decided I would stick my
On Sat, Apr 20, 2002 at 03:19:40AM -0400, George Hester wrote:
>Do you have all your toes?
Sure. My toes are not so sensitive that they become burned off if
I encounter a problem with my system.
I'm also the kind of guy who thinks that if something is working for 99%
of the people out there and
IMHO, cygwin setup works like a champ. I've install cygwin on 4
machiness in the past year, nary a BSOD.
Stick your toes back in. The water was never that bad in the first
place.
;-)
David
On Sat, 2002-04-20 at 12:35, Christopher Faylor wrote:
> On Sat, Apr 20, 2002 at 03:19:40AM -0400, Ge
Not wanting to put salt an open wound...just commenting...fact is, Cygwin can not
cause BSOD. Only OS can
regurgitate BSODs.
Also, if you had checked memory dumps, you would probably know it had nothing
to do with Cygwin.
Probably had something to do with a faulty (pirated?) version
26 matches
Mail list logo
