I have a problem while installing Windows server 2003, It gives me BSOD With error 0*000007b, and comments like check for virus, chkdsk f paramater is not defined. remove any newly add hardware drive . i am using compaq cq60-104tu machine. now how should i install it. any guidance. Regards

You computer is not server type host: 1. If you have any stop error, reveal the accompanying message 2. Drivers not known by native W2K3 operating system installation medium should be "delivre" on diskette after pressing F6 in initial phase on installation 3. Probably you have not set BIOS properly (AHCI) This applies to W XP but I guess it would be valid for W2K3 http://support.microsoft.com/kb/324103 http://support.microsoft.com/kb/316401 General comments: 0x0000007B INACCESSIBLE_BOOT_DEVICE A problem occurred during the initialization of the I/O system; often the startup device or the file system. Windows XP lost access to the system volume or boot volume during the startup process. Initialisation of the I/O system failed (usually the boot device or the file system), Windows lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following: Hardware problems e.g. A failed boot device Corrupted or incompatible storage drivers SCSI, RAID, UDMA IDE, SATA File system problems Boot sector viruses Outdated firmware During I/O system initialisation, this error can occur when the controller or driver for the startup device (typically the hard disk) failed to initialise the necessary hardware; The file system initialisation failed because the system did not recognise the data on the boot device. This error can also be caused by an incorrect Advanced RISC Computing (ARC) path in BOOT.INI. ARC paths are used to define the path to the Windows installation on Intel x86-processor-based machines. See: BOOT.INI and ARC Path Naming Conventions and Usage. Regards Milos

Resolution This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult or impossible. Resolving a failed boot device problem: If a boot device is at fault, you must edit the boot options. Resolving an incompatible disk hardware problem: If Setup autodetects the controller, you might have to skip detection and use a specific manufacturer's disk to load the driver. Also, check the availability of updates for the system BIOS and SCSI controller firmware. Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer. Remove any recently added hardware, especially hard disk drives or controllers, to see if the error is resolved. If the problematic hardware is a hard disk drive, the disk firmware version might be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you removed another piece of hardware and the error is resolved, IRQ or I/O port conflicts likely exist. Reconfigure the new device according to the manufacturer's instructions. Confirm that all hard disk drivers, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List. If you recently added a driver, restart your computer, and press F8 at the character-based menu that displays the operating system choices. In the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time. In addition, check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses. This error can also occur because of hard disk corruption. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r. If you cannot start the system in the last known good configuration, you should try to start off the Windows CD. Then, you can run Chkdsk from the Repair Console. Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk drive from MS-DOS. Always use the version of Chkdsk that matches your version of Windows. If your system has SCSI adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For IDE devices, define the onboard IDE port as Primary only. Also check each IDE device for the proper master/subordinate/stand alone setting. Try removing all IDE devices except for hard disks. Finally, check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. For more Information: http://msdn.microsoft.com/en-us/library/ff559218(v=VS.85).aspx Instead of using your laptop for Windows server, you can install virtual PC on Win7 or Win XP and test the windows 2003 server on it. Thanks