"Granted, though even when it is ON, it STILL allows all NETBIOS and SMB traffic through to/from anywhere in the world."
Wrong. By default it only allows computers on the local subnet to connect to File and Pring Sharing ports.
Trust me, I've already deployed SP2 to our 70+ workstation network and am using Active Directory to granularly define and lock down the firewall settings. I can specify settings by Organizational Unit (Groups of computers/users), specifying subnets or hosts that can connect to specific ports (Good for administrative purposes), with different settings for on the network or off the network. Basically, I can lock down everything and only open up the specific access that is needed. I can even define what programs can open up ports and restrict the users' ability to open up more ports. It doesn't even matter if they're a local admin on their workstation. The option to manually add more ports is locked to them and other programs are unable to open up ports. The ability to do all this from my admin console for no additional cost is a beautiful thing.
Also, many people are concerned that it doesn't monitor outbound connections. I attended a Microsoft security conference and the keynote speaker said that they did this on purpose and it was a tough decision. Their reasoning is that most people don't know what to allow and what not to allow. The hassle to the end users and help desks isn't worth it. Personally, I agree completely. The added benefit doesn't outweight the many drawbacks. However, maybe a better decision would have been to include the functionality, but have it off by default. That would have given power users and admins the ability to turn it on if they choose to.
What nazis modded your post down as Troll and Flamebait? It's not like you said you didn't like the movie because Moore's fat or something like that. I guess some people with mod points really like to shoot down opinions they don't agree with.
As a former Windows NT4 Server, Workstation, and 2k pro support rep and current admin, I can tell you that this behavior is not normal. If it's rebooting like someone hit the reset button, you have a hardware problem. Usually, it's the motherboard or PSU. Other hardware problems will cause blue screens. If you're getting a blue screen for a few seconds followed by a reboot, you need to disable the auto reboot option in the System applet (Control panel). Then troubleshoot the blue screen now that you can actually take the time to copy down the parameters. Usually, blue screens are caused by bad hardware, incorrect drivers, or software that needs to be updated. The amount of clues or direction the blue screen provides depends on the problem. Some errors like storage system errors give very specific codes. Buggy drivers on the other hand can give nearly useless parameters. Just google the main error and hex code. If there's too many different types of articles and newsgroup posts going in different directions, try including some of the hex parameters (There's four of them) to help narrow the search down.
This is just another example of the US government trying to take away its citizens rights. No doubt, George Bush is doing this in the name of "Fighting terrorism" and only cares to get rich through secret connections and deals.
"There are many tactics which are perfectly acceptable when you own 5% of the market and which are not only unacceptable but illegal when you own 95% of the market."
This is the same mentality that terrorists have when they target civilians (The definition of terrorism).
What they should have done was hit the power button on the computer so no more write operations could be performed. They could then take the drive and give you another one in exchange. Next, configure the jumper setting to make it read only (if possible) and hook it up as a secondary drive to another system. Boot up and make an image of the drive using Winhex. If there was no jumper setting for read only, use X-Ways Replica. Either method will make a file containing an exact raw image of the drive without changing a single bit of data. Use the image for forensics and keep the original for evidence.
Sony's development platform was not a standard prior to the release of the Playstation 2. Microsoft's DirectX already was a standard and most of the PC game developers out there were already skilled at using it. That's the point of the statement that you criticized, so don't start with the spin.
Considering that the majority of the games released on the PC market focus on DirectX, I'd have to say that it's the standard. Just because it isn't designed by some open consortium, doesn't mean something with a dominant share can't be considered the standard.
Exactly. That article was published in late Nov. 2002. The prediction is that Tablet PCs would be the most popular personal computer within five years. That means by late Nov. 2007. Umm, we're not even at the half way mark on that five year timeframe in his prediction.
I've had plenty of serious buyers ask me about them. It's a possibility if they only look at percentage of new computers being sold, but I don't think they'll catch on that fast. If I had to place a bet, I'd bet against his prediction. The point though is that it's too early to tell.
If you read the page, you'd see that this has to do with the ACLs on the downloaded file, not compression. And the fact that "Not everybody runs Windows" isn't a good excuse. If you read the page, you'd also see in the first comment that someone else bumped up the severity rating to Major. To me, it was just an annoyance bcause I had to manually reset the permissions wherever I downloaded files to. I do agree with that person though that it's important from a security perspective. When the hell did I ask for a pat on the back? I saw a series of posts claiming that Mozilla fixes stuff fast, but my own experience is the complete opposite.
The bug I submitted was marked as "Major" due to the security implications. I submitted it in early Nov. of last year. After 24 days of finger pointing and name calling towards Redmond, someone finally admitted it's a bug. The problem still isn't fixed. It gets the occasional comment and that's about it.
I'm sorry, but if it takes 24 days to get past the name calling when confronted with a security flaw deemed major, OSS doesn't stand a chance.
We only replaced it on the one side for now. Limited budget and the completely worn out struts and control arms were more urgent. Yes, we did use a cotter pin.;)
"Imagine a car manufacturer produced a car where the wheels were held on by one big nut."
That's not at all hard to imagine. My girlfriend and I replaced a wheel hub bearing on one of her wheels. One big nut is what holds the wheel hub onto the axle shaft. The tire is then attached to the hub with five smaller nuts.
Well the guy sure did add a lot of fiction to the story to make it more interesting. And why wouldn't he add more details to get another story published?
While reading this, I couldn't help but think that someone made this whole story up. The best example is the static electricity. I know it's best practice to wear a strap, but I've found that touching the power supply before touching anything else is enough to prevent mishaps. Before I was doing that I never had any zapped parts either. I'm not saying static electricty won't kill a part, but I am saying that in my own personal experience, it's not so common that it should happen to this guy along with all these other mistakes in one building experience.
To top it off, he claims that after going from a VIA KT400 chipset (The Soyo mobo) to a Nvidia chipset (The Asus mobo), everything booted up fine. Bullshit.
Slashdot Mirror
Nope. I'm running the RTM.
-Lucas
Wrong. By default it only allows computers on the local subnet to connect to File and Pring Sharing ports.
Trust me, I've already deployed SP2 to our 70+ workstation network and am using Active Directory to granularly define and lock down the firewall settings. I can specify settings by Organizational Unit (Groups of computers/users), specifying subnets or hosts that can connect to specific ports (Good for administrative purposes), with different settings for on the network or off the network. Basically, I can lock down everything and only open up the specific access that is needed. I can even define what programs can open up ports and restrict the users' ability to open up more ports. It doesn't even matter if they're a local admin on their workstation. The option to manually add more ports is locked to them and other programs are unable to open up ports. The ability to do all this from my admin console for no additional cost is a beautiful thing.
Also, many people are concerned that it doesn't monitor outbound connections. I attended a Microsoft security conference and the keynote speaker said that they did this on purpose and it was a tough decision. Their reasoning is that most people don't know what to allow and what not to allow. The hassle to the end users and help desks isn't worth it. Personally, I agree completely. The added benefit doesn't outweight the many drawbacks. However, maybe a better decision would have been to include the functionality, but have it off by default. That would have given power users and admins the ability to turn it on if they choose to.
-Lucas
-Lucas
-Lucas
-Lucas
I know you're all with me on this one.
-Lucas
This is the same mentality that terrorists have when they target civilians (The definition of terrorism).
-Lucas
-Lucas
-Lucas
-Lucas
LOL, thanks. I'm an idiot. I didn't even read that last line.
-Lucas
-Lucas
I've had plenty of serious buyers ask me about them. It's a possibility if they only look at percentage of new computers being sold, but I don't think they'll catch on that fast. If I had to place a bet, I'd bet against his prediction. The point though is that it's too early to tell.
-Lucas
-Lucas
-Lucas
I'm sorry, but if it takes 24 days to get past the name calling when confronted with a security flaw deemed major, OSS doesn't stand a chance.
-Lucas
One thing that interests me is that it says my company's web server is Apache. We switched to IIS6 like two months ago.
-Lucas
We only replaced it on the one side for now. Limited budget and the completely worn out struts and control arms were more urgent. Yes, we did use a cotter pin. ;)
-Lucas
-Lucas
That's not at all hard to imagine. My girlfriend and I replaced a wheel hub bearing on one of her wheels. One big nut is what holds the wheel hub onto the axle shaft. The tire is then attached to the hub with five smaller nuts.
-Lucas
-Lucas
To top it off, he claims that after going from a VIA KT400 chipset (The Soyo mobo) to a Nvidia chipset (The Asus mobo), everything booted up fine. Bullshit.
-Lucas
meant to say less than. Anyway...
-Lucas