Hey lets take this from the top...
1. Make sure the data cable of the hard disk is connected
2. Make sure the power cable on the hard disk is connected
3. Make sure the computer detects the hard disk.
4. Hit any ket to run setup from the CD when prompted.
5. If you still get that error message, use another copy of a Windows Operating System (OS) disk (CD).
6. Make sure you format the new hard disk before you try to install the OS.
Good luck!
2006-09-04 03:38:45
·
answer #1
·
answered by HushP 2
·
1⤊
0⤋
This depends on how big the hard drive is, and what version of Windows you are using.
If you are using Windows XP, you should be able to insert the Windows Disk and begin the installation on any size drive. With Windows 2000, you would be limited to a 137GB size drive. So you would want to make a partition first. If you are using Windows 98, you would be severely limited. You would have to make your partitions first, using FDISK.
Oh, does this say that NTLDR is missing from your Windows CD? YIKES, you need a new Windows Disk.
2006-09-04 03:27:02
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋
Installation procedure.
Insert the winxp cd in your cd drive and reboot your computer from the cd. The cd starts the installation procedure.
It asks if you want to upgrade or to do a new install.
Select new install.
The computer works for a while.
Then a screen comes up where it asks in which drive or partition you want to install the windows.
At this time read the options , which keys you have to press to do what etc. carefully.
First of all select every partition that you see in the box, and delete it.
When you delete all the partitions you will get one sigle unformatted space.
Now it is the turn to create a new partition in the unpartitioned space.
Create partitions of your liking.
When all unpartitioned space has been converted to partitions, select the uppermost c drive, or c partition to install windows on.
The computer will format the drive. It will ask what type of format you want NTFS/ FAT32.
For winXP NTFS is better, unless you have special resaons to convert in FAT32.
That's all ,
There will be many screens where you have to click on to proceed. And your computer will reboot a few times and Finished.
2006-09-04 03:24:28
·
answer #3
·
answered by Anonymous
·
1⤊
0⤋
Your exterior complicated tension might desire to teach as an icon on your reveal. in basic terms drag and drop each little thing you want on that tension. in case you opt to sparkling area on your gadget's complicated tension then do no longer ignore to delete regardless of you progression onto the Lacie as quickly as you have checked that it has transferred effectively. in case you opt to initiate putting stuff at as quickly as on the Lacie then in basic terms specify it because of the fact the trip spot whenever you save some thing. you have a huge quantity of potential because it stands and that i'm uncertain why you opt to bypass stuff onto the Lacie, except that's for motives of backup, that's clearly a solid theory. that's a shame you at the instant are not on a Mac, as you will possibly then have, on Leopard, the magnificent Time gadget facility which will mean by no ability dropping something ever back. in case you do no longer think of you're lots solid at desktops make your next one a Mac - they're easier, smarter, and cooler than a working laptop or computing device, and lots much less stressful to apply. Vista is the place Mac became approximately ten years in the past.
2016-11-06 09:51:28
·
answer #4
·
answered by awad 4
·
0⤊
0⤋
NTLDR (abbreviation of NT Loader) is the boot loader for Windows NT, including its later versions (2000/XP/Server 2003 but not Vista, which divides the functionality of NTLDR between two new components: winload.exe and the Windows Boot Manager). NTLDR can be run from either portable storage (such as a CD-ROM or USB flash drive), or the primary hard disk. NTLDR can also load a non NT-based operating system given the appropriate boot sector in a file.
NTLDR requires, at a minimum, the following two files to be on the system volume: NTLDR, which contains the main boot loader itself, and boot.ini, which contains configuration options for a boot menu. To load an NT-based OS, ntdetect.com must also be present.
The Volume Boot Record written to disc by the Windows NT format command attempts to load and to run the NTLDR program.
NTLDR has several names. On installed IA-32 systems the boot loader is stored in a file named NTLDR in the system volume. On setup discs created for Windows 2000, the boot loader is stored in a file named SETUPLDR.BIN, which is loaded by the Volume Boot Record of the setup disc. On bootable CD-ROMs, the boot loader is stored in a file named I386/SETUPLDR.BIN. On ARC machines, the boot loader is stored in a file named OSLOADER.EXE. Windows XP and Windows Server 2003 on IA-64-based systems the boot loader is stored in a file named IA64ldr.efi on the EFI System Partition.
All of these files contain the same boot loader code, with minor variations:
Instead of reading the system registry hive (which will not be present when no system has been installed) to locate device driver files to load, SETUPLDR.BIN is hardwired to use TXTSETUP.SIF.[1] Other flavours of NTLDR read the system registry hive.
On IA-32 platforms, the loader proper, which is stored in the file in the Portable Executable format, is preceded by a small, real mode, stub loader program that switches the processor into 32-bit flat memory mode before invoking the loader proper. On ARC and Extensible Firmware Interface platforms (such as IA-64), where there is no need for a real-mode stub, there is no stub and the file comprises solely the loader proper, which is started directly by the system firmware.
When booting, the loader proper portion of NTLDR does the following in order:
Accesses the file system on the boot drive (either FAT or NTFS).
If hiberfil.sys is found, and it finds a hibernation image, its contents are loaded into memory and the system resumes where it left off.
Otherwise, reads boot.ini and prompts the user with the boot menu accordingly.
If a non NT-based OS is selected, then NTLDR loads the associated file listed in boot.ini (bootsect.dos if no file is specified) and gives it control.
If an NT-based OS is selected, then NTLDR runs ntdetect.com, which gathers information about the computer's hardware. (If ntdetect hangs during hardware detection there is a debug version called ntdetect.chk which can be found on Microsoft support.
Starts Ntoskrnl.exe, passing to it the information returned by ntdetect.com.
NTLDR allows the user to choose which operating system to boot from at the menu; for NT and NT-based operating systems, it also allows the user to pass preconfigured options to the kernel. The menu options are stored in boot.ini, which itself is located in the root of the same disk as NTLDR.
For NT-based OSs, the location of the operating system is written as an Advanced RISC Computing (ARC) path.
boot.ini is protected from user configuration by having the following file attributes: system, hidden, read-only. To make it editable, you must first unlock it with the following command under a console attrib -s -h -r boot.ini. A more secure fashion to edit the file is to use the bootcfg command from a console. bootcfg will also relock the file (setting the file back to system, hidden and read-only).
2006-09-04 03:23:05
·
answer #5
·
answered by Johny0555 3
·
0⤊
0⤋
Try dropping it out of a third story window a couple of times.
2006-09-04 03:22:49
·
answer #6
·
answered by Privratnik 5
·
0⤊
0⤋
Have you tried fomat your harddisk to a bootable disk.You need to format it in NTFS or FAT32 to install windows
2006-09-04 03:23:56
·
answer #7
·
answered by Thu 2
·
0⤊
0⤋
I think you've done something wrong!
2006-09-04 03:21:50
·
answer #8
·
answered by Heather J 2
·
0⤊
0⤋
fix it
2006-09-04 03:23:35
·
answer #9
·
answered by Misha 1
·
0⤊
0⤋