The following reply was made to PR os-windows/3220; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Jeremy Sippel <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: os-windows/3220: after installing apache, connecting to an NT server to get/share files produces a bluescreen Date: Sun, 18 Oct 1998 00:08:05 -0700 (PDT) I'm really doubtful that this is an Apache problem. There really isn't much we can do to solve it. Win95 can start being unstable because you look at it the wrong way... Does it happen if Apache isn't running at all? On Thu, 15 Oct 1998, Jeremy Sippel wrote: > Sorry, guess I was a little vague. Once I'd installed apache on my win95 > box I began to have this problem (bluescreen from network neighborhood). I > originially figured it was a win95 feature so i reinstalled my box from > scratch and the problem was fine until I installed apache again. My guess > is that there is some sort of shared memory violation with the TCP/IP stack > or something else way over my head. Ordinarily I'd just look for something > else to run, but I like apache too much to dismiss it right away. > Hopefully this makes more sense... > -Jeremy > > At 09:30 AM 10/15/98 -0700, you wrote: > >On 15 Oct 1998, Jeremy Sippel wrote: > > > >> >How-To-Repeat: > >> I assume (i've done this) that a win95b install and apache will provide > a duplication. > >> >From there browsing the network neighborhood should produce this once > you select a file to open. > >> It sometimes (rarely) will let you open the file, but a few attempts > should give you a bluescreen. > > > >Huh? What does browsing the network neighborhood have to do with Apache? > > > > > > >
