Well a short cut is basically a file that points to another file. It is an antiquated, pointing system from the Windows 95 days. Shortcuts not only use up space on your hard drive, they also linger around after the item they are pointing to has been deleted and break if the item is renamed.

A symbolic link is like a short cut, but instead of being saved as a file, they are registered to the file system. This means they do not use hard disk space; all programs recognise and can read where the link is pointing to. A symbolic link can point to any file, folder either locally on the computer or over a network using a SMB path.

A file hard link and the directory junction are a little different. It not only points to the item but duplicates it, but does so without taking up the extra hard disk space required by a copied file. Also if you have a hard link pointing to a file then delete that original file, the hard link will still retain a copy. A limitation of the file hard link though is that the link can only be made on the same file partition as the file.

Finally a junction is a hard link for directories. To me they are the most useful and unlike file hard links, you can create junctions on different partitions to where the original folder is located. Again a junction is stored on the file system, does not take up space and is treated by the operating system and programs as a local folder.

Windows Vista/7 uses the command line program called mklink to create these symbolic links. It has 3 arguments and then requires both a link name and target.

[From: 100 Places for Free Books Online]

Wireless
Touchscreen
Graphics card is not detected
Sleep

[From: How to install Mac OSX 10.5.7 on hp Elitebook 2730p (dual boot with win7) « A Developer's blog]

The Virtual Hard Disk (VHD) is the container for the installed operating system. Because everything is inside a single file, there are a number of benefits that can be realized for data center server environments, as well as managed desktop environments. The following article dives into the technical details of implementing two operating systems. Both are installed in a VHD file and can easily be booted by selecting the preferred environment at power on. This could easily be scripted and automated.

Boot your machine with a blank hard drive using the Windows 7 DVD.
Click next on the language screen if English is appropriate.
SHIFT+F10 to launch a WinPE command console. Although the commands below are in upper case, the commands are not case sensitive. I am only using upper case for readability here.
Enter DISKPART to run the utility.
LIST DISK to see the available disks in your system. I am assuming a single raw disk.
SEL DISK 0
CREATE PARTITION PRIMARY
FORMAT FS=NTFS QUICK
LIST VOL
ASSIGN
LIST VOL
CREATE VDISK FILE=c:\windows7rc.vhd MAXIMUM=200000 TYPE=EXPANDABLE
SELECT VDISK FILE=c:\windows7rc.vhd
ATTACH VDISK
CRE PART PRI
FORMAT FS=NTFS QUICK
ASSIGN LETTER=V:
LIST VOL
LIST VDISK
exit DISPART
exit WinPE command console
Install to the newly created 200GB (fuzzy math) virtual hard disk which looks just like a partition to Windows Setup
Repeat steps 11-18 for the Windows Server 2008 R2 VHD but with the obvious changes for the vdisk filename, size, etc.
[From: Keith Combs' Blahg : Dual Boot from VHD Using Windows 7 and Windows Server 2008 R2]

Firefox 3.5 is out. And the more users download it, the more designers will be able to take advantage of the @font-face CSS rule. How can @font-face be used with currently implemented CSS selectors to create engaging, nuanced and more mature typography? Let’s find out.

[From: @font-face: The Potential of Web Typography]