Pages

123

January 19, 2011

Windows XP hidden apps


To run any of these apps go to Start > Run and type the executable name (ie charmap).

WINDOWS XP HIDDEN APPS:
=========================================


1) Character Map = charmap.exe (very useful for finding unusual characters)

2) Disk Cleanup = cleanmgr.exe

3) Clipboard Viewer = clipbrd.exe (views contents of Windows clipboard)

4) Dr Watson = drwtsn32.exe (Troubleshooting tool)

5) DirectX diagnosis = dxdiag.exe (Diagnose & test DirectX, video & sound cards)

6) Private character editor = eudcedit.exe (allows creation or modification of characters)

7) IExpress Wizard = iexpress.exe (Create self-extracting / self-installing package)

8) Microsoft Synchronization Manager = mobsync.exe (appears to allow synchronization of files on the network for when working offline. Apparently undocumented).

9) Windows Media Player 5.1 = mplay32.exe (Retro version of Media Player, very basic).

10) ODBC Data Source Administrator = odbcad32.exe (something to do with databases)

11) Object Packager = packager.exe (to do with packaging objects for insertion in files, appears to have comprehensive help files).

12) System Monitor = perfmon.exe (very useful, highly configurable tool, tells you everything you ever wanted to know about any aspect of PC performance, for uber-geeks only )

13) Program Manager = progman.exe (Legacy Windows 3.x desktop shell).

14) Remote Access phone book = rasphone.exe (documentation is virtually non-existant).

15) Registry Editor = regedt32.exe [also regedit.exe] (for hacking the Windows Registry).

16) Network shared folder wizard = shrpubw.exe (creates shared folders on network).

17) File siganture verification tool = sigverif.exe

18) Volume Contro = sndvol32.exe (I've included this for those people that lose it from the System Notification area).

19) System Configuration Editor = sysedit.exe (modify System.ini & Win.ini just like in Win98! ).

20) Syskey = syskey.exe (Secures XP Account database - use with care, it's virtually undocumented but it appears to encrypt all passwords, I'm not sure of the full implications).

21) Microsoft Telnet Client = telnet.exe

22) Driver Verifier Manager = verifier.exe (seems to be a utility for monitoring the actions of drivers, might be useful for people having driver problems. Undocumented).

23) Windows for Workgroups Chat = winchat.exe (appears to be an old NT utility to allow chat sessions over a LAN, help files available).

24) System configuration = msconfig.exe (can use to control starup programs)

25) gpedit.msc used to manage group policies, and permissions
EnjOy .. :)
MamoOn..

January 16, 2011

How To Increase Download Speeds By 100-200 Kbsec!!!!


First of all download this wonderful program:

http://www.speedguide.net/files/TCPOptimizer.exe

Then when u start da program goto settings and thn goto cable modem or dsl whatever u have.

Go to MaxMTU and set it to 1500 this is optimal anything above this will not work as well.

Thats bout it!! Enjoy the speed!!
MamoOn..

January 15, 2011

Windows XP Shut Down and Automatic Reboot Problems



Well, that is annoying, isn't it? Let's look at what can cause the problem, and point Mr. Herman to a solution. There are three basic sources of automatic reboot problems:

Recovery settings

Software incompatibilities, including driver issues

BIOS problems

Here's a tip about searching the Microsoft Knowledge Base for information on the automatic reboot problem: Microsoft rarely, if ever, refers to a “reboot” in their Knowledge Base articles, so searching for that will yield little. Try searching with “restart” or “restarts” instead.

Recovery Settings

One of the things that is quite different about Windows XP compared to Windows 9x (9x is shorthand for Windows 95, Windows 98, and Windows Me in all their various versions), is that one can control how it responds to certain critical errors—those that cause the infamousBlue Screen of Death (BSOD). In Windows XP, the default setting is for the computer to reboot automatically when a fatal error occurs. If that fatal error only occurs when you're shutting down, the system reboots automatically.

If you haven't changed any of the system failure settings, you should be able to see the error by looking in the Event Log. But a better long-term solution is to turn off the automatic reboot so you can actually see the error when it happens—chances are it will tell you enough about itself to let you troubleshoot further. To change the recovery settings to disable automatic rebooting:

1.

Right-click My Computer, and then click Properties.

2.

Click the Advanced tab.

3.

Under Startup and Recovery, click Settings to open the Startup and Recovery dialog box.

4.

Clear the Automatically restart check box, and click OK the necessary number of times.

5.

Restart your computer for the settings to take effect.

Now when you go to shut down and a fatal error occurs, you'll at least see it and it won't cause an automatic reboot. You still have to sort out what's causing the problem, but that gets us to the next section quite nicely.


Software Incompatibility

The most common cause of a fatal error or BSOD is a software or driver problem, and troubleshooting these can be tricky. The mechanism for troubleshooting, however, is pretty much the same for any problem on a PC. The first thing to look at is what's changed—what new software program or driver have you added, usually just before the problem started. This sounds easy and it often is, but if it's something you've lived with for a while, you'll often have no idea what the proximate cause is. When you do, it's a lot easier. When you don't, you need to do a bit of research to find out if there is a specific cause for the particular error message you're getting (when you have one) or a known issue with certain programs or drivers that causes the behavior you're seeing. In the case of automatic reboots, even when you've selected a shutdown, a search of the Microsoft Knowledge Base turns up Windows XP Restarts When You Try to Shut Down Your Computer, which points to a known problem with Roxio's Easy CD Creator 5.0 and Windows XP. And, sure enough, a check of the Roxio Web site shows that there's an update from them for Windows XP. Here's a suggestion—in my experience, solving problems with CD-writing software requires one to follow the outlined steps exactly. Many of us have installed numerous programs, patches, and drivers over the years and think we know what to do. For most things, we probably do. However, I've been a happy user of Easy CD Creator since version 2 and if there's one thing I've learned the hard way, it's the need to follow their instructions exactly when doing an update.

I don't want to pick on Roxio, though. I like their software and always have. You should always read the instructions for installing a driver or patch carefully and follow them exactly whatever the source it's just smarter.

So, is Easy CD Creator the only program that will cause this problem? Probably not, it just happens to be the only one I managed to find searching the Knowledge Base. But the Knowledge Base is by no means complete. If you don't find what you're looking for there, it's often a good idea to ask on the newsgroups. Often someone else has had a similar problem and will offer a solution. And it's always a good idea to check for updates to any of your critical hardware drivers on the manufacturer's Web site, although Windows Update helps keep you up to date.

BIOS Problems

Finally, the last and often trickiest to troubleshoot source of reboot problems: your computer's BIOS. If there is a problem in your BIOS, or sometimes even in the firmware for one of the other pieces of hardware installed in your machine, it could cause an instability and lead to one of those automatic restarts that we talked about in the first section. Especially if the problem is in the Advanced Configuration and Power Interface (ACPI) portion. The good news is that these problems are much less common than they used to be in the bad old days. But it never hurts to check with your computer manufacturer to see if there's an updated BIOS available.

EnjOy.. :))

MamoOn..



Firefox Crash Problem Solved

Processed reports are given a crash "signature" which is often indicative of what caused the crash. Because there are so many possible causes for crashes, the best way to get help is to post your crash signature in the forum or live chat.

In the Firefox Location bar, go to about:crashes. A page listing crash reports that you've submitted will appear.

  1. Click on the latest crash under Report ID.

    24c48a8c02ecf64e07dba246c5405b30-1246117331-677-1.jpg
  2. You will be taken to a page on crash-stats.mozilla.com, saying that "Your report is being processed". When it is finished processing your report, the crash signature will appear under the ID. (e.g. nsCrasher::Crash())

    24c48a8c02ecf64e07dba246c5405b30-1246117331-677-2.jpg
  3. In the top right corner of the page, click on Search Mozilla Support for Help to search for Support articles that match the crash signature.

    215010f38dee6bf3a51e3a5762269101-1279968843-822-2.png

When you go to Ask a question about your crash, it's important to provide your crash signature in the forum topic or live chat question. That way, our volunteers will be able to provide help that is specific to your circumstances and you can get help much faster.

EnjOy.. :)

MamoOn..

January 13, 2011

Chat with ur friends through Ms-dos command

1) All you need is your friend's IP Address and your Command Prompt.

2) Open Notepad and write this code as it is.....!

@echo off
:A
Cls
echo MESSENGER
set /p n=User:
set /p m=Message:
net send %n% %m%
Pause
Goto A

3) Now save this as "Messenger.Bat".

4) Open Command Prompt.

5) Drag this file (.bat file) over to Command Prompt and press Enter.

6) You would then see something like this:

7) Now, type the IP Address of the computer you want to contact and press enter
You will see something like this:

8) Now all you need to do is type your message and press Enter.
Start Chatting.......!

EnjOy :))
MamoOn..

How To Remove Windows Genuine notification error

Following three simple steps now you can get rid of the buggy Windows Genuine Advantage (WGA) notifications:

You should backup up the registry , in case somethiong goes wrong.

1. Reboot Windows in sa

fe mode (hold the f8 key while booting and you will get the option to boot in safe mode) and then:

2. Open Registry Editor (regedit.exe) and search for wgalogon folder and delete it.

3. In your windows directory search for files wga* and delete them.

You are done!Now reboot back normally and continue your work. Windows Genuine Advantage wil

l not affect you anymore …

EnjOy..
MamoOn..