I'm running on a Gateway 400mH 128MB system with 10GB hd (about half
filled), so it's probably nothing all that obvious. I keep my temp files
scrupulously cleared out, etc etc. My system resources tend to run fairly
low (35-50% or so) but I'm used to that. Restarting Eudora sometimes clears
the error up, sometimes doesn't, but almost always a reboot does, making me
think that resource-hog Eudora has maybe hosed me again? Still, that error
message is a mystery.
Any ideas anyone?
TIA
--
Elaine P. Pack, Web Analyst, Charlottesville, VA
The 2nd mouse gets the cheese, but the early worm gets eaten!
Visit my new Border Terrier database! http://www9.ewebcity.com/epack
ICQ: 6165307 - AIM: EPPoppie/PopLes/EPPackCo - PGP Public Key: 0xCE923F8B
> Recently when scanning for inbounds, all my EP 5.1 personalities will
> randomly fail immediately with an error message stating: No buffer space
> (10055). This message isn't in the help, nor anywhere on the Eudora site
> that I could find--I'm wondering if it's a new one? Or maybe an old one :)
>
> I'm running on a Gateway 400mH 128MB system with 10GB hd (about half
> filled), so it's probably nothing all that obvious. I keep my temp files
> scrupulously cleared out, etc etc. My system resources tend to run fairly
> low (35-50% or so) but I'm used to that. Restarting Eudora sometimes clears
> the error up, sometimes doesn't, but almost always a reboot does, making me
> think that resource-hog Eudora has maybe hosed me again? Still, that error
> message is a mystery.
>
> Any ideas anyone?
Error getting a network socket. Cause: no buffer space available (10055)
http://www.cit.cornell.edu/helpdesk/win/email/eud10055.html
--
Over and Out
Daniel Jacobson
WSAENOBUFS (10055) No buffer space available.
Berkeley description: An operation on a socket or pipe was
not performed because the system lacked sufficient buffer
space
or because a queue was full.
WinSock description: Same as Berkeley. The WinSock
implementation was unable to allocate additional memory to
accommodate the function request.
User suggestions: This error indicates a shortage of
resources on your system. It can occur if you're trying to
run too many
applications (of any kind) simultaneously on your machine.
If this tends to occur after running certain applications
for a
while, it might be a symptom of an application that doesn't
return system resources (like memory) properly. It may also
indicate you are not closing the applications properly. If
it persists, exit Windows or reboot your machine to remedy
the
problem. You can monitor available memory with Program
Manager's "Help/About..." command.
WinSock functions: accept(), bind(), connect(), listen(),
send(), sendto(), socket(), WSAAsyncGetHostByAddr(),
WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(),
WSAAsyncGetProtoByNumber(),
WSAAsyncGetServByName(), WSAAsyncGetServByPort(), FD_CONNECT
Additional functions: Any other functions that use network
system buffer space, like the "database functions",
setsockopt()
with SO_RCVBUF or SO_SNDBUF options.
Cheers,
John
--
JOHN AMERO, Parksville, B. C. Canada E-Mail:-
joh...@netscape.net
** NOTE:- See S P A M warning on my website.**
Check out my Web Site at:- http://www.island.net/~johna/
Thanks!
elaine
"John Amero" <joh...@netscape.net> wrote in message
news:3B8236D5...@netscape.net...
Try dumping unnecessary background programs and drivers.
HTH,
Cheers,
John