A
Andy
I get a very good to excellent local area connection but I can't get on the internet.
I am looking for things to check.
Thanks.
I am looking for things to check.
Thanks.
A
Andy
I have xp sp3 and I found my winsock.dll is dated 2004.
Have that not been updated ?
Thanks.
P
Paul
Andy said:
You do realize, that there are still files with the original
release date of the OS. Not every file needs to be updated
once a month, and downloaded again. Some of those files are
"trivial".
Same goes for drivers. Once hardware becomes "old", the manufacturer
doesn't really pay attention any more. They release a new driver
(maybe a 100MB download), but the major changes are for their
spiffy new $500.00 video card. Not that old $39.95 card you
bought years ago. And thus, there's no point continuing to update
the video driver. You're basically getting the same code if you
do decide to download it. Not every problem requires a download
to resolve it!
Getting on the Internet requires:
1) A reasonable value for the IP address. If the IP address
is the APIPA one, that means you never made it to a DHCP
server (like, the facilities provided by your home router).
2) Each symbolic address ("www.foxnews.com") needs to be
translated into an IP address ("203.102.98.16"). The
service there is DNS, and the setup of that is usually
done automatically when your computer talks to the router.
There is a networking dialog on your computer, that has two
sections, and by default they're set to automatic via DHCP
(i.e. get the info from the router).
When you do it this way, your router provides the details.
And in turn, the router does the same sort of query, against
the facilities at your ISP.
http://i.technet.microsoft.com/dynimg/IC244441.gif
You can manually intervene. If you did a reasonable job
debugging your network setup, and DNS was broken beyond
repair for some reason, Google offers a DNS server. You
could set the bottom part of the dialog to manual mode,
and assign an address from this article.
http://en.wikipedia.org/wiki/Google_Public_DNS
A "bad" IP address assignment (top part of dialog) is listed here.
You can fix this by assign an address manually, but if it was
really this broken, you wouldn't be able to log into the web
interface on your router and check the setup.
http://en.wikipedia.org/wiki/Apipa
169.254.x.x
You can check for that from the command prompt:
ipconfig
There's a whole list of stuff I could write (I've done
it before), but I'm not typing in all that stuff again
There's got to be a tutorial out there somewhere, with the
basics...
Paul
N
Nil
A
Andy
You do realize, that there are still files with the original
release date of the OS. Not every file needs to be updated
once a month, and downloaded again. Some of those files are
"trivial".
Same goes for drivers. Once hardware becomes "old", the manufacturer
doesn't really pay attention any more. They release a new driver
(maybe a 100MB download), but the major changes are for their
spiffy new $500.00 video card. Not that old $39.95 card you
bought years ago. And thus, there's no point continuing to update
the video driver. You're basically getting the same code if you
do decide to download it. Not every problem requires a download
to resolve it!
Getting on the Internet requires:
1) A reasonable value for the IP address. If the IP address
is the APIPA one, that means you never made it to a DHCP
server (like, the facilities provided by your home router).
2) Each symbolic address ("www.foxnews.com") needs to be
translated into an IP address ("203.102.98.16"). The
service there is DNS, and the setup of that is usually
done automatically when your computer talks to the router.
There is a networking dialog on your computer, that has two
sections, and by default they're set to automatic via DHCP
(i.e. get the info from the router).
When you do it this way, your router provides the details.
And in turn, the router does the same sort of query, against
the facilities at your ISP.
http://i.technet.microsoft.com/dynimg/IC244441.gif
You can manually intervene. If you did a reasonable job
debugging your network setup, and DNS was broken beyond
repair for some reason, Google offers a DNS server. You
could set the bottom part of the dialog to manual mode,
and assign an address from this article.
http://en.wikipedia.org/wiki/Google_Public_DNS
A "bad" IP address assignment (top part of dialog) is listed here.
You can fix this by assign an address manually, but if it was
really this broken, you wouldn't be able to log into the web
interface on your router and check the setup.
http://en.wikipedia.org/wiki/Apipa
169.254.x.x
You can check for that from the command prompt:
ipconfig
There's a whole list of stuff I could write (I've done
it before), but I'm not typing in all that stuff again
There's got to be a tutorial out there somewhere, with the
basics...
Paul
So are you saying that winsock.dll isn't used in Win7 and beyond since they have much higher hardware requirements. ?
New hardware can't be added to an older system ?
Windows XP 64-Bit Edition will currently support up to 16 GB of RAM, with the potential to support up to 16 TB of virtual memory as hardware capabilities and memory sizes grow. " (http://www.microsoft.com/technet/pro...e/xp64ovw.mspx)
http://en.wikipedia.org/wiki/Usage_share_of_operating_systems
Net Market Share[14][15] December 2012
Microsoft Windows
8 7 Vista XP
1.45% 40.68% 4.82% 34.47%
J
J. P. Gilliver (John)
In message <[email protected]>, Andy
Are those figures available subdivided into 32- and 64-bit versions?
(_Is_ there a 32-bit 8?)
Are those figures available subdivided into 32- and 64-bit versions?
(_Is_ there a 32-bit 8?)
P
Paul
Andy said:
There's plenty of info out there.
http://en.wikipedia.org/wiki/Winsock
"Specifications
* Version 1.0 (June 1992) defined the basic operation of Winsock.
* Version 1.1 (January 1993) made many minor corrections and clarifications
* Winsock 2 was a backwards-compatible extension of Winsock 1.1.
* Versions 2.0.x (May 1994 onwards) had internal draft status
* Version 2.1.0 (January 1996) was the first public release of the Winsock 2 specification.
* Version 2.2.0 (May 1996) included many minor corrections, clarifications
* Version 2.2.1 (May 1997) and Version 2.2.2 (August 1997) introduced minor
functionality enhancements.
* The IPv6 Technical Preview for Windows 2000 (December 2000) saw the first
implementation of RFC 2553 (March 1999, later obsoleted by RFC 3493),
a protocol-independent API for name resolution, which would become part
of Winsock in Windows XP.
Updates in Windows 8
Windows 8 includes the "RIO" (Registered IO) extensions for Winsock.
"
You can see, there is a 13 year gap in design activity, between around the end of
2000 and now. So there could be an old file, they didn't need to change.
Paul
P
Paul
David said:
I downloaded Win8/32 and added it to my ISO9660 collection,
so yes, it exists
And the reason I wanted a copy, is very occasionally, a situation
arises where you need the 32 bit version of a file. The last time
it was needed, was to make the microsoftstore USB key preparation
program, work properly. So while I have no intention of installing
the 32 bit version of Windows 8, I do want access to the file set.
Just in case another obscure situation arises.
Paul
B
BillW50
In Paul typed:
Why are you into 64 bit Paul? If you like 64 bit, why are you not going
after 128 bit? Yes 128 bit Windows does exists, but I am not sure who
you have to know to get a copy.
Why are you into 64 bit Paul? If you like 64 bit, why are you not going
after 128 bit? Yes 128 bit Windows does exists, but I am not sure who
you have to know to get a copy.
A
Andy
I wasn't complaining about the file.
With winsock being pretty important...but there may be other dependent dlls that have been updated.
I have been having a lot of problems with my cable modem/router.
One of many things to check are winsock.dll that may not be updated or got corrupted.
I did a winsock reset and those support tools are great.
It may also be the cable company.
The router puts off a lot of heat and it has no fan.
I used a 12 V power supply fan to make a custom fan.
So far so good.
J
J. P. Gilliver (John)
In message <[email protected]>, Andy
Why a 12V fan - is it running from the router's own supply? (Is that
12V?)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
"What happens if I press this button?" "I wouldn't ..." (pinggg!) "Oh!" "What
happened?" "A sign lit up, saying `please do not press this button
again'!"(s1f2)
Why a 12V fan - is it running from the router's own supply? (Is that
12V?)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
"What happens if I press this button?" "I wouldn't ..." (pinggg!) "Oh!" "What
happened?" "A sign lit up, saying `please do not press this button
again'!"(s1f2)
A
Andy
The fan is running off a transformer. 120 VAC -> 12 V DC.
I made a stand for it and mounted it.
I save transformers from things I salvage.
A lot of times I will use it to power some battery powered devices if portability isn't needed.
D
dadiOH
David said:
LOL
--
dadiOH
____________________________
Winters getting colder? Tired of the rat race?
Taxes out of hand? Maybe just ready for a change?
Check it out... http://www.floridaloghouse.net
P
Paul
David said:
You're assuming everyone who makes consumer electronics, is honest.
They're not honest.
Example:
http://www.legitreviews.com/article/785/1/
"The original version 1.0 Linksys SD2008 switches came with a cooling
fan inside, but was removed on later revisions due to the noise level
of the fan."
Clever. Oh so friendly.
I'm fully in favor of consumers taking matters into their own hands.
If it means cutting a hole in the chassis, and fixing nonsense like
that, I'm all for it.
I'm not in favor, of everything you buy, being a "Dremel victim".
But if the consensus is, something has been "designed to screw
consumers", then by all means, fix it. Have at it.
Paul
A
Andy
Paul,
You are right.
I don't think everybody is dishonest.
For 20+ years I repaired laboratory instruments as part of my job duties as a chemical lab technician.
Electronics is a hobby I enjoy as well.
Thanks for not being a know-it-all like some others.
Andy
J
J. P. Gilliver (John)
By the way, you emailed this to me as well. I understand Google have
recently made it rather too east to accidentally tick a "Cc" box when
posting.
(It's also making you do double line spacing.)
Ah, I see. (I'd been concerned that running it from the router's own
supply would _add_ to the heat problem [like those laptop fans that run
from a USB].)
You mean power supplies (a transformer only converts AC to AC).
Good policy.
recently made it rather too east to accidentally tick a "Cc" box when
posting.
(It's also making you do double line spacing.)
Andy said:
Ah, I see. (I'd been concerned that running it from the router's own
supply would _add_ to the heat problem [like those laptop fans that run
from a USB].)
You mean power supplies (a transformer only converts AC to AC).
Good policy.
A
Andy
Sorry about sending it accidentally.
I am still not used to the new google.
Andy
J
J. P. Gilliver (John)
In message <[email protected]>, David H.
All electronics generate heat. Even if VHF-RF devices are particularly
lossy (which I question as a general principle), the amount of it in a
router is minimal - milliwatts - so not that relevant here. (And it's
well above VHF, too: 2.4 GHz mostly, some 5 GHz in some recent devices.)
How very trusting! (Plus, also, even if it happens to be true in a
particular case, users have a habit of using things in ways they weren't
designed: in hotter than specified temperatures, on their side, with
inadequate ventilation [such as resting on a carpet], ...) I've
certainly encountered equipment running hot enough that I'd be unsure of
its long-term reliability.
We're in agreement that those are good ...
While I agree that I wouldn't immediately blame a piece of kit that had
apparently been running hot for a while _before_ the problem occurred, I
wouldn't rule it out either.
It _could_ if all of those communications are going via the device that
is running hot.
tend to agree with you that the hot device is probably not the cause, I
would not make such absolute statements - and I'd try to find a kinder
way to say so as well.
Lipman said:
All electronics generate heat. Even if VHF-RF devices are particularly
lossy (which I question as a general principle), the amount of it in a
router is minimal - milliwatts - so not that relevant here. (And it's
well above VHF, too: 2.4 GHz mostly, some 5 GHz in some recent devices.)
How very trusting! (Plus, also, even if it happens to be true in a
particular case, users have a habit of using things in ways they weren't
designed: in hotter than specified temperatures, on their side, with
inadequate ventilation [such as resting on a carpet], ...) I've
certainly encountered equipment running hot enough that I'd be unsure of
its long-term reliability.
We're in agreement that those are good ...
While I agree that I wouldn't immediately blame a piece of kit that had
apparently been running hot for a while _before_ the problem occurred, I
wouldn't rule it out either.
It _could_ if all of those communications are going via the device that
is running hot.
You are smug. (I realise I am being a bit, too, in response.) While I
tend to agree with you that the hot device is probably not the cause, I
would not make such absolute statements - and I'd try to find a kinder
way to say so as well.
A
Andy
It's been 2 days that the fan has been cooling off the router.
I have not had a single loss of internet connectivity.
It's not enuf to prove it was heat related.
But I think it's pretty hard to prove that the cable company is at fault.
Andy