Nahwan Erlingga Blogs

You are no doubt reading this article because you’ve looked in task manager and wondered what on earth all those rundll32.exe processes are, and why they are running… So what are they?

Explanation

If you’ve been around Windows for any amount of time, you’ve seen the zillions of *.dll (Dynamic Link Library) files in every application folder, which are used to store common pieces of application logic that can be accessed from multiple applications.
Since there’s no way to directly launch a DLL file, the rundll32.exe application is simply used to launch functionality stored in shared .dll files. This executable is a valid part of Windows, and normally shouldn’t be a threat.

Note: the valid process is normally located at \Windows\System32\rundll32.exe, but sometimes spyware uses the same filename and runs from a different directory in order to disguise itself. If you think you have a problem, you should always run a scan to be sure, but we can verify exactly what is going on… so keep reading.

Using Windows Vista’s Task Manager
One of the great features in Windows Vista’s Task Manager is the ability to see the full command line for any running application. For instance, you’ll see that I have two rundll32.exe processes in my list here:

If you go to View \ Select Columns, you’ll see the option for “Command Line” in the list, which you’ll want to check.

Now you can see the full path for the file in the list, which you’ll notice is the valid path for rundll32.exe in the System32 directory, and the argument is another DLL that is actually what is being run.

If you browse down to locate that file, which in this example is nvmctray.dll, you’ll usually see what it actually is when you hover your mouse over the filename:

Otherwise, you can open up the Properties and take a look at the Details to see the file description, which usually will tell you the purpose for that file.

Once we know what it is, we can figure out if we want to disable it or not, which we’ll cover below. If there isn’t any information at all, you should either Google it, or ask somebody on a helpful forum.
Using Process Explorer on Vista or XP
Instead of using Task Manager, we can use the freeware Process Explorer utility from Microsoft to figure out what is going on, which has the benefit of also working in Windows XP.
Simply launch Process Explorer, and if you are using Vista you’ll want to choose File \ Show Details for All Processes.

Now when you hover over the rundll32.exe in the list, you’ll see a tooltip with the details of what it actually is:

Or you can right-click, choose Properties, and then take a look at the Image tab to see the full pathname that is being launched, and you can even see the Parent process, which in this case is the Windows shell (explorer.exe), indicating that it was likely launched from a shortcut or startup item.

You can browse down and view the details of the file just like we did in the task manager section above. In my instance, it’s a part of the NVIDIA control panel, and so I’m not going to do anything about it.
Disabling the Process
Depending on what the process is, you won’t want to necessarily disable it, but if you would like to, you can type msconfig.exe into the start menu search or run box and you should be able to find it by the Command column, which should be the same as the “Command line” field we saw in Process Explorer. Simply uncheck the box to prevent it from starting automatically.

Sometimes the process doesn’t actually have a startup item, in which case you’ll likely have to do some research to figure out where it was started from. For instance, if you open up Display Properties on XP you’ll see another rundll32.exe in the list, because Windows internally uses rundll32 to run that dialog.

Are you looking for a way to quickly convert a movie for your iPhone, PSP, or Android device without messing with confusing settings and options?  Today, we’ll look at a simple way to convert your video files with Miro Video Converter.
We’ve previously covered how to convert videos to 3GP for mobile phones with Pazera, and today we take a look at how to convert them for several different mobile devices with Miro Video Converter. We’ll be using Windows 7 in our examples, so your screen may look slightly different.
Installation
Installation is straightforward. You can find the link below.

When you open the Miro Video Converter you’ll notice instantly that the interface could not be much simpler.

Essentially all the instruction you need to use Miro Video Converter are displayed for you on the interface. To begin, just drag and drop your video file onto the designated area or click choose a file to browse for your selection.

Next, select your output or device from the drop down list.
 
If you select iPhone or one of the other Apple devices, you’ll have the option to Send to iTunes. This will automatically add your video to your iTunes Library when finished.

Then just click Convert.

While your video is being converted, you can track the conversion process on progress bar. Conversion times will vary depending on hardware and file size, but we found converting 700 MB to 1 GB files took between 15-20 minutes.

You final video will be output in the same directory as your original file. Miro will append the chosen format to the output filename. For example, when converting Friday.avi for the Droid, the final output file will be Friday.droid.mp4.
 
Now just transfer your video to your device and you’re ready to go.
 
Conclusion
When we first tested Miro Video Converter we found the audio output to be rather poor, but in their latest version (2.4) the audio issues have improved. While Miro gets the job done quick and easy, it’s not without it’s drawbacks. You’re likely to find yourself with a larger file size in exchange for speed and ease of use. In addition, there is no way to process more than one file at a time and you can’t convert directly from a DVD.

Miro Video Converter is available for both Mac and Windows

Download Miro Video Converter

ref : howtogeek

Interested in Android but think you need to buy a new phone to try it out? Actually, your Windows Mobile phone may already have the capability of running Android. Today we show you how and the type of phone you’ll need.

Installing Android
To run Android you will need a microSD card that is not SDHC (typically a card less than 2GB) and a supported Windows Mobile phone (see below). You can check your microSD card compatibility by looking at the card to see if it shows the “HC” label.

The microSD card will need to be formatted in FAT32. Plug the microSD card into the computer and right click on it and choose format.
Note: Formatting a microSD drive will erase everything on that drive. Make sure you have any important files backed up before you format it.

Now that the microSD card is formatted, the first step to installing Android is finding the right Android port for your phone (see below). You will need to find the port that works on your phone as well as the version of Android you want to run. Versions start at 1.0 but typically you will find ports for version 1.6 or 2.1.

Once you have found the right port for your phone and Android version you want to use, extract the files to a folder using 7-zip.

After the files have extracted there should be a folder called “andboot”. Go into the andboot folder and there will be another folder called “startup config” or “startup”. Open this folder and you will need to find the right startup.txt file for your phone. Inside each folder will be a single “startup.txt” file. Copy the file for your phone model to the root of the andboot folder. This file will tell Android what type of hardware you have, how big your screen is, how much RAM your phone has etc. so it is very important to choose the right file. If you are confused on what these phone names are please read below on finding your phone model.

Once you have moved the correct startup.txt file to the andboot folder, copy the entire andboot folder to the root of your newly formatted microSD card.
Plug the microSD card back in the phone and open the file browser on your phone and browse to the memory card. Make sure the phone is plugged into power before the next few steps because on some phones running on battery may cause the phone to hang.

Open the andboot folder and run haret.exe. If the right startup.txt file is in the root of the andboot folder you should be able to click “Run” and you will get a quick loading screen while haret turns off Windows Mobile and starts up Android.

You should get some scrolling text and probably a nice Android logo while the phone boots up the first time.
Note: The first boot is going to take a considerably longer time than subsequent boots. and you may need to calibrate your screen during the boot process so make sure you keep an eye on it.

Once the basic Linux settings are done your new “Android” phone will boot to a welcome screen so you can walk through the rest of the settings like setting up your email account.
Tip: If you are running Android on a phone that does not have an active data plan but does have wifi, you can get around the startup screen by tapping on the welcome screen in this order: top left corner, top right corner, bottom right corner, bottom left corner then tap the Android logo. You can then enable wifi and join a network and set up your gmail account manually.

It is usually recommended that you leave your phone alone while it syncs your information for at least 10 minutes. Once the initial syncing is done the phone should start running faster and you can play around with installing apps. If you don’t wait for the phone to fully sync you may have problems with apps crashing prematurely and a force close dialog popping up.

Change any settings and install any apps you want, they will be saved to your memory card and ready on next boot. All phones that run Android from the microSD card will automatically boot Windows Mobile when the phone restarts. To run Android again, just open the file browser and run haret.exe again.

Android Ports
There are a few different Android ports for Windows Mobile devices and each one supports a different family of device; each family of device has a varying amount of hardware support. Most phones will support the touch screen, hardware buttons, cell phone radio, and data connection, but some ports may not support bluetooth, GPS, or power management. This is not a complete list of Android ports available, but it should cover the most popular Windows Mobile phones.

Would you like to test drive the latest version of Google’s Android OS without buying a new mobile device?  Here’s how you can run Android on your PC for free with the Android SDK Emulator.
Android is the latest mobile OS to take the world by storm, but everyone doesn’t have access to the latest mobile devices.  Thankfully, there’s an easy way to run Android on your Windows, Mac, or Linux computer.  Google provides an Android emulator with their SDK, which is designed to let developers test their apps on Android before running them on handsets.  We can use this to test drive Android on our computer, here’s how to do it.
Getting Started
The Android Emulator requires Java to run, so if you don’t already have Java installed on your computer, download it from the link below and install as normal.

Note: When installing Java, make sure not to install any crapware it tries to sneak in like the worthless Yahoo toolbar.

Then, download the Android SDK from Google (link below), and make sure to select the correct version for your computer.  Once it’s downloaded, unzip the files as normal.

In Windows, run the SDK Setup.exe program to get started running Android on your PC.

The SDK will check Google’s servers for available packages.

If you see an SSL error message, click the Settings tab on the left in the SDK and AVD Manager window that opened in the background.  Here, uncheck the Force https box, click Ok, and then reopen the setup.

Now, the Package Installer will open.  You can choose what you want to install, and then click Install to begin installing the Android emulator on your computer.

By default, all of the SDK platforms, samples, and APIs will be selected for install.  This can take quite a while to download, as several versions of Android are currently available.  If you only want to play around with Android, choose the version you want.  You’ll want the SDK Platform Android your.version.  Then click the Reject bullet on all the other entries, and click Install.  We wanted to try out the latest Android 2.2 as well as the older 1.5, so we downloaded both of them.

Once you’ve started installing, you’ll see a window showing the download and installation progress.  This may take a few minutes, depending on your Internet speed.

You’ll have some little Androids in your taskbar, but unfortunately they don’t show the download progress.

Setup an Android Emulator
Once the download is completed, you can setup an emulator to test drive Android on your computer.  Select the Virtual Devices from the left menu, and then click the New button on the right.

Enter a name for your virtualized Android, and select the version of Android you want to use from the drop-down menu.  This will only show the version you installed previously, so you may only see one version listed depending on your selection.

Enter a size under the SD Card entry; this is a virtual SD card that’s actually an IMG file that Android will use to store your settings and files in.  Then, select a screen size from the skin options.  The default is a standard, Nexus One-type display, while the others are different sizes including even a BlackBerry-style device.

Click Create AVD when you’re finished.

The program may appear to freeze while it is creating the AVD, so just wait until you see the confirmation window.

You’re now ready to run Android on your PC!  Select your new virtual Android, and click Start on the right.

You can choose to scale the display if you’ve chosen a larger screen size than your monitor will fit, and then select Launch.

Android will now begin to load in your emulator.  Several command prompt windows may open, and then you’ll see the emulator itself.  Notice that the default, large screen size will display a keypad and virtual buttons on the right side of the emulated device.

Android may take several minutes to load, especially on your first run.  After a while, the boot screen will switch to an Android boot animation.

Finally, you’ll be presented with your new Android home screen!  Use your mouse as you would normally, though remember that you don’t need to double-click to open apps.

You can open pre-installed apps from the launcher menu, though unfortunately these emulator images do not include the Android Marketplace.

View your favorite websites in the browser, and they will render just as they would on an Android device.  Note that you can enter text using the on screen keyboard in the emulator, or with your standard keyboard.  Since this is an emulator, you may notice some lag in entering text.

You can also install Apps that are directly available online.

Default apps such as Email work great, and you can even see most of the device settings in Android.

Click and hold on the home screen to change the background or try out widgets.

You’ll even see the nifty Android Lock screen if you leave your virtual machine alone for a few minutes.  Just click the arrow and drag it to the other side of the screen to unlock.

You can always repeat the steps later to create a new Android virtual machine.  Here we’ve created an Android 1.5 virtual machine with the QVGA screen size.

We did experience a few crashes in our tests, and the emulator felt somewhat sluggish, but in all, it’s fun to try  out a new mobile OS without spending money on a new phone.

Launch Android Virtual Machines Later
Anytime you want to launch your Android virtual machines in the emulator, just run the SDK Setup.exe as before, and select them from the Virtual Devices list.  Alternately, you can launch an emulator directly from the command line.  To do this, browse to your Android SDK folder and open the Tools folder.  Press the Shift key and right-click, and then select Open Command Window Here.

Now enter the following in the Command Prompt, substituting the name of your Android virtual machine for your_device:

emulator @your_device