This copy of Windows must be activated before you can log on.

You can actually get in by doing the steps below. NOTE: You are not in any way violating any Microsoft policy’s by doing this.
Instructions:
1. Boot into “Safe Mode“. To do this, press F8 as it is booting up. Go into “Safe Mode” by choosing the “Safe Mode” option.
2. Once you are at the desktop in “Safe Mode”, Click “Start” then click “Run“.
3. At the run command prompt type the following EXACTLY:
rundll32.exe syssetup,SetupOobeBnk
(NOTE: The “Oo”’s in Oobe are “o’s” – not “zero’s” There is one space after rundll32.exe. It is case sensitive.)
4. Click OK – wait a few seconds – This just reset Windows Activation for 30 days.
5. Reboot the PC into normal mode – log in – re-activate Windows.

You can read more about it here -> PSX-Scene

The source website is here -> The Oatmeal

Requirements
USB device passthrough requires:

• Virtual hardware version 7 or higher
• A USB Arbitrator
• A USB controller
• A USB device or device hub

Limitations
The USB Controller has these limitations:

• USB controller hardware and modules that support USB 2.0 and USB 1.1 devices must be present on the host.
• You can add only one virtual USB controller to each virtual machine.
• The USB arbitrator can monitor a maximum of 15 USB controllers. If your system includes an additional number of controllers and you connect USB devices to these controllers, the devices are not available to the virtual machine.
• You must add the USB controller to the virtual machine before you can add a USB device.
• You must remove all USB devices before you remove the controller.

• You can add multiple USB devices to a virtual machine that resides on an ESX/ESXi host to which the devices are physically attached.
• A USB device is available to only one virtual machine at a time.
• You can add up to 20 USB devices to a virtual machine.
• Unsupported USB devices may not interact as expected with other ESX/ESXi features. For a list of supported USB devices, see Supported USB device models for passthrough from an ESX or ESXi host to a virtual machine (1021345).
• Before you hot add memory, CPU, or PCI devices, you must remove any USB devices. Hot adding these resources disconnects USB devices, which may result in data loss.
• When you suspend and resume a virtual machine, USB devices behave as if they have been disconnected, then reconnected.

Adding a USB controller and a USB device
To add a USB controller:

1. Right-click on the virtual machine and click Edit Settings.
2. Click Add.
3. Choose USB Controller and click Next.
4. Click OK.

1. Right-click on the virtual machine and click Edit Settings.
2. Click Add.
3. Choose USB Device and click Next.Note: To support vMotion, select Support vMotion while device is connected.
4. Click OK.

• Vlance — An emulated version of the AMD 79C970 PCnet32 LANCE NIC, an older 10 Mbps NIC with drivers available in most 32bit guest operating systems except Windows Vista and later. A virtual machine configured with this network adapter can use its network immediately.
• VMXNET — The VMXNET virtual network adapter has no physical counterpart. VMXNET is optimized for performance in a virtual machine. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET network adapter available.
• Flexible — The Flexible network adapter identifies itself as a Vlance adapter when a virtual machine boots, but initializes itself and functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it. With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher performance VMXNET adapter.
• E1000 — An emulated version of the Intel 82545EM Gigabit Ethernet NIC. A driver for this NIC is not included with all guest operating systems. Typically Linux versions 2.4.19 and later, Windows XP Professional x64 Edition and later, and Windows Server 2003 (32-bit) and later include the E1000 driver.
• VMXNET 2 (Enhanced) — The VMXNET 2 adapter is based on the VMXNET adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames and hardware offloads. This virtual network adapter is available only for some guest operating systems on ESX/ESXi 3.5 and later.

  VMXNET 2 is supported only for a limited set of guest operating systems:

  • 32 and 64bit versions of Microsoft Windows 2003 (Enterprise and Datacenter Editions).
    Â
    Note: You can use enhanced VMXNET adapters with other versions of the Microsoft Windows 2003 operating system, but a workaround is required to enable the option in VMware Infrastructure (VI) Client or vSphere Client. See Enabling enhanced vmxnet adapters for Microsoft Windows Server 2003 (1007195) if Enhanced VMXNET is not offered as an option.
     
  • 32bit version of Microsoft Windows XP Professional
  • 32 and 64bit versions of Red Hat Enterprise Linux 5.0
  • 32 and 64bit versions of SUSE Linux Enterprise Server 10
  • 64bit versions of Red Hat Enterprise Linux 4.0
  • 64bit versions of Ubuntu Linux
• VMXNET 3 — The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.

  VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems:

  • 32 and 64bit versions of Microsoft Windows XP, 2003, and 2008
  • 32 and 64bit versions of Red Hat Enterprise Linux 5.0 and later
  • 32 and 64bit versions of SUSE Linux Enterprise Server 10 and later
  • 32 and 64bit versions of Asianux 3 and later
  • 32 and 64bit versions of Debian 4/Ubuntu 7.04 and later
  • 32 and 64bit versions of Sun Solaris 10 U4 and later
  • 32 and 64bit versions of Ubuntu