I'm coming in late to this thread, but here's the HUGE reason companies are going to have for moving specific systems to 64bit - memory. Windows has been bottlenecked from a scalability perspective for awhile now with the way it addresses memory, making it rely on disk subsystems (which compared to processor power and RAM speeds, are ridiculously slow).
Check this URL out, then think about big database servers or other memory intensive apps running on 64bit vs 32bit.
>Adaware and Spybot report a lot of cookies. >MS's program didn't. On the other hand, the >AntiSpyware program found stuff the other two >didn't. Total "hits" weren't 2-3x, but I've >decided to keep AntiSpyware in addition to the >other two programs.
From what I've seen/heard of the MS offering, it does NOT detect/remove ID cookies, on purpose.
Actually, I'm somewhat surprised (well, not really, this IS/.) that nobody has pointed out this quote from the security bulletin.
"The product of such a rearchitecture effort would be sufficiently incompatible with Windows NT 4.0 that there would be no assurance that applications designed to run on Windows NT 4.0 would continue to operate on the patched system. "
It appears any "fix" for the problem on NT4 might actually be worse than the problem itself. Would you rather have a possibility open for a DoS attack on an NT4 box, or most RPC apps "broken" by a security hotfix?
I live in Canyon Gate @ Northpointe, another Clearworks neighborhood just outside Houston, TX. I believe this was the first neighborhood Clearworks wired in 1999. We do have fiber running to every home, amusingly they run seperate copper and coax runs for phone and cable TV - even if you get all service from Clearworks (as I do) the cable and phone don't use the fiber - it's for ethernet only (and "only" at 10mbit).
Service? Well, there have been two outages since I've had them (nearly a year) and both were repaired within 24 (one was a fiber cut, other a failed switch).
Speed? Easily comparable (and usually better than) cablemodem or DSL service. I have seen as high as 6mbit/sec substained (over the course of a 100meg download), but 1.5-2.0mbit/sec is more the norm.
I had a filling come out awhile back, and when the dentist went to replace it, he used a laser to clean up the "cavity" (more of a hole @ that point) prior to putting the new filling in place.
Granted, it wasn't true "drilling", but there was no novacain, no NO (laughing gas - I get nauseated with the stuff, so always needed novacain before), and most importantly - no pain...
I was "in the chair" for like 10 minutes tops - quickest dentist trip I've ever had!
Haven't had a true "cavity" needing drilling/filling in at least a decade, and hope I never do, but IF I do, hope they can use laser on it.;-)
As the other poster mentioned, you can use a different port for your webserver, but than anyone who hits your site has to KNOW that specific port and put it in their browser whenever they come to your site.
A better (but subscription) solution is to use a dynamic DNS service that can redirect incoming port 80 to a specific port on your dynamic IP address. Take a look at:
http://www.tzo.com/MainPageServices/ProductSumma ri es/3SummaryStandardTzoRelay.html
for details. Very slick, IMHO.....
BTW, just make sure to secure your server, and make sure to keep up on patches for your OS - part of the reasoning behind the ISPs blocking port 80 are that clueless users run WWW servers and get their machines hacked (ie, code red, nimda, etc).
Slashdot Mirror
I'm coming in late to this thread, but here's the HUGE reason companies are going to have for moving specific systems to 64bit - memory. Windows has been bottlenecked from a scalability perspective for awhile now with the way it addresses memory, making it rely on disk subsystems (which compared to processor power and RAM speeds, are ridiculously slow).
; en-us;294418
Check this URL out, then think about big database servers or other memory intensive apps running on 64bit vs 32bit.
http://support.microsoft.com/default.aspx?scid=kb
(BTW - who knew "hyperspace" as an "Architectural component" on Windows??!)
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item =6372056442#ebayphotohosting
>Adaware and Spybot report a lot of cookies.
>MS's program didn't. On the other hand, the
>AntiSpyware program found stuff the other two
>didn't. Total "hits" weren't 2-3x, but I've
>decided to keep AntiSpyware in addition to the
>other two programs.
From what I've seen/heard of the MS offering, it does NOT detect/remove ID cookies, on purpose.
...is that it was a move to generate the worlds most ironic headline :
"Microsoft acquires Giant Company"
Actually, I'm somewhat surprised (well, not really, this IS /.) that nobody has pointed out this quote from the security bulletin.
"The product of such a rearchitecture effort would be sufficiently incompatible with Windows NT 4.0 that there would be no assurance that applications designed to run on Windows NT 4.0 would continue to operate on the patched system. "
It appears any "fix" for the problem on NT4 might actually be worse than the problem itself. Would you rather have a possibility open for a DoS attack on an NT4 box, or most RPC apps "broken" by a security hotfix?
I live in Canyon Gate @ Northpointe, another Clearworks neighborhood just outside Houston, TX. I believe this was the first neighborhood Clearworks wired in 1999. We do have fiber running to every home, amusingly they run seperate copper and coax runs for phone and cable TV - even if you get all service from Clearworks (as I do) the cable and phone don't use the fiber - it's for ethernet only (and "only" at 10mbit).
;-)
Service? Well, there have been two outages since I've had them (nearly a year) and both were repaired within 24 (one was a fiber cut, other a failed switch).
Speed? Easily comparable (and usually better than) cablemodem or DSL service. I have seen as high as 6mbit/sec substained (over the course of a 100meg download), but 1.5-2.0mbit/sec is more the norm.
I've got no complaints.
Actually, yes, they have :
/ te chnet/security/news/IARWSV.asp
http://www.microsoft.com/technet/treeview/?url=
This is one click from www.microsoft.com/security (at the top of the page, no less)
I had a filling come out awhile back, and when the dentist went to replace it, he used a laser to clean up the "cavity" (more of a hole @ that point) prior to putting the new filling in place.
;-)
Granted, it wasn't true "drilling", but there was no novacain, no NO (laughing gas - I get nauseated with the stuff, so always needed novacain before), and most importantly - no pain...
I was "in the chair" for like 10 minutes tops - quickest dentist trip I've ever had!
Haven't had a true "cavity" needing drilling/filling in at least a decade, and hope I never do, but IF I do, hope they can use laser on it.
As the other poster mentioned, you can use a different port for your webserver, but than anyone who hits your site has to KNOW that specific port and put it in their browser whenever they come to your site.
:
a ri es/3SummaryStandardTzoRelay.html
A better (but subscription) solution is to use a dynamic DNS service that can redirect incoming port 80 to a specific port on your dynamic IP address. Take a look at
http://www.tzo.com/MainPageServices/ProductSumm
for details. Very slick, IMHO.....
BTW, just make sure to secure your server, and make sure to keep up on patches for your OS - part of the reasoning behind the ISPs blocking port 80 are that clueless users run WWW servers and get their machines hacked (ie, code red, nimda, etc).