This problem may occur if the 'Single-click to open an item (point to select)' option is not selected. This post provide Technical Support to fix error with Windows Vista Business If you unable to open an item with single click.
Solution: Click 'Start' and click 'Control Panel'. Click 'Appearance and Personalization'. Click 'Folder Options'. In the 'General' tab, from the 'Click items as follows' section, select the 'Single-click to open an item (point to select)' option. Click 'OK'.
Details: Windows Vista Business allows easy management of files and folders. You can use either mouse or keyboard to navigate files and folders. Sometimes, you may not be able to open an item with a single click.
Follow the step to fix it
1) Click 'Start' and click 'Control Panel'. (The 'Control Panel' window appears.)
' Control Panel' window
2) Click 'Appearance and Personalization'. (The 'Appearance and Personalization' window appears.)
'Appearance and Personalization' window
3) Click 'Folder Options'. (The 'Folder Options' dialog box appears.)
' Folder Options' dialog box
4) In the 'General' tab, from the 'Click items as follows' section, select the 'Single-click to open an item (point to select)' option.
5) Click 'OK'.
Showing posts with label Operating System Support. Show all posts
Showing posts with label Operating System Support. Show all posts
How to Assign a Mandatory user Profile
This post provide technical support tips to assign a mandatory user profile in Windows XP. It provides step by step instruction to assingn a mandatory user profile.
Open and Configure the User Profile Name Form
To complete these procedures successfully, log on as an administrator or as a member of the Administrators group. If your computer is connected to a network, you may be unable to complete this procedure due to network policy settings.
1. Click Start menu, click Control Panel, click Performance and Maintenance, and then click Administrative Tools.
2. Double-click Computer Management.
3. In the console tree, double-click Computer Management, double-click System Tools, double-click Local Users and Groups, and then double-click Users.
4. Right-click the user account that you want to modify, and then click Properties.
5. On the Profile tab, in the profile path, type the location of the profile that you want to assign in the following format
\\ServerName\ProfilesShareName\UserProfileName
where:
* ServerName is the name of the computer where the profiles are stored.
* ProfilesShareName is the share name where the profiles are stored.
* UserProfileName is the specific folder for this user profile.
Assign a Mandatory User Profile
To assign a mandatory user profile, you must also copy a preconfigured user profile to the location that you specified in the last step opening the user profile form.
1. Click Start, click Control Panel, click Performance and Maintenance, and then click System.
2. On the Advanced tab, under User Profiles, click Settings.
3. Click the profile that you want to copy, and then click Copy To.
4. In the Copy profile to box, type or browse to the path of the folder that you specified in step 5 in the "Open and Configure the User Profile Name Form" section, and then click OK.
5. Confirm that the user that is specified under Permitted to use is the user who will be accessing this profile. If more than one user will be using the copied user profile, you need to select a group that contains all of these users, such as the Everyone group.
6. Click OK.
7. Rename Ntuser.dat to Ntuser.man.
Open and Configure the User Profile Name Form
To complete these procedures successfully, log on as an administrator or as a member of the Administrators group. If your computer is connected to a network, you may be unable to complete this procedure due to network policy settings.
1. Click Start menu, click Control Panel, click Performance and Maintenance, and then click Administrative Tools.
2. Double-click Computer Management.
3. In the console tree, double-click Computer Management, double-click System Tools, double-click Local Users and Groups, and then double-click Users.
4. Right-click the user account that you want to modify, and then click Properties.
5. On the Profile tab, in the profile path, type the location of the profile that you want to assign in the following format
\\ServerName\ProfilesShareName\UserProfileName
where:
* ServerName is the name of the computer where the profiles are stored.
* ProfilesShareName is the share name where the profiles are stored.
* UserProfileName is the specific folder for this user profile.
Assign a Mandatory User Profile
To assign a mandatory user profile, you must also copy a preconfigured user profile to the location that you specified in the last step opening the user profile form.
1. Click Start, click Control Panel, click Performance and Maintenance, and then click System.
2. On the Advanced tab, under User Profiles, click Settings.
3. Click the profile that you want to copy, and then click Copy To.
4. In the Copy profile to box, type or browse to the path of the folder that you specified in step 5 in the "Open and Configure the User Profile Name Form" section, and then click OK.
5. Confirm that the user that is specified under Permitted to use is the user who will be accessing this profile. If more than one user will be using the copied user profile, you need to select a group that contains all of these users, such as the Everyone group.
6. Click OK.
7. Rename Ntuser.dat to Ntuser.man.
How to Configure Device Manager
This Post describe and provide computer repair help for how to Configure Device Manager to Display Detailed Information. If you require additional device information that is not typically displayed in Device Manager, you can configure Device Manager to show detailed information.
To configure Device Manager to show details:
1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set DEVMGR_SHOW_DETAILS=1, and then press ENTER.
3. Type start devmgmt.msc, and then press ENTER. In Device Manager the properties for a device should now provide a Details tab that contains additional information about the device.
You can view the Details tab to see the following device information:
* Device Instance ID
* Hardware IDs
* Compatible IDs
* Matching Device ID
* Service
* Enumerator
* Capabilities
* Devnode Flags
* Config Flags
* CSConfig Flags
* Ejection Relations
* Removal Relations
* Bus Relations
* Device Upper Filters
* Device Lower Filters
* Class Upper Filters
* Class Lower Filters
* Class Installer
* Class Coinstallers
* Device Coinstallers
* Firmware Revision
* Current Power State
* Power Capabilities
* Power State Mappings
NOTE: Not all of these properties will be populated for a given device. In other words, although all of these properties are listed, some may not contain information when viewing a particular device.
To configure Device Manager to show details:
1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set DEVMGR_SHOW_DETAILS=1, and then press ENTER.
3. Type start devmgmt.msc, and then press ENTER. In Device Manager the properties for a device should now provide a Details tab that contains additional information about the device.
You can view the Details tab to see the following device information:
* Device Instance ID
* Hardware IDs
* Compatible IDs
* Matching Device ID
* Service
* Enumerator
* Capabilities
* Devnode Flags
* Config Flags
* CSConfig Flags
* Ejection Relations
* Removal Relations
* Bus Relations
* Device Upper Filters
* Device Lower Filters
* Class Upper Filters
* Class Lower Filters
* Class Installer
* Class Coinstallers
* Device Coinstallers
* Firmware Revision
* Current Power State
* Power Capabilities
* Power State Mappings
NOTE: Not all of these properties will be populated for a given device. In other words, although all of these properties are listed, some may not contain information when viewing a particular device.
How to install the Recovery Console
In this section I am going to discuss about How to Install Recovery Console. You can install the Recovery Console on your computer to make it accessible if you cannot restart Windows. You can then select the Recovery Console option from the list of available operating systems for the duration of startup. Install the Recovery Console on important servers and on the workstations of IT personnel. This addition describes how to install the Recovery Console to your Microsoft Windows XP-based computer. To install the Recovery Console, you have to be logged on as an administrator.
Although you can run the Recovery Console by starting directly from the Windows XP CD, it is generally more suitable to set it up as a startup option on your startup menu. To run the Recover Console directly from the CD, see the "How to use the Recovery Console" section.
Follow the steps given below:
1. Insert the Windows XP CD into the CD-ROM drive.
2. Click Start, and then click Run.
3. In the Open box, type d:\i386\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive. In the case of 'Microsoft Windows XP Professional x64 Edition, type d:\amd64\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive.
4. A Windows Setup Dialog Box appears. The Windows Setup Dialog Box describes the Recovery Console option. To confirm the installation, click Yes.
5. Restart the computer. The next time that you start your computer, "Microsoft Windows Recovery Console" appears on the startup menu.
Alternatively, you can use a Universal Naming Convention (UNC)-established connection to install the Recovery Console from a network share point.
Note You may receive an error message that is similar the following:
Setup cannot continue because the version of Windows on your computer is newer than the version on the CD.
Resolve this problems get use Microsoft Support Recovery Console on a Microsoft Windows XP Service Pack 2-based computer
More Related Search
How to fix OS/2 Family API Calls Problems
How to Manage devices with Device Manager
How to edit the Boot.ini file in Windows Server 2003
Computer Help
Troubleshooting Device Conflicts with Device Manager
Although you can run the Recovery Console by starting directly from the Windows XP CD, it is generally more suitable to set it up as a startup option on your startup menu. To run the Recover Console directly from the CD, see the "How to use the Recovery Console" section.
Follow the steps given below:
1. Insert the Windows XP CD into the CD-ROM drive.
2. Click Start, and then click Run.
3. In the Open box, type d:\i386\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive. In the case of 'Microsoft Windows XP Professional x64 Edition, type d:\amd64\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive.
4. A Windows Setup Dialog Box appears. The Windows Setup Dialog Box describes the Recovery Console option. To confirm the installation, click Yes.
5. Restart the computer. The next time that you start your computer, "Microsoft Windows Recovery Console" appears on the startup menu.
Alternatively, you can use a Universal Naming Convention (UNC)-established connection to install the Recovery Console from a network share point.
Note You may receive an error message that is similar the following:
Setup cannot continue because the version of Windows on your computer is newer than the version on the CD.
Resolve this problems get use Microsoft Support Recovery Console on a Microsoft Windows XP Service Pack 2-based computer
More Related Search
How to fix OS/2 Family API Calls Problems
How to Manage devices with Device Manager
How to edit the Boot.ini file in Windows Server 2003
Computer Help
Troubleshooting Device Conflicts with Device Manager
How to fix OS/2 Family API Calls Problems
This post provide computer help, If windows does not support OS/2 Family API.Windows and Windows 95 do not support 16-bit Windows-based applications coded with OS/2 Family API (FAPI) calls. To fix this error follow the instruction.
FAPI works in the following manner:
1. The code contains references to OS/2 FAPI calls (such as DosOpen, DosRead, and so on).
2. When the program is loaded into OS/2 protected mode, the system loader dynamically links the FAPI calls to the OS/2 system-services DLLs (Dynamic-Link Libraries).
3. When the program is loaded into real mode (MS-DOS or OS/2 compatibility box), what actually gets loaded is a small program called the "FAPI Loader and Linker." It is this program that loads the real code; it dynamically links the FAPI calls to a special library of support routines that translate FAPI calls into 80x86 code and MS-DOS interrupts (INT 21H Function xx).
FAPI works well for programs that need to run in MS-DOS and OS/2 protected mode. The problem is that Windows uses the "New EXE Format" for programs, bypassing the standard MS-DOS entry point. For example, if a Windows program is run outside of Windows (in MS-DOS), the following message appears, and the program terminates:
This program requires Microsoft Windows
MS-DOS is not responsible for this message; the Windows program itself is responsible. The way the Windows program works is very similar to OS/2: it uses dual entry points into the .EXE file. In MS-DOS, a short program that prints the above message runs; however, in Windows, a true Windows-based application runs using the other entry point in the .EXE file.
Therefore, the problem is narrowed down to the following: if the FAPI Loader and Linker program is run using the standard MS-DOS .EXE file entry point, and Windows starts an application using a different entry point, the dynamic linking of the FAPI routines will not occur.
To avoid this problem, do the following:
Instead of using low-level MS-DOS calls (INT 21H Function xx) in a Windows-based application and OS/2 API calls (DosRead, DosOpen, and so on) in a Presentation Manager (PM) application, use the C run-time I/O routines for all of these applications.
This will work because the Microsoft C Compiler and the run-time libraries supply versions of the libraries that work in both OS/2 and MS-DOS. By moving C code to PM and to Windows, it will not be necessary to rewrite it, and the appropriate conversion routines will be supplied at link time.
FAPI works in the following manner:
1. The code contains references to OS/2 FAPI calls (such as DosOpen, DosRead, and so on).
2. When the program is loaded into OS/2 protected mode, the system loader dynamically links the FAPI calls to the OS/2 system-services DLLs (Dynamic-Link Libraries).
3. When the program is loaded into real mode (MS-DOS or OS/2 compatibility box), what actually gets loaded is a small program called the "FAPI Loader and Linker." It is this program that loads the real code; it dynamically links the FAPI calls to a special library of support routines that translate FAPI calls into 80x86 code and MS-DOS interrupts (INT 21H Function xx).
FAPI works well for programs that need to run in MS-DOS and OS/2 protected mode. The problem is that Windows uses the "New EXE Format" for programs, bypassing the standard MS-DOS entry point. For example, if a Windows program is run outside of Windows (in MS-DOS), the following message appears, and the program terminates:
This program requires Microsoft Windows
MS-DOS is not responsible for this message; the Windows program itself is responsible. The way the Windows program works is very similar to OS/2: it uses dual entry points into the .EXE file. In MS-DOS, a short program that prints the above message runs; however, in Windows, a true Windows-based application runs using the other entry point in the .EXE file.
Therefore, the problem is narrowed down to the following: if the FAPI Loader and Linker program is run using the standard MS-DOS .EXE file entry point, and Windows starts an application using a different entry point, the dynamic linking of the FAPI routines will not occur.
To avoid this problem, do the following:
Instead of using low-level MS-DOS calls (INT 21H Function xx) in a Windows-based application and OS/2 API calls (DosRead, DosOpen, and so on) in a Presentation Manager (PM) application, use the C run-time I/O routines for all of these applications.
This will work because the Microsoft C Compiler and the run-time libraries supply versions of the libraries that work in both OS/2 and MS-DOS. By moving C code to PM and to Windows, it will not be necessary to rewrite it, and the appropriate conversion routines will be supplied at link time.
How to Change a Hard Drive
With today's new software programs and advanced technology, you might find your hard drive is too small for your needs. Instead of buying a new computer, you can change your hard drive. Changing a hard drive on a personal computer is not difficult to do. It is easy task to change your hard drive Follow these operating system support instructions to change a hard drive with ease.
Removing a Hard Drive
Removing a Hard Drive
- Determine if you are adding a main hard drive or a back up hard drive. Disconnect the computer from the power source.
- Remove the screws on the back left of the tower when you are looking at the front of the computer.
- Remove the left-side panel carefully.
- Locate the hard drive which is located near the front of the computer.
- Remove the screws from the sides of the hard drive and remove the hard drive from the bracket.
- Disconnect the hard drive from the ribbon and unplug the power plug from the hard drive and remove.
- Determine if you are adding a main hard drive or a back-up hard drive.
- Check the hard drive connectors for the jumper setting. Make sure the plastic pin on the end of the hard drive is set to "Master" or "CS (cable select)" if you are installing a main hard drive. Make sure the plastic pin on the end of the hard drive is set to "Slave" if you are installing a back up hard drive. The setting of the new hard drive should be the same as the old hard drive.
- Attach the ribbon to the matching plug on the hard drive.
- Place the hard drive in the slot at the front top of the case or screw it into the bracket at the front of the tower.
- Screw the side back on the tower.
- Format your hard drive if it is blank. Your new hard drive is now ready to use.
Subscribe to:
Posts (Atom)