I just want to add -- that when I say "reseat every memory module" I mean: physically remove each module in turn, clean out the motherboard connector with canned air, do the same with the module if its coated with dust, and snap the module back in, making sure it is seated correctly. You may have to disconnect power supply wires in order to get access to the memory modules. Be careful not to snap the white memory module levers at each end of the module. Be careful to take electrostatic discharge precautions too -- wear an antistatic wrist strap, and touch an unpainted metal surface to discharge your static before you touch a memory module. Never work on carpet. Even standing on carpet is not acceptable.
According to Scott Mueller. in his book Upgrading and Repairing PC's, 17th Edition, older Dell computer systems use a non-standard ATX power supply wiring configuration for both the motherboards and the power supplies. If you have a Dell system and need to replace the power supply, I recommend you purchase the new supply only from PC Power and Cooling, or from Dell's parts distributors. Mueller states that using a regular ATX power supply in an older Dell computer could very easily cause a fire and will in any case destroy the system. Bob Cochran Robert L Cochran wrote: > 700 Mb and a spontaneous reboot? This sounds to me like possible cpu > overheating, a bad power supply, or poorly seated memory modules. I have > these suggestions: > > 1. Check that the power supply is working properly. A failed bad power > supply is the source of numerous problems. Use a power supply tester and > if the supply fails, replace it with a very high quality supply -- such > as the PC Power & Cooling brand. Antec power supplies are also acceptable. > > 2. Reseat every memory module. A loosely seated memory module will cause > spontaneous reboots. Give the memory module connectors a great big blast > of canned air to make sure that all dust is out of the connectors. A > connector with just a small amount of dust in it will prevent a module > from seating properly and will prevent the machine from booting, too. > > 3. Check that the CPU fan is running. The cpu fan should be running all > the time. If it is not running, the cpu will overheat. Since you have to > open the system case to check this, give the cpu heatsink and fan a > really good blast of canned air to get rid of any dust bunnies before > you plug the unit in and turn power on. > > Bob Cochran > Greenbelt, Maryland, USA > > Matt Smollinger wrote: > >> Only 2 things I can think of: Either the Simpletech is faulty, or your >> HD is already on its way out. When you get that clicking noise, it >> means the armature that moves the heads around is having issues >> moving, and it may be right around that 700 Meg mark that the arm >> fails. I have no idea though why G4U would boot you out like that >> though... Are there any errors that flash by as it hits that mark and >> beeps a bunch of times? >> >> Matt Smollinger >> Application Engineer for Convergence Tech. >> AdvancedAV ATG >> >> >> ------------------------------------------------------------------------ >> *From: *Jam Talk <[EMAIL PROTECTED]> >> *Date: *Sun, 5 Aug 2007 19:23:49 -0700 >> *To: *<g4u-help@feyrer.de> >> *Subject: *[g4u-help] g4u local copy problem >> >> I bought a simpletech external hard drive to try to save my internal >> drive that has been making a clicking noise and I know it is a matter >> of time before it dies! >> >> Anyhow, when I do the copydisk wd0(55 gigs) sd0(160gigs) it copys upto >> around 700mb, beeps three times, and reboots to a black screen. >> >> Anyone know how to fix this? >> >> ------------------------------------------------------------------------ >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ------------------------------------------------------------------------ >> _______________________________________________ >> g4u-help mailing list >> g4u-help@feyrer.de >> https://lists.sourceforge.net/lists/listinfo/g4u-help >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> g4u-help mailing list >> g4u-help@feyrer.de >> https://lists.sourceforge.net/lists/listinfo/g4u-help >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > g4u-help mailing list > g4u-help@feyrer.de > https://lists.sourceforge.net/lists/listinfo/g4u-help > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ g4u-help mailing list g4u-help@feyrer.de https://lists.sourceforge.net/lists/listinfo/g4u-help
