I have problems when I use the admin tool or access the swiki from the
server machine. I'm on Beta 12 right now ( will upgrade as soon as I have
a few minutes to spare :-(.
Why does it do that?
-Mike
"Jochen F. Rick" <[EMAIL PROTECTED]>@cc.gatech.edu on 05/15/2001 01:06:22
PM
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: [pws] Possible solution to Win2k socket problems?
Wow! We'll have to try that out.
As is, the only thing that we can find that will crash Win2K Swiki 1.0 is
to use the AdminTool on the local machine. Otherwise, it is solid (even
under extreme load).
Peace and Luck!
Je77
On Tue, May 15, 2001 at 10:38:46AM -0400, Anthony Engel wrote:
> A couple months ago, there was some discussion of problems running Swiki
on
> a Windows 2000 box... I just came across this Microsoft update, and it
> sounds promising.
>
> From the Knowledge Base article:
> http://support.microsoft.com/support/kb/articles/q278/5/22.asp
>
> SYMPTOMS
> In Windows 2000 Service Pack 1 (SP1), calls to the Socket function may
not
> be returned, causing the creation of sockets not to succeed. Therefore,
> socket programs may become unresponsive and cause 100 percent CPU usage.
>
> Download fix at:
>
http://www.microsoft.com/Windows2000/downloads/recommended/q278522/default.asp
>
>
> Congrats on release of 1.0!
>
> Tony
