The wily hardware hackers over at XDA Developers have pushed the 1GHz Qualcomm Snapdragon chip in the HTC Nexus One to 1.113GHz. Poster Persiansown outlined the procedure:
1. Root your Nexus and install the latest Cyanogen rom (5.0.2 as of 2/15/2010)
2. Download SetCPU from either XDA for free, or support the developer as I did and buy it on the market
3. Reboot into fastboot and type “fastboot flash zimage zImagekmobs”
4. Once your phone boots, open SetCPU and tell it to autodetect your CPU (Don’t choose Nexus from the list!)
5. Set the max clock to the highest and tell it to set on boot.
6. Enjoy
Microsoft does not invite many people to join the official MS Office 2010 RC (Release Candidate) beta testing program in Connect website. For people who downloads and installs Office Professional 2010 RC (RTM Escrow) build 14.0.4734.1000 for volume licensing distribution channel, it’s possible to install the Office 2010 without any product key. For user who wants to activate the installed Office 2010, which may become the final RTM version (the RTM version is now rumored to be build 14.0.4740.1000), here’s the trick or hack on how to activate Office 2010 RC.
The workaround to crack Office 2010 activation as detailed below works by replacing the unactivated tokens.dat and pkeyconfig-office.xrm-ms, with activated version, which provided for free by Microsoft for Office 2010 Beta program. The free product key for Office 2010 Beta is a MAK type (Multiple Activation Key), which is now required to activate volume licensing version of Office 2010 products.
One benefit of using MAK to activate a Microsoft product is that, the system does not required to update or refresh its activation status, internally or externally against any activation servers. The convenience is provided from computers, such as laptops or notebooks, which does not connected to the corporate network persistently or consistently. Reactivation is only required when there is a hardware change. Best of all, if for any reason the software product which has received a MAK product key loses activation or fails validation, its functionality is not limited or restricted. Only nagging notifications will appear, which will disappear when the product is activated again.
Furthermore, the time bomb, which renders the pre-release Office 2010 useless after an expiry date does not exist in the leaked volume or Select versions of Office 2010. So, the activated Office 2010 RC (RTM Escrow) will likely to stay activated forever, even if it’s been activated with license files from the beta.
- If there is any existing Office 2010 been installed, uninstall it, then reboot the system.
- Download and install official Microsoft Office 2010 Beta (the version of Office 2010 suites to install is Office Professional 2010 Beta build 14.0.4536.1000, and must be the same system architecture of x86 or x64 that intends to be installed at RC, i.e. 32-bit Office 2010 Beta activation files will activate 32-bit Office 2010 RC/RTM while 64-bit Office 2010 Beta activation files will activate 64-bit Office 2010 RC/RTM).While at the Office 2010 Beta page, register and request for a free product key (which is a MAK – Multiple Activation Key) for Office 2010 to activate the installed Office Professional 2010 Beta over Internet against Microsoft’s activation key.
- Once Office Professional 2010 Beta has been installed and activated, copy the pkeyconfig-office.xrm-ms file from the following folder to another folder location for safekeeping:%ProgramFiles%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Tip: User who installs 32-bit Office 2010 in 64-bit OS should find the file at %ProgramFiles(x86)%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\ folder. Continue reading “How To – Microsoft Office 2010 RC Activation Hack”
This is a hidden feature on the server, but its one of those options you are able to see on esx, workstation and early versions of vmware server, so here is a method to enable it.
Go to the location where your vmware virtual machines are running, if in linux then more than likely here:
/var/lib/vmware/Virtual\Machines/
Locate the .vmx file of the virtual machine you want to enable VNC on and open it with nano/pico/vi or any editor you want, notepad if under windows.
Add the following lines to the file towards the end of the file:
RemoteDisplay.vnc.enabled = "TRUE"
RemoteDisplay.vnc.password = "password"
RemoteDisplay.vnc.port = "5900"
Change the password to whatever you need it to.
Notice if you enable VNC on more than 1 Virtual Machine then make sure the port is always different on all of them.
Now launch your favorite VNC Client such as RealVNC and connect to the IP address of the server (not the virtual machine).
By default these versions of Microsoft Exchange have a limitation of 16GB per Database, if you have problems trying to mount the database you have to make sure you defrag it then do this reghack to increase the size by 1GB temporarily.
- Click Start, click Run, and then type regedit.exe. Locate the following key in the registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\NameOfServer\Private-
- Make a DWORD Value Entry called: “Temporary DB Size Limit Extension”
- Change the hex value from 0 to 1.
Whatever you do dont upgrade your current PHP 5.2 to 5.3 as it will mess up Apache on Plesk.
If you do this by mistake then make sure you downgrade PHP to 5.2 (yum downgrade php).
But note that this might remove plesk components, so you might end up reinstalling plesk.
God mode. A term usually reserved for games of all shapes and sizes, with the coolest being Rise Of The Triad’s god mode, it has now found its way to the world of operating systems. Someone has discovered that Windows 7 has a god mode – but it’s not what you think it is.
I’ve been searching my bum off trying to find the origin of the story, and as far as I can tell, Carsten Knobloch is the first to make a mention of this way back on December 12, 2009. For some arbitrary reason, it only started exploding all over the web the past few days.
Basically, god mode creates a folder which contains all the various search results strings (if that makes any sense) that pop up when you search using the search field in the Control Panel. These strings are used to make it more “natural” to search for settings in Windows (try it).
Enabling god mode is quite easy:
- Create a new folder
- Name it:
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} - That’s it
This creates a folder which more or less gives you categorised access to each and every setting in Windows – at least, each and every setting that is accessible as a search string – 265 settings in 50 sections. This could be handy if you’re setting up a machine for the first time and need to access many settings.
An important note needs to be made about Windows Vista. While this trick is safe for all versions of Windows 7 (both 32bit and 64bit), the situation for Vista is different. Windows Vista 32bit users can use this trick, but Vista 64bit users can not. It will cause your system to enter an Explorer crash loop. If this happens to you, boot into a Safe mode command prompt, navigate to the god mode’s parent folder, and execute rd /s God[Tab].
Continue reading “Activate God-Mode on Windows 7″
This was very tricky to get to work, but I was forced into changing to VirtualBox since VMWare Server 2.0.2 is being completely anoying on the server (crashing due to glibc).
OK so first of all make sure you have python26 installed on your server:
- rpm -Uvh http://yum.chrislea.com/centos/5/i386/chl-release-5-3.noarch.rpm rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-CHL
- yum install python26 Django python26-devel.i386 python26-libs.i386 python26-setuptools-devel.noarch python26-setuptools.noarch python26-tools.i386 python-simplejson python26-simplejson
Then download virtualbox:
- wget http://download.virtualbox.org/virtualbox/3.1.2/VirtualBox-3.1-3.1.2_56127_rhel5-1.i386.rpm
Now we install it:
- rpm -Uvh VirtualBox-3.1-3.1.2_56127_rhel5-1.i386.rpm
Once installed we go ahead and install the API:
Download the VirtualBox SDK from: http://download.virtualbox.org/virtualbox/vboxsdkdownload.html
- wget http://download.virtualbox.org/virtualbox/3.1.2/VirtualBoxSDK-3.1.2-56127.zip
- unzip VirtualBoxSDK-3.1.2-56127.zip
- export VBOX_INSTALL_PATH=/usr/lib/virtualbox/
- python26 vboxapisetup.py install
Download VBoxWeb:
- yum install mod_dav_svn subversion
- svn checkout http://vboxweb.googlecode.com/svn/trunk/ vboxweb-read-only
- cd vboxweb-read-only
Run VBoxWeb:
- python26 VBoxWebSrv.py adduser username password
- python26 VBoxWebSrv.py
On a browser nagivate to http://ipaddress:8080
Login with the username and password you set on the previous line.
There is currently a problem on CentOS where if you have vmware server 2.0.2 installed and have decided to upgrade/update the system, then it would have updated the glibc libraries.
Vmware server uses the glibc libraries and the new ones seem to be incompatible with the server which will make vmware-hostd crash your virtual machines.
By looking at the log of a crash you will see something like:
Jan 07 12:48:21.316: vmx| SymBacktrace[16] 0xbf92dfb8 eip 0×80504ef in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0×8048000
Jan 07 12:48:21.316: vmx| SymBacktrace[17] 0xbf92e028 eip 0×99ee9c in function __libc_start_main in object /lib/libc.so.6 loaded at 0×989000
Jan 07 12:48:21.316: vmx| SymBacktrace[18] 00000000 eip 0×804d3d1 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0×8048000
Jan 07 12:48:21.316: vmx| Msg_Post: Error
Jan 07 12:48:21.316: vmx| [msg.log.error.unrecoverable] VMware Server unrecoverable error: (vmx)
Jan 07 12:48:21.316: vmx| Unexpected signal: 6.
Jan 07 12:48:21.316: vmx| [msg.panic.haveLog] A log file is available in “/var/lib/vmware/Virtual Machines/WinMail-01/vmware.log”. [msg.panic.requestSupport.withLog] Please request support and include the contents of the log file. [msg.panic.requestSupport.vmSupport.windowsOrLinux]
Jan 07 12:48:21.316: vmx| To collect data to submit to VMware support, select Help > About and click “Collect Support Data”. You can also run the “vm-support” script in the Workstation folder directly.
Jan 07 12:48:21.316: vmx| [msg.panic.response] We will respond on the basis of your support entitlement.
Jan 07 12:48:21.316: vmx| —————————————-
Jan 07 12:48:21.416: vcpu-0| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.420: mks| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.424: Worker#13| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.424: Worker#7| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.425: Worker#0| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.425: Worker#8| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.425: Worker#1| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.425: Worker#11| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.425: Worker#4| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.425: Worker#3| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.425: Worker#17| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.425: Worker#14| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.425: Worker#2| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.427: Worker#9| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.427: Worker#16| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.427: Worker#15| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.428: Worker#12| VTHREAD watched thread 4 “vcpu-0″ died
Jan 07 12:48:21.428: Worker#6| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.428: Worker#10| VTHREAD watched thread 0 “vmx” died
Jan 07 12:48:21.428: Worker#5| VTHREAD watched thread 0 “vmx” died
To fix this or at least to get around it, you can try the several workarounds:
Manually removing rootkit-based malware can be extremely difficult. You can’t delete the offending Registry entries because the malware process is running. You halt the malware process, but Windows restarts the malware before you can delete the Registry entries. Many rootkits also set the Registry entries’ owner to someone other than the user, thus complicating things further.
To fairly easily remove rootkits by hand, boot the infected computer with a Windows distribution CD. Use the repair option’s command line interface to delete the malware executable file. Then, at your leisure, delete the offending Registry entries and data files.
