I'm not a U.S. citizen (I'm an Australian), but I totally agree with your sentiments - if the U.S. are bailing out corporations with U.S. taxpayers money, then they should at the very least be employing U.S. citizens!
Oh, good plan old boy. Let's break everything even worse than it might already be by rolling back a widely adopted major release. That's a step in the right direction.
You're reading slashdot and you're complaining that I can't think bigger than American Idol? Wow!
I don't suppose you would care to explain? In small words please, my tiny brain can't understand, but as your brain is the size of a planet then I'm happy to have it explained to me. I'm genuinely curious whether you can.
It appears that they are getting a "Service unavailable" prompt. Could it really be that they are running their blogs on an IIS server that is running Windows 7? Shock horror, it appears that someone has elevated privileges using vbscript to bypass UAC and has changed the IIS app pool to run under a guest account!
OS+Libraries tells me that you didn't really understand what I wrote above. Libraries are loaded in user space, not kernel space.
What the kernel does with the lower 2GB, I don't precisely know, nor do I really care. But it sounds like you don't believe me, so perhaps I should quote Microsoft:
On Windows, by default, the lower 2 GB are reserved for user-mode programs and the upper 2 GB are reserved for kernel-mode programs. You can use this parameter to test the performance of your driver when it is running in a 1 GB kernel.
Windows by default (on 32-bit architectures) reserves 2GB of the virtual address space for the operating system and 2GB for user processes. This can be changed to 1GB of virtual address space for the OS and 3GB for user spaces. I have a post here that explains things better.
Just be careful when looking at the columns that refer to memory. Some of them are a bit misleading. I detail a few of them in an article I wrote a while ago (it was mainly for my own reference).
Oh they are trying. Trying to bugger up systems! Surely if they validated the firmware update before releasing it the problems would have been caught in the QA process? I'd love to have been a fly on the wall in the QA meeting after the latest fix was released.
They are talking about the Ancilliary Function Driver that is used for Windows sockets. By setting HKLM\CurrentControlSet\Services\AFD\DefaultSendWindow to 0x7800 allows them to set this to 480KB of data before flow control kicks in. Great if your hardware can handle it, not so great if you have crappy hardware. I believe that if you have > 32MB of RAM that the default is 8KB of data gets received before flow control throttles the connection.
Probably will work OK if your NIC can handle it and you have enough memory. And of course if you have high enough bandwidth:-)
Slashdot Mirror
I'm not a U.S. citizen (I'm an Australian), but I totally agree with your sentiments - if the U.S. are bailing out corporations with U.S. taxpayers money, then they should at the very least be employing U.S. citizens!
Oh, good plan old boy. Let's break everything even worse than it might already be by rolling back a widely adopted major release. That's a step in the right direction.
You're reading slashdot and you're complaining that I can't think bigger than American Idol? Wow!
I don't suppose you would care to explain? In small words please, my tiny brain can't understand, but as your brain is the size of a planet then I'm happy to have it explained to me. I'm genuinely curious whether you can.
Apparently Raymond Chen posted a response at http://blogs.msdn.com/oldnewthing/archive/2009/01/21/9353310.aspx
It appears that they are getting a "Service unavailable" prompt. Could it really be that they are running their blogs on an IIS server that is running Windows 7? Shock horror, it appears that someone has elevated privileges using vbscript to bypass UAC and has changed the IIS app pool to run under a guest account!
Speaking of symbols, it appears that you're treating this post like one. What the hell are you on about?
Doh! Sorry about that. Don't know how I missed the scheme name in the URI.
Wait till you see what Songsmith did to David Lee Roth!
OS+Libraries tells me that you didn't really understand what I wrote above. Libraries are loaded in user space, not kernel space.
What the kernel does with the lower 2GB, I don't precisely know, nor do I really care. But it sounds like you don't believe me, so perhaps I should quote Microsoft:
Wrong on so many levels.
Windows by default (on 32-bit architectures) reserves 2GB of the virtual address space for the operating system and 2GB for user processes. This can be changed to 1GB of virtual address space for the OS and 3GB for user spaces. I have a post here that explains things better.
Someone modded this as "Interesting"?
I didn't know that Dvorak posted on slashdot.
Did you do that before or after taking out the power cable to shake out the loose electrons?
Just be careful when looking at the columns that refer to memory. Some of them are a bit misleading. I detail a few of them in an article I wrote a while ago (it was mainly for my own reference).
Oh you laugh now, but it appears that John C. Dvorak got caught on this one. The asshat.
On Not Getting It
He didn't, he read it in a book... oh wait.
On that note, I don't believe that he wrote that comment because I didn't hear it myself.
Uh? You write that "I have no idea why Windows puts its backing store in the filesystem." Where else would it put the backing store?
And yes, Linux uses a filesystem to store the pagefile.
Oh they are trying. Trying to bugger up systems! Surely if they validated the firmware update before releasing it the problems would have been caught in the QA process? I'd love to have been a fly on the wall in the QA meeting after the latest fix was released.
That wouldn't be One.Tel by any chance would it? If so, then it figures.
Before or after he reads the comments that weren't correctly de-escaped?
For a security authority, you'd think SANS would know they escape their quotes and handle this when it outputs the comment to readers.
I thought that IEEE 802.11n used OFDM to help prevent this sort of thing from being a problem?
They are talking about the Ancilliary Function Driver that is used for Windows sockets. By setting HKLM\CurrentControlSet\Services\AFD\DefaultSendWindow to 0x7800 allows them to set this to 480KB of data before flow control kicks in. Great if your hardware can handle it, not so great if you have crappy hardware. I believe that if you have > 32MB of RAM that the default is 8KB of data gets received before flow control throttles the connection.
Probably will work OK if your NIC can handle it and you have enough memory. And of course if you have high enough bandwidth :-)
lol!
Fridge Skynet is evil. It might well happen.
Yeah, it was a sad day when their article was deleted from Wikipedia.
Nokia had it for ages? Heck the CueCat had it some time ago. Seriously, big deal.
I bow to you, oh evil one.