you can download office from here
http://download.openoffice.org/index.html
Open office is an alternate to microsoft office. it has a lot of new features which are not available in MS office.
Monday, December 3, 2007
Getting Rid of Undeletable Desktop Icons
You want to delete "undeletable" desktop icons such as the Recycle Bin, Outlook, and Internet Explorer, but you can't delete them by highlighting them and pressing the Delete key. Unnecessary desktop icons take up screen real estate, clutter the interface, and use system RAM.
Using the Registry
1. Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\CurrentVersion\Explorer\Desktop\ NameSpace. Here's where you'll find various special desktop icons, such as the Recycle Bin. They're not listed by name, but instead by class ID (CLSID), a unique identifier, such as {645FF040-5081-101B-9F08-00AA002F954E} for the Recycle Bin.
2. Find the CLSID of the desktop icon you want to delete.
Here are the CLSIDs for desktop objects
My Computer - {20D04FE0-3AEA-1069-A2D8-08002B30309D}
Recycle Bin - {645FF040-5081-101B-9F08-00AA002F954E}
Microsoft Outlook - {00020D75-0000-0000-C000-000000000046}
Internet Explorer - {FBF23B42-E3F0-101B-8488-00AA003E56F8}
The Internet - {3DC7A020-0ACD-11CF-A9BB-00AA004AE837}
My Network Places - {208D2C60-3AEA-1069-A2D7-08002B30309D}
Briefcase - {85BBD920-42A0-1069-A2E4-08002B30309D}
Dial-Up Networking - {992CFFA0-F557-101A-88EC-00DD010CCC48}
America Online - {955B7B84-5308-419c-8ED8-0B9CA3C56985}
3. Delete the key of the icon that you want gone from the desktop, such as {645FF040-5081-101B-9F08-00AA002F954E} for the Recycle Bin.
4. Exit the Registry, go to your desktop, and hit F5 to refresh the screen. The icon should now be gone.
5. On some systems, the icons may not be immediately deleted. Instead, after making the Registry change, you might have to right-click on the icon and choose Delete.
6. If you want to restore the icon, re-create the key that you deleted.
-----------------------------
Using downloadable software
TweakUI, one of a suite of free, unsupported utilities from Microsoft called PowerToys for Windows XP, can also hide these undeletable icons. Get it from
http://www.microsoft.com/windowsxp/pro/downloads/powertoys.asp
After you install it and run it, go to the Desktop section, and you'll see a list of icons that can't otherwise be deleted. Uncheck the box next to any that you don't want to show up on your desktop, and click on OK. The icons will be immediately removed. To make them appear again, check the box next to them.
Note:Some CLSIDs that you'll find in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\Desktop\NameSpace can be deleted from the desktop without having to edit the Registry, but when you try to delete them, they may give you a special warning message. For example, depending on your system, when you try to delete Microsoft Outlook from the desktop, you get the warning message "The Outlook Desktop icon provides special functionality and we recommend that you do not remove it." If you'd like, you can edit that message so that it displays whatever you want. In the CLSID's subkey, for example {00020D75-0000-0000-C000-000000000046} for Microsoft Outlook, you'll find the value Removal Message. Edit its value to whatever text you want, save it, and whenever someone tries to delete it, your warning message will appear.
Also, keep in mind that when you remove desktop icons, you're only removing icons, not the underlying feature or program. So, for example, the Recycle Bin still works even if you remove its icon. To open the Recycle Bin, go to C:\RECYCLER and open the folder inside it. To restore an item that's been deleted, right-click on it and choose Properties Restore. You can delete items from the folder as you would any other item.
Using the Registry
1. Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\CurrentVersion\Explorer\Desktop\ NameSpace. Here's where you'll find various special desktop icons, such as the Recycle Bin. They're not listed by name, but instead by class ID (CLSID), a unique identifier, such as {645FF040-5081-101B-9F08-00AA002F954E} for the Recycle Bin.
2. Find the CLSID of the desktop icon you want to delete.
Here are the CLSIDs for desktop objects
My Computer - {20D04FE0-3AEA-1069-A2D8-08002B30309D}
Recycle Bin - {645FF040-5081-101B-9F08-00AA002F954E}
Microsoft Outlook - {00020D75-0000-0000-C000-000000000046}
Internet Explorer - {FBF23B42-E3F0-101B-8488-00AA003E56F8}
The Internet - {3DC7A020-0ACD-11CF-A9BB-00AA004AE837}
My Network Places - {208D2C60-3AEA-1069-A2D7-08002B30309D}
Briefcase - {85BBD920-42A0-1069-A2E4-08002B30309D}
Dial-Up Networking - {992CFFA0-F557-101A-88EC-00DD010CCC48}
America Online - {955B7B84-5308-419c-8ED8-0B9CA3C56985}
3. Delete the key of the icon that you want gone from the desktop, such as {645FF040-5081-101B-9F08-00AA002F954E} for the Recycle Bin.
4. Exit the Registry, go to your desktop, and hit F5 to refresh the screen. The icon should now be gone.
5. On some systems, the icons may not be immediately deleted. Instead, after making the Registry change, you might have to right-click on the icon and choose Delete.
6. If you want to restore the icon, re-create the key that you deleted.
-----------------------------
Using downloadable software
TweakUI, one of a suite of free, unsupported utilities from Microsoft called PowerToys for Windows XP, can also hide these undeletable icons. Get it from
http://www.microsoft.com/windowsxp/pro/downloads/powertoys.asp
After you install it and run it, go to the Desktop section, and you'll see a list of icons that can't otherwise be deleted. Uncheck the box next to any that you don't want to show up on your desktop, and click on OK. The icons will be immediately removed. To make them appear again, check the box next to them.
Note:Some CLSIDs that you'll find in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\Desktop\NameSpace can be deleted from the desktop without having to edit the Registry, but when you try to delete them, they may give you a special warning message. For example, depending on your system, when you try to delete Microsoft Outlook from the desktop, you get the warning message "The Outlook Desktop icon provides special functionality and we recommend that you do not remove it." If you'd like, you can edit that message so that it displays whatever you want. In the CLSID's subkey, for example {00020D75-0000-0000-C000-000000000046} for Microsoft Outlook, you'll find the value Removal Message. Edit its value to whatever text you want, save it, and whenever someone tries to delete it, your warning message will appear.
Also, keep in mind that when you remove desktop icons, you're only removing icons, not the underlying feature or program. So, for example, the Recycle Bin still works even if you remove its icon. To open the Recycle Bin, go to C:\RECYCLER and open the folder inside it. To restore an item that's been deleted, right-click on it and choose Properties Restore. You can delete items from the folder as you would any other item.
Moving a New Microsoft Application to Another Windows XP Sys
You want to move a Microsoft application from one Windows XP system to another because you want to be able to reuse your settings on the new system. If you merely installed the application on the new system, you would lose all of your settings.
Here is how you do it:
1.Install the software on your new PC.
2. Connect the old and the new PC, either over a network, or via a null modem serial cable.
3. On the PC that has the settings you want to transfer, run the Files and Settings Transfer Wizard by choosing Start--All Programs--Accessories--System Tools--Files and Settings Transfer Wizard.
4. Click Next on the introductory screen, then from the following screen choose Old computer, and click Next.
5. On the Select a transfer method screen that appears, choose the method you're using to connect the two computers (direct cable, network, etc.). If you choose a network, or Other, select the folder location on your new PC where you want to transfer the settings. Click Next.
(In some instances, if you choose a network as the way to transfer your settings, the wizard will not be able to recognize the network. If that happens, choose Other. That will let you browse through your network for a location, even though the Network choice didn't recognize your network.)
6.The "What do you want to transfer" screen appears next. You can choose to transfer settings, files, or both files and settings. Make your choice.
7. You now have to choose what settings to transfer. The default is settings for applications and Windows such as taskbar options and Outlook Express, specific folders such as Desktop, Fonts, My Documents, and My Pictures, and file type associations (what files open with what programs). To add or remove settings, select the "Let me select a custom of files and settings" checkbox, and then click Next.
8. From the screen that appears, add new files and settings, or remove existing ones. Click Next when you're done.
9. The wizard will gather the files and settings, and save them in the location you've chosen. Click Finish when you're done.
10. Go to the computer onto which you're going to transfer the settings. If you've copied the settings to a removable disk, put the removable disk in its drive.
11. Run the run the Files and Settings Transfer Wizard on the computer onto which you're transferring settings.
12. Click Next on the introductory screen, then from the following screen choose New computer, and click Next.
13. From the screen that appears, choose "I don't need the Wizard Disk. I have already collected my files and settings from my old computer." Click Next and Next again from the screen that appears.
14. From the screen that appears, choose the location where the wizard should look for your settings, for example, direct cable connection, floppy drive, or other. Use other if you've saved it to a removable drive, network drive, or to a location on your new PC. If you choose other, browse to the location of where you saved your settings. Select the folder where the data is stored.
15. Click Next. The wizard will gather your settings and apply them. When it's done, click Next and then Finish. Your settings are now transferred to your new computer.
Note:The wizard only transfers settings, not the application itself. So you have to remember to first install the application on the new computer before running the wizard. Simply copying the program's folders, files, and executables from your old computer to your new computer won't work, because there may be Registry settings the program requires, as well as DLLs and other files that it may have installed in folders that you don't know about.
Keep in mind that the File and Settings Transfer Wizard works with Microsoft applications, but with only a very few non-Microsoft applications. So don't count on using it if you want to transfer settings for any applications other than those written by Microsoft.
--------------------------------
For more details about using the Files and Settings Transfer Wizard, see
http://www.microsoft.com/windowsxp/using/setup/expert/crawford_november12.mspx
PCmover from LapLink
http://www.laplink.com/products/pcmover/overview.asp
will move entire applications and settings from one PC to another, as will Alohabob PC Relocator
http://www.alohabob.com/
Here is how you do it:
1.Install the software on your new PC.
2. Connect the old and the new PC, either over a network, or via a null modem serial cable.
3. On the PC that has the settings you want to transfer, run the Files and Settings Transfer Wizard by choosing Start--All Programs--Accessories--System Tools--Files and Settings Transfer Wizard.
4. Click Next on the introductory screen, then from the following screen choose Old computer, and click Next.
5. On the Select a transfer method screen that appears, choose the method you're using to connect the two computers (direct cable, network, etc.). If you choose a network, or Other, select the folder location on your new PC where you want to transfer the settings. Click Next.
(In some instances, if you choose a network as the way to transfer your settings, the wizard will not be able to recognize the network. If that happens, choose Other. That will let you browse through your network for a location, even though the Network choice didn't recognize your network.)
6.The "What do you want to transfer" screen appears next. You can choose to transfer settings, files, or both files and settings. Make your choice.
7. You now have to choose what settings to transfer. The default is settings for applications and Windows such as taskbar options and Outlook Express, specific folders such as Desktop, Fonts, My Documents, and My Pictures, and file type associations (what files open with what programs). To add or remove settings, select the "Let me select a custom of files and settings" checkbox, and then click Next.
8. From the screen that appears, add new files and settings, or remove existing ones. Click Next when you're done.
9. The wizard will gather the files and settings, and save them in the location you've chosen. Click Finish when you're done.
10. Go to the computer onto which you're going to transfer the settings. If you've copied the settings to a removable disk, put the removable disk in its drive.
11. Run the run the Files and Settings Transfer Wizard on the computer onto which you're transferring settings.
12. Click Next on the introductory screen, then from the following screen choose New computer, and click Next.
13. From the screen that appears, choose "I don't need the Wizard Disk. I have already collected my files and settings from my old computer." Click Next and Next again from the screen that appears.
14. From the screen that appears, choose the location where the wizard should look for your settings, for example, direct cable connection, floppy drive, or other. Use other if you've saved it to a removable drive, network drive, or to a location on your new PC. If you choose other, browse to the location of where you saved your settings. Select the folder where the data is stored.
15. Click Next. The wizard will gather your settings and apply them. When it's done, click Next and then Finish. Your settings are now transferred to your new computer.
Note:The wizard only transfers settings, not the application itself. So you have to remember to first install the application on the new computer before running the wizard. Simply copying the program's folders, files, and executables from your old computer to your new computer won't work, because there may be Registry settings the program requires, as well as DLLs and other files that it may have installed in folders that you don't know about.
Keep in mind that the File and Settings Transfer Wizard works with Microsoft applications, but with only a very few non-Microsoft applications. So don't count on using it if you want to transfer settings for any applications other than those written by Microsoft.
--------------------------------
For more details about using the Files and Settings Transfer Wizard, see
http://www.microsoft.com/windowsxp/using/setup/expert/crawford_november12.mspx
PCmover from LapLink
http://www.laplink.com/products/pcmover/overview.asp
will move entire applications and settings from one PC to another, as will Alohabob PC Relocator
http://www.alohabob.com/
Forcing Older Programs to Use Windows XP Common Controls
You want programs written for earlier versions of Windows to use the rounded, XP-type common graphical controls for things such as checkboxes and buttons. Normally, when you run an older program in XP, the operating system applies an XP-type frame around it, with rounded title bars. But the older program itself still uses its older style interface.
To force older programs to use XP-type common controls, you have to create a manifest fileâ€â€a specifically formatted XML fileâ€â€and place it in the same folder as the older program.
The manifest file should be almost exactly the same for each older program that you want to use XP common controls, changing only the name and description of the program itself.
Following is the code to put in your manifest file. Note that for "Description of Program" you should enter a description for the program, and for "Program Name" you should enter the name of the program.
To create the file, open Notepad, type the following text into it, and save it to the same folder as the executable file of the program you want to force to use XP common controls. Give it the same name as the program's executable file, but with an extension of .manifest. So, for example, if the program's executable file were named oldprogram.exe, you'd give the manifest file the name oldprogram.exe.manifest.
Use the following code to create a .manifest file to force an older program to use XP common controls:
Description of Program
When you create the manifest file, the program will not only use XP common controls in the older Windows application, but will also apply whatever current XP theme you're using. If you don't want to use the XP common controls any longer, delete the manifest file or rename it. Also, keep in mind that the manifest file will not necessarily work with every older Windows application, such as old versions of Microsoft Money.
If you want to force an older Windows program to use XP's common controls, but don't want to have to go through the trouble of creating a manifest file, you can download XPME for Windows from
http://www.tlhouse.co.uk/XPME.shtml
Run it and select the program that you want to use common controls. The program automatically creates a manifest file for you. XPME is freeware.
To force older programs to use XP-type common controls, you have to create a manifest fileâ€â€a specifically formatted XML fileâ€â€and place it in the same folder as the older program.
The manifest file should be almost exactly the same for each older program that you want to use XP common controls, changing only the name and description of the program itself.
Following is the code to put in your manifest file. Note that for "Description of Program" you should enter a description for the program, and for "Program Name" you should enter the name of the program.
To create the file, open Notepad, type the following text into it, and save it to the same folder as the executable file of the program you want to force to use XP common controls. Give it the same name as the program's executable file, but with an extension of .manifest. So, for example, if the program's executable file were named oldprogram.exe, you'd give the manifest file the name oldprogram.exe.manifest.
Use the following code to create a .manifest file to force an older program to use XP common controls:
When you create the manifest file, the program will not only use XP common controls in the older Windows application, but will also apply whatever current XP theme you're using. If you don't want to use the XP common controls any longer, delete the manifest file or rename it. Also, keep in mind that the manifest file will not necessarily work with every older Windows application, such as old versions of Microsoft Money.
If you want to force an older Windows program to use XP's common controls, but don't want to have to go through the trouble of creating a manifest file, you can download XPME for Windows from
http://www.tlhouse.co.uk/XPME.shtml
Run it and select the program that you want to use common controls. The program automatically creates a manifest file for you. XPME is freeware.
Checking Drivers with the Driver Verifier Tool
You need to determine which drivers are loaded and the characteristics about them.
1. Click Start, then select Run.
2. Type in 'verifier' without quotes and click OK.
3. In the Driver Verifier Manager dialog, with the Create standard settings radio button selected under Select a Task, click Next.
4. To see the analysis of all drivers on your system, select the Automatically Select All Drivers Installed on This Computer radio button, and click Finish.
5. Your choices will be stored and you will receive a pop-up indicating that you must reboot for the changes to take effect. Click OK, then reboot at your convenience.
6. After rebooting your PC, re-run Verifier to see the analysis of all running drivers and the state they are in.
Windows' device driver verification tool will trace the loading and activity of any device driver you choose. This tool is intended for developers and low-level system engineers, but it can tell you which drivers are or have been loaded during Windows operation and help you debug them in case you experience system or device crashes.
1. Click Start, then select Run.
2. Type in 'verifier' without quotes and click OK.
3. In the Driver Verifier Manager dialog, with the Create standard settings radio button selected under Select a Task, click Next.
4. To see the analysis of all drivers on your system, select the Automatically Select All Drivers Installed on This Computer radio button, and click Finish.
5. Your choices will be stored and you will receive a pop-up indicating that you must reboot for the changes to take effect. Click OK, then reboot at your convenience.
6. After rebooting your PC, re-run Verifier to see the analysis of all running drivers and the state they are in.
Windows' device driver verification tool will trace the loading and activity of any device driver you choose. This tool is intended for developers and low-level system engineers, but it can tell you which drivers are or have been loaded during Windows operation and help you debug them in case you experience system or device crashes.
Revealing Hidden Devices
1. Right-click My Computer and select Properties.
2. Select the Hardware tab, then click Device Manager.
3. Select View, then select Show Hidden Devices from the menu.
Note the appearance of dozens of new items appearing under Network adapters, system devices, and a new non-Plug and Play drivers device grouping.
2. Select the Hardware tab, then click Device Manager.
3. Select View, then select Show Hidden Devices from the menu.
Note the appearance of dozens of new items appearing under Network adapters, system devices, and a new non-Plug and Play drivers device grouping.
Keeping USB Devices from Disappearing
Every so often, a USB device fails to be recognized and usable even though it has been connected for as long as the PC has been running.
Using the USB cable
1. Unplug the USB device and wait for Windows to signal the disconnect, or for 30 to 60 seconds to be sure Windows knows the device is gone.
2. Reconnect the USB device and wait for Windows to recognize it again.
Using a graphical user interface
1.Click Start, then right-click My Computer and select Properties.
2. Select the Hardware tab, then click Device Manager.
3. Locate and expand the USB device, right-click on it, then select Properties.
4. If the device properties dialog includes a power management tab, click on it.
5. Uncheck the box next to Allow the Computer to Turn Off This Device to Save Power.
6. Click OK, then close Device Manager.
Using the USB cable
1. Unplug the USB device and wait for Windows to signal the disconnect, or for 30 to 60 seconds to be sure Windows knows the device is gone.
2. Reconnect the USB device and wait for Windows to recognize it again.
Using a graphical user interface
1.Click Start, then right-click My Computer and select Properties.
2. Select the Hardware tab, then click Device Manager.
3. Locate and expand the USB device, right-click on it, then select Properties.
4. If the device properties dialog includes a power management tab, click on it.
5. Uncheck the box next to Allow the Computer to Turn Off This Device to Save Power.
6. Click OK, then close Device Manager.
Using System Restore to Recover from a Hardware-Induced Prob
Using a graphical user interface
Log on to Windows using an account with administrator rights.
Navigate Start All Programs Accessories System Tools, and then click System Restore.
On the Welcome to System Restore page, click Restore My Computer to an Earlier Time, then click Next.
On the Select a Restore Point Page, click the most recent or a specific checkpoint in the On This List, click a Restore Point list, then click Next.
Click OK to accept the changes listed.
Click Next on the Confirm Restore Point Selection page.
After the system restarts, log on using an account with administrator rights.
Click OK to acknowledge the System Restore Restoration Complete page.
Using a command-line interface
Restart your computer, and then press F8 during the initial startup to start your computer in Safe Mode with a command prompt.
Log on using an account with administrator rights.
Enter the following command at the command prompt:
> %systemroot%\system32\restore\rstrui.exe
Press the Enter key and follow the instructions to restore your computer to a previous state.
Log on to Windows using an account with administrator rights.
Navigate Start All Programs Accessories System Tools, and then click System Restore.
On the Welcome to System Restore page, click Restore My Computer to an Earlier Time, then click Next.
On the Select a Restore Point Page, click the most recent or a specific checkpoint in the On This List, click a Restore Point list, then click Next.
Click OK to accept the changes listed.
Click Next on the Confirm Restore Point Selection page.
After the system restarts, log on using an account with administrator rights.
Click OK to acknowledge the System Restore Restoration Complete page.
Using a command-line interface
Restart your computer, and then press F8 during the initial startup to start your computer in Safe Mode with a command prompt.
Log on using an account with administrator rights.
Enter the following command at the command prompt:
> %systemroot%\system32\restore\rstrui.exe
Press the Enter key and follow the instructions to restore your computer to a previous state.
Move the Paging File in Windows XP
The paging file is the area on the hard disk that Windows uses as if it were random access memory (RAM) This is sometimes known as "virtual memory." By default, Windows stores this file on the same partition as the Windows system files. You can increase the performance of Windows, and increase free space on the boot partition, by moving this file to a different partition.
... Log on to the computer as Administrator.
... Click Start, and then click Control Panel.
... Click Performance and Maintenance, and then click System.
... Click the Advanced tab, and then under Performance, click Settings.
... Click the Advanced tab, and then under Virtual memory, click Change.
... In the Drive [Volume Label] list, click a drive other than the one on which Windows is installed (Windows is usually installed on the drive C). Under Total paging file size for all drives, note the value that is displayed next to Recommended.
... Click Custom size, and then type the recommended value in the Initial size (MB) box. Type the maximum size that you want to allow for paging in the Maximum size (MB) box, and then click Set.
... In the Drive [Volume Label] box, click the drive on which Windows is installed (usually the drive C), and then use one of the following steps:
... If you do not want a paging file on the drive, click No paging file, and then click Set. A message similar to the following message appears: If the pagefile on volume C: has an initial size of less than 126 megabytes, then the system may not be able to create a debugging information file if a STOP error occurs.
Continue anyway?
... Click Yes.
... If you want to keep the minimum size of the paging file on the drive, click Custom size, and then type a value that is equal to or greater than the amount of RAM in the computer in the Initial size (MB) box. Type that same value in the Maximum size (MB) box, and then click Set. The following message appears: The changes you have made require you to restart your computer before they can take effect.
... Click OK, click OK, click OK.
... Then click Yes when you are prompted to restart the computer.
... Log on to the computer as Administrator.
... Click Start, and then click Control Panel.
... Click Performance and Maintenance, and then click System.
... Click the Advanced tab, and then under Performance, click Settings.
... Click the Advanced tab, and then under Virtual memory, click Change.
... In the Drive [Volume Label] list, click a drive other than the one on which Windows is installed (Windows is usually installed on the drive C). Under Total paging file size for all drives, note the value that is displayed next to Recommended.
... Click Custom size, and then type the recommended value in the Initial size (MB) box. Type the maximum size that you want to allow for paging in the Maximum size (MB) box, and then click Set.
... In the Drive [Volume Label] box, click the drive on which Windows is installed (usually the drive C), and then use one of the following steps:
... If you do not want a paging file on the drive, click No paging file, and then click Set. A message similar to the following message appears: If the pagefile on volume C: has an initial size of less than 126 megabytes, then the system may not be able to create a debugging information file if a STOP error occurs.
Continue anyway?
... Click Yes.
... If you want to keep the minimum size of the paging file on the drive, click Custom size, and then type a value that is equal to or greater than the amount of RAM in the computer in the Initial size (MB) box. Type that same value in the Maximum size (MB) box, and then click Set. The following message appears: The changes you have made require you to restart your computer before they can take effect.
... Click OK, click OK, click OK.
... Then click Yes when you are prompted to restart the computer.
Creating a Boot Disk for an NTFS or FAT Partition
how to create a Windows boot disk to access a drive with a faulty boot sequence on an Intel x86-processor-based computer. This Windows boot disk can access a drive that has the Windows NT file system (NTFS) or
File allocation table (FAT) file system installed. The procedures in this article can be useful to work around the following boot problems:
... Corrupted boot sector.
... Corrupted master boot record (MBR).
... Virus infections.
... Missing or corrupt NTLDR or Ntdetect.com.
... Incorrect Ntbootdd.sys driver.
This boot disk can also be used to boot from the shadow of a broken mirror, although you may need to change the Boot.ini file to do that. This Windows boot disk cannot be used for the following problems:
... Incorrect or corrupt device drivers that have been installed into the Windows System directory.
... Boot problems that occur after the OSLOADER screen. To work around or fix these problems, run the Emergency Repair disk, load the last known good control set, or reinstall Windows, if necessary. The Windows floppy disk must include the files NTLDR, Ntdetect.com, Boot.ini, and the correct device driver for your hard drive.
Note: The NTLDR, Ntdetect.com, and Boot.ini files usually have their file attributes set to System, Hidden, and Read-Only. You do not need to reset these attributes for this disk to work properly.
Method 1: You Do Not Have Access to a Computer Running Windows
... Create a copy of the first Windows Setup disk using the diskcopy command, and then delete all files on the new disk.
... Copy the Ntdetect.com and NTLDR files from the i386 folder on the CD-ROM to the new disk.
... Rename the NTLDR file to "Setupldr.bin".
... Create a Boot.ini file. The following example works for a single partition SCSI drive with Windows installed under \WINNT; however, the exact value in the [operating systems] section depends upon the configuration of the Windows System you want to boot:
[boot loader]
timeout=30
Default= scsi(0)disk(0)rdisk(0)partition(1)\winnt[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT"
... If your computer boots from an IDE, EIDE, or ESDI hard drive or a SCSI adapter that does not have a built in BIOS, replace the scsi(0) with multi(0).
If you are using scsi(x) in the Boot.ini file, copy the correct device driver for the SCSI controller in use on the computer, and then rename it to Ntbootdd.sys. If you are using multi(x) in the Boot.ini, you do not need to do this.
... Start your computer using the floppy disk, and then log on to Windows.
Method 2: You Have Access to a Computer Running Windows
... Format a floppy disk using the Windows format utility.
... Copy NTLDR from the Windows Setup CD-ROM, Windows Setup floppy disk, or from a computer running the same version of Windows as the computer you want to access with the boot floppy. You may need to expand this file from NTLDR._ to NTLDR by using the following command line:
1. expand ntldr._ ntldr
... Copy the Ntdetect.com file to the disk.
... Create a Boot.ini file or copy one from a running Windows computer, and then modify it to match the computer you are trying to access. The following example works for a single partition SCSI drive with Windows installed under \WINNT; however, the exact value in the [operating systems] section depends upon the configuration of the Windows computer you are trying to access:
[boot loader]
timeout=30
Default= scsi(0)disk(0)rdisk(0)partition(1)\winnt[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT"
... If your computer starts from an IDE, EIDE, or ESDI hard drive, replace the scsi(0)with multi(0).
... If you are using scsi(x) in the Boot.ini, copy the correct device driver for the SCSI controller in use on the computer, and then rename it to Ntbootdd.sys. If you are using multi(x) in the Boot.ini, you do not need to do this.
... Start using the floppy disk, and then log on to Windows.
Troubleshooting You may encounter one or more of the following problems when you attempt to start your computer using your Windows boot floppy disk: If the path pointing to the system files is incorrect or includes the drive letter, you may receive the following error message: Windows could not start because of the following ARC firmware boot configuration problem: Did not properly generate ARC name for HAL and system paths. Please check the Windows . documentation about ARC configuration options and your hardware reference manuals for additional information. Boot Failed. If an incorrect SCSI driver has been selected or the Ntbootdd.sys file does not exist, you may receive the following message: Windows could not start because of a computer disk hardware configuration problem. Could not read from selected boot disk. Check boot path and disk hardware. Please check the Windows . documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals for additional information. Boot Failed.
File allocation table (FAT) file system installed. The procedures in this article can be useful to work around the following boot problems:
... Corrupted boot sector.
... Corrupted master boot record (MBR).
... Virus infections.
... Missing or corrupt NTLDR or Ntdetect.com.
... Incorrect Ntbootdd.sys driver.
This boot disk can also be used to boot from the shadow of a broken mirror, although you may need to change the Boot.ini file to do that. This Windows boot disk cannot be used for the following problems:
... Incorrect or corrupt device drivers that have been installed into the Windows System directory.
... Boot problems that occur after the OSLOADER screen. To work around or fix these problems, run the Emergency Repair disk, load the last known good control set, or reinstall Windows, if necessary. The Windows floppy disk must include the files NTLDR, Ntdetect.com, Boot.ini, and the correct device driver for your hard drive.
Note: The NTLDR, Ntdetect.com, and Boot.ini files usually have their file attributes set to System, Hidden, and Read-Only. You do not need to reset these attributes for this disk to work properly.
Method 1: You Do Not Have Access to a Computer Running Windows
... Create a copy of the first Windows Setup disk using the diskcopy command, and then delete all files on the new disk.
... Copy the Ntdetect.com and NTLDR files from the i386 folder on the CD-ROM to the new disk.
... Rename the NTLDR file to "Setupldr.bin".
... Create a Boot.ini file. The following example works for a single partition SCSI drive with Windows installed under \WINNT; however, the exact value in the [operating systems] section depends upon the configuration of the Windows System you want to boot:
[boot loader]
timeout=30
Default= scsi(0)disk(0)rdisk(0)partition(1)\winnt[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT"
... If your computer boots from an IDE, EIDE, or ESDI hard drive or a SCSI adapter that does not have a built in BIOS, replace the scsi(0) with multi(0).
If you are using scsi(x) in the Boot.ini file, copy the correct device driver for the SCSI controller in use on the computer, and then rename it to Ntbootdd.sys. If you are using multi(x) in the Boot.ini, you do not need to do this.
... Start your computer using the floppy disk, and then log on to Windows.
Method 2: You Have Access to a Computer Running Windows
... Format a floppy disk using the Windows format utility.
... Copy NTLDR from the Windows Setup CD-ROM, Windows Setup floppy disk, or from a computer running the same version of Windows as the computer you want to access with the boot floppy. You may need to expand this file from NTLDR._ to NTLDR by using the following command line:
1. expand ntldr._ ntldr
... Copy the Ntdetect.com file to the disk.
... Create a Boot.ini file or copy one from a running Windows computer, and then modify it to match the computer you are trying to access. The following example works for a single partition SCSI drive with Windows installed under \WINNT; however, the exact value in the [operating systems] section depends upon the configuration of the Windows computer you are trying to access:
[boot loader]
timeout=30
Default= scsi(0)disk(0)rdisk(0)partition(1)\winnt[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT"
... If your computer starts from an IDE, EIDE, or ESDI hard drive, replace the scsi(0)with multi(0).
... If you are using scsi(x) in the Boot.ini, copy the correct device driver for the SCSI controller in use on the computer, and then rename it to Ntbootdd.sys. If you are using multi(x) in the Boot.ini, you do not need to do this.
... Start using the floppy disk, and then log on to Windows.
Troubleshooting You may encounter one or more of the following problems when you attempt to start your computer using your Windows boot floppy disk: If the path pointing to the system files is incorrect or includes the drive letter, you may receive the following error message: Windows could not start because of the following ARC firmware boot configuration problem: Did not properly generate ARC name for HAL and system paths. Please check the Windows . documentation about ARC configuration options and your hardware reference manuals for additional information. Boot Failed. If an incorrect SCSI driver has been selected or the Ntbootdd.sys file does not exist, you may receive the following message: Windows could not start because of a computer disk hardware configuration problem. Could not read from selected boot disk. Check boot path and disk hardware. Please check the Windows . documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals for additional information. Boot Failed.
Subscribe to:
Posts (Atom)
