Links
- Journal's Current Page
- To Lum Aves' Home Page
- luminus310@hotmail.com
Deaf Bloggers
- Golden Notebook
- ASL Poetry Prize
- gnarlyDORKETTE
- Spoo Blog
- Golden Notebook
- SwimPC's thing
- Daveynin's thing
- Bionic Ear Blog
- Amanita.net
- Why Try
- Semi-Cathartic
- Job Hunt Larry
- Burninglight
- My Voice
- Diana's Place
- Arcadian Expressions
Lurking in . . .
Archives
"From the darkness, sleeping light." Formerly luminus dormiens. Lux pacis, light of peace.
Quote: "Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us." --Bill Watterson, cartoonist, Calvin and Hobbes
20040214
Unable to Initialize Windows Sockets Interface (a solution)
I've noticed that some people are getting into my website, but looking for a solution to the "Unable to Initialize Windows Sockets Interface," so I've posted a solution to fixing that pesky Windows problem.
Fix that socket.
Unable to Initialize Windows Sockets Interface Solutions at Microsoft.com: I think Microsoft has the tendency to move pages around where they can't be found, so if you get a broken link, just follow the instructions from Fix that socket.
In the future, go to support.microsoft.com and search for help over there. Google can't help nothing because it's too stupid to rank anything that cannot be or are not linked to very often, i.e. Windows problems and solutions.
However, there's a problem (of course). Microsoft is planning to remove support for Windows 98, which was where I had that problem. So I've copied all the instructions necessary to re-initialize the windows sockets at Fix that socket.
Fix that socket.
Unable to Initialize Windows Sockets Interface Solutions at Microsoft.com: I think Microsoft has the tendency to move pages around where they can't be found, so if you get a broken link, just follow the instructions from Fix that socket.
In the future, go to support.microsoft.com and search for help over there. Google can't help nothing because it's too stupid to rank anything that cannot be or are not linked to very often, i.e. Windows problems and solutions.
However, there's a problem (of course). Microsoft is planning to remove support for Windows 98, which was where I had that problem. So I've copied all the instructions necessary to re-initialize the windows sockets at Fix that socket.
