Re: [H] Thoughts on 1TB HDs?
If you all are looking for a good NAS, take a look at the NorcoTek stuff. I had a DS500 (actually going to sell it since I upgraded it) and loved it. The DS500 is direct attached storage, but they have a NAS version out now. Julian (Sabre) On Mon, Feb 2, 2009 at 9:09 AM, Naushad, Zulfiqar zulfiqar.naus...@siemens.com wrote: Very nice!!! Must have been much more than a normal 500GB HDD. How much did u fork out for that drive? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Monday, February 02, 2009 5:06 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? 7200.3 http://www.seagate.com/ww/v/index.jsp?locale=en-USname=DB35_Series__720 0.3_SerialATA_500GB-8_ST3500830SCEvgnextoid=3dff7ea70fafd010VgnVCM1 0dd04090aRCRDvgnextchannel=85d4b1774aafd010VgnVCM10dd04090aRCRDreq Page=Model At 15:34 02/02/2009 +0300, you wrote: Is it the 7200.10 or 7200.11?
Re: [H] Thoughts on 1TB HDs?
Is it the 7200.10 or 7200.11? It's a 7200.11 According to their website I shouldn't have a problem because I have the ST31000340AS http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw
Re: [H] Thoughts on 1TB HDs?
Very nice!!! Must have been much more than a normal 500GB HDD. How much did u fork out for that drive? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Monday, February 02, 2009 5:06 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? 7200.3 http://www.seagate.com/ww/v/index.jsp?locale=en-USname=DB35_Series__720 0.3_SerialATA_500GB-8_ST3500830SCEvgnextoid=3dff7ea70fafd010VgnVCM1 0dd04090aRCRDvgnextchannel=85d4b1774aafd010VgnVCM10dd04090aRCRDreq Page=Model At 15:34 02/02/2009 +0300, you wrote: Is it the 7200.10 or 7200.11?
Re: [H] Thoughts on 1TB HDs?
Very nice. By the way I also have a 1 tb wd gp series drive and the heat output (or lack thereof) is astounding!! On Feb 2, 2009 6:11 PM, Jason Carson ja...@jasoncarson.ca wrote: Is it the 7200.10 or 7200.11? It's a 7200.11 According to their website I shouldn't have a problem because I have the ST31000340AS http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw
Re: [H] Thoughts on 1TB HDs?
7200.3 http://www.seagate.com/ww/v/index.jsp?locale=en-USname=DB35_Series__7200.3_SerialATA_500GB-8_ST3500830SCEvgnextoid=3dff7ea70fafd010VgnVCM10dd04090aRCRDvgnextchannel=85d4b1774aafd010VgnVCM10dd04090aRCRDreqPage=Model At 15:34 02/02/2009 +0300, you wrote: Is it the 7200.10 or 7200.11?
Re: [H] Thoughts on 1TB HDs?
What NAS do you have? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Saturday, January 31, 2009 10:47 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? Bino, I do not yet used 1TB hard drives. I'll leave that focus to the Collective. I do now use 500GB Seagate drives in my NAS (new toy!). They
Re: [H] Thoughts on 1TB HDs?
Is it the 7200.10 or 7200.11?
[H] ?small problem
Have what seems to be a small problem. WXPproXP3.. Was an Upgrade from W2KproSP4. Otherwise works superb! But, Can Not boot to Safe Mode...Hangs at mup.sys. Do have reading for this, but, am wondering if there may be something else going on? My network connection pointer in the CP is at #2. In the past, I have found that #1 was never totally ripped out :) I do not recall how to fully erase net connections, if this is what is going on... I have sat for 40+ minutes waiting, at the blue (Windows is Starting) screen trying to do a Restore Install. Not yet. I really do NOT wish to erase/reformat my C: partition; UNLESS the Collective convinces me this is the ONLY way. Hmmm. Perhaps Windows CAN NOT really be Upgraded? Sure looks like it at the moment. This is NOT a call to Resurrect. I am not Down. WXP is fully running (and I remain totally confused!) If this is a boot.ini file trouble, I can read/correct. (?) If this is a mbr partition error, I can read/correct. (?) Where to start? Ideas? Suggestions? Opinions (except Vista) welcome? Duncan
Re: [H] ?small problem
Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at http://www.annoyances.org/exec/forum/winxp/t1047532372. Sean correctly determined that the cause of all these disparate hung at Mup.sys failures were actually caused by problem with the Extended System Configuration Data (ESCD) stored in the system BIOS. The ESCD maintains a static list of Plug-and-Play resource allocations. This avoids recalculating all the allocations at each restart. If the ESCD gets corrupted, then the operating system cannot assign resources correctly. Windows makes this resource decision just after it loads the Mup.sys driver because that's when it loads the Advanced Configuration and Power Interface (ACPI) drivers. You can download the (mercifully short) ESCD specification from http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/escd.rtf. Once we knew that something in BIOS might be causing the problem, solving it was a snap. We downloaded the most current firmware revision from Dell's web site and flashed the BIOS and that was that. (Some motherboards come with an ESCD rebuild option in CMOS, so it would not be necessary to flash the BIOS.) The system booted without a hitch and performance was right back to where it had been before the problems started. If it hadn't been for Sean's insight, we would have spent time and money replacing the PERC controller, which unfortunately might well have solved the problem because replacing the board would have refreshed the ESCD. It's difficult to determine whether the system crash earlier in the week caused the ESCD problem or vice-versa, or if some other problem caused both. At this point, Anon is going to keep an eye on the system and hope for the best. I'd like to thank Sean both for solving this tricky problem and for taking the time to post a detailed account. This was the first time I'd visited the Annoyances.org web site, and it looks like a great resource. -- JRS steinie**...@pacbell.net Please remove **X** to reply... Facts do not cease to exist just because they are ignored. From: DHSinclair dsinc...@bellsouth.net To: Hardware Group hardware@hardwaregroup.com Sent: Monday, February 2, 2009 2:37:03 PM Subject: [H] ?small problem Have what seems to be a small problem. WXPproXP3.. Was an Upgrade from W2KproSP4. Otherwise works superb! But, Can Not boot to Safe Mode...Hangs at mup.sys. Do have reading for this, but, am wondering if there may be something else going on? My network connection pointer in the CP is at #2. In the past, I have found that #1 was never totally ripped out :) I do not recall how to fully erase net connections, if this is what is going on... I have sat for 40+ minutes waiting, at the blue (Windows is Starting) screen trying to do a Restore Install. Not yet. I really do NOT wish to erase/reformat my C: partition; UNLESS the Collective convinces me this is the ONLY way. Hmmm. Perhaps Windows CAN NOT really be Upgraded? Sure looks like it at the moment. This is NOT a call to Resurrect. I am not Down. WXP is fully running (and I remain totally confused!) If this is a boot.ini file trouble, I can read/correct. (?) If this is a mbr partition error, I can read/correct. (?) Where to start? Ideas? Suggestions? Opinions (except Vista) welcome? Duncan
Re: [H] Thoughts on 1TB HDs?
Interesting :) I have a HP MediaSmart Server which uses Windows Home Server. It's a great machine and it really really fits my needs. Regards, Zulfiqar Naushad. On Mon, Feb 2, 2009 at 6:01 PM, DHSinclair dsinc...@bellsouth.net wrote: I paid $77.64 for it delivered from Provantage. The ReadyNAS Duo came with one of these pre-installed. I just matched it. The original 2d 500GB that was part of the initial buy (kit) was a Seagate ST3500630AS (7200.1), but it is now my emergency spare. I say emergency because it ran for ~2weeks and then started logging overheat entries. Hmm. I do suspect that the silly little 60mm cooling fan is weak, but since re-matching the drives, the NAS is a solid as a stone in a 24/7 duty cycle. I allow the drives to go to sleep w/no activity in 2 hrs. I believe that the internal OS is some form of *nix. It is a very tiny box... :) It is a keeper! At 17:09 02/02/2009 +0300, zool wrote: Very nice!!! Must have been much more than a normal 500GB HDD. How much did u fork out for that drive? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Monday, February 02, 2009 5:06 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? 7200.3 http://www.seagate.com/ww/v/index.jsp?locale=en-USname=DB35_Series__720 0.3_SerialATA_500GB-8_ST3500830SCEvgnextoid=3dff7ea70fafd010VgnVCM1 0dd04090aRCRDvgnextchannel=85d4b1774aafd010VgnVCM10dd04090aRCRDreq Page=Model At 15:34 02/02/2009 +0300, you wrote: Is it the 7200.10 or 7200.11? -- Best Regards, Zulfiqar Naushad
Re: [H] Thoughts on 1TB HDs?
Mine are the ST31000340AS model as well.. So far, so good.. :) -- JRS steinie**...@pacbell.net Please remove **X** to reply... Facts do not cease to exist just because they are ignored. From: Jason Carson ja...@jasoncarson.ca To: hardware@hardwaregroup.com Sent: Monday, February 2, 2009 7:10:43 AM Subject: Re: [H] Thoughts on 1TB HDs? Is it the 7200.10 or 7200.11? It's a 7200.11 According to their website I shouldn't have a problem because I have the ST31000340AS http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw
Re: [H] ?small problem
Steine, Thank you. That share is part of the print I have made and not yet read thru. Sometimes the Collective Mind is on the same track! The bios ESCD business I can shortly fix, but I think I've already done this. We'll see. I will do this routine immediately! I do understand this from long, long ago. I did go from one asus bios to a brand new asus bios; across m/b's, but WTF! Yet again, perhaps I still screwed up! LOL! Thank you very much, Duncan At 14:45 02/02/2009 -0800, you wrote: Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at http://www.annoyances.org/exec/forum/winxp/t1047532372. Sean correctly determined that the cause of all these disparate hung at Mup.sys failures were actually caused by problem with the Extended System Configuration Data (ESCD) stored in the system BIOS. The ESCD maintains a static list of Plug-and-Play resource allocations. This avoids recalculating all the allocations at each restart. If the ESCD gets corrupted, then the operating system cannot assign resources correctly. Windows makes this resource decision just after it loads the Mup.sys driver because that's when it loads the Advanced Configuration and Power Interface (ACPI) drivers. You can download the (mercifully short) ESCD specification from http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/escd.rtf. Once we knew that something in BIOS might be causing the problem, solving it was a snap. We downloaded the most current firmware revision from Dell's web site and flashed the BIOS and that was that. (Some motherboards come with an ESCD rebuild option in CMOS, so it would not be necessary to flash the BIOS.) The system booted without a hitch and performance was right back to where it had been before the problems started. If it hadn't been for Sean's insight, we would have spent time and money replacing the PERC controller, which unfortunately might well have solved the problem because replacing the board would have refreshed the ESCD. It's difficult to determine whether the system crash earlier in the week caused the ESCD problem or vice-versa, or if some other problem caused both. At this point, Anon is going to keep an eye on the system and hope for the best. I'd like to thank Sean both for solving this tricky problem and for taking the time to post a detailed account. This was the first time I'd visited the Annoyances.org web site, and it looks like a great resource. -- JRS steinie**...@pacbell.net Please remove **X** to reply... Facts do not cease to exist just because they are ignored. From: DHSinclair dsinc...@bellsouth.net To: Hardware Group hardware@hardwaregroup.com Sent: Monday, February 2, 2009 2:37:03 PM Subject: [H] ?small problem Have what seems to be a small problem. WXPproXP3.. Was an Upgrade from W2KproSP4. Otherwise works superb! But, Can Not boot to Safe Mode...Hangs at mup.sys. Do have reading for this, but, am wondering if there may be something else going on? My network connection pointer in the CP is at #2. In the past, I have found that #1 was never totally ripped out :) I do not recall how to fully erase net connections, if this is what is going on... I have sat for 40+ minutes waiting, at the blue (Windows is Starting) screen trying to do a Restore Install. Not yet. I really do NOT wish to erase/reformat my C: partition; UNLESS the Collective convinces me this is the ONLY way. Hmmm. Perhaps Windows CAN NOT really be Upgraded? Sure looks like it at the moment. This is NOT a call to Resurrect. I am not Down. WXP is fully running (and I remain totally confused!) If this is a boot.ini file trouble, I can read/correct. (?) If this is a mbr partition error, I can read/correct. (?) Where to start? Ideas? Suggestions? Opinions (except Vista) welcome? Duncan
Re: [H] Thoughts on 1TB HDs?
Netgear (Infrant) RND2150 ReadyNAS Duo w/2 ST3500630SCE (db35.2) in RAID1. At 15:34 02/02/2009 +0300, zool wrote: What NAS do you have? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Saturday, January 31, 2009 10:47 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? Bino, I do not yet used 1TB hard drives. I'll leave that focus to the Collective. I do now use 500GB Seagate drives in my NAS (new toy!). They
Re: [H] ?small problem
Superb idea! But, for some odd reason my current 0502 bios does NOT have
the Reset ESCD {whatever} switch. NOW, it is back to the BOOK!
I do know that there is a NEW bios (0603), but, my read of the Asus site
indicates ZERO about this.
WOW! This one is again odd, and fun to work at.
Close to the crest of the wave again!
Thanks,
Duncan
At 14:45 02/02/2009 -0800, you wrote:
Found this after a google of mup.sys. :)
So, we started scouring the Internet looking for other possible
causes. We found quite a few instances of the hung at Mup.sys
symptom, but with a variety of fixes. Several administrators solved the
problem by replacing memory. Several others solved it by replacing drive
controllers or by simply moving the controllers to a different slot. One
administrator even replaced both processors.
Then we found a posting by Sean Branham at the Annoyances.org web
site. See the full text of the thread at
http://www.annoyances.org/exec/forum/winxp/t1047532372.
Sean correctly determined that the cause of all these disparate hung at
Mup.sys failures were actually caused by problem with the Extended
System Configuration Data (ESCD) stored in the system BIOS.
The ESCD maintains a static list of Plug-and-Play resource
allocations. This avoids recalculating all the allocations at each
restart. If the ESCD gets corrupted, then the operating system cannot
assign resources correctly. Windows makes this resource decision just
after it loads the Mup.sys driver because that's when it loads the
Advanced Configuration and Power Interface (ACPI) drivers.
You can download the (mercifully short) ESCD specification from
http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/escd.rtf.
Once we knew that something in BIOS might be causing the problem,
solving it was a snap. We downloaded the most current firmware revision
from Dell's web site and flashed the BIOS and that was that. (Some
motherboards come with an ESCD rebuild option in CMOS, so it would not be
necessary to flash the BIOS.) The system booted without a hitch and
performance was right back to where it had been before the problems
started. If it hadn't been for Sean's insight, we would have spent time
and money replacing the PERC controller, which unfortunately might well
have solved the problem because replacing the board would have refreshed
the ESCD.
It's difficult to determine whether the system crash earlier in the
week caused the ESCD problem or vice-versa, or if some other problem
caused both. At this point, Anon is going to keep an eye on the system
and hope for the best.
I'd like to thank Sean both for solving this tricky problem and for
taking the time to post a detailed account. This was the first time I'd
visited the Annoyances.org web site, and it looks like a great resource.
--
JRS steinie**...@pacbell.net
Please remove **X** to reply...
Facts do not cease to exist just
because they are ignored.
From: DHSinclair dsinc...@bellsouth.net
To: Hardware Group hardware@hardwaregroup.com
Sent: Monday, February 2, 2009 2:37:03 PM
Subject: [H] ?small problem
Have what seems to be a small problem.
WXPproXP3..
Was an Upgrade from W2KproSP4.
Otherwise works superb!
But,
Can Not boot to Safe Mode...Hangs at mup.sys.
Do have reading for this, but, am wondering if there may be something else
going on?
My network connection pointer in the CP is at #2.
In the past, I have found that #1 was never totally ripped out :)
I do not recall how to fully erase net connections, if this is what is
going on...
I have sat for 40+ minutes waiting, at the blue (Windows is Starting)
screen trying to do a Restore Install. Not yet.
I really do NOT wish to erase/reformat my C: partition; UNLESS the
Collective convinces me this is the ONLY way. Hmmm.
Perhaps Windows CAN NOT really be Upgraded? Sure looks like it at the moment.
This is NOT a call to Resurrect. I am not Down. WXP is fully running
(and I remain totally confused!)
If this is a boot.ini file trouble, I can read/correct. (?)
If this is a mbr partition error, I can read/correct. (?)
Where to start? Ideas? Suggestions? Opinions (except Vista) welcome?
Duncan
Re: [H] ?small problem
Here are some more to try. :) Here are some troubleshooting suggestions: • ESCD corruption, Try resetting ESCD and/or changing ACPI setting in the BIOS. If there is no specific way to reset the ESCD data via the BIOS you can force this by reflashing. For added value check to see if there is a BIOS update available first. • If your system is overclocked, Try reverting to the original standard spec.'s • If you have USB devices connected, including any hubs, try removing them all before you boot • If you have devices connected to the serial or parallel ports, Try disconnecting them, again before you boot • If you added any new hardware recently, including PCI,PCI-E, ISA cards, Or memory DIMMs Try removing them one at a time, reboot and see if this allows the system to boot correctly • If you have access to a DMM (Multimeter), Check all the power supply voltages and try to watch each as you try to boot. If they are more than 7% below normal and\or your PSU is over 5 years old, less than 350W and you have a 3D gaming graphics card with 128MB or more of graphics memory. Consider replacing the power supply with an upgrade of 500W or better. For more information on troubleshooting PC Power Supplies see my article on ATX PSU Troubleshooting • If you have PCI, PCI-E or AGP Graphics card and also have a video connector on your motherboard try taking out the graphics card and run off the motherboard video. Be sure to adjust your BIOS accordingly • Try moving around your System RAM DIMMs and/or try removing one • Try running an antivirus scan from CD or Diskette if you have that capability. If needed boot the recovery CD to a prompt first • Try booting with as minimal a system you can. Remember to disconnect optical and floppy drives. Also, try using a non-USB kybd and a regular ball mouse that plugs into the PS\2 port in place of an optical USB type • If all this fails to identify or fix your problem, Try Running Chkdsk from the Windows XP\2000 Recovery Console. If chkdsk fails to resolve the problem, at this point you may need to reinstall windows but first ... • Try checking out my Windows XP Boot Issues article to find out how to fix mup.sys hangs by manually restoring your registry. The process I detail is reversible if you back up the original hives first as instructed so it is worth a try ;) The fundementals of this procedure should also work on Windows 2000.I can say from experience that this absolutely fixes the windows XP mup.sys boot hang when the cause is a corrupted registry! • The motherboard my have failed or was damaged in a particular way such as from an excessive power draw by USB devices or AGP graphics card. One astute and observant reader provided this feedback: We actually found this problem (mup.sys hang) was bulging capacitors on the motherboard - Thanks MOH for the much appreciated feedback!On Feb 2, 2009, at 3:08 PM, DHSinclair wrote: Steine, Thank you. That share is part of the print I have made and not yet read thru. Sometimes the Collective Mind is on the same track! The bios ESCD business I can shortly fix, but I think I've already done this. We'll see. I will do this routine immediately! I do understand this from long, long ago. I did go from one asus bios to a brand new asus bios; across m/ b's, but WTF! Yet again, perhaps I still screwed up! LOL! Thank you very much, Duncan At 14:45 02/02/2009 -0800, you wrote: Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at http://www.annoyances.org/exec/forum/winxp/t1047532372 . Sean correctly determined that the cause of all these disparate hung at Mup.sys failures were actually caused by problem with the Extended System Configuration Data (ESCD) stored in the system BIOS. The ESCD maintains a static list of Plug-and-Play resource allocations. This avoids recalculating all the allocations at each restart. If the ESCD gets corrupted, then the operating system cannot assign resources correctly. Windows makes this resource decision just after it loads the Mup.sys driver because that's when it loads the Advanced Configuration and Power Interface (ACPI) drivers. You can download the (mercifully short) ESCD specification from http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/escd.rtf . Once we knew that something in BIOS might be causing the problem, solving it was a snap. We
Re: [H] Thoughts on 1TB HDs?
I paid $77.64 for it delivered from Provantage. The ReadyNAS Duo came with one of these pre-installed. I just matched it. The original 2d 500GB that was part of the initial buy (kit) was a Seagate ST3500630AS (7200.1), but it is now my emergency spare. I say emergency because it ran for ~2weeks and then started logging overheat entries. Hmm. I do suspect that the silly little 60mm cooling fan is weak, but since re-matching the drives, the NAS is a solid as a stone in a 24/7 duty cycle. I allow the drives to go to sleep w/no activity in 2 hrs. I believe that the internal OS is some form of *nix. It is a very tiny box... :) It is a keeper! At 17:09 02/02/2009 +0300, zool wrote: Very nice!!! Must have been much more than a normal 500GB HDD. How much did u fork out for that drive? -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Monday, February 02, 2009 5:06 PM To: hardware@hardwaregroup.com Subject: Re: [H] Thoughts on 1TB HDs? 7200.3 http://www.seagate.com/ww/v/index.jsp?locale=en-USname=DB35_Series__720 0.3_SerialATA_500GB-8_ST3500830SCEvgnextoid=3dff7ea70fafd010VgnVCM1 0dd04090aRCRDvgnextchannel=85d4b1774aafd010VgnVCM10dd04090aRCRDreq Page=Model At 15:34 02/02/2009 +0300, you wrote: Is it the 7200.10 or 7200.11?
Re: [H] ?small problem
John, Thanks. I'll drill into your send. I choose to wait to update the bios; I do not meet the minimum ATM. mup.sys remains the stop for a boot to Safe Mode. I'll find it in time. Time I do still have. Yes, have a new bios also. Already discussed.. :) Really odd glitch; from my perspective. Have patience. Can wait. winXP-SP3 is still AOK here ... (as long as I don't drill into either mup.sys or network'.)... odd I remain in this Stuff Happens! Mode right now; still digging. Duncan At 15:36 02/02/2009 -0800, you wrote: Here are some more to try. :) Here are some troubleshooting suggestions: ESCD corruption, Try resetting ESCD and/or changing ACPI setting in the BIOS. If there is no specific way to reset the ESCD data via the BIOS you can force this by reflashing. For added value check to see if there is a BIOS update available first. If your system is overclocked, Try reverting to the original standard spec.'s If you have USB devices connected, including any hubs, try removing them all before you boot If you have devices connected to the serial or parallel ports, Try disconnecting them, again before you boot If you added any new hardware recently, including PCI,PCI-E, ISA cards, Or memory DIMMs Try removing them one at a time, reboot and see if this allows the system to boot correctly If you have access to a DMM (Multimeter), Check all the power supply voltages and try to watch each as you try to boot. If they are more than 7% below normal and\or your PSU is over 5 years old, less than 350W and you have a 3D gaming graphics card with 128MB or more of graphics memory. Consider replacing the power supply with an upgrade of 500W or better. For more information on troubleshooting PC Power Supplies see my article on ATX PSU Troubleshooting If you have PCI, PCI-E or AGP Graphics card and also have a video connector on your motherboard try taking out the graphics card and run off the motherboard video. Be sure to adjust your BIOS accordingly Try moving around your System RAM DIMMs and/or try removing one Try running an antivirus scan from CD or Diskette if you have that capability. If needed boot the recovery CD to a prompt first Try booting with as minimal a system you can. Remember to disconnect optical and floppy drives. Also, try using a non-USB kybd and a regular ball mouse that plugs into the PS\2 port in place of an optical USB type If all this fails to identify or fix your problem, Try Running Chkdsk from the Windows XP\2000 Recovery Console. If chkdsk fails to resolve the problem, at this point you may need to reinstall windows but first ... Try checking out my Windows XP Boot Issues article to find out how to fix mup.sys hangs by manually restoring your registry. The process I detail is reversible if you back up the original hives first as instructed so it is worth a try ;) The fundementals of this procedure should also work on Windows 2000.I can say from experience that this absolutely fixes the windows XP mup.sys boot hang when the cause is a corrupted registry! The motherboard my have failed or was damaged in a particular way such as from an excessive power draw by USB devices or AGP graphics card. One astute and observant reader provided this feedback: We actually found this problem (mup.sys hang) was bulging capacitors on the motherboard - Thanks MOH for the much appreciated feedback!On Feb 2, 2009, at 3:08 PM, DHSinclair wrote: Steine, Thank you. That share is part of the print I have made and not yet read thru. Sometimes the Collective Mind is on the same track! The bios ESCD business I can shortly fix, but I think I've already done this. We'll see. I will do this routine immediately! I do understand this from long, long ago. I did go from one asus bios to a brand new asus bios; across m/ b's, but WTF! Yet again, perhaps I still screwed up! LOL! Thank you very much, Duncan At 14:45 02/02/2009 -0800, you wrote: Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at http://www.annoyances.org/exec/forum/winxp/t1047532372 . Sean correctly determined that the cause of all these disparate hung at Mup.sys failures were actually caused by problem with the Extended System Configuration Data (ESCD) stored in the system BIOS. The ESCD maintains a static list of Plug-and-Play resource allocations. This avoids recalculating all the allocations at each restart. If the ESCD gets corrupted, then the operating system cannot assign resources
Re: [H] ?small problem
Does a REPAIR INSTALL require a reboot/boot from a COLD/DEAD machine? I've been testing with WARM reboots? Can/will change! Duncan At 19:32 02/02/2009 -0500, you wrote: John, Thanks. I'll drill into your send. I choose to wait to update the bios; I do not meet the minimum ATM. mup.sys remains the stop for a boot to Safe Mode. I'll find it in time. Time I do still have. Yes, have a new bios also. Already discussed.. :) Really odd glitch; from my perspective. Have patience. Can wait. winXP-SP3 is still AOK here ... (as long as I don't drill into either mup.sys or network'.)... odd I remain in this Stuff Happens! Mode right now; still digging. Duncan At 15:36 02/02/2009 -0800, you wrote: Here are some more to try. :) Here are some troubleshooting suggestions: ESCD corruption, Try resetting ESCD and/or changing ACPI setting in the BIOS. If there is no specific way to reset the ESCD data via the BIOS you can force this by reflashing. For added value check to see if there is a BIOS update available first. If your system is overclocked, Try reverting to the original standard spec.'s If you have USB devices connected, including any hubs, try removing them all before you boot If you have devices connected to the serial or parallel ports, Try disconnecting them, again before you boot If you added any new hardware recently, including PCI,PCI-E, ISA cards, Or memory DIMMs Try removing them one at a time, reboot and see if this allows the system to boot correctly If you have access to a DMM (Multimeter), Check all the power supply voltages and try to watch each as you try to boot. If they are more than 7% below normal and\or your PSU is over 5 years old, less than 350W and you have a 3D gaming graphics card with 128MB or more of graphics memory. Consider replacing the power supply with an upgrade of 500W or better. For more information on troubleshooting PC Power Supplies see my article on ATX PSU Troubleshooting If you have PCI, PCI-E or AGP Graphics card and also have a video connector on your motherboard try taking out the graphics card and run off the motherboard video. Be sure to adjust your BIOS accordingly Try moving around your System RAM DIMMs and/or try removing one Try running an antivirus scan from CD or Diskette if you have that capability. If needed boot the recovery CD to a prompt first Try booting with as minimal a system you can. Remember to disconnect optical and floppy drives. Also, try using a non-USB kybd and a regular ball mouse that plugs into the PS\2 port in place of an optical USB type If all this fails to identify or fix your problem, Try Running Chkdsk from the Windows XP\2000 Recovery Console. If chkdsk fails to resolve the problem, at this point you may need to reinstall windows but first ... Try checking out my Windows XP Boot Issues article to find out how to fix mup.sys hangs by manually restoring your registry. The process I detail is reversible if you back up the original hives first as instructed so it is worth a try ;) The fundementals of this procedure should also work on Windows 2000.I can say from experience that this absolutely fixes the windows XP mup.sys boot hang when the cause is a corrupted registry! The motherboard my have failed or was damaged in a particular way such as from an excessive power draw by USB devices or AGP graphics card. One astute and observant reader provided this feedback: We actually found this problem (mup.sys hang) was bulging capacitors on the motherboard - Thanks MOH for the much appreciated feedback!On Feb 2, 2009, at 3:08 PM, DHSinclair wrote: Steine, Thank you. That share is part of the print I have made and not yet read thru. Sometimes the Collective Mind is on the same track! The bios ESCD business I can shortly fix, but I think I've already done this. We'll see. I will do this routine immediately! I do understand this from long, long ago. I did go from one asus bios to a brand new asus bios; across m/ b's, but WTF! Yet again, perhaps I still screwed up! LOL! Thank you very much, Duncan At 14:45 02/02/2009 -0800, you wrote: Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at http://www.annoyances.org/exec/forum/winxp/t1047532372 . Sean correctly determined that the cause of all these disparate hung at Mup.sys failures were actually caused by problem with the Extended System Configuration Data (ESCD) stored in the system BIOS. The ESCD maintains a static list of
Re: [H] ?small problem
At 17:37 02/02/09, DHSinclair wrote: Have what seems to be a small problem. WXPproXP3.. Was an Upgrade from W2KproSP4. Otherwise works superb! But, Can Not boot to Safe Mode...Hangs at mup.sys. Do have reading for this, but, am wondering if there may be something else going on? My network connection pointer in the CP is at #2. In the past, I have found that #1 was never totally ripped out :) I do not recall how to fully erase net connections, if this is what is going on... I have sat for 40+ minutes waiting, at the blue (Windows is Starting) screen trying to do a Restore Install. Not yet. I really do NOT wish to erase/reformat my C: partition; UNLESS the Collective convinces me this is the ONLY way. Hmmm. Perhaps Windows CAN NOT really be Upgraded? Sure looks like it at the moment. This is NOT a call to Resurrect. I am not Down. WXP is fully running (and I remain totally confused!) If this is a boot.ini file trouble, I can read/correct. (?) If this is a mbr partition error, I can read/correct. (?) Where to start? Ideas? Suggestions? Opinions (except Vista) welcome? Hi Duncan You mentioned that you changed motherboards (presumably without doing a clean reinstall of Windows 2K or XP). This is something that I've done a few times while running one Win2k installation and I've run into a problem similar to yours. With XP running normally, check to see how large (the single file) SYSTEM is. Problems like yours can occur if this file (no file extension, its name is just system, without the quotes of course) gets too large. Why would it get too large? Because Windows XP and 2K don't remove hardware information from the registry when you physically remove hardware devices from your box. By the way, SYSTEM is usually in the folder C:\WINNT\system32\config or C:\WINDOWS\system32\config). SYSTEM is the file that holds the part of the registry with all the hardware information (past and present). If SYSTEM approaches 10 MB in size (in Win2k, not sure the actual number in WinXP), Windows will not boot fully because it doesn't allocate enough memory for all the files needed in memory during the boot process for all the files that need to go into memory during boot. It doesn't matter how much RAM you have, it's just the way Microsoft handles things. I've lost the Microsoft Knowledge Base article that described all this, or I'd give you a copy or a URL for it. So if SYSTEM gets near 10 MB, Windows will think the registry is corrupt and will refuse to boot fully. You can shrink the size of SYSTEM by using ADD-REMOVE HARDWARE in Control Panel (or wherever it is in WinXP) to remove all ghost hardware. By ghost, I mean hardware that was once in the system but has been physically removed from the system but not from the registry. Windows hides this stuff in Device Driver and ADD-REMOVE HARDWARE. It might take an hour or two to remove all the hardware from previous motherboards, previously removed disk drives, USB devices, etc. When my Windows periodically failed to boot, I shrunk the SYSTEM file from 9.8 MB to 4.4 MB and the problem has never returned. I do recall that this problem occurs in both Win2k and WinXP. Maybe it's not your problem...but why not just check the size of your SYSTEM file and see if maybe it's too large. When I had this problem, I found over a hundred hidden disc drives in ADD-REMOVE HARDWARE, as well as dozens of hidden copies of every hardware device that you'd normally see once in Device Manager or ADD-REMOVE HARDWARE. If you deed to, you can get a copy of the free VERITAS Volume Manager 4.2 to remove more stuff from SYSTEM due to old disc drives. Let me know. Regards, Bill
Re: [H] ?small problem
Can you do a stepped boot not in safe mode and get hung up at the same place? Mup.sys is blamed a lot just because it is the last thing loaded, it is not really causing the problem in most cases. -Original Message- From: hardware-boun...@hardwaregroup.com [mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DHSinclair Sent: Monday, February 02, 2009 6:33 PM To: hardware@hardwaregroup.com Subject: Re: [H] ?small problem John, Thanks. I'll drill into your send. I choose to wait to update the bios; I do not meet the minimum ATM. mup.sys remains the stop for a boot to Safe Mode. I'll find it in time. Time I do still have. Yes, have a new bios also. Already discussed.. :) Really odd glitch; from my perspective. Have patience. Can wait. winXP-SP3 is still AOK here ... (as long as I don't drill into either mup.sys or network'.)... odd I remain in this Stuff Happens! Mode right now; still digging. Duncan At 15:36 02/02/2009 -0800, you wrote: Here are some more to try. :) Here are some troubleshooting suggestions: . ESCD corruption, Try resetting ESCD and/or changing ACPI setting in the BIOS. If there is no specific way to reset the ESCD data via the BIOS you can force this by reflashing. For added value check to see if there is a BIOS update available first. . If your system is overclocked, Try reverting to the original standard spec.'s . If you have USB devices connected, including any hubs, try removing them all before you boot . If you have devices connected to the serial or parallel ports, Try disconnecting them, again before you boot . If you added any new hardware recently, including PCI,PCI-E, ISA cards, Or memory DIMMs Try removing them one at a time, reboot and see if this allows the system to boot correctly . If you have access to a DMM (Multimeter), Check all the power supply voltages and try to watch each as you try to boot. If they are more than 7% below normal and\or your PSU is over 5 years old, less than 350W and you have a 3D gaming graphics card with 128MB or more of graphics memory. Consider replacing the power supply with an upgrade of 500W or better. For more information on troubleshooting PC Power Supplies see my article on ATX PSU Troubleshooting . If you have PCI, PCI-E or AGP Graphics card and also have a video connector on your motherboard try taking out the graphics card and run off the motherboard video. Be sure to adjust your BIOS accordingly . Try moving around your System RAM DIMMs and/or try removing one . Try running an antivirus scan from CD or Diskette if you have that capability. If needed boot the recovery CD to a prompt first . Try booting with as minimal a system you can. Remember to disconnect optical and floppy drives. Also, try using a non-USB kybd and a regular ball mouse that plugs into the PS\2 port in place of an optical USB type . If all this fails to identify or fix your problem, Try Running Chkdsk from the Windows XP\2000 Recovery Console. If chkdsk fails to resolve the problem, at this point you may need to reinstall windows but first ... . Try checking out my Windows XP Boot Issues article to find out how to fix mup.sys hangs by manually restoring your registry. The process I detail is reversible if you back up the original hives first as instructed so it is worth a try ;) The fundementals of this procedure should also work on Windows 2000.I can say from experience that this absolutely fixes the windows XP mup.sys boot hang when the cause is a corrupted registry! . The motherboard my have failed or was damaged in a particular way such as from an excessive power draw by USB devices or AGP graphics card. One astute and observant reader provided this feedback: We actually found this problem (mup.sys hang) was bulging capacitors on the motherboard - Thanks MOH for the much appreciated feedback!On Feb 2, 2009, at 3:08 PM, DHSinclair wrote: Steine, Thank you. That share is part of the print I have made and not yet read thru. Sometimes the Collective Mind is on the same track! The bios ESCD business I can shortly fix, but I think I've already done this. We'll see. I will do this routine immediately! I do understand this from long, long ago. I did go from one asus bios to a brand new asus bios; across m/ b's, but WTF! Yet again, perhaps I still screwed up! LOL! Thank you very much, Duncan At 14:45 02/02/2009 -0800, you wrote: Found this after a google of mup.sys. :) So, we started scouring the Internet looking for other possible causes. We found quite a few instances of the hung at Mup.sys symptom, but with a variety of fixes. Several administrators solved the problem by replacing memory. Several others solved it by replacing drive controllers or by simply moving the controllers to a different slot. One administrator even replaced both processors. Then we found a posting by Sean Branham at the Annoyances.org web site. See the full text of the thread at
