crashed after h/disk installed

[brit21]

I have a pc running win98 pentium 3 500mhz, i wanted to increase the disk space by adding another harddisk, the hard disk that i obtained already had data on it in NTFS format. I linked it up as a third disk and the system seemed to find it, i then ran fdisk to format the new disk and it told me i had no h/disks present. I rebooted after removing the new disk but my system is now bleeping about 7 times and nothing is on the monitor

Please help!!!!!

 

[edfair]

What kind of drive? How did you link it up?
What else did you do when you ran fdisk?
Sounds like you wiped your primary master out.
You might try fdisk /mbr to rewrite the boot record.
fdisk is used to modify partitions and mbr , not format. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[ceh4702]

Sounds like bad news, FDISK is kind of final if you make a mistake on the disk. Use FDISK from an emergency boot disk and look at all the harddrives. Might be you wiped out your bootable partition and have lost all of the data. See what it says when you try to display all of the hard disks.

Maxtor use to let you download a porgram called EZMax or EZDrive or something like that. It lets you look at the drives and even displays the serial numbers. It also had the settings of the jumpers for most drives. It was made by some drive company.

IBM has another version they use and it makes a little picture like a diagram to point to the drives.

EZDRIVE HAD A utility like ghost copy, which is made by norton, that copies a drive as one entire drive in minutes. I bought an FIC AD11 and it came with about 8 different Norton Utility programs. Quite interesting. If you do not like my post feel free to point out your opinion or my errors.

 

[Guest_imported]

To me, I sounds like some other problem rather than
the HD. It sounds more like a memory chip problem
than the HD because even the HD screw up, the system
won't beep. Try unplugged the HD and see if the beep
comes on again.

 

[neomagic]

I may be wrong but....your GSFS (Gonna Start From Scratch).
FAT32 and NTFS are incompatable, they are only compatable in Win2k and Win-xp. When you ran FDISK I'm guessing you wiped out the wrong partition and wrote a FAT32 signature to your NTFS disk...bad...bad...techie. These problems are hard to recover from but not impossible to recover from. Disconnect all H/D's from the MOBO and boot to floppy. If it boots you know your system is fine but I'm guessing that it's not gonna boot. Why? 7 beeps is the clue. You or anybody out there can correct me if I'm wrong but I've never herd of a mother board beeping for bad partitions other than one or two beeps for a disk controller failure. See if you dislogged the memory module or video card. ATX MOBO's have to have video,ram,processor to pass POST. If you resolve this problem then you can tackel the other. Get it to boot the DOS disk and then check your partition info then give me the info and we'll see if we can't solve your problem. GL