December 25, 2007

Speed Up Those Drives

If you didn't know, Windows Vista operates external hard drives that are connected via USB differently than internal drives. Write caching is disabled so that you can safely remove the drive at almost any time. This is a great feature for USB flash drives that are frequently inserted and removed from your computer. But, if you have a large hard drive in an external enclosure that you never disconnect from your computer, write caching is also disabled, which can decrease performance. So, let's change that around a little, shall we?!

Today, I'm cialis usa going to show you a tweak that will increase the performance of your external hard drive by turning the write cache back on, as well as, activating an advanced performance. Let’s get started!

1.) First, in Vista, right click on the Computer icon on your desktop and select Manage.

2.) Click on Device Manager from the side menu.

3.) Next, expand the Disk Drives option and locate your external drive from the list.

4.) Once you've found it, right click on the drive and select Properties.

5.) Under the Policies tab, select Optimize for Performance.

6.) Next, checkmark both the options of "Enable write caching on the disk" and "Enable advanced performance," as shown below:

7.) Hit OK and then restart your computer.

That's all you have to do. Now, go on and enjoy your increased performance!

Permalink • Print • Comment

December 19, 2007

Mac versus Windows vulnerability stats for 2007

December 18th, 2007

Posted by George Ou

The year 2007 has been an interesting year that brought us improved security with Windows Vista and Mac OS X Leopard (10.5).   But to get some perspective of how many publicly known holes found in these two operating systems, I’ve compiled all the security flaws in Mac OS X and Windows XP and Vista and placed them side by side.  This is significant because it shows a trend that can give us a good estimate for how many flaws we can expect to find in the coming months.  The more monthly flaws there are in the historical trend, the more likely it is that someone will find a hole to exploit in the future.  For example back in April of this year, hackers took over a fully patched Macbook and won $10,000 plus the Macbook they hacked.

I used vulnerability statistics from an impartial third party vendor Secunia and I broke them down by Windows XP flaws, Vista flaws, and Mac OS X flaws.  Since Secunia doesn’t offer individual numbers for Mac OS X 10.5 and 10.4, I merged the XP and Vista vulnerabilities so that we can compare Vista + XP flaws to Mac OS X.  In case you’re wondering how 19 plus 12 could equal 23, this is because there are many overlapping flaws that is shared between XP and Vista so those don’t get counted twice just as I don’t count something that affects Mac OS X 10.4 and 10.5 twice.

Windows XP, Vista, and Mac OS X vulnerability stats for 2007
  XP Vista XP + Vista Mac OS X
Total extremely critical 3 1 4 0
Total highly critical 19 12 23 234
Total moderately critical 2 1 3 2
Total less critical 3 1 4 7
Total flaws 34 20 44 243
Average flaws per month 2.83 1.67 3.67 20.25

 X Extremely critical
 H Highly critical
 M Moderately critical
 L Less critical

So this shows that Apple had more than 5 times the number of flaws per month than Windows XP and Vista in 2007, and most of these flaws are serious.  Clearly this goes against conventional wisdom because the numbers show just the opposite and it isn’t even close.

Also noteworthy is that while Windows Vista shows fewer flaws than Windows XP and has more mitigating factors against exploitation, the addition of Windows Defender and Sidebar added 4 highly critical flaws to Vista that weren’t present in Windows XP.  Sidebar accounted for three of those additional vulnerabilities and it’s something I am glad I don’t use.  The lone Defender critical vulnerability that was supposed to defend Windows Vista was ironically the first critical vulnerability for Windows Vista.

Windows XP, Vista, and Mac OS X vulnerability details for 2007
Month Windows XP Windows Vista Mac OS X
DEC CVE-2007-0064 H
CVE-2007-3039 L
CVE-2007-3895 H
CVE-2007-3901 H
CVE-2007-5355 L
CVE-2007-0064 H
CVE-2007-5350 L
CVE-2007-3895 H
CVE-2007-3901 H
CVE-2007-5351 M
CVE-2007-5355 L
 
CVE-2006-0024 H
CVE-2007-1218 H
CVE-2007-1659 H
CVE-2007-1660 H
CVE-2007-1661 H
CVE-2007-1662 H
CVE-2007-3798 H
CVE-2007-3876 H
CVE-2007-4131 H
CVE-2007-4351 H
CVE-2007-4572 H
CVE-2007-4708 H
CVE-2007-4709 H
CVE-2007-4710 H
CVE-2007-4766 H
CVE-2007-4767 H
CVE-2007-4768 H
CVE-2007-4965 H
CVE-2007-5379 H
CVE-2007-5380 H
CVE-2007-5398 H
CVE-2007-5476 H
CVE-2007-5770 H
CVE-2007-5847 H
CVE-2007-5848 H
CVE-2007-5849 H
CVE-2007-5858 H
CVE-2007-5850 H
CVE-2007-5851 H
CVE-2007-5853 H
CVE-2007-5854 H
CVE-2007-5855 H
CVE-2007-5856 H
CVE-2007-5857 H
CVE-2007-5859 H
CVE-2007-5860 H
CVE-2007-5861 H
CVE-2007-5863 H
CVE-2007-6077 H
CVE-2007-6165 H
CVE-2006-4339 H
CVE-2006-6731 H
CVE-2006-6736 H
CVE-2006-6745 H
CVE-2007-0243 H
CVE-2007-2435 H
CVE-2007-2788 H
CVE-2007-2789 H
CVE-2007-3004 H
CVE-2007-3005 H
CVE-2007-3503 H
CVE-2007-3504 H
CVE-2007-3655 H
CVE-2007-3698 H
CVE-2007-3922 H
CVE-2007-4381 H
CVE-2007-5232 H
CVE-2007-5862 H
CVE-2007-6276 M
NOV     CVE-2007-6165 H
CVE-2007-4702 L
CVE-2007-4703 L
CVE-2007-4704 L
CVE-2005-0953 H
CVE-2005-1260 H
CVE-2007-0464 H
CVE-2007-0646 H
CVE-2007-2926 H
CVE-2007-3456 H
CVE-2007-3749 H
CVE-2007-3756 H
CVE-2007-3758 H
CVE-2007-3760 H
CVE-2007-3999 H
CVE-2007-4267 H
CVE-2007-4268 H
CVE-2007-4269 H
CVE-2007-4671 H
CVE-2007-4678 H
CVE-2007-4679 H
CVE-2007-4680 H
CVE-2007-4681 H
CVE-2007-4682 H
CVE-2007-4683 H
CVE-2007-4684 H
CVE-2007-4685 H
CVE-2007-4686 H
CVE-2007-4687 H
CVE-2007-4688 H
CVE-2007-4689 H
CVE-2007-4690 H
CVE-2007-4691 H
CVE-2007-4692 H
CVE-2007-4693 H
CVE-2007-4694 H
CVE-2007-4695 H
CVE-2007-4696 H
CVE-2007-4697 H
CVE-2007-4698 H
CVE-2007-4699 H
CVE-2007-4700 H
CVE-2007-4701 H
CVE-2007-4743 H
OCT CVE-2007-5587 L
CVE-2007-2217 H
CVE-2007-2228 L
CVE-2007-3897 H
CVE-2007-2228 L
CVE-2007-3897 H
 
SEPT CVE-2007-4916 M CVE-2007-3036 L  
AUG CVE-2007-1749 H
CVE-2007-3034 H
CVE-2007-2224 H
CVE-2007-3033 H
CVE-2007-3032 H
CVE-2007-3891 H
CVE-2007-1749 H
CVE-2004-0996 H
CVE-2004-2541 H
CVE-2005-0758 H
CVE-2005-3128 H
CVE-2006-2842 H
CVE-2006-3174 H
CVE-2006-4019 H
CVE-2006-6142 H
CVE-2007-0450 H
CVE-2007-0478 H
CVE-2007-1001 H
CVE-2007-1262 H
CVE-2007-1358 H
CVE-2007-1460 H
CVE-2007-1461 H
CVE-2007-1484 H
CVE-2007-1521 cialis soft H
CVE-2007-1583 H
CVE-2007-1711 H
CVE-2007-1717 H
CVE-2007-1860 H
CVE-2007-2403 H
CVE-2007-2404 H
CVE-2007-2405 H
CVE-2007-2406 H
CVE-2007-2407 H
CVE-2007-2408 H
CVE-2007-2409 H
CVE-2007-2410 H
CVE-2007-2442 H
CVE-2007-2443 H
CVE-2007-2446 H
CVE-2007-2447 H
CVE-2007-2589 H
CVE-2007-2798 H
CVE-2007-3742 H
CVE-2007-3744 H
CVE-2007-3745 H
CVE-2007-3746 H
CVE-2007-3747 H
CVE-2007-3748 H
CVE-2007-3944 H
 
JUL CVE-2007-3896 H
CVE-2007-4041 H
CVE-2007-5020 H
   
JUN CVE-2007-2219 H
CVE-2007-2218 H
CVE-2007-1658 H
CVE-2007-2225 H
CVE-2007-2227 H
CVE-2007-1658 H
CVE-2007-2225 H
CVE-2007-2227 H
CVE-2007-2229 L
CVE-2007-2399 H
CVE-2007-2401 H
CVE-2007-2242 M
MAY     CVE-2005-3011 H
CVE-2006-4095 H
CVE-2006-4096 H
CVE-2006-4573 H
CVE-2006-5467 H
CVE-2006-6303 H
CVE-2007-0493 H
CVE-2007-0494 H
CVE-2007-0740 H
CVE-2007-0750 H
CVE-2007-0751 H
CVE-2007-0752 H
CVE-2007-0753 H
CVE-2007-1536 H
CVE-2007-1558 H
CVE-2007-2386 H
CVE-2007-2390 H
APR CVE-2007-1205 H
CVE-2007-1206 L
CVE-2007-1973 L
CVE-2007-1209 L CVE-2006-0300 H
CVE-2006-5867 H
CVE-2006-6143 H
CVE-2006-6652 H
CVE-2007-0022 H
CVE-2007-0465 H
CVE-2007-0646 H
CVE-2007-0724 H
CVE-2007-0725 H
CVE-2007-0729 H
CVE-2007-0732 H
CVE-2007-0735 H
CVE-2007-0736 H
CVE-2007-0737 H
CVE-2007-0738 H
CVE-2007-0739 H
CVE-2007-0741 H
CVE-2007-0742 H
CVE-2007-0743 H
CVE-2007-0744 H
CVE-2007-0745 H
CVE-2007-0746 H
CVE-2007-0747 H
CVE-2007-0957 H
CVE-2007-1216 H
MAR CVE-2007-0038 X CVE-2007-0038 X CVE-2005-2959 H
CVE-2006-0225 H
CVE-2006-0300 H
CVE-2006-1516 H
CVE-2006-1517 H
CVE-2006-2753 H
CVE-2006-3081 H
CVE-2006-3469 H
CVE-2006-4031 H
CVE-2006-4226 H
CVE-2006-4829 H
CVE-2006-4924 H
CVE-2006-5051 H
CVE-2006-5052 H
CVE-2006-5330 H
CVE-2006-5679 H
CVE-2006-5836 H
CVE-2006-6061 H
CVE-2006-6062 H
CVE-2006-6097 H
CVE-2006-6129 H
CVE-2006-6130 H
CVE-2006-6173 H
CVE-2007-0229 H
CVE-2007-0236 H
CVE-2007-0267 H
CVE-2007-0299 H
CVE-2007-0318 H
CVE-2007-0463 H
CVE-2007-0467 H
CVE-2007-0588 H
CVE-2007-0719 H
CVE-2007-0720 H
CVE-2007-0721 H
CVE-2007-0722 H
CVE-2007-0723 H
CVE-2007-0724 H
CVE-2007-0728 H
CVE-2007-0726 H
CVE-2007-0730 H
CVE-2007-0731 H
CVE-2007-0733 H
CVE-2007-1071 H
FEB CVE-2006-1311 L
CVE-2007-0025 L
CVE-2007-0026 M
CVE-2007-0210 L
CVE-2007-0211 L
CVE-2006-5559 H
CVE-2007-0214 H
CVE-2006-5270 H CVE-2007-0021 H
CVE-2007-0023 H
CVE-2007-0197 H
CVE-2007-0614 H
CVE-2007-0710 H
JAN CVE-2007-0024 X   CVE-2007-0462 L
CVE-2007-0023 L
CVE-2007-0355 L
CVE-2007-0236 L
CVE-2007-0229 H

Permalink • Print • Comment

December 18, 2007

Microsoft to relax XP activation rules with SP3

December 16th, 2007

Posted by Ed Bott

17-Dec 9:00AM PST: Post updated with more details about behavior after grace period expires. 

Last week Microsoft released a whitepaper outlining the changes in Windows XP Service Pack 3, which was just released for MSDN and TechNet subscribers and should be ready for final release in the first half of 2008. The introduction is low-key:

Windows XP Service Pack 3 (SP3) includes all previously released updates for the operating system. This update also includes a small number of new functionalities, which do not significantly change customers’ experience with the operating system. This white paper summarizes what is new in Windows XP SP3.

Sounds innocuous enough, right?

But the very last item in the “New and Enhanced Functionality” section, buried in a box on page 9 of the 11-page PDF document, represents a pretty dramatic change:

As in Windows Server 2003 SP2 and Windows Vista, users can now complete operating cialis professional vs cialis system installation without providing a product key during a full, integrated installation of Windows XP SP3. The operating system will prompt the user for a product key later as part of Genuine Advantage. As with previous service packs, no product key is requested or required when installing Windows XP SP3 using the update package available through Microsoft Update.

This change allows you to install Windows XP with Service Pack 3 on any PC without entering a product key and use it in trial mode until the 30-day activation grace period expires. That’s the same way that Windows Vista and Windows Server 2003 now work. After the 30 days are up, you’ll have to enter a valid product key and activate the system before you can log on (see the end of this post for more details). put up with some nagging, but you should be able to continue using the system. By contrast, you can’t even complete an installation of current XP builds (SP2 and earlier) without entering a product key that at least looks valid.

The biggest caveat is that this change requires XP installation media that incorporate a “slipstreamed” copy of SP3. The MSDN downloads directory contains only a standalone updater (in .exe format) for the SP3 RC. Fortunately, the well-publicized hacks widely used to create slipstreamed XP SP2 media work just as well for SP3.

I’ve just made one of those slipstream disks and used it to install a clean copy of Windows XP Professional. During the portion of setup where I normally am asked to enter a product key, I see this dialog box instead:

xp_sp3_product_key_dialog.jpg

A closer look reveals that the text reflects the same wording as that found in its Vista counterpart, with the product key listed as “optional.” I’ve highlighted the relevant text below:

New wording in the Windows XP SP3 dialog box confirms that entering a product key is now optional during setup.

And sure enough, when I left the box blank and continued with Setup, I was given this one final warning:

If you choose not to enter a product key, you can use XP for 30 days without activating it

Once you’re past that, it’s (relatively) smooth sailing. At first boot, a taskbar notification reminded me I had 30 days to activate Windows. Ignoring the message allowed me to continue.

Combine this news with the recent announcement of major changes to activation and validation in Vista’s forthcoming SP1, and it appears that Microsoft has decided to dial back on WGA across the board. I’ll monitor this installation over the next 30 days and see what happens as the end of the grace period approaches.

Update: I simulated the expiration of the 30-day grace period by resetting the clock on my test system and diabling Internet time sync. At the end of the grace period, the Welcome screen displays this dialog box over the list of user names:

You’re forced to activate XP SP3 when the grace period expires

If you click No, you’re returned to to the logon screen. Click yes and you go to a desktop where your only option is to enter a product key. If you click Remind Me Later in that box, you’ll also be sent back to the logon screen. And unlike Windows Vista, there’s apparently no rearm option to extend the grace period by an additional 30 days.

It’s worth noting that this option applies only to systems that have never been activated. After the initial activation completes, any WGA failure results in notifications, without affecting the ability to log on or use the system.

Permalink • Print • Comment

December 14, 2007

New Update: XP SP3

Today, I come bearing good news for all you Windows XP users out there! If you recall, it wasn't too long ago that I gave you a little update on the new Service Pack 3 for XP. I wasn't able to give you an exact release date for it, but I told you it should arrive in the first half of 2008. Well, I just received word that it may be moving along a little faster than we all thought. Yep, on December 12, 2007 (just this past Wednesday), the Release Candidate 1 for the Windows XP SP3 was released and it is now available for download. Check it out!

Are you a little confused as to what a Release Candidate is? Well, it's basically a test code that is given out to various people who have been helping with the testing process thus far. It's always a good thing when a new application reaches this point, because it means the full version will be along shortly. Now, I want to make it very clear that what I'm talking about today is not the full version of the XP SP3. You can download the Release Candidate 1 for yourself, but it is not the final version. cialis prices I just want to make sure everyone understands that!

If you do want to give it a try, you can download the SP3 Release Candidate 1 from this Web site. Just click on the Download Now link and follow the directions. I've read some reviews and it looks like there are still several flaws in the SP3, but you can at least get a feel for what it will be like and what will change on your computer. I don't really recommend that you download it quite yet, but if you just can't wait any longer, feel free to do so. Otherwise, the official version should be released in the early part of next year. As always, I will continue to keep you updated as new information on this becomes available. Just keep your eyes and ears open!

Permalink • Print • Comment

December 13, 2007

Fsutil

fsutil is quite powerful, it should only be used by advanced users who have a thorough knowledge of Windows XP. In addition, you must be logged on as an administrator or a member of the Administrators group in order to use fsutil.

 

The following table lists the fsutil subcommands.

 

Comm and Description

 

behavior

Queries, changes, enables, or disables the settings for generating 8.3 character-length file names, accepting extended characters in 8.3 character-length file names on NTFS volumes, updating the last access timestamp on NTFS volumes, how often quota events are written to the system log, and the amount of disk space reserved of the MFT Zone.

 

dirty

Queries whether volume's dirty bit is set. Sets a volume's dirty bit. When a volume's dirty bit is set, autochk automatically checks the volume for errors the next time the computer is restarted.

 

file

Typically used by support professionals. Finds a file by its security identifier, queries allocated ranges for a file, sets a file's short name, sets a file's valid data length, or sets zero data for a file.

 

fsinfo

Typically used by support professionals. Lists all drives, queries the drive type, queries volume information, queries NTFS-specific volume information, or queries file system statistics.

 

hardlink

Creates a hard link. A hard link is a directory entry for a file. Every file can be considered to have at least one hard link. On NTFS volumes, each file can have multiple hard links, and thus a single file can appear in many directories (or even in the same directory with different names). Because all of the links reference the same file, programs can open any of the links and modify the file. A file is deleted from the file system only after all links to it have been deleted. After you create a hard link, programs can use it like any other file name.

 

objectid

Typically used by support professionals. Manages object identifiers, which are used by Windows XP to track objects such as files and directories.

 

quota

Manages disk quotas on NTFS volumes in order to provide more precise control of network-based storage. Disk quotas are implemented on a per-volume basis and enable both hard- and soft-storage limits to be implemented on a per-user basis.

 

reparsepoint

Typically used by support professionals. Queries or deletes reparse points, which are NTFS file system objects that have a definable attribute containing user-controlled data, and are used to extend functionality in the input/output (I/O) subsystem. Reparse points are used for directory junction points and volume mount points. They are also used by file system filter drivers to mark certain files as special to that driver.

 

sparse

Manages sparse files A sparse file is a file with one or more regions of unallocated data in it. A program will see these unallocated regions as containing bytes with the value zero, but there is actually no disk space used to represent these zeros. In other words, all meaningful or nonzero data is allocated, whereas all non-meaningful data (large strings of data composed of zeros) is not allocated. When a sparse file is read, allocated data is returned as stored and unallocated data is returned, by default, as zeros, in accordance with the C2 security requirement specification. Sparse file support allows data to be deallocated from anywhere in the file.

 

usn

Typically used by support professionals. Manages the update sequence number (USN) change journal, which provides a persistent log of all changes made to files on the volume.

 

volume

Manages a volume. Dismounts a volume or queries to see how much free space is available on a disk.

 

 Note

 

To view help for the available subcommands at the command prompt, type fsutil, type the subcommand, and then type cialis prescription online help (that is, fsutil subcommand help).

 

Fsutil: behavior

Fsutil: dirty

Fsutil: file

Fsutil: fsinfo

Fsutil: hardlink

Fsutil: objectid

Fsutil: quota

Fsutil: reparsepoint

Fsutil: sparse

Fsutil: usn

Fsutil: volume

Command-line reference A-Z

 

 

Pasted from <http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?pf=true>

Permalink • Print • Comment
« Previous PageNext Page »
Made with WordPress and a healthy dose of Semiologic • Sky Gold skin by Denis de Bernardy