2000 won't boot up, computer beeps
-
2000 won't boot up, computer beeps
The other day I went to turn on my win 2000 pc and it wouldn't boot up. Instead it would constantly beep. I figured that beeping was bad so I turned it off and tried again later to get the same response.
If my pc is shot I was thinking of just taking the hard drive and moving it to an older pc with Windows Millenium. If I do that the hard drive would need to have the drivers on the ME computer to run correctly, right?
Is there a program I can dl to pull all the drivers off of my ME HD and dl into them into the 2000 pc?
I never attached a second hard drive before so I am not sure what I need to do to set it up. Any help would be appreciated!
I don't have the internet at home so I have to dl whatever I need at work and put it on my 2 gig jump drive.
Thanks!
-
Apologies for a lack of response thus far. If you still have this problem;
Constant beeping can mean bad memory, overheating or bad CPU, bad display adapter. Beep codes are different for different bios's.
What is the bios on this Win 2000 machine? (AMI, AWARD, PHOENIX, etc)
Do you get any display on the Win 2000 machine?
Was Win 2000 installed on a FAT32 or NTFS file system? If NTFS, the Win ME machine probably won't be able to "work" the hard disk. However, there are utilities available which allow you to "read" NTFS files/disks, but not "run" them.
If Win 2000 was installed on a FAT32 file system, the ME machine will have no problems reading/writing to the Win 2000 hard disk.
"Drivers" are O/S (Operating System) specific. Drivers for one O/S won't work on another O/S. (Win 2000 & Win XP being the exception.)
See this link on installing;
IDE hard disks:
http://www.easeus.com/resource/insta...hard-drive.htm
SATA Hard disks:
http://www.easeus.com/resource/insta...hard-drive.htm
SCSI Hard disks:
http://www.easeus.com/resource/insta...hard-drive.htm
Post back with your results or further questions.
-
A friend gave me the system and I am out of touch with him. The system wont boot so I don't know what the BIOS are.
As far as FAT or ntfs again I am not sure. The ME is FAT32.
There is no display, I hooked my ME machine up to the monitor and the monitor is fine.
Sorry for not responding faster!
Thanks,
Derrek
-
"The system wont boot so I don't know what the BIOS are."
Read this on Troubleshooting POST problems.
Does the problem machine have a floppy disk drive?
If so, (once you go through the above troubleshooting sequences, and get any kind of results,) you could try booting with a Win98SE Boot Disk* just to get to a DOS prompt where further hardware testing can be undertaken.
*The above bootdisk image file is a self extracting file and has to be executed (run) from a running Windows machine in order to create the actual startup diskette on one of your floppy disks. (This image file produces the same bootdisk which 98SE creates.) This downloaded image file will format the floppy disk to ensure its integrity, write the files to the disk, then verify the file write, so it'll take a minute or three to create the bootdisk.
Ensure the floppy drive is set as the first boot device in the bios.
NOTE: When you boot a machine with this boot floppy, it creates a RAMDRIVE in system memory to contain DOS system tools/drivers. Thus it will move your "normal" CDROM device/drive letter "up" one level. (If your CDROM is normally E: it will be F: when booting with this bootdisk.)
The path to the found CDROM will be set with the bootfiles, so entering (example) A:\>f:\setup is the same as entering A:\>setup at the A:\> prompt. There is no need to include the cdrom drive letter. The path dictates that the instruction (command line input) will look at the CDROM for Setup before it looks elsewhere. The CDROM device letter will be assigned near the end of the floppy boot process, right after MSCDEX is loaded.
Post back with your results and any further questions.