I really love the way Google changes there Homepage according to events and seasons.
Check this out "Romance not Found"
Check out the Slide-show I mage for the Year 2006.
Enjoy...
Things that are happening in this tech world...
I really love the way Google changes there Homepage according to events and seasons.
Check this out "Romance not Found"
Check out the Slide-show I mage for the Year 2006.
Enjoy...
You should be careful where you hack. Unfortunately these two made a big mistake trying to hack in to 911. The teenager might face a 18 year prison sentence.
PS: Why in the world do you want to hack into the 911 Emergency Response system, lives could have been lost if the system went totally down.
Seems like this is the 2nd time of such an alert. A Trojan that masks itself as a Skype user and steals personal information from other Skype user.
After commenting at the web site about the Immediate Shutdown of Autopatcher. I tried to contact Microsoft regarding this issue. Below is the exact letter I got. Its as follows:
Thank you for contacting us about AutoPatcher.
I would like provide you with more information on our position.
It is our policy that the distribution of supplemental code such as hotfixes, security updates, and service packs is discouraged. This policy is in place due to concern for the safety and security of our customers, as we can only guarantee the download’s contents when it comes from a Microsoft web site. Distribution of these materials without permission is also an infringement of our copyright.
We try and contact anyone who is in violation of our policy as soon as we can, once we are aware of what they are doing. AutoPatcher is not the only company we have contacted.
We recommend that our customers sign up for Microsoft Update (MU) and enable Automatic Update functionality to receive all updates directly from us. In addition, we have enterprise services such as Windows Server Updates Services (WSUS) that we recommend our enterprise customers to use.
We provide this guidance as it is common to see email scams encouraging people to download our latest patches, but the URL takes them to sites where they are actually exposed to malware. In order to ensure that customers are getting actual Microsoft updates and not malware, we recommend customers get their updates directly from us.
I hope this information has answered your query, but if you have any more questions please give us a call on 0870 60 10 100. The lines are open from 8am to 6pm, Monday to Friday, excluding public holidays. If you still have any more questions, please reply to this email.
Many thanks for contacting us.
Warm regards,
JACOB RAJ
Customer Service Professional
Microsoft Customer Services
Protect Your PC: Microsoft recommends that you protect your PC from Viruses and Security threats. Please visit our website http://www.microsoft.com/uk/security/protect/alert.mspx and follow the steps to stay secure.
First of all. The main reason Autopatcher must have been shutdown is because that they suspected them of spreading malicious coding (eg. Malware) in there distribution (This is Crap...). But initially saying that its was also because of copyright infringement saying that "Hey you can't distribute that patch without asking US."
Are the people people nuts? They should put up a poll in their M$ Technet Site and see what the public thinks about Autopatcher.
I for all Love Autopatcher. Its a time saver and is less complicated than a WSUS server that they ask me to try. What's the point of having SUS server for a PC that is totally offline? Like a Distributor PC (Totally remote and offline, except for a 56k Modem). They cannot be updating there Windows Updates from Scratch (Like takes about 8 Hours or more + Telephone Bills). Lame excuse by M$, more or less it seems that they are jealous that a 3rd Party is providing a free service that they didn't provide
Still Praying that Autopatcher will make a Victorious Comeback.
Good Luck..
On the 29th August, 2007, Antonis Kaladis informed that Microsoft have sent then an email to immediately take down their download page for Autopatcher.
Posted by Antonis Kaladis on August 29th, 2007 |
Today we received an e-mail from Microsoft, requesting the immediate take-down of the download page, which of course means that AutoPatcher is probably history. As much as we disagree, we can do very little, and although the download page is merely a collection of mirrors, we took the download page down.
We would like to thank you for your support. For the past 4 years, it has been a blast. Unfortunately, it seems like it's the end of AutoPatcher as we know it.
Comments are welcome...
Antonis Kaladis
----
Some people have been asking for the E-mail to be published. Heres a copy:
http://www.autopatcher.com/takedown-notice
Lyndon Brown (Blaze)
I was very disappointed to know that M$ after 4 years of their existences sent them a email to stop. Why all of a sudden? As a user of Autopatcher I can safely say there is not problems with Autopatcher whatsoever. Just Hoping that Autopatcher Team Can make a comeback.
Regards.
Julie Amero, 40, was convicted in January of causing a series of sex advertisements to pop up on a classroom computer, which were seen by pupils in October 2004. She faces up to 40 years in jail.
But the defence filed a motion for a retrial, and at a sentencing hearing on Wednesday Judge Hillary Strackbein granted the application.
The prosecution at the trial in Connecticut had alleged Amero must have clicked on porn websites for the pop-ups to begin appearing. But after the trial 28 computer science academics in the state sought to prove that the rapid-fire sequence could have appeared automatically.
Sympathetic campaigners argue such pop-ups are one of the scourges of the internet and say she is the victim of a witchhunt.
The computer was sent to a state laboratory after the trial, and Judge Strackbein said its report might contradict evidence presented by the state computer expert, a police detective. "The jury may have relied, at least in part, on that faulty information."
The prosecution did not oppose the defence motion for a retrial. Neither the prosecution nor the jury appear to have been fully aware of the extent to which computers can be infiltrated, especially old ones that do not have firewall protection.
Outside the court Amero said: "A great weight has been lifted off my back."
Her lawyer, William Dow, commended the prosecutors for acting responsibly. "The lesson from this is all of us are subject to the whims of these computers."
Pupils, some of them as young as 12, told police that the computer had been left on for several hours and they had seen men and women engaged in oral sex.
Guardian News & Media
As with most cool new techniques, there are a few catches. For starters, not every PC is capable of booting from a USB flash drive. For the most part, computers manufactured within the last two years are generally able to boot from a flash drive. Older systems may require a BIOS update, or might not be able to boot from a flash drive at all.
Another catch is that not every flash drive will get the job done. The primary factors that limit your use of a particular flash drive are capacity and speed. Technically, speed isn't really a limiting factor, but booting Windows will be painfully slow unless you use a flash drive that supports USB 2.0.
The flash drive's capacity is actually a limiting factor though. Surprisingly though, there are size limits on both the upper and lower end. Your flash drive can't be too large or too small. There isn't really a documented minimal size for a flash drive. You just need something large enough to hold Windows XP and a few applications. As you probably know, Windows XP normally consumes over a gigabyte of disk space. Later I will show you how to use a free utility to trim the excess fat off of Windows XP and make it a whole lot smaller. Even so, I still recommend that your flash drive be at least a minimum of 256 MB in size.
As I mentioned, there is a maximum size for the USB flash drive that you can use. Currently, USB flash drives exist in sizes of up to 4 GB, and 8 GB flash drives are expected to be available by the end of the year. As nice as it would be to have 8 GB to play with, the flash drive that you use for this project can be no larger than 2 GB. The reason for this is because you will have to format the flash drive using the FAT-16 file system, which has a 2 GB limit. Presently, you are stuck using FAT-16 because most computers will not recognize a flash drive as being bootable if the drive is formatted with anything other than FAT-16.
One of the requirements for creating our bootable USB flash drive is a Windows XP with Service Pack 2 installation CD. If your Windows XP installation CD doesn't already include Service Pack 2, then you will have to make a CD that includes Service Pack 2 through a technique called slipstreaming.
In addition to your Windows XP installation CD, there are a couple of other things that you are going to need. For starters, you will need the HP USB Disk Storage Format Tool. You can download this tool for free.
Another utility that you are going to need is Bart's Preinstalled Environment Bootable Live Windows CD / DVD, or BartPE for short. You can download this utility for free from the BartPE Web site.
In addition to the software requirements, you must verify that the PC that you will be using to create the Windows deployment has 1.5 GB of free hard disk space (minimum) and supports booting from a USB device. I also strongly recommend that the PC be running Windows XP Service Pack 2. Prior to Service Pack 2, Windows XP sometimes had trouble interacting with USB storage devices.
Formatting the flash driveNow that you have all of the prerequisites taken care of, it's time to actually start setting up our flash drive. The first step in doing so, as strange as it sounds, is to format the flash drive. Windows will actually let you format a flash drive in the same way that you format a floppy disk. However, formatting a flash drive in this way will not work for this project. Furthermore, using Windows to format a flash drive directly has been known to destroy some types of flash drives.
Instead, you must format the flash drive by using the HP USB Disk Storage Format Tool that you downloaded earlier. To do so, simply open the utility, select the device followed by the FAT file system option and click Start.
Once the device has been formatted, you must make it bootable. To do so, you must copy the BOOT.INI, NTLDR, and NTDETECT from the root directory of your PC's boot drive to the flash drive. These files are hidden by default, so you will either have to configure Windows Explorer to show hidden files (including protected operating system files) or you will have to open a Command Prompt window and use the COPY command to copy the files.
If you choose to use the Windows Explorer method, then open Internet Explorer and enter C: into the address bar so that you are looking at your local hard drive. Next, select the Folder Options command from the Tools menu. When the Folder Options properties sheet opens, select the View tab. Now, just select the Show Hidden Files and Folders and deselect the Hide Extensions for Known File Types and the Hide Protected Operating System Files check boxes. Click OK to continue.
Now that you have formatted your USB flash drive and installed the boot files onto it, the next thing that you must do is to configure your PC to allow you to boot from the flash drive. This is all done through the computer's BIOS Setup. I can't give you specific instructions for this part, because every computer is different. I can give you a few pointers though.
You can access your computer's BIOS by pressing a specific key immediately after you turn the PC on. The key varies, but it is usually either [F1], [F2], or [Delete]. Once you are in the BIOS Setup, you should verify that all of your computer's USB options are enabled. This might include things like support for legacy USB devices or support for USB 2.0. If there is a time out setting for USB devices, you should set it to the max to insure that the system doesn't time out while waiting on the USB device to boot.
Next, find the section on boot device priority. Normally, a USB flash drive (which is usually listed as USB-HDD, but may be listed as a removable device) will have a very low boot priority. If the USB flash drive's boot priority is lower than the hard disk (listed as HDD) then the only time the computer would ever boot off of the USB flash drive is if the system were to fail to boot from the hard disk. You must therefore rearrange the boot device priority so that the flash drive has a higher priority than the hard drive.
Now that we have finally made it through all of the prep work, it's time to start setting up Windows. As you have probably already guessed, the process of installing Windows to a flash drive is quite a bit different from your normal, run of the mill installation. There are a couple of reasons for this.
For starters, a full blown Windows XP deployment takes up over a Gigabyte of hard disk space. When you are installing to a flash drive, disk space is a scarce commodity. Even if you have over a Gigabyte of space on your flash drive, you probably don't want to use it all on Windows. It would be nice to have room to install a few applications. Therefore, you need to trim the excess fat off of Windows.
The other reason why the installation process is so different from the usual Windows installation is because Windows Setup is not designed to install Windows to a flash drive. You therefore have to configure Windows using an alternate method.
The PEBuilder utility that you downloaded earlier can take care of both of these issues. PEBuilder is designed to create a build of Windows XP (or Windows Server 2003) that does not take up as much space as a full blown installation. Once you create this new build, you can copy it to the flash drive. For right now, I will show you how to create a basic Windows build and copy it to the memory stick. Unfortunately, it's rather difficult to install applications once Windows is up and running. Therefore, after I show you how to create a basic Windows build, I will show you how to create a build that includes some applications.
Begin the process by opening PEBuilder. When you open PEBuilder, you will see a screen similar to the one that's shown in Figure A. Simply enter the path to the Windows installation files (the ones from your Windows XP with Service Pack 2 installation CD). Next, verify that the Create ISO Image and the Burn to CD check boxes are not selected and then click the Build button. PEBuilder will now create the new Windows build.
Now, it's time to copy Windows to the flash drive. To do so, you will have to use a special batch file that's included with PEBuilder. Open a Command Prompt window and navigate to c:\pebuilder313\plugin\peinst. Now, insert an empty flash drive into the computer's USB port and then execute the file PEINST.CMD. You will now see a menu appear as shown in Figure B.
Type 1 and press [Enter] and you will be prompted to enter the path to the build that you have created. Enter C:\pebuilder313\BartPE. Now, type 2, press [Enter], and you will be prompted for the target path. Enter the drive letter that Windows has assigned to your USB flash drive. After doing so, the menu is updated as shown in Figure C. The menu now displays the source path and the destination drive. Type 5 and press [Enter] to install Windows to the flash drive.
Now that I have shown you how to create and install a basic Windows build, I want to talk for a moment about how you can add an application to the build (prior to creating it). The PEBuilder program comes pre-configured to support a number of common Windows applications, but does not come with the applications themselves.
The reason why installing applications can be a little bit tricky is because most Windows applications modify the Windows registry. The build that you are creating is basically a collection of installation files, and the build itself does not contain a registry (the registry gets created when Windows is installed onto the flash drive). As such, PEBuilder uses a sort of registry emulator.
If you go to the C:\PEBUILDER313\PLUGIN folder, you will see sub folders for a number of different applications. If you open one of these application folders, you will see that the folder contains an INF file and a FILES folder. The INF file contains all of the information that would normally go into the registry, and the FILES folder stores all of the program's files.
To see how this works, let's install an application that I'm sure most of you are familiar with; Nero. Begin by installing Nero onto the machine that's running PEBuilder, as if you planned to run Nero locally on that machine. When the installation completes, copy all of the files from C:\Program Files\ahead\Nero to C:\pebuilder313\plugin\nero burning rom\files. In this particular case, the nero burning rom folder is the folder that has been set aside for the Nero application. The Files sub folder is intended to store Nero's system files.
Now, you must take care of Nero's registry entries. To do so, go to the C:\pebuilder313\plugin\nero burning rom folder and open the PENERO.INF file using Notepad. As I explained earlier, the INF file in an application's folder is used to store the application's registry entries. For Nero and all of the other applications that PEBuilder predefines, the INF file is pre-configured. You just have to make a few changes that are specific to your system.
In this particular case, the PENERO.INF file is designed to support both Nero versions 5.x and 6.x. Initially, the lines for both versions are commented out. You must therefore determine which version you have and then remove the semi colon from the beginning of the lines that apply to that version. If you look at Figure D, you can see how the two versions are separated.
Once you uncomment the appropriate lines, just replace "Your Name", "Your Company Name" and "Your Serial Number" with your name, your company's name, and your Nero product key. Save the file, and your set to go. The next time that you click the Build button, Nero will be included in the build.
Running Windows from a flash drive isn't an exact science. Sometimes the process just doesn't work and there is no good reason why. As more PCs start to support booting from USB devices though, USB boots should become more standardized, and the technique should become more reliable.
Fox's latest work, Red Hat Enterprise Linux 5 Administration Unleashed, arrived this month intended as a tome of knowledge for intermediate to advanced Linux system administrators. Before it was published, Fox sat down with SearchEnterpriseLinux.com to provide some insight on the latest version of the Linux community's leading commercial distribution, Red Hat Enterprise Linux 5 (RHEL 5).
What general best practices or tips can you share to make an upgrade to RHEL 5 a smooth one?
Tammy Fox: Performing an upgrade with the installation program basically updates any existing RPM packages on your system. If the new version of the package includes changes that make your existing configuration invalid, some packages will try to migrate your existing data, but it is not required.
The best practice is to have your data on a dedicated storage system that does not get reformatted during a fresh installation. Depending on the size of your organization, this can be a SAN, a data cluster, or just a set of dedicated hard drives in the system. Back up any existing data and configuration files, and perform a fresh installation. Restore your configuration files one by one, testing each program. Be sure to pay close attention to whether or not the software version has changed from your previous version of RHEL to RHEL 5. Finally, reconnect your data storage solution and perform any additional tests necessary.
Of course, all of these steps should be performed on a test system before the plan is implemented on a production system.
What are some key differences between what administrators see in RHEL 4 deployments, and RHEL 5 ones?
Fox: The most immediate change they will notice is the introduction of installation codes. During installation, an installation code must be entered. These codes are generated by Red Hat. Depending on what services you purchased, they unlock different RHEL 5 components such as virtualization and high availability. RHEL 5 also uses new RPM GPG keys. If upgrading, you will need to install the new keys before updating packages.
The next big noticeable change is the move to YUM for software management and maintenance. In previous versions of RHEL, the up2date command could be used to download and install software updates from Red Hat Network. It has been replaced with the YUM command, and all the up2date graphical program has been replaced with a graphical program that use YUM as well. If you schedule package updates and installation with the RHN Web site, you will not notice a difference.
Administrators must also consider whether to use the virtualization feature in RHEL5. (Editor's Note: Due to trademark issues, Red Hat currently refers to Xen-based hypervisor technology as virtualization.) If your hardware is supported and you have systems with enough resources to share between the host system and the virtual machines, virtualization can help reduce the number of physical machines that need to be maintained. If you are a hosting service or allow your customers shell access to their Web site, virtualization can be beneficial.
Administrators should read the release notes for a complete list of caveats and known issues with RHEL 5. For example, dual-booting with Windows Vista requires additional steps for GRUB to boot Windows Vista.
Has SELinux become any easier to use with RHEL 5?
Fox: As with any developing open source technology, SELinux is improving with each release and version of Red Hat Enterprise Linux and Fedora. Of course there will be IT managers who continue not to use SELinux, but the version in RHEL 5 has improved significantly.
With the introduction of the SELinux Management Tool and the SELinux Troubleshooter, it is much easier to determine which services and programs are protected by SELinux. It is also much easier to customize the policy without having to write your own policy. SELinux booleans are used for this and can be enabled and disabled with the SELinux Management Tool.
The SELinux Troubleshooter alerts administrators of when a service has failed to start due to SELinux. It also provides suggestions on how to work around the issue without just disabling SELinux protection for the service.
How has the typical Red Hat Linux administrator's job changed with the introduction of Xen to RHEL 5?
Fox: With the introduction of virtualization in RHEL 5, administrators must now consider whether to continue using individual physical servers for each operating system instance or whether the performance of a virtual machine (VM) will suffice. Certainly, Web hosting companies who offer dedicated Web servers will benefit from virtualization since each client can have their own IP address and guest OS. The VMs on a host system can't access the data on the other VMs or the host, so client data is separated, yet one physical server can serve multiple clients.
IT managers should know that there are hardware requirements for virtualization. Currently, virtualization on RHEL 5 is only supported on x86 and x86_64 systems. It is offered for the Itanium2 but only as a technology preview. In addition to the obvious need for enough processors, memory and disk space to dedicate to each VM, the processor must have Physical Address Extension support. To use full virtualization -- the guest OS does not have to be aware of the VM layer -- the processor must be 64-bit and must have a hardware virtual machine layer.
An eWEEK review of RHEL5 said the Xen support is "half-baked" -- what are your thoughts on this?
Fox: As with SELinux, you will see the virtualization support improve over time. The basic functionality is there. You can create a virtual machine, install a guest OS on the VM, and connect to the guest OS as if it is a OS running on a separate set of hardware. The VM has its own IP address, doesn't have access to the data on its host system, and so on.
There are still parts that can be greatly improved, as with any software when it is first introduced. Because it is open source, it is important to provide these types of new technologies so that they can be used by the masses and so other developers and companies will get behind it. A few of the known issues such as the virtual Machine Manager not being able to start the VM are listed in the RHEL 5 release notes. However, this particular issue has a workaround by starting the VM from the command line first. This issue is also discussed in my book.
Have a question or a comment about the article? Email Jack Loftus, News Writer or visit our new blog at the Enterprise Linux Log.
I think Dell pre-loading Linux will have a significant impact on Linux adoption, although not necessarily because so many end users comfortable with Windows will decide to switch. Rather, Dell's involvement will motivate many hardware manufacturers to make reliable Linux drivers available, the lack of which has significantly retarded the adoption of Linux by many individuals and organizations interested in trying out Linux.
By reducing the barrier of drivers and thereby enabling these trials, Linux will start to achieve some momentum, which will in turn increase its adoption rate. So, I applaud Dell for moving forward on this initiative.
Closing Windows
Heather Carver, brought on as the director of technology and information services at Windsor in August 2006, said her hiring was a result of the district's desire to vet alternatives to a Windows upgrade for its network of seven schools.
When Carver arrived, Windsor had an aging Microsoft Windows environment running on 70 Hewlett-Packard and Dell servers spread across seven schools. Upgrades would have meant purchasing more powerful hardware and additional licensing costs totaling $100,000 – far too expensive for their limited IT budget, she said.
That said, Carver still investigated ways to remain on Windows, but an upgrade proved impossible. "We looked at keeping the physical environment, and how we could accomplish that. But in that scenario, if we could afford the software upgrades, then we could not afford the new hardware required to run it and vice versa," she said.
With Windows ruled out, Carver decided to standardize on SUSE Linux Enterprise Server with thin-client desktops running SUSE Linux Enterprise Desktop. Novell won out because of what Carver perceived as better support for the thin client desktops she planned to use in the classrooms and faculty areas.
Using Wyse terminals, the district also planned to offer students and staff thin-client desktops running OpenOffice.org. Ericom software – a Citrix alternative -- enabled the terminals to run the district's existing and irreplaceable Microsoft Windows educational applications, including Type to Learn, Reading Counts and Kid Pix.
The migration officially began in January at the Brooks school building, one of seven schools in the district that would serve as the testing environment for the project. ZENworks, Novell's systems management product, was also installed to serve as a central management and monitoring hub for the other six sites when they go online this summer.
Identity hiccup
Windsor did go over a few speed bumps in the migration to Linux involving managing user identities and authentication. For Carver, the ID issues were not debilitating enough to deter her from making the switch from Windows to SUSE, but the issue was still noticeable.
Specifically, custom scripts had to be developed to perform tasks such as granting faculty access privileges to student grade information, for example. These tasks had to be completed locally on a server-by-server basis. "We had to add all the system's users one-by-one," Carver said. "That's a pain when you have 500 users."
This problem was especially apparent on the thin clients she had set up in classrooms and teacher workstations. "At our Brooks facility, the OS wasn't that easy to manipulate for our thin clients," Carver said. "I love the OS, but it is not built for the thin client."
Carver said Novell promised more identity support during the summer in the form of a software update.
Linux thrives
Ultimately, though, the migration from Windows to Linux progressed quite smoothly.
"Each site has a server room with 10 servers," Carver said, for a total of 70 servers running applications like file and print, plus Novell's ZENworks and GroupWise for collaboration.
In particular, implementing ZENworks as a help desk for teachers and staff has resulted in a 90% reduction in the amount of time it takes IT staff to resolve problems. "We basically had no help desk before, but in the new system, each user has a distinct name and log-in credentials. Most places have that already, I know," she said.
The new setup also allows for better remote management. "[With Windows] we had spent half our time driving around; we had to touch every machine," Carver said. In a school system like Windsor, all that driving was costing an already strapped IT department too many resources.
Carver said it cost the district about $2,500 per school to migrate to Linux, compared with the estimated $100,000 it would have cost to upgrade their Windows infrastructure. In addition, buying more Microsoft Office licenses would have cost the district $100 per license, she said, whereas OpenOffice was free.
Linux as a learning tool
Ultimately, moving to Linux has enabled the Windsor School District to build out technology capabilities that wouldn't have been possible with Windows.
"[The students] are able to do more because Linux cost less," Carver said. "Our new computer lab [at Brooks] was set to cost $35,000 and ended up costing us $16,000 with Linux [on thin clients]."
And the kids love it too. "The kids think Linux is cool because it's new, but what they're really doing is stepping into the 21st century," Carver said.
LAS VEGAS--Architecture, entertainment and vice. Everything about this city is famous for being over the top. You can now add vending machines to the list.
Can't sleep after bucking the roulette wheel? Forget the flat soda and stale chips. Patter downstairs and pick up an 80GB iPod for $349. Don't worry about scrounging for change. The machine only takes credit cards.
This from Zoom Systems resides in the lobby of the Las Vegas Hilton. The hotel is a stone's throw from where the is holding its annual conference this week.
In addition to an array of multicolored Nanos, from $199 to $249, the machine also dispenses headsets from JBL and Sony.
Dino Dai Zovi, who lives in New York, sent along a URL that exposed the hole. Because the contest was only open to attendees in Vancouver, he sent it to a friend who was at the conference and forwarded it on.
The URL opened a blank page but exposed a vulnerability in input handling in Safari, Comeau said. An attacker could use the vulnerability in a number of ways, but Dai Zovi used it to open a back door that gave him access to anything on the computer, Comeau said.
The vulnerability won't be published. 3Com's TippingPoint division, which put up the cash prize, will handle disclosing it to Apple.
The prize for the contest was originally one of the Macs. But on Thursday evening, TippingPoint put up the cash award, which may have spurred a wider interest in the contest.
One reason Macs haven't been much of a target for hackers is that there are fewer to attack, said Terri Forslof, manager of security response for TippingPoint. "It's an incentive issue. The Mac is not as widely deployed of a platform as, say, Windows," she said. In this case, the cash may have provided motivation.
The contest was a chance for hackers to demonstrate techniques they may have boasted about. "I hear a lot of people bragging about how easy it is to break into Macs," Ruiu said.
Some attendees didn't think it was a coincidence that on late Thursday Apple released a patch for 25 vulnerabilities in OS X.
Macs haven't been targets for hackers and malicious code writers nearly to the degree that Windows machines have historically. That's in part because there are fewer Macs in use, thus making the potential impact of malicious code smaller than on the more widely used PCs.Also, Apple is "extremely litigious when people do find stuff," noted Theo de Raadt, OpenBSD project leader and an attendee at the conference. He suspects that will backfire on Apple, which could begin to "look evil" if hackers begin to publish potentially threatening letters from the company.
This story was updated on April 20, 2007
In essence, they have sold your PC to the highest bidder long before you take it out of the box. Instead of having Windows defaults or your own preferences, the system is set up to maximize the profits of the computer maker and its business partners at the expense of your convenience.
All this extra unwanted software takes its toll on system performance and reliability. Each time the system starts, many of the applications run in the background. While running, they may access the Internet to find updates or change the behavior of standard Windows functions. These freeloaders also take up system resources such as processor, memory and disk space, resulting in longer start-up and shutdown times.
Many of them clutter the desktop, system tray and browser with icons, buttons, yellow balloon dialogs and other visible reminders in the hope that you will click on them and use their services. Apple even pokes fun of this phenomenon in one of its "I'm a PC; I'm a Mac" commercials, called "Stuffed" (requires QuickTime plug-in).
Out of the box, my brand-new Acer notebook had a system tray brimming with icons, including two volume controls. |
Uninvited applications and utilities often target product or service categories where competition is fierce. Take music, for example. Nearly every new computer comes with preinstalled software designed to grab your business for music downloads. It may be Napster, MusicMatch, RealPlayer or Microsoft's own Windows Media Player. The preinstalled software usually takes over all sound-related file extensions, such as .MP3 or .WAV, and launches an in-your-face barrage of advertising any time you want to play something as simple as a sound effect.
Uninstalling isn't always as simple as it should be, either -- many preinstalled processes don't offer a standard uninstall routine.
On my new notebook, Internet Explorer 7 is loaded down with preinstalled toolbars. (Click image to see larger view.) |
Microsoft is certainly aware of this problem, but to some extent the solution is out of its hands. The computer maker, not Microsoft, is responsible for the extra software installed on the system and for making sure the final combination works correctly before it's sent to the customer.
When Windows XP was released in 2001, Microsoft attempted two changes to address this problem. The first was to prompt the user with a message offering to clean up unused desktop icons a few weeks after the system is installed. The second was a prompt offering to hide the tray icons that the user has not clicked on recently. But both changes merely mask the clutter; neither removes the underlying mess.
For all its changes in other areas, Windows Vista hasn't improved things much when it comes to dealing with the junk installed by hardware makers. I just purchased a new Acer notebook with Vista Home Premium installed, and it suffers from the same old plague of icons, advertisements and start-up utilities.
And several of the third-party applications consistently misbehave in ways that make me think that they are not yet Vista-compatible. For example, the PC came with Symantec's Norton Internet Security, which would often pop up error dialogs when the system resumed from sleep. The Windows error logs indicated that several Symantec software components were causing trouble.
Vista's error logs showing preinstalled Symantec software impacting system performance. (Click image to see larger view.) |
Is there any way to avoid the clutter? For medium and large businesses, yes. Hardware makers often give bulk buyers more flexible setup options than they do consumers. You may be able to get a bare-bones operating system setup or even select your own preinstalled set of software. Small system makers may also offer bare-bones Windows setups to both consumers and businesses.
However, if you purchase these you should be sure that you are getting a legal Windows license for the system. The system builder should provide a certificate of authenticity at the very least, and preferably an original Windows DVD that you can use to reinstall or repair the operating system. You can verify that your Microsoft software is not pirated by going to the Genuine Microsoft Software site.
Taking Out the Trash
Nearly every name-brand consumer or small-business PC will have the same software mess that I've seen on my Acer. So, the first thing to do with any new PC isn't to start using it, but to clean it up.
Step 1: Back up.
Before starting, plan for a way to recover in case you delete important files. If you've literally just taken the system out of the box and haven't yet moved over your own files, you can just restore from the recovery CD or DVD that the manufacturer provides -- assuming that they provided one. Some vendors don't offer a disc but provide a reinstall image on a hidden partition on the drive.
If you've been using the PC for a while, backing up your own documents and data is a necessity. An external USB hard drive is a great option.
Step 2: Run PC Decrapifier.
After the backup, you're ready to start hacking through the clutter. One quick way to remove the junk is to use a utility called PC Decrapifier, which can automatically uninstall programs that it knows to be supplied by many hardware vendors -- even those that don't provide uninstallers. It's free for personal use or $20 for IT personnel who plan to use it on multiple computers.
When you run PC Decrapifier, you'll be presented with a list of items it can delete or change for you. Although it was originally written to clean up the junk installed by Dell on its computers (and still works best with Dell machines), it can be useful on other brands as well. The screenshot below shows what it found on my Acer.
PC Decrapifier at work. (Click image to see larger view.) |
Step 3: Uninstall programs manually.
Even after using PC Decrapifier, you will probably find that there are other programs that you would like to eliminate. To uninstall programs manually, go to Control Panel, then to Add or Remove Programs (for XP) or Programs and Features (for Vista). You may need to switch to Classic View to see these options listed.
Just a few of the applications preinstalled on my Acer. (Click image to see larger view.) | |
On the other hand, do not remove entries that are listed as drivers; they are often required so that the associated hardware will work properly.
A few examples of software that can be deleted on my system include Acer Registration, Acer ScreenSaver and Acer Tour. Most of the other Acer software is optional as well, but you might want to keep Acer Arcade Deluxe if any of the games there interest you. I don't plan to use Symantec's Norton security software, so that can be uninstalled. Finally, I prefer the simplicity of Google's home page and don't like toolbars in my browsers, so the Yahoo Toolbar can be uninstalled as well.
To uninstall a program in XP, select it, click the Remove button, and click Yes. On Vista, right click the program and choose Uninstall.
Step 4: Boot into Safe Mode to uninstall any remaining programs.
It's not uncommon for programs that are OEM installed to either not have an Add/Remove Programs option or to have one that doesn't work. Your next step is boot into Safe Mode (hold down the F8 key as Windows begins to start) and try to uninstall the program in Add or Remove Programs (for XP) or Programs and Features (for Vista).
Unfortunately, some applications block their own uninstallation from Windows Safe Mode. To get around this problem, try installing a utility called SafeMSI, which lets you uninstall software from Safe Mode. Once it's installed, reboot to Safe Mode and try again.
Tip: Use SafeMSI to clean up Vista software conflicts When you've installed Windows Vista as an upgrade to your existing Windows XP environment, you might find that many background programs for supporting minor hardware-oriented functions (such as DVD label creation) don't work under Vista or conflict with Vista in some way. It's quite common to see a bunch of error messages inside Windows after it boots on Vista-upgraded machines. The way to turn off these errors is to eliminate software, but oftentimes it just won't uninstall. And Vista seems less permissive than XP about letting you uninstall things in Safe Mode, which is when SafeMSI can come in very handy. | ||||
Step 5: As a last resort for software that remains "stuck," turn to Google.
Despite your best efforts, certain pieces of software may resist being removed through normal channels. In most cases, a Google search on its name will turn up some custom instructions for removing it. There are also various third-party products for removing unwanted software, but cleanup for these tenacious programs is likely to be very app-specific and you'll likely have more luck with specialized instructions you find via Google.
Step 6: When you're done removing software, do a driver check.
While you're doing cleanup, it's also a good idea to check for new drivers. The most recent official drivers for a system are usually available at the vendor's site. Often you'll find that the drivers installed on the system are not the most recent versions available. This is especially true with PCs sold in retail stores, where the computer may have been on the shelf for several weeks or even months.
When the vendor doesn't have a working driver, another source is the Windows Update site. The Automatic Updates feature of Windows does not update drivers, so you must do this manually by going to windowsupdate.microsoft.com.
Step 7: Defragment and clean the disk.
Once all the undesirable software is removed and the drivers updated, you can defragment the drive (Start > Programs > Accessories > System Tools > Disk Defragmenter). Deleting and creating files creates significant disk fragmentation, and a fragmented drive degrades performance. You will also want to run Disk Cleanup (Start > Programs > Accessories > System Tools > Disk Cleanup) as well, because some setup or uninstall programs leave junk files behind.
Defragmenting the drive on a weekly basis will keep performance from degrading. Vista does this automatically through a scheduled task, but you'll need to do this yourself on XP.
Finally, the system is clean and ready to install the software that you really want. You may be surprised how much better the system behaves once you remove the junk that was put there by the system manufacturer.
Tip: Down the road, don't fall into the renewal trap If you decide to purchase or subscribe to any of the applications or services preinstalled on your new system, remember that these companies expect you to stay with them when the time comes to renew. When a dialog pops up telling the user that his subscription has expired, most users will simply enter their credit card without doing any competitive shopping. Microsoft, Symantec and McAfee have even started to automatically bill users when their renewals are due. As a result, companies generally offer the least favorable deals to renewing customers. Better prices are available through retail purchases or through competitive upgrades to different products. Even if you want to stay with Symantec, for example, you may be financially better off uninstalling it and purchasing a local copy from a retail store that includes a rebate. | ||||
Dave Methvin is chief technology officer of PC Pitstop, a free site that automatically diagnoses and fixes common PC problems.
Full subsidization isn't the only problem; we're all under constant attack from the hordes of zombie armies born from software piracy. The vast majority of pirated black-market software being sold in the back alleys from Moscow to Bangladesh are laced with backdoors and rootkits. Not selling them software at prices proportional to their income levels simply means the bad guys get rich selling the software and they get a zombie army to boot. Software companies like Microsoft have the opportunity to undercut the pirates by selling low-cost legitimate software, since people would rather not break the law and they would rather not have infected computers. We would all benefit with fewer zombie botnet armies roaming the Internet.
• Steve Gibson’s SpinRite 6.0 (http://www.spinrite.com) for finding and fixing or moving bad data blocks on FAT, NTFS, Linux, Novell, Macintosh, and even TiVo volumes
• Ontrack’s Easy Data Recovery (http://www.ontrack.com) for digging deep inside a drive and extracting recovered data to other media
• Symantec’s GHOST (http://www.symantec.com) to “peel” data off a bad drive to a disk image for replacement onto another drive, or to extract individual datafiles with Ghost Explorer
• Kurt Garloff’s dd_rescue (http://www.garloff.de/kurt/linux/ddrescue/) to image Linux partitions to other media for later recovery use (see http://www.oreillynet.com/pub/wlg/5205 for an excellent write-up and tips)