Friday, August 22, 2008
Shutting Down Windows XP
Although the big argument used to be about saturated and unsaturated fats, today's generation has found a new source of disagreement: Should a computer be left on all the time or turned off at the end of the day? Both camps have decent arguments, and there's no real answer (except that you should always turn off your monitor when you won't be using it for a half hour or so).
However, if you decide to turn off your computer, don't just head for the off switch. First, tell Windows XP about your plans. To do that, click the Start button, choose the Turn Off Computer command, and ponder the choices Windows XP places on-screen.
Click Stand By to temporarily put the computer to sleep, click Turn Off to turn off your computer, or click Restart to make Windows XP shut down and come back to life.
Stand By: Save your work before choosing this option; Windows XP doesn't save your work automatically. Instead, it lets your computer doze for a bit to save power, but the computer wakes up at the touch of a button.
Turn Off: Clicking here tells Windows XP to put away all your programs and to make sure that you've saved all your important files. Then it turns off your computer and most of the newer monitors. Poof! Use this option when you're done computing for the day. (If your monitor doesn't turn off automatically, you'll have to push its power button yourself.)
Restart: Here, Windows saves your work and prepares your computer to be shut off. However, it then restarts your computer. Use this option when installing new software, changing settings, or trying to stop Windows XP from doing something awfully weird.
Hibernate: Only offered on some computers, this option works much like Shut Down. It saves your work and turns off your computer. However, when turned on again, your computer presents your desktop just as you left it: Open programs and windows appear in the same place. Putting your computer into hibernation mode is not as safe as shutting it down. (Don't see the Hibernate feature? Hold down Shift, and it will replace the Standby button.)
The Hibernate command takes all of your currently open information and writes it to the hard drive in one big chunk. Then, to re-create your desktop, it reads that big chunk and places it back on your desktop.
Don't ever turn off your computer unless you've chosen the Turn Off command from the Start button. Windows XP needs to prepare itself for the shutdown, or it may accidentally eat some of your important information — as well as the information of anybody else using the computer at the time.
Remember, if you're done with the computer but other people might want to use it, just click Log Off from the Start menu: Windows XP saves your work and brings up the Welcome screen, allowing other people to log on and play video games.
Thursday, August 21, 2008
Mega Shutdown and Restart Troubleshooting Guide
Thus far, Windows XP shutdown issues most resemble those of Windows Millennium Edition. That is, most of them center around a very few issues, especially driver version and other legacy hardware and software compatibility issues. These are detailed below. The driver and software issues are expected to resolve substantially as hardware and software manufacturers release updated versions, now that Win XP has been officially launched.
Reboot Instead of Shutdown
The majority of shutdown problems reported with Windows XP thus far have been that it reboots when shutdown is attempted. This may be a global symptom emerging from several distinct causes, because XP executes an automatic restart in the event of a system failure. I'm guessing that this means that more or less anything compromising the operating system during the shutdown process could force this reboot. If this is true, then our job will be to prepare a series of steps suitable to isolate the most likely cause. Disabling the "restart on system failure" feature may permit the exact cause to be isolated:
Right-click on My Computer and select Properties. Click the Advanced tab. Under 'Startup & Recovery,' click Settings. Under 'System Failure,' uncheck the box in front of 'System reboot.'
Some things that have produced this reboot-instead-of-shutdown symptom are:
" By now, Roxio's Easy CD / Direct CD software is well documented as being a major cause - possibly the major cause - of this undesirable shutdown behavior. On November 1, Roxio released new drivers to solve this problem in Easy CD Creator 5 Platinum in its Windows XP updater for the Platinum product. A fix for Easy CD Creator 5 Basic is in the works. In the first few hours of its release, several peple have written me saying that this fix has resolved their Windows XP shutdown problem. I suspect that <>of the Windows XP shutdown problems will go away with Roxio's release of this patch for Platinum and the pending patch for Basic. This has been the single most common cause of Win XP shutdown problems thus far. One person after another has written to me with the simple message that this reboot behavior went away as soon as they uninstalled Easy CD. HINT No. 1: PCBUILD subscribers, by trial and error, identified the file CDRALW2K.SYS (version 1.0.0.1048) as the Roxio file that was causing his shutdown problems and error conditions. When he deleted this one file, his problems went away. HINT No.2: The Mystic Overclocker and others have reported that installing Easy CD 5.0 does not cause the shutdown problem, provided they do not install the Direct CD component. Though this isn't universally true, enough people have mentioned it by now for me to suggest it as a work-around.
Unassigned Device Drivers
PCBUILD subscribers have found that Windows XP won't shutdown properly if unsigned device drivers are used. Since all necessary device drivers have not yet been created for Win XP, this will be a problem for the next few months. It resembles the pattern for Win ME shutdown problems, because even today, many hardware manufacturers have not prepared suitable drivers for use with ME.
SBLive: DEVLDR32.EXE PROBLEMS
In the early days of Win ME, one of the biggest culprits for shutdown issue was the Creative Labs SoundBlaster Live. History repeated itself in the early stages of Win XP. This now has been fixed for some users (but not for all) by the release of new drivers.
Here's the commonly reported scenario: On attempting shutdown, nothing at all appears to happen for a prolonged period of time. Eventually, an "End Task" window appears wanting to terminate DEVLDR32.EXE. No matter what one does, one ultimately is locked out of shutting down other than by a power switch shutoff. (This problem exists with the SBLive in Windows 2000 also.)
In mid-July, Microsoft posted new Win XP drivers for the SBLive on the Windows Update site. According to PCBUILD subscribers, these drivers solve the shutdown problem the SBLive was causing. I recommend you go to Windows Update and download the new driver if you have an SBLive card. However, some users are reporting that the DEVLDR problem continues to plague them even with the new drivers:
" In the event installing the new drivers does not solve your shutdown problem, try some of the solutions people have been using prior to the release of these new drivers. PCBUILD subscribers have written that they solved the well-documented SBLive/DEVLDR32 problem by downloading and installing the LiveService software. (We caution that one should disable all antivirus software while executing this program. I do recommend that you at least virus-check anything you download first!)
" PCBUILD subscribers" gave another solution to this problem: Uninstall the LiveWare software pack (of which DEVLDR is part). Uninstall the SBLive card. Restart Windows, let it detect the new hardware, and use the Windows XP driver. However, other users have reported that this isn't satisfactory because the XP native driver gives very poor sound quality. If the new drivers work for you, they are definitely the preferred option.
3D PROPHET 4500 VIDEO CARD
Other video cards that have created problems are those based on the Kyro II video chip, such as the Hercules Prophet 4500. PCBUILD subscribers have reported that until they removed the Kyro II / Prophet 4500, they could shutdown, hibernate, or go to stand by just fine, but Restart wouldn't work - it would shutdown Windows instead. Others with this video card have reported this strange behavior on both restart and shutdown.
Apparently, this problem is now solved. Microsoft reports that new drivers for this card, specific to Windows XP, are now available from Hercules. At present, they remain uncertified (PowerVR, who makes the Kyro II chip, is working on that), but they reportedly work just fine. Download the Kyro II drivers here.
SHUTDOWN HANGS ON "SAVING YOUR SETTINGS"
During shutdown or reboot, Win XP may hang (stop responding) at the "saving your settings" screen. During such a hang, there is no response to Ctrl+Alt+Del; the mouse may or may not work. (The problem may be intermittent.)
This is a known bug in Windows XP, for which Microsoft has a supported fix. Because this patch is scheduled for further quality assurance testing in the future, Microsoft only recommends that you install it if you have a serious problem; otherwise, they recommend waiting for Service Pack 1, which will include the more permanent version of the fix. To learn how to get this patch, see Windows XP Stops Responding (Hangs) During Windows Shutdown.
As a workaround, we resolved this problem by dismantling the Windows XP logon Welcome screen. In the Control Panel, click User Accounts, then click "Change the way users log on or off." Uncheck the box that says "Use the Welcome screen." This removes the initial logon screen with individual icons for each user and, instead, pops up the classic logon prompt that requires each user to type a user name and password.
"ShutMeDown" REGISTRY PATCH
Download the "ShutMeDown" Registry patch. Please follow sensible Registry editing protocol. Backup your Registry before the change (or run System Restore to create a restore point). This is not the appropriate fix for most machines, but does help a significant number. After installing, test Windows shutdown. If the fix does not work for you, remove it by restoring the Registry to its prior state.
For those who want a little more background information, the fix provided by this patch is based on a Microsoft Knowledge Base article Q155117 for Windows NT 4.0. It apparently still works in NT 5.1; that is, in Windows XP.
Stop Erros messages at shutdown
Some users have gotten an error message similar to the following when attempting either to shutdown or restart Win XP:
STOP 0000009F, DRIVER_POWER_STATE_FAILURE
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
TechNet and the Microsoft Knowledge Base have numerous articles discussing this type of error condition; for example, these. As a review of these articles will show, these are commonly device driver problems, but may also be caused by troublesome software (such as the notorious CrashGuard), or a problem in a system service. MSKB article Q262575 discusses a shutdown problem of this type, known to exist in Windows 2000 due to a resource (IRQ) conflict, if you have PACE Interlok anti-piracy software installed. This problem may occur in Windows XP as well.
Try the following as one approach to these problems: Restart the computer. Press F8 during the restart and select "Last Known Good Configuration." If you catch the problem when it first occurs (meaning you likely have installed only one or two drivers or new service), this will return you to a previous working condition.
It has been reported by a PCBUILD Subscriber that these STOP code error message occur when Windows XP is trying to shut down devices. He says that he has seen this twice: once with Logitech Quickcam installed (with an unsupported driver), and once with a USB DSL modem that would hang if it wasn't disconnected before shutdown.
Shutdown Works but its real slow
If it appears that Win XP is not shutting down, give it some time. Some users have reported a minute or longer for shutdown to visibly start. Thus far, it appears that this is a consequence of software that is running when shutdown is attempted, and it also may have something to do with particular hardware. If you are experiencing this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
One specific solution for this can be found: In Control Panel | Administrative Tools | Services. (You can also get this by launching SERVICES.MSC from a Run box. This utility is also built into the Computer Management console.) Stop the Nvidia Driver Helper service. Many other newsgroup participants quickly confirmed that this solved this "extremely slow shutdown" problem for them.
Powerdown Issues
"Powerdown issues" are quite distinctive from "shutdown issues." I define a shutdown problem as one wherein Windows doesn't make it at least to the "OK to shut off your computer" screen. If Windows gets that far, or farther, then it has shut down correctly. However, the computer may not powerdown correctly after that. This is a different problem, and I encourage people reporting these issues to make a clear distinction in their labeling.
When Windows XP won't powerdown automatically, the APM/NT Legacy Power Node may not be enabled. To enable this, right-click on the My Computer icon, click Properties | Hardware | Device Manager | View. Check the box labeled "Show Hidden Devices." If it's available on your computer, there will be a red X on the APM/NT Legacy Node. Try enabling it and see if this resolves the powerdown problem. (Tip from Terri Stratton.)
This should resolve the powerdown issue in most cases. However, other factors can sometimes interfere with correct powerdown functioning. In that case, consider the following tips:
" If you changing the default power settings in the BIOS, it can lead to a powerdown problem. Restoring all BIOS power settings to default will likely fix it.
PCBUILD subscribers reported that, when the above didn't work , they restored powerdown functioning by disabling his CD-ROM's AutoRun feature. The fastest way to do this is with the "Disable AutoRun" Registry patch which you can download here.
Other Known Issues and Hints
" BIOS UPGRADE. As with every new operating system that comes along - especially one that is as much of a "step up" as Windows XP is from Windows 9x - the recommendation is made to be sure your BIOS is updated. Many people have reported that this has solved their shutdown problems (and had other advantages) with Win XP, just as it has in earlier versions of Windows.
Quick Switching user Accounts
One reported quirk affecting shutdown is the three-account shuffle. Windows XP gives the ability to rapidly bounce between user accounts, with Win+L. If at least three user accounts exist, and you quick-switch through all three, and then log off all three in reverse order - "backing out" in an orderly way - then the machine may hang on shutdown. There may be other variations of account shuffling that cause this, but this one, clear example was provided by newsgroup correspondent John Ward. So far, I have no concrete clue on what may be occurring here.
Make XP boot even Faster
Microsoft has chosen a completely different path for XP and it's boot features by trying to incorporate as much support for newer fastboot BIOSes that are on most current motherboards. They built XP in such a way as to make it able to take advantage of features in these new BIOSes, and one of the coolest things is a small application called bootvis. bootvis.
Bootvis watches everything that loads at boot time, from the moment the OS begins to load just after POST (Power On Self-Test) to the moment you get to a usable Desktop. Some programs, most notably Norton AntiVirus 2002, suck up valuable seconds before you can actually DO anything even though you're at the Desktop. bootvis generates a trace file that you load and can then "see" a visual representation of what's happening. Every file, driver, hard drive read/write, etc., is recorded. You can then use bootvis to optimize the loading of files during the boot sequence. bootvis will rearrange the ways these very files are stored on the hard drive, thereby improving the boot time dramatically.
XP Hibernate Option
Whenever you want to logoff, shut down or reboot your Windows XP machine you have only 3 choices
(1) Standby ONLY IF the ACPI/APM function is properly enabled BOTH in your motherboard's BIOS AND in WinXP!
(2) Restart
(3) Shutdown.
To properly enable Hibernation in WinXP:
Start button -> Control Panel -> Power Options -> Hibernate tab -> check Enable hibernate support box -> Apply/OK -> reboot.
NOTE: If the Hibernate tab is unavailable your computer does NOT support it!
For some reason Microsoft did NOT enable the 4th option:
(4) Hibernate, which should be available on power saving (ACPI) enabled PCs and laptops.
But you CAN bring it back: just hold the Shift key while the Shut down menu is displayed on your screen, and notice the Standby button being replaced by a new, fully functional Hibernate button, which can be clicked with the left button of your mouse.
If you release the Shift key, the Hibernate option will disappear once again, to be replaced by Standby.
Tuesday, August 19, 2008
Win XP Won’t Completely Shutdown
- Goto Control Panel, then goto Power Options.
- Click on the APM Tab, then check the "Enable Advanced Power Management support."
- Shut down your PC. It should now successfully complete the Shut Down process.
How To Enable Hibernation
Under Windows 98, Me, or 2000 there was an option in the shutdown dialog box to enter the computer into hibernation (where all the content of the RAM is copied to the hard disk). The shutdown dialog box of Windows XP doesn't offer any longer the hibernation button. Some users may get confused about how to enable the hibernation mode. If this mode is supported by your motherboard (ACPI) you have to do the following:
1: Click Start and Shut Down,
2: Point the standby button and maintain the shift key pushed,
3: A new hibernation button appears: click it while still holding the shift key: voila your PC will hibernate.
User Accounts and Fast User Switching
Introduction
Windows XP represents Microsoft's big push to get the largely Windows 9X-based user community to an operating system family based on the Windows NT-kernel. In Windows XP, new client services not only blend the ease of use of familiar Windows 9X profiles with the robustness of Windows NT (and Windows 2000) user management, but significantly improve on the combination. While the majority of these advancements will be appreciated most by home users, enterprise customers that share assets-for instance, with shift workers and telecommuters or with users who access e-mail from multiple machines while roaming-will also see improvements.
Many computers are shared between multiple users, particularly in the home environment where studies have shown that 80% of computers are used routinely by multiple people. In previous versions of Windows NT, user account management-which could be strictly enforced across the enterprise by administrators-was a somewhat tricky process that was beyond the abilities of most non-computing professionals. Simple-to-use Windows 9X profiles, however, were not enabled by default and were largely ignored: The cost of actually using the profiles, which required that users log off before allowing other users to access the system, meant that the vast majority of machines made do with a single shared profile, with all of the corresponding security, configuration, and data-loss risks.
In Windows XP, user profiles are always enabled and even non-enterprise users are encouraged to create accounts during the Setup process. These accounts are based on Windows NT profiles and allow Windows XP to provide strong isolation and protection of users' data and settings. If multiple user accounts are configured on a machine, then users are presented with a Welcome screen that appears featuring separate-and customizable-graphics for each user. Users of Windows XP machines that are members of an NT-style domain do not see this screen, since presenting a list of machine users could be considered a security violation. A new control panel applet replaces the familiar Windows NT User Manager and Windows 2000 Computers and Users snap-in, providing a simple interface that allows almost anyone to set up a new user and give them appropriate rights and privileges.
Fast User Switching
Windows XP introduces fast user switching. Undoubtedly, fast user switching is the single most important feature that makes sharing Windows-based computers workable. Using fast user switching, it is not necessary for a user to log off the computer before allowing a second user to access their own account. Instead, the first user's account is "disconnected," which leaves all the programs running; the second user can then log on, and then the users can switch quickly between logged-on accounts. Many accounts can be open simultaneously on one computer, though only one account at a time will be able to interact with the keyboard, screen, and input devices.
In the home environment, for instance, fast user switching allows a parent working on a personal finance program to yield the computer to a child to work on homework by browsing the Internet, without requiring the parent to shut down and restart the finance program and without exposing the child to the parent's financial information. In the business environment, fast user switching can allow multiple users in a common environment, such as a research lab, to share a single machine.
Fast user switching is just one of two mechanisms that allow multiple users to work with a single system. Remote desktop, another built-in Windows XP feature, allows users to interact with machines remotely across a network and to access data and applications on those remote machines. While fast user switching is aimed principally at the home market, remote desktop enables business users to access their corporate desktops from remote computers-and vice versa, enabling them to operate home machines while at work.
Programming Issues
Both fast user switching and remote desktop use Windows XP's updated terminal services technology. Improvements have been made to both the server and client components of terminal services. Windows XP now features support for both local and remote sound, 24-bit video, performance optimizations, and the mapping of the local drives and printers.
Fortunately, most applications don't have to be rewritten to work with terminal services and, thus, fast user switching and remote desktop. Rather, they need to respect basic user settings management guidelines. These guidelines are not new: Most are covered in the Windows 2000 Certified for Windows Application Specification, which has been available on Microsoft's Web site for some time. The Data and Settings Management section of this specification includes several topics that are particularly important when supporting multiple users on a single machine:
· Default to the My Documents folder for storage of user-created data;
· Classify and store application data correctly;
· Degrade gracefully on "Access denied" messages.
Mostly, this means isolating data and settings for each user. And an important step in this direction is to ensure that you are using the HKEY_CURRENT_USER registry key rather than HKEY_LOCAL_MACHINE for storing settings in the system registry. You should also be careful to install programs correctly and to classify and store data correctly. You can use the ShGetFolderPath API to obtain the path of a specific named folder-such as "My Documents" or even "Program Files"-as well as the appropriate directories for storing Roaming, Non-Roaming, and Shared application data. The following are some general guidelines for locating data:
· Profiles\username\Application Data\appname
- Roaming, auto-created user files (e-mail DB, custom dictionaries…)
· Profiles\username\Application Data\Local Settings\appname
- Discardable/local-only user data files (e.g., offline stores)
· Profiles\All Users\Application Data\appname
- Last-resort for local-only, common dynamic data (e.g., log files)
A notable exception to the isolation rule is that you should support "All Users" installations: It is extremely frustrating for users to install the same application repeatedly for multiple user accounts.
By carefully locating user data, user settings, and computer settings, applications can make it easier for users to backup individual documents and settings, share a computer among multiple users, and even to work with the same documents and settings on multiple computers. By handling data and settings properly, you can enable your application to run in both the home (fast user switching) and business enterprise (remote desktop) marketplaces.
Controlling Running Instances
It is common for applications to control their startup so that only a single instance may be running on a machine at any given time. There are many valid reasons for doing this: licensing restrictions, required dedicated access to specific hardware resources, and perhaps even enforcing data integrity. However, with multiple users on the same machine, it might be desirable to allow multiple users-each with their own instance-to work with (for example) a personal finance program as long as their data remains isolated. At this point, the commonly used mechanisms for controlling running instances may exhibit some unwanted side effects when operating under Windows XP's fast user switching or remote desktop.
The most common method for discovering whether another instance is running is to use the FindWindow or FindWindowEx APIs to search for a window that, if your application is running, you know to be open. Somewhat unexpectedly, both of these APIs work in a single user session only. So using this method won't prevent another instance of your application from being started by another user.
A more robust method for controlling multiple instances is to use one of the NT kernel objects: events, semaphores, mutexes, waitable timers, file-mapping objects, and job objects can all be used with Global\ or Local\ prefixes on Windows 2000 and Windows XP. By default, each user (terminal service) session will have its own namespace for kernel objects. By creating a Global\ object-for instance, a mutex or semaphore-when your application is started (and closing it upon exit), your application can detect running instances across multiple user (terminal service) sessions. Of course, you can't just switch to the previous instance: It may be in another session! What typically happens in that case is the user clicks on an icon and then nothing appears to happen (since the app thinks it's located another running instance). At a minimum, you should warn the user that there's another instance running.
What about sound? Well, the terminal services in Windows XP have been designed to configure sound to both the interactive and disconnected sessions. While it may be difficult to imagine at first, there may be valid scenarios where it would desirable to output multiple audio streams. For instance, what if you used a sound card in one user session to output audio to the home stereo system and at the same time the active user wanted to hold an interactive meeting with sound? In this case, you certainly would not want to blend the two streams. And neither would you want to suspend the audio stream in the disconnected session. Getting this right can be particularly important when working with shared media devices like DVD players.
One general guideline is to do "as little as possible, as much as necessary" when you are the disconnected session. To do this, it can be helpful to know when a session switch occurs. While most applications won't need to be notified, if your application accesses a shared resource-such as a serial port or other hardware device-you may want to know when the machine switches between user sessions. To be notified when a session switch occurs, you must register to receive the WM_WTSSESSION_CHANGE message by calling the WTSRegisterConsoleNotification API. Using this function, you can choose to be notified for a single session or for all sessions, and when either local or remote sessions connect or disconnect. When you no longer require notification, you should unregister using the WTSUnRegisterConsoleNotification API.
Summary
If you isolate access to your application's data and settings and take care not to tie up shared resources, your application should work well with Windows XP's terminal services. By developing your application to assume it's not the only thing running on the machine, your users are likely to have a much better experience when they start using it with Windows XP's new fast user switching and remote desktop features.
Slow Shutdown
Some people have noticed that they are experiencing a really slow shutdown after installing Windows XP Home or Professional. Although this can be caused a number of ways, the most clear cut one so far is happening on systems with an NVidia card installed with the latest set of drivers. A service called NVIDIA Driver Helper Service is loading up on start up and for whatever reason doesn't shut itself down properly. The service isn't needed and can also increase the amount of memory available to your system. Here is how to disable it.
1: Go into your Control Panel
2: Select Administrative Tools and then click on Services
3: Right click on the file "NVIDIA Driver Helper Service" and then select STOP.
4: To stop this loading up every time you boot up your PC Right click it again and select properties - then where the option "Startup Type" is shown - make sure it is set at Manual like
For a Safer, faster XP Close Unwanted Services
To disable unneeded startup services for a safer, faster XP, use the "Services" Admin Tool (Control Panel > Administrative Tools > Services). If you are a single user of a non-networked machine, you can disable the following items, with no ill effect.
Alerter
Clipbook
Computer Browser
Fast User Switching
Human Interface Access Devices
Indexing Service (Slows the hard drive down)
Messenger
Net Logon (unnecessary unless networked on a Domain)
Netmeeting Remote Desktop Sharing (disabled for extra security)
Remote Desktop Help Session Manager (disabled for extra security)
Remote Procedure Call Locator
Remote Registry (disabled for extra security)
Routing & Remote Access (disabled for extra security)
Server
SSDP Discovery Service (this is for the utterly pointless "Universal P'n'P", & leaves TCP Port 5000 wide open)
TCP/IP NetBIOS Helper
Telnet (disabled for extra security)
Universal Plug and Play Device Host
Upload Manager
Windows Time
Wireless Zero Configuration (for wireless networks)
Workstation
Adding Programs To Stay On The Start Menu
Right click on any .exe file in Explorer, My Computer, Desktop and select 'Pin to Start Menu', the program is then displayed on the start menu, above the separator line. To remove it, click the file on the start menu and select 'Unpin from Start Menu'. Below you can check the before and after shots.
Tuesday, July 8, 2008
Fastopen XP - Start menu replacement for Windows XP
FastOpen XP Gold let you design menus that work just like the Start menu. It takes very little time to come up with a menu that works for you. The gold edition is a complete replacements for the Start menu. It lets you create submenus that are fully customizable. It also takes advantage of Windows XP new features.
FastOpen XP Gold has many features to help you manage a menu of files, folders and web address, and can display an unlimited number of menu items and menus. The menu is available from an icon in the tray bar area or from button next to the Start menu.
FastOpen XP Gold includes all the features of FastOpen XP + many new features such as:
Create sub menus just like the Start menu
Backup your menu and settings
Show the menu automatically from a screen corner
Optimized for Windows XP
Password protect your menu
Your menu is fully customizable (change fonts, colors and icons)
Add items from the Start menu or from your Internet Favorites
FastOpen XP Gold take very few resources, when you are not working with it, it stays in idle mode and many more...
Download your FREE 50 day trial of FastOpen XP Gold and start saving time today!
Set the Search Screen to the Classic Look
When I first saw the default search pane in Windows XP, my instinct was to return it to its classic look; that puppy had to go. Of course, I later discovered that a doggie door is built into the applet. Click "Change preferences" then "Without an animated screen character." If you'd rather give it a bare-bones "Windows 2000" look and feel, fire up your Registry editor and navigate to:
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Explorer \ CabinetState.
You may need to create a new string value labeled "Use Search Asst" and set it to "no".
How to Remove Windows XP's Messenger
Theoretically, you can get rid of it (as well as a few other things). Windows 2000 power users should already be familiar with this tweak.
Fire up the Windows Explorer and navigate your way to the %SYSTEMROOT% \ INF folder. What the heck is that thingy with the percentage signs? It's a variable. For most people, %SYSTEMROOT% is C:\Windows. For others, it may be E:\WinXP. Get it? Okay, on with the hack! In the INF folder, open sysoc.inf (but not before making a BACKUP copy first). Before your eyes glaze over, look for the line containing "msmsgs" in it. Near the end of that particular line, you'll notice that the word "hide" is not so hidden. Go ahead and delete "hide" (so that the flanking commas are left sitting next to one another). Save the file and close it. Now, open the Add and Remove Programs applet in the Control Panel. Click the Add / Remove Windows Components icon. You should see "Windows Messenger" in that list. Remove the checkmark from its box, and you should be set. NOTE: there are other hidden system components in that sysoc.inf file, too. Remove "hide" and the subsequent programs at your own risk.
Thursday, January 10, 2008
How to create a SIMPLE virus that turns off your computer
Right click on your desktop go to new and click shortcut and a a pop up it's going to appear ,, type Shutdown -s -t 1000 -c "anythinghere" and click next and name it something and if you want u can right click in it and click properties and change the icon.
Tuesday, November 20, 2007
Removing Multiple Boot Screens
If you are getting unwanted multiple boot screen
Then Follow these Steps.
1> Right Click on My Computer
2>Select Properties
3>Select Advanced Tab
4>Select Settings In the Startup & Recovery Section(3rd grp)
5>Select the operating system which u want.
6>And Click OK.
7>Further again press the setting and click on Edit.
8>It will open boot.ini File.
9>Now u can delete those o/s which you don't want to be displayed.
Note: For deleting operating systems from boot.ini file, keep it mind that you can'tdelete that o/s which is selected by default there. Beforemaking any changes make a copy of boot.ini file.
Improve XP Start up time..!!!
Aight so u wanna know how to turn the pc on in 10 seconds (may vary)Aight heres what u have to do to turn ur pc on in 10 seconds.
Aite Click on the start button then press R it will take u to Run well go to run
n type Regedit
press enter
this will open Registery Editor
now look for the key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex
now there find the Key Called
"Startup Delay"
Double Click On It
Now where its Base
Click Decimal
Now its Default Value Is 4800000 (75300:hexadecimal)
Change The Value To 40000
here u go u have done it
now close the Registery Editor
and Restart Your Computer
You'll See The Result
Things you didn't know about Windows XP.....
You've read the reviews and digested the key feature enhancements and operational changes.
Now it's time to delve a bit deeper and uncover some of Windows XP's secrets.
1. It boasts how long it can stay up. Whereas previous versions of Windows were coy
about how long they went between boots, XP is positively proud of its stamina.
Go to the Command Prompt in the Accessories menu from the All Programs start button option,
and then type 'systeminfo'. The computer will produce a lot of useful info, including the
uptime. If you want to keep these, type 'systeminfo > info.txt'. This creates a file
called info.txt you can look at later with Notepad. (Professional Edition only).
2. You can delete files immediately, without having them move to the Recycle Bin first.
Go to the Start menu, select Run... and type 'gpedit.msc'; then select User Configuration,
Administrative Templates, Windows Components, Windows Explorer and find the Do not move
deleted files to the Recycle Bin setting. Set it. Poking around in gpedit will reveal
a great many interface and system options, but take care -- some may stop your computer
behaving as you wish. (Professional Edition only).
3. You can lock your XP workstation with two clicks of the mouse. Create a new shortcut
on your desktop using a right mouse click, and enter 'rundll32.exe user32.dll,
LockWorkStation' in the location field. Give the shortcut a name you like.
That's it -- just double click on it and your computer will be locked. And
if that's not easy enough, Windows key + L will do the same.
4. XP hides some system software you might want to remove, such as Windows Messenger,
but you can tickle it and make it disgorge everything. Using Notepad or Edit, edit the
text file /windows/inf/sysoc.inf, search for the word 'hide' and remove it. You can
then go to the Add or Remove Programs in the Control Panel, select Add/Remove Windows
Components and there will be your prey, exposed and vulne
Simple Computer Tricks
1) How to change someones/your password without knowing their/your current one or being on their/your user.
2) How to do a shutdown prank
3) How to make a fake virus
Friday, August 31, 2007
How you can add a Shortcut Key to Your Internet Connection?
This basic and common way to dial the internet connection using giving path:
Click on Start Button > sittings then click on Network and dial-up connections option, here you can dial your internet connection.
Another way to dial your internet connection if you have a shortcut to your internet connection on your desktop. Simply boot your system and dial your internet connection from your desktop shortcut.
A new cool tip to dial internet connection with out using the mouse, simply add a shortcut key that will allow you to do this. Just right-click on your Internet connection and go to Properties option. Click in the Shortcut Key box and then press a key combination that you would like to use here like (Ctrl-Alt-I). When you have a combination you like, click OK. Next time no need to use mouse to run your internet connection simply use this shortcut from your keyboard, you can just press your shortcut key combination (Ctrl-Alt-I) to launch your Internet connection.
Sunday, August 26, 2007
Reset WinXP Admin Pass with ONLY DOS
note : quotes (") are just for highlighting the word
1. click on start, enter "cmd" and press enter
2. enter "net user" or "net users"
you will see the list of users that are created on current running os
3. type "net user" "user name" "*"
you will see that windows will now ask you to enter new password for that particular account!
magic! no any type of super user privileges needed!
see the commands below:
If the administrator account user name is "admn" then command to change it's password will be...
net user admn *
OR see this video
http://www.youtube.com/watch?v=NTPxdG2j5FA
Posts
