1. Click on Start button.
2. Click on Run.
3. Type regedit into the Run text box and press Enter.
4. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
5. Note: From this step onward, the cracking process must be performed as quickly as possible, as it hacks activation stuff and Windows may change back the setting if there is a delay of more than few seconds.
Locate a string value named OOBETimer.
6. Right-click on OOBETimer, and click on Modify.
7. Change the value to FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD.
Activation OOBETimer
8. Click on OK.
9. Right-click on WPAEvents and select Permissions?.
10. Click on Advanced button.
11. Uncheck the check box for Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.
12. Click on Apply.
13. When prompted, click COPY.
14. From there, highlight the SYSTEM line, and click Edit.
15. Choose the Deny option to ban all users from accessing and editing the key.
16. Click on OK.
17. Reboot the computer.
After the hack, Windows Home Server should run completely as a free copy, with users able to access Windows Update to get latest hotfixes and patches. The crack does not require BIOS mod.
To verify that the activation crack works after restarting the system, go to Start -> All Programs -> Activate Windows. The dialog should say Windows is already activated. Alternatively, go to Start -> Run and type oobe/msoobe /a.
Note: Some users reported that the method does not actually remove the activation grace period, even though it makes the system activated.
Thursday, November 4, 2010
Thursday, October 7, 2010
Problems Installing Windows on GPT Hard Disks
Computers with Extensible Firmware Interface (EFI) use GUID Partition Table (GPT) as the standard hard disk partitioning system. Intel proposes it as the replacement for the PC BIOS that uses Master Boot Record (MBR).In GPT partitioned disks, data that is important to platform operation is placed in partitions and not in hidden or unpartitioned sectors as done in MBR partitioned disks.
Due to this and similar other factors, you sometimes observe issues, especially while installing a Windows operating system. To solve such issues, you might need to delete all hard disk partitions and opt for suitable partitioning scheme. This deletes all data and thus to restore information, you require using your recent data backup that should be complete and valid to restore data. However, if data backup is not updated, is corrupt or absent, you can use Data Recovery applications to scan and recover your data.
As a practical instance, when you attempt to install Windows Server 2003, a x64-based Windows Server 2003 version or Windows XP, you might receive the below error message:
"Setup cannot install to the selected partition. You can only install to GPT disks on IA-64 machines and MBR disks on X-86 machines. You can only upgrade installations on GPT disks on IA-64 machines and MBR disks on X-86 machines. To go back to the previous screen press ENTER."
An operating system is already installed on hard drive or it had an operating system, which has now been removed.
Hard disk is GPT formatted
You fail to install required operating systems on GPT hard drives because of following reasons:
On GPT hard drives, you can only set up Windows Server 2003 on systems that are Itanium-based.
You can't set up Windows x64 and Windows 32-bit operating systems on GPT based hard drives.
Stellar Phoenix Windows Data Recovery is a complete and robust Data Recovery software. It supports FAT16, FAT32, VFAT, NTFS and NTFS5 file system based drives and volumes. It is a read-only Hard Drive Recovery application. It is compatible with Windows 7 ( currently in RC1), Vista, Server 2003, XP and 2000).
Due to this and similar other factors, you sometimes observe issues, especially while installing a Windows operating system. To solve such issues, you might need to delete all hard disk partitions and opt for suitable partitioning scheme. This deletes all data and thus to restore information, you require using your recent data backup that should be complete and valid to restore data. However, if data backup is not updated, is corrupt or absent, you can use Data Recovery applications to scan and recover your data.
As a practical instance, when you attempt to install Windows Server 2003, a x64-based Windows Server 2003 version or Windows XP, you might receive the below error message:
"Setup cannot install to the selected partition. You can only install to GPT disks on IA-64 machines and MBR disks on X-86 machines. You can only upgrade installations on GPT disks on IA-64 machines and MBR disks on X-86 machines. To go back to the previous screen press ENTER."
Cause
This error message occurs if these both conditions are true:An operating system is already installed on hard drive or it had an operating system, which has now been removed.
Hard disk is GPT formatted
You fail to install required operating systems on GPT hard drives because of following reasons:
On GPT hard drives, you can only set up Windows Server 2003 on systems that are Itanium-based.
You can't set up Windows x64 and Windows 32-bit operating systems on GPT based hard drives.
Solution
You need to convert your GPT hard disk to a MBR drive. You can use Disk Management or Diskpart command for it, if an operating system is already installed. You can also delete all existing drive partitions while running Setup program and opting for the option to convert the partitioning scheme. In Windows Server 2003-based systems, it must have Windows Server 2003 Service Pack 1 installed. After this, you can restore lost information from backup. If backup produces errors or has not been taken, you can use Recovery applications.Stellar Phoenix Windows Data Recovery is a complete and robust Data Recovery software. It supports FAT16, FAT32, VFAT, NTFS and NTFS5 file system based drives and volumes. It is a read-only Hard Drive Recovery application. It is compatible with Windows 7 ( currently in RC1), Vista, Server 2003, XP and 2000).
Simpson a student of Mass Communication doing research on hard drive recovery software. He is also a freelancer for image recovery software.
Article Source: http://EzineArticles.com/?expert=Simpson_Raid
Tuesday, September 14, 2010
How to Set a Static IP address in Ubuntu 8.10
There seems to be a known bug with the Gnome Network Manager included with the Ubuntu 8.10 release that resets any static ip address settings that are set manually when the system is rebooted reverting back to a DHCP setup. These steps will remove the Gnome Network Manager and help you manually setup the required files for your static network configuration.
Solution 1
Step 1 – Remove the Gnome Network Manager: You need to complete this step first because if left installed this application will overwrite any changes you make to your configuration when the system is rebooted. This is apparently where the bug is located.
To remove the Gnome Network Manager issue the following command in the terminal:
This will disable and remove the Gnome Network Manager application. Now you will have to edit your configuration manually.
Restart your System
Step 2 – Manual configuration of your network interface: In this step you will manually configure your network interface by editing the following two files using your preferred text editor(nano gedit vi). For the purpose of this example I am using the nano editor.
Step 2.1 – Manually configure your network interface file: You can edit the appropriate file by entering the following command into the terminal:
Once your prefered editor opens the file you want to enter the following information (changing your addresses where necessary):
Be sure to save your changes.
Step 2.2 – Manually configure your dns configuration file: You can edit the appropriate file by entering the following command into the terminal:
Once your preferred editor opens the file you want to enter the following information (changing your addresses where necessary):
Be sure to save your changes.
Step 2.3 – Manually restart your network interface with the new settings: Enter the following command in the terminal:
This should return a result that looks like the following:
At this point in your terminal you should be able to run the ifconfig command and the results should reflect your new settings. If the addressing is correct you should have full network access, even after a system restart.
Haven’t tried reinstalling the Network Manger after doing these steps to see if it still works.
Solution 2
Install Wicd if you need both wired and wireless connection
Solution 3
Also, it is said that adding a new config in networkmanager (instead of editing the system default ‘Auto eth0′ stuff) and assign the right MAC address (and the static ip) will fix it, every thing’s fine even after reboot, and you can still use that gnome-networkmanager.
Check this simple guide
Credit Goes here
Solution 1
Step 1 – Remove the Gnome Network Manager: You need to complete this step first because if left installed this application will overwrite any changes you make to your configuration when the system is rebooted. This is apparently where the bug is located.
To remove the Gnome Network Manager issue the following command in the terminal:
sudo update-rc.d -f NetworkManager remove
This will disable and remove the Gnome Network Manager application. Now you will have to edit your configuration manually.
Restart your System
Step 2 – Manual configuration of your network interface: In this step you will manually configure your network interface by editing the following two files using your preferred text editor(nano gedit vi). For the purpose of this example I am using the nano editor.
Step 2.1 – Manually configure your network interface file: You can edit the appropriate file by entering the following command into the terminal:
sudo nano /etc/network/interfaces
Once your prefered editor opens the file you want to enter the following information (changing your addresses where necessary):
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address xxx.xxx.xxx.xxx(enter your ip here)
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx(enter gateway ip here)
iface lo inet loopback
iface eth0 inet static
address xxx.xxx.xxx.xxx(enter your ip here)
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx(enter gateway ip here)
Step 2.2 – Manually configure your dns configuration file: You can edit the appropriate file by entering the following command into the terminal:
sudo nano /etc/resolv.conf
Once your preferred editor opens the file you want to enter the following information (changing your addresses where necessary):
# Generated by NetworkManager
nameserver xxx.xxx.xxx.xxx(enter your dns server ip)
nameserver xxx.xxx.xxx.xxx(enter your alt dns server ip)
nameserver xxx.xxx.xxx.xxx(enter your dns server ip)
nameserver xxx.xxx.xxx.xxx(enter your alt dns server ip)
Step 2.3 – Manually restart your network interface with the new settings: Enter the following command in the terminal:
sudo /etc/init.d/networking restart
This should return a result that looks like the following:
*Reconfiguring network interfaces… [OK]
At this point in your terminal you should be able to run the ifconfig command and the results should reflect your new settings. If the addressing is correct you should have full network access, even after a system restart.
Haven’t tried reinstalling the Network Manger after doing these steps to see if it still works.
Solution 2
Install Wicd if you need both wired and wireless connection
Solution 3
Also, it is said that adding a new config in networkmanager (instead of editing the system default ‘Auto eth0′ stuff) and assign the right MAC address (and the static ip) will fix it, every thing’s fine even after reboot, and you can still use that gnome-networkmanager.
Check this simple guide
Credit Goes here
Tuesday, July 13, 2010
Uninstalling Windows Movie Maker in Windows XP
Windows Movie Maker
If you've never edited your own movies, or if you have a better-equipped video editor, you might want to get rid of Windows Movie Maker. Sadly, with Microsoft's System-File-Protection mechanism, you cannot simply delete the relevant files from the Program Files folder. Windows will restore the files within a few minutes and Windows Movie Maker will keep working. If you are really stubborn about removing Windows Movie Maker from Windows XP, there is a workaround which will allow you to delete all the concerned files and free-up some space which would otherwise be taken up by Windows Movie Maker.
Uninstallation
Removing Windows Movie Maker requires a workaround since Windows considers it an essential part of Windows. Here is the procedure to delete Windows Movie Maker completely from Windows.
Restart Windows XP in Safe Mode. To do this, start tapping on the F8 key as soon as your computer boots, before the Windows XP loading screen. In the menu that is then shown, select Safe Mode.
Once Safe Mode starts, Click on Start Menu, then go to Run and type "cmd". This will open up a command prompt where you will be entering a few commands:
Type these commands one-by-one and you will completely remove Windows Movie Maker.
Once Safe Mode starts, Click on Start Menu, then go to Run and type "cmd". This will open up a command prompt where you will be entering a few commands:
Type these commands one-by-one and you will completely remove Windows Movie Maker.
- del "c:\system32\dllcache\*wmm*.dll"
- del "c:\system32\dllcache\moviemk.exe"
- del "c:\Program Files\Movie Maker\*.*"
- rmdir /s "c:\Program Files\Movie Maker"
Final Words
Removing Windows Movie Maker, while possible, can be dangerous if you do not take care while typing the above commands and delete anything important by mistake. Remember that the system32 directory contains the core of Windows system files and any important files being deleted will cause big problems. If in doubt, make sure to backup everything before you start with this procedure.
Thursday, July 8, 2010
Subscribe to:
Posts (Atom)