REBOOT INSTEAD OF SHUTDOWN January 30, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, WINDOWS XP SHUTDOWN & RESTART TROUBLESHOOTING.Tags: fix shutdown error in xp, Windows how to, Windows shutdown problems
2 comments
Shutdown problems in Windows XP can be caused by many factors, just like earlier versions of Windows. These included: a damaged exit sound file; incorrectly configured, damaged, or incompatible hardware; conflicting programs, or an incompatible, damaged, or conflicting device driver. This post describe in windows how to manage this issue.
Most Win XP shutdown problems reported thus far have been that it reboots when shutdown is attempted. This may be a global symptom rising from several distinct causes, because, by default, XP executes an automatic restart in the event of a system failure. Therefore, more or less anything compromising the operating system during the shutdown process could force this reboot.
Disabling the “restart on system failure” feature may permit the exact cause to be isolated: Right-click on My Computer, click Properties, click the Advanced tab. Under “Startup & Recovery,” click Settings. Under “System Failure,” uncheck the box in front of “Automatically restart.”
Here are some things that have produced this reboot-instead-of-shutdown symptom:
• By now, the Roxio/Adeptec Easy CD / Direct CD software is well documented as being the major cause of this undesirable shutdown behavior. SOLUTION: Roxio has released new drivers (here) to solve this problem in both the Platinum and Basic editions of Easy CD Creator 5. As expected, at least half of the Win XP shutdown problems went away with the release of these patches.
One warning about this patch comes from correspondent Bert Smith: Be sure to read the directions! “Roxio Easy CD Creator Platinum 5.0 can be a real hassle to get working under Win XP,” Bert wrote, “and there is the risk of your computer not booting if you blindly go ahead and install it without first consulting the Roxio Web site.” Bert also mentioned that Roxio’s “Take Two” backup program (normally part of Easy CD Creator 5 Platinum) is uninstalled when the Roxio patch is applied.
o Direct CD. Many Easy CD users (but not all) found that installing Easy CD 5.0 does not cause the shutdown problem, provided they do not install the Direct CD component.
o UDFRINST. Several people solved this reboot-on-shutdown problem by deleting the UDFRINST file. This file is part of the Roxio CD-RW software for systems not using Direct CD.
o CDRALW2K.SYS. Correspondent Larry Blumette identified the CDRALW2K.SYS file (version 1.0.0.1048) as the Roxio file causing his shutdown problems and error conditions. When he deleted or renamed this one file, his problems went away. (Of course, you lose your CD functionality that way, too.)
o Video Pack 5. Roxio’s Video Pack 5 causes the same problem because it contains includes the main parts of Easy CD 5. SOLUTION: Uninstall Video Pack 5 and also delete CDRALW2K.SYS (Tip from Christian Männchen). However, this solution may also have the side-effect of disabling access to your CD or DVD drive. SOLUTION TO THE SIDE-EFFECT: Apply one of the repair methods in MSKB Article 270008, Code 31 Messages Occur After Removing Adaptec Easy CD Creator 4.02c in Windows 2000 .
• Whether or not APM is enabled makes a difference — but the effect could go two ways. Some users report that XP reboots on shutdown if APM is enabled, but shuts Windows down just fine if APM is disabled. Other users report exactly the opposite behavior. According to Jack Dunne, this is similar to a known Windows 2000 problem. The issue seems related to the computer’s specific hardware or BIOS — so, as with all NT operating systems, stick to the Hardware Compatibility List where possible.
• USB Connections As can be seen from remarks in the Misc. Hardware Issues section, several different USB-related issues can impact shutdown. One of the most concrete examples was a “reboot on shutdown” problem contributed by correspondent Rick Bross. If his several USB devices (PDA cradle, flash card reader, etc) were plugged into the motherboard’s USB ports, his computer would reboot on an attempted shutdown; but when, instead, he plugged them into an external USB 2.0 hub, shutdown went just fine. (This was with Win XP Professional SP1 on a Supermicro X5DAE dual Xeon motherboard. The same devices plugged into an Asus A7M-266D dual AMD 2000MP system on the same OS worked without problem.)
• “Wake on” power settings Power-management settings that have the computer “wake” on LAN, USB, modem, or (for that matter) probably anything else may also trigger a restart after shutdown. Correspondent Simon Wei provided this tip after a friend of his found an old old Logitech USB mouse would trigger “wake on USB” after every Windows shutdown. Their solution was to remove that particular mouse and all worked fine. The principle is much more far-reaching than this one example.
• Hidden “wake on” power settings If you have an Ethernet card integrated into your motherboard, you may have hidden “wake on” settings that are harder to find. Site visitor Jim Porter found that his Asus P5GDC-V Deluxe motherboard had a “wake on” setting in Device Manager | Properties | Advanced rather than in the BIOS or Power Management settings. (The Asus P5AD2 and P5GD2 boards have this also.)
• Y-SB3 Logitech Internet Keyboard can also cause this problem. If you use it as a simple generic keyboard, there’s no problem; but, if you install the Key Commander software that drives the special Internet functions, Win XP will restart instead of shut down. Unfortunately, Logitech has decided that they will not be updating this driver for this keyboard.
• Logitech MouseWare 8.6. Windows reboots when shutdown is attempted. The software caused a BSOD with KBDCLASS.SYS. Removing the software solved the BSOD the problem. (Tip from Pablo Cheng.) MouseWare 9.0 and 9.1 also have been linked to reboot-instead-of-shutdown in Win XP. Removing the software resolves the problem.
• Webstar DPX USB cable modem. In the one case known to me, the problem was solved by switching the modem’s connector from the USB 1.1 port on the motherboard to the USB 2.0 PCI card. (The modem was provided by Telewest Broadband, manufactured by Scientific Atlanta.)
Fix “Access Denied” error when trying to install SP2 January 27, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows XP.Tags: How to windows, Windows Installation
1 comment so far
This post describe While installing SP 2 you received an error stating “Access is denied”.
The following three approaches to be tried in order have been suggested by MS. Note that you should be trying the install windows from and Admin acount:
1. Try using a different Admin acount.
2. Use an Admin account and install from Safe mode.
3. Use SubInAcl. The following is from an MS representative. It assumes that you have installed your system on C:\ so that subinacl is installed at C:\Program Files\Windows Resource Kits\Tools. Adjust this if you’ve installed XP in a different partition.
1. Download and install subinacl from:
http://www.microsoft.com/downloads/deta … laylang=en
2. Create a file named reset.cmd in C:\Program Files\Windows Resource
Kits\Tools folder.
3. Edit the reset.cmd file with the following content.
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f
4. Enter into CMD prompt.
5. Enter the following commands one at a time and click Enter.
cd\
cd “C:\Program Files\Windows Resource Kits\Tools”
reset.cmd
6. After a few minutes by processing subinacl, please test the problem
again.
Fix XP Memory Dump File Error January 21, 2009
Posted by computerhelpandsupport in Operating System, Windows XP.Tags: fix dump file error, fix regiastry error, Windows support
12 comments
Windows XP came out as one of the greatest revolutions in the world of computers. The major drawbacks of the windows 98 and other previous versions were removed and new features were embedded. But the problem of Blue Screen errors and memory dump still persist. The annoying factor is that these blue screens lead to a catastrophic system crash and data loss in the Windows. It is therefore necessary to fix XP memory dump as soon as you see it.This post describe how to windows Fix dump file error.
What causes the XP memory dump?
Memory dump is not different from the Blue Screen errors or memory dump issues in the previous version of windows. The stop error messages like 0×0000001E, KMODE_EXCEPTION_NOT_HANDLED or
Beginning of Physical Memory Dump in windows comes when any of the following occurs:
* The .dll files of any of the programs of the applications are missing or corrupt. This causes critical system errors and the system fails to recover from the error. The system crashes completely and the data is lost. This critical system error occurs because, a kernel or a driver running in the Kernel mode or the mode where the programs are actually trusted not to crash crashes. This is a deadly hit to the operating system and the Blue Screen of death appears or the memory dump takes place.
* In Microsoft operating system, the memory is allocated in different places and in different amounts. If there is a deadly and incorrect misallocation of the memory, the memory dump takes place and the system faces the Blue screen of death and there are stop error messages appearing every time you reboot the computer.
How to Fix XP Memory Dump?
Memory dump can also occur because of the RAM issues or because of the communication errors. Whatever be the case, there is a solution. The Memory Dump caused by the hardware can be solved by replacing them. However, in case the Kernel is there in the picture, the registry needs to be cleaned and repaired.
There is different registry cleaner software available in the market and are capable of doing the following tasks:
* Removes unwanted and invalid entries from the registry and helps to Fix XP Memory Dump.
* Fixes registry errors.
* Optimizes the windows based computer performance.
All you need to do is to grab the best registry cleaner software and use it to keep you computer fit and Fix XP Memory Dump. For detailed info on various registry cleaners, contact computer support expert.
If you would like to know what happens to your computer, you can have a free scan by visiting the site, Fix XP Memory Dump and find out he most effective, easiest, and cheapest way to fix and maintain your computer in the same time.
Related Search:
How to configure registry keys to generate the memory dump file
Install standard VGA compatible driver January 16, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows Vista, Windows XP.Tags: Install Windows, Operating System Support
17 comments
This post describe how to Forcing Windows to Use the Standard VGA Mode Drivers Without Having to Use Safe Mode. When you install Windows on a computer that is using an unsupported video adapter, Windows Setup installs a standard VGA mode driver. However, after you install Windows, you may be able to obtain and install a Windows-compatible driver for your video adapter from an original equipment manufacturer (OEM). If you are running Windows Vista, visit the Windows Vista Compatibility Center to find links to the latest VGA drivers.
Follow the step to Forcing Windows to Use the Standard VGA Mode Drivers Without Having to Use Safe Mode
1. When you install an OEM driver, the Windows installer program copies the OEM installation file (Oemsetup.inf) to the %Systemroot%\Inf folder, and then renames the Oemsetup.inf file to Oem#.inf, where # is an incremental number for each OEM driver that is installed. To identify the OEM video-specific Oem#.inf file, you can open each Oem#.inf file in Microsoft Notepad (Notepad.exe), and then compare each one with the original Oemsetup.inf file that is located on the OEM drivers media. After you find a match, move that specific Oem#.inf and Oem#.pnf file to an alternate location, or rename the files to a different file extension.
2. In Device Manager, right-click your video adapter, and then click Uninstall to remove the video adapter.
3. Restart your computer. After you log on, you receive a New Hardware Found dialog box with Video Controller (VGA Compatible) listed as the description and the Found New Hardware Wizard starts.
4. Click Next to start the wizard.
5. Click search for suitable driver, and then click Next.
6. Click to clear all of the search option check boxes, and then click Next.
7. Click disable the device, and then click Finish.
After you finish the preceding steps, you computer is using the Vga.sys generic video driver, and this is the same VGA driver that is used in Safe mode. Note that Video Controller (VGA Compatible) (with a yellow question mark next to it) is displayed under the Other Devices branch in Device Manager.
If the computer becomes stable or shuts down normally while you are using the Microsoft Standard VGA driver, you may need to contact the OEM driver vendor to report the problems you encountered when you used the OEM driver. You may also need to obtain and install a newer driver (if one is available) that resolves these problems.
To use the OEM drivers again, copy or move the Oem#.inf and Oem#.pnf files back into the %Systemroot%\Inf folder, use Device Manager to uninstall the VGA video adapter, and then restart the computer. Windows Plug and Play should locate the OEM video adapter and reinstall the OEM drivers automatically without requiring any user input.
More Related Search
How to Manage devices with Device Manager January 13, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows XP.1 comment so far
Device Manager provides a graphical view of the hardware that is installed on the computer, as well as the device drivers and resources associated with that hardware. Using Device Manager provides a central point to change the way the hardware is configured and interacts with the computer’s microprocessor.
Using Device Manager to manage devices and their drivers require the following permissions, all of which are granted to Administrators:
* The Load\Unload Drivers privilege.
* The permissions needed to copy files to the system32\drivers directory.
* The permissions needed to write settings to the registry.
Device Manager allows the following functionality:
* Determine if the hardware on your computer is working properly.
* Change hardware configuration settings.
* Identify the device drivers that are loaded for each device and obtain information about each device driver.
* Change advanced settings and properties for devices.
* Install updated device drivers.
* Disable, enable, and uninstall devices.
* Reinstall the previous version of a driver.
* Identify device conflicts and manually configure resource settings.
* Print a summary of the devices that are installed on your computer.
Typically, Device Manager is used to check the status of computer hardware and update device drivers on the computer. If you are an advanced user, and you have a thorough understanding of computer hardware, you can use Device Manager’s diagnostic features to resolve device conflicts, and change resource settings.
To access Device Manager, use any of the following methods:
* Click Start, click Run, and then type devmgmt.msc.
* Right-click My Computer, click Manage, and then click Device Manager.
* Right-click My Computer, click Properties, click the Hardware tab, and then click Device Manager.
* Type the following command at a command prompt:
start devmgmt.msc
If you want to access Device Manager on a local or remote computer:
1. Click Start, click Run, and then type mmc.
2. Click Add/Remove Snap In on the File menu (or press CTRL+M), click Add, and then click Device Manager.
When you use this procedure, a shortcut to Device Manager is created that you can use to open Device Manager.
Additional Search:
Troubleshooting Device Conflicts with Device Manager
Computer Help
Computer Technician
How to install the Recovery Console
Windows 7 Beta Available for Public Download January 12, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows Vista, Windows XP.Tags: Windows Operating System
1 comment so far
Here is some good news for all you windows lover, and thsoe who were really looking for some thing other than vista.
Guys windows 7 is out there for Beta download, if you are looking for it from a long time then it’s time to act fast
As the Windows 7 beta download is altough available to the public but will only be available for 2.5 million downloads.
Here is the links for your perusal, but be carefull while chossing the links what you are looking for among either of 32 / 64 bit
Windows 7 Beta Customer Preview Program Download
Windows 7 32-bit direct download
Windows 7 64-bit direct download
The minimum requrements for the windows 7 Beta1 are
* Processor: 1 GHz 32-bit or 64-bit processor
* Memory: 1 GB of system memory
* Hard drive: 16 GB of available disk space
* Video card: Support for DirectX 9 graphics with 128MB memory (in order to enable Aero theme)
* Drive: DVD-R/W drive
* Internet connection (to download the Beta and get updates)
How to edit the Boot.ini file in Windows Server 2003 January 8, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows Vista, Windows XP.Tags: Operating System Support, Windows Boot file
4 comments
In Windows Server 2003, you can quickly and easily locate the Boot.ini file to verify or edit the Microsoft Windows startup configurations and make changes to the Advanced RISC Computing (ARC) path as required. Additionally, you can add switches to the Boot.ini file.
Edit the Boot.ini File
Follow the steps to Edit Boot.ini file
1. Click Start, point to Settings, and then click Control Panel.
2. In Control Panel, double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Under System startup, click Edit.
NOTE: In a multiple-boot operating system configuration, select the default operating system to start by clicking the operating system that you want in the Default operating system list.
Typical scenarios
The following list describes some typical scenarios where the user must manually update the ARC path in the Boot.ini file after storage configuration has changed.
* If you add a new controller that has the BIOS disabled, you may have to check and manually correct the ARC path in the Boot.ini file.
Note The additional controller may also affect the controller section of the ARC path.
* Whenever you add or remove disks from the computer, you create the potential for a situation where the ARC path must be updated.
* Although the operating system may sometimes offer to update the Boot.ini file, you still have to manually update the ARC path. Whether the ARC path must be manually updated depends on the extent and nature of the changes to the Boot.ini file.
If this change to the ARC path causes problems when you start the computer, follow these steps:
1. Start the Recovery Console and run the map ARC command. From the results of the map ARC command, you can determine the correct ARC path.
2. Create a new Boot.ini file on another computer.
3. Copy the new Boot.ini file. Use one of the following methods:
o Copy the new Boot.ini file to a floppy disk, and then use Recovery Console to copy the new Boot.ini file to the system.
o Copy the new Boot.ini file on an NT Boot floppy. If the following files are also needed, copy them on the same floppy disk: Ntldr, Ntdetect.com, and the Mass Storage Device driver that you have renamed as Bootdd.sys.
Alternatively, you can use Recovery Console and the /bootcfg switch to fix the ARC paths in either Microsoft Windows XP or Microsoft Windows Server 2003.
More Related Search:
How to use System Restore to restore Windows XP
How to Create a FAT32 Partition or Logical Drive
How to perform disk error checking in Windows XP
How to install the Recovery Console
Problems with drive overlay programs in Windows XP
Computer Support
How to use System Restore in Windows Vista January 5, 2009
Posted by computerhelpandsupport in Computer Help, Operating System, Windows Vista.Tags: Computer Support, Operating, Operating System Support
add a comment
This post describe How to use System Restore to log on to Windows Vista when you lose access to an account. It provides computer help, if you can’t log on to windows vista, you can use the windows vista system restore feature.
You may be unable to log on to Windows Vista in the following scenarios:
* Scenario 1: You recently set a new password for the protected administrator account. However, you do not remember the password.
* Scenario 2: You type the correct logon password. However, Windows Vista does not accept the password because the system is corrupted.
* Scenario 3: You delete a protected administrator account. Now, you cannot log on to another administrator account.
* Scenario 4: You change a protected administrator account to a standard user account. Now, you cannot log on to another administrator account.
Follow these steps for use System Restore to log on to Windows Vista when you lose access to an account
Note To do this, there must be a System Restore point at which the logon was successful.
1. Insert the Windows Vista DVD, and then restart the computer.
2. When you receive the following message, press any key:
Press any key to boot from CD or DVD.
3. Set the following preferences, and then click Next:
* Language to install
* Time and currency format
* Keyboard or input method
4. Click Repair your computer, select the operating system that you want to repair, and then click Next.
5. Click System Restore, and then click Next.
6. Click the restore point that you want to use, and then click Next.
Note Click a restore point that will return the computer to a state where the logon is successful. After you use the System Restore feature, reinstall any programs or updates that may be removed. You will not lose any personal documents. However, you may have to reinstall programs. You may also have to reset some personal settings.
7. Confirm the disks that you want to restore, and then click Next.
8. Click Finish, and then click Yes when you are prompted.
9. When the System Restore process is complete, click Restart to restart the computer.
10. After the computer restarts, click Close to confirm that the System Restore process has finished successfully.
11. Use an appropriate method to log on. For example, log on by using an older password, or log on by using another computer account.
Related Topics:
How to use System Restore to restore Windows XP
How to install the Recovery Console
How to Create a FAT32 Partition or Logical Drive
How to uninstall Windows Vista SP1 as a troubleshooting step
