This security update resolves two privately reported vulnerabilities and one publicly disclosed vulnerability in Microsoft Server Message Block (SMB) Protocol. The vulnerabilities could allow remote code execution on affected systems. An attacker who successfully exploited these vulnerabilities could install programs; view, change, or delete data; or create new accounts with full user rights. Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.

This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003, and Moderate for all supported editions of Windows Vista, and Windows Server 2008.

ScriptCopy.com web directory allows you to find scripts on the net that are similar or mimic functionalities of popular websites.

Usually the lounge chair is the chair that is long enough to support the legs. Usually they are pretty comfortable have a cool but similar design and costs a fortune. Although there are some exclusions from this rule. The design could be unique and even weird.

Not all API providers know how to make developers happy. In fact, although there are now over 1,100 web service APIs available, many of those API providers fail to really understand the needs and motivations of their (potential) developer community. For evidence of how developers can react to both well-run and badly-run API programs, look no further than a very insightful blog post from mashup developer Alexander Lucas on Making Your Webservice More Developer Friendly (Alex is the creator of Migratr a useful desktop mashup that uses APIs from 11 different web services in order to let you migrate photos between different online photo services).

In his detailed post he gives what’s clearly real-world, from-the-trenches feedback (and wit) from an experienced mashup developer on what works and what doesn’t..

    But it takes more than just publishing an API. You have to make your developers WANT to write stuff for your service. Make it easy and enjoyable for them, and remove as many roadblocks and speedbumps as you possibly can so that they can complete their brilliant idea before throwing up their hands in frustration, or slowly, quietly losing motivation amidst a sea of vicious bugs, counter-intuitive behavior and documentation that either looks like it was written by Hemingway or run through babelfish.

He then goes on to provide an on-the-money “checklist for being developer-friendly”:

SEAGATE'S FLAGSHIP desktop Barracuda 7200.11 drives, in particular the 1TB (ST31000340AS) units, are failing at an alarming rate and prompting outrage from their faithful customers.

A new self-bricking feature apparently resides in faulty firmware microcode which will rear its ugly head sometime at boot detection. Essentially the drive will be working as normal for a while, then - out of the blue - it'll brick itself to death. The next time you reboot your computer the drive will simply lock itself up as a failsafe and won't be detected by the BIOS. In other words, there's power, spin-up, but no detection to enable booting.
...
According to data recovery experts Seagate has diagnosed the problem and issued a new firmware to address it. However, drives that have already been affected can't have the firmware applied to them due to their locked-down status.

The plan: Ring in the new year by switching over to Linux for a week, documenting each day of the transition.

My impressions of the Linux operating system are coloured by memories of the first time my computer-whiz friend unveiled his sort-of-new copy of Redhat Linux to me. “Check this out!” he said. “This OS doesn’t suck like everything Microsoft makes!” It came in an over-sized jewel case with 4 CDs, handed down second-hand from another computer-whiz friend who recommended we try it.

Upon installing it we were greeted with an unceremonious command console that might as well have been written in the ancient tongue of the long-dead tribe of Gnitth Shhta Star-God worshippers. We had no idea what to do, and it was exciting. Linux had that combination of sparseness, functionality and seriousness that gave it the feel of being a real operating system, unlike that flighty Windows 95. In short, Linux seemed cool.

But that was my first and last encounter with Linux. In the ten or fifteen years since that first Linux install other operating systems have shown up, like XP and OSX, that have mostly pulled my attention away from Linux. Now my impression of Linux is bundled up with old memories of screwing around with the config.sys file on my DOS computer in order to allocate enough virtual memory to get Ultima running. In short, Linux to me has always been synonymous with “command console,” and although command consoles may work well, they definitely aren’t easy to use.

All these year later, now that those newer and simpler operating systems are available, I find myself wondering: why use Linux at all? Why go through all the trouble of installing an operating system that’s difficult to use, when almost everyone has a perfectly fine operating system already installed on their PC? I’ve never seen the reason to make the switch.

But I’ve also heard all the reports about how Linux is different nowadays. “It’s easy to use!” they say. “It’s even easy to install, and it’s way more stable than Windows!” they insist. “It’s not like the old days; Linux has changed, man! Just give a try, all the cool and smart and handsome people are using it!” Linux still has that indie cred that I experienced all those years ago that makes it seem just a little bit more elite than its competitors, and power-nerds everywhere seem to be cajoling me into trying it.

Lucky for them I have an incredibly weak will. So I’ve decided to give in to peer pressure, light me up some Linux, and trip my way through the alternative operating system carnival in the sky.