Hi i have connected a floppy disk drive to my Dell PowerEdge 1600SC Server but the pc cant find it. i know that the drive forks cos if i insert the ide cables the other way the disk drive led turns on but when i turn them back the right way agen nothing hapens the led dont light up i cant find it in the bios nothing. thanks jannis

SOURCE: No Boot on 1600sc

The easy answer is: Did you ensure the CPU fan connector is attached to the PROPER motherboard CPU fan power pins? The 2nd easy answer is: Are you sure your CPU is properly placed inside the socket? Could it be tilted slightly up on one side? The more complicated 3rd answer is: I've seen people use the spray can of AIR, which, believe it or not causes a moisture problem AND can overly cool a component. Although the motherboard looks fine, it won't boot or power on until the part(s) rewarm to room temperature or the moisture dissipates. This is how I solve this problem. I remove the motherboard or open it completely up to clean it with 80psi of compressed air. (remove all components) If it had previously been cleaned with a can of AIR, I let it sit for half an hour. When putting the parts back together (leave the HD, the CD, the floppy disconnected), (oh...ensure your front panel connectors are properly on the correct motherboard pins too.) 1)take extra caution with both the video card and the memory chip slots!! Inspect the video card gold edge and video card slot for a few strands of carpet fiber or DUST bunnies wedged or attached to the card/slot (which causes the computer to not power ON) 2) Inspect the memory sticks and memory slots in the same manner. (I had to see it with a magnifying glass, to see the problem) Once back together, if it boots, I'm done. If it didn't boot, I replace the power supply. If that didn't solve it, I reposition or change the RAM memory. Attention to detail is the key to success. ZT3000 "Beta tester of "0"s and "1's"

SOURCE: Dell PowerEdge 1600SC Server occasionally beeps when running

Check out this site:

http://bioscentral.com/postcodes/dellbios.htm

Write down the exact number of beeps and how long they last to find what the error means. The are call BIOS post codes and they resemble Morse Code. (ie. one long, 3 short, 2 long = RAM issue) Good luck!!

SOURCE: Boot from CD is not recognizing the Windows 2003 Server CD

hv u tried booting from other CDs .
if u can boot from other CDs , then this 2003 CD is botched , change it.

SOURCE: Adding DVD to Poweredge 2600

PE2600 has lots of spare power (unless you are already using all 6 SCSI drive bays) ..

You can fit 3 x SATA drives in the space where the (useless) tape backup unit is sitting [you can even buy a 'proper' enclosure = Icy Dock MB453SPF or I think the SNT-2131 will fit ] .. and you can split the power off the Tape drive (4pin) power socket ..

I've not found a DVD burner (only a combined DVD reader / CD burner = TS-L462C) .. however if you have a spare IDE port you should be able to use an external unit [you will need an e-ide cable & enclosure for the drive]

SOURCE: Poweredge 1800 server

Hey,

I looked over the spesifications for the poweredge 1800 servers, go ahead, it will work perfectly but there is one problem in the windows XP setup, you will need to insert / load SCSI or SATA drivers for the hard drive With a floppy disk, or if you don't have a floppy drive your going to need to create a custom windows xp setup cd and add the drivers into it so it can start the SCSI or SATA hard drive and finish the install. without the drivers it might not find the hard drive.

Aside from that I don't see any other problems. You should be able to get the drivers, and everything ese from dell site
http://support.dell.com/support/downloads/

Actually I looked over the dell downloads, I see only windows 2000 on the list with windows server 2003, and 2008 and linux distributions.

This could be a 2nd problem, drivers might not be avaialble, or work with xp, but we might be able to get it to work.


So two problems, SCSI or SATA drivers in windows xp / windows 2000 setup

2nd problem is in windows xp drivers, you could try windows 2003's drivers and 2000's and see if they work, if not, then we would have to look for drivers ourselfs from the internet.

So xp might cause headache but we might get it working, windows 2000 seems to be supported perfectly.

Let me know how the project goes
Thanks,
Ekse