Sam,
The 100xx errors returned by WinSock are generally the Berkeley errno
values with 10000 added to them. This one has no Berkeley equivalent. The
information I have on it is:
The WinSock implementation cannot function at this time because the
underlaying system it uses to provide network services is currently
unavailable.
o Check that WINSOCK.DLL is in the current path.
o Check that WINSOCK.DLL is from the same vendor as the underlaying
protocol stack.
o Check that all WinSock components are installed and configured.
Not much I know but maybe it will be of some help.
Regards,
Bob
------------------------------------------------------------------------
-------------------
Bob Withers Two things are infinite: the
universe and
bwit_at_pobox.com human stupidity, and I'm not sure
about
http://www.pobox.com/~bwit the universe. - Albert Einstein
------------------------------------------------------------------------
-------------------
----- BEGIN GEEK CODE BLOCK -----
Version 3.1
http://www.geekcode.com
GCS d- s: a+ C++ UO++ P L++ E--- W++ N++ o-- w++
O M V- PS PE Y+ PGP t+ 5 X++ r* tv+ b++ DI++ D--- G
e++ h--- r+++ y+++
----- END GEEK CODE BLOCK -----
On Tuesday, June 22, 1999 1:15 AM, Sellam Ismail
[SMTP:dastar_at_ncal.verio.com] wrote:
>
> I would normally not post such a lame question to this list but I need
> help desparately and don't have time to go wading through a haystack for
a
> needle. Its bad enough I have to keep re-visiting this problem of
windows
> deciding to kill itself every few months for the joy of it.
>
> My IP stack is hosed on my Win95 machine. When I try to ping any host I
> get "Transmit failed, error code 10091". If I try to run WINIPCFG I get
> "Fatal error: cannot read IP configuration".
>
> Since MS is fucked and doesn't have any sort of technical documentation
> anywhere useful that would list these errors I must now try to go
> searching for what this bullshit means. Unless you already have the
> answer?
>
> This started to happen after I had to re-install windows over the
existing
> install, because it all of a sudden started coming up with a "Windows
> exception" during boot and would not boot any further.
>
> TIA.
>
> Sellam Alternate e-mail:
dastar_at_siconic.com
>
------------------------------------------------------------------------
------
> Don't rub the lamp if you don't want the genie to come out.
>
> Coming this October 2-3: Vintage Computer Festival 3.0!
> See http://www.vintage.org/vcf for details!
> [Last web site update: 05/25/99]
>
Received on Tue Jun 22 1999 - 06:39:22 BST