All Kool Stuff for Window XP (Part - 4)

Getting an Older Program to Run on Windows XP

1.Right–click the executable or the program shortcut to the executable, and then click Properties.

2.Select the Run this program in compatibility mode check box.

3.From the list, select an operating system that the program runs in comfortably.

If necessary, also change the display settings and/or resolution, or disable the Windows XP visual themes.
Run the program again when you’re finished changing the settings. Adjust the compatibility settings again if the program is still not running smoothly: a program that’s unhappy on Windows 2000 may flourish on Windows 98.

Changing The Internet Time Update Synchronisation

To change the interval that Windows updates the time using the internet time servers via regedit, navigate to:
1. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services \W32Time\TimeProviders\NtpClient
2. Select "SpecialPollInterval"
3. Change decimal value from 604800 to a different value in seconds. i.e.: 172800 (2 Days) or 86400 (1 Day) and so on.

We don't recommend changing this unless you are on a broadband connection.

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 we have shown in the image below.

Using Remote Desktop

You must first enable the Remote Desktop feature on your office computer so that you can control it remotely from another computer. You must be logged on as an administrator or a member of the Administrators group to enable Remote Desktop on your Windows XP Professional-based computer.

To setup your office computer to use Remote Desktop:

• Open the System folder in Control Panel. Click Start, point to Settings, click Control Panel, and then double-click the System icon.

• On the Remote tab, select the Allow users to connect remotely to this computer check box, as shown below.

• Ensure that you have the proper permissions to connect to your computer remotely, and click OK.

• Leave your computer running and connected to the company network with Internet access. Lock your computer, and leave your office.
  
  The Remote Desktop Connection client software allows a computer running Windows 95, Windows 98, Windows 98 Second Edition, Windows Me, Windows NT 4.0 or Windows 2000 to control your Windows XP Professional computer remotely. The client software is available on the installation CD for Windows XP Professional and Windows XP Home Edition. The client software is installed by default on computers running Windows XP Professional and Windows XP Home Edition.
  

To install Remote Desktop Connection software on a client computer

• Insert the Windows XP compact disc into your CD-ROM drive.

• When the Welcome page appears, click Perform additional tasks, and then click Setup Remote Desktop Connection as shown below.

• When the installation wizard starts, follow the directions that appear on your screen.
  
  Once you have enabled your Windows XP Professional computer to allow remote connections, and installed client software on a Windows-based client computer, you are ready to start a Remote Desktop session.

To create a new Remote Desktop Connection

• Open Remote Desktop Connection. (Click Start, point to Programs or All Programs, point to Accessories, point to Communications, and then click Remote Desktop Connection.)

• In Computer, type the computer name for your computer running Windows XP Professional that has Remote Desktop enabled and for which you have Remote Desktop permissions

• Click Connect.

• The Log On to Windows dialog box appears.

• In the Log On to Windows dialog box, type your user name, password, and domain (if required), and then click OK. The Remote Desktop window will open and you will see the desktop settings, files, and programs that are on your office computer. Your office computer will remain locked.

• Nobody will be able to work at your office computer without a password, nor will anyone see the work you are doing on your office computer remotely. Note: To change your connection settings, (such as screen size, automatic logon information, and performance options), click Options before you connect.
  

To open a saved connection

• In Windows Explorer, open the My DocumentsRemote Desktops folder.

• Click the .Rdp file for the connection you want to open. Note: A Remote Desktop file (.rdp) file contains all of the information for a connection to a remote computer, including the Options settings that were configured when the file was saved. You can customize any number of .rdp files, including files for connecting to the same computer with different settings. For example, you can save a file that connects to MyComputer in full screen mode and another file that connects to the same computer in 800×600 screen size. By default, .rdp files are saved in the My DocumentsRemote Desktops folder. To edit an .rdp file and change the connections settings it contains, right-click the file and then click Edit.

To log off and end the session

• In the Remote Desktop Connection window, click Start, and then click Shut Down.

• The Shut Down Windows dialog box appears.

• In the drop-down menu, select Log Off , and then click OK.

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.

Rename a Series of Files

When you download photos from your digital camera, they often have unrecognizable names. You can rename several similar files at once with the following procedure. This also works for renaming other types of files.

1.Open the My Pictures folder. (Click Start, and then click My Pictures.) Or open another folder containing files that you want to rename.
2.Select the files you want to rename. If the files you want are not adjacent in the file list, press and hold CTRL, and then click each item to select it.
3.On the File menu, click Rename.
4.Type the new name, and then press ENTER.

All of the files in the series will be named in sequence using the new name you type. For example, if you type Birthday, the first will be named Birthday and subsequent files in the series will be named Birthday (1), Birthday (2), and so on. To specify the starting number for the series, type the starting number in parentheses after the new file name. The files in the series will be numbered in sequence starting with the number you type. For example, if you type Birthday (10), the other files will be named Birthday (11), Birthday (12), and so on.

Licensing Issues

Here you can find a Description of the things which are done by the Program or you can manually change the following settings to have the same effect:

• - MediaPlayer: Don't Acquire licenses automatically - Open the MediaPlayer-Extras - Options... Click the tab 'Player', look at the groupbox 'Internetsettings' and uncheck 'Acquire licenses automatically'.

• - MediaPlayer: No identification by internetsites - Open the MediaPlayer-Extras-Options... Click the tab ‘Player’, look at the groupbox 'Internet settings' and uncheck 'Allow identification by internet sites'

• - MediaPlayer: don't download codecs automatically - Open the MediaPlayer-Extras-Options... Click the tab 'Player', look at the groupbox 'Automatic Updates' and uncheck 'Download Codecs Automatically'

• - Error report: Don't report errors - Open the Explorer, right-click on 'My Computer' and select 'Properties', click on the Tab 'Advanced' and click the button 'Errorreports', in the upcoming dialog uncheck all 3 items and select 'Disable Errorreports'

To change drive letters

To change drive letters (useful if you have two drives and have partitioned the boot drive, but the secondary drive shows up as "D")

Go to Start > Control Panel > Administrative Tools > Computer Management, Disk Management, then right-click the partition whose name you want to change (click in the white area just below the word "Volume") and select "change drive letter and paths."
From here you can add, remove or change drive letters and paths to the partition.

My Computer Won't Shut Down Itself After Installing XP

There are a number of users who are noticing that their PC will no longer automatically power down/shut off without pressing the power off button on the computers unlike in Windows Me/95/2000. There could be a number of reasons for this - but the main one seems to be that ACPI is not enabled on the computer or in Windows XP. Here is how to try that out:

1. Click - Start - Control Panel - Performance and Maintenance - Power Options Tab

2. Then click APM - Enable Advanced Power Management Support

Never Re-Activate After Installation

If you have to reinstall Windows XP you normally will have to reactivate too. Well not anymore. Just copy wpa.dbl after you activated the first time. It is located in the WINDOWS\system32 folder. Now if you reinstall Windows XP just copy the file back and you're up and running again.

On Screen Keyboard

Want to use an on screen keyboard? Well it is this simple - Click on the start button and select run. Then type in osk in the box and click OK.

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.