Re: Computer always restarts



I guess Intel ATM does not allow BIOS control of "Wake LAN from S5."
In any case, I'm pretty sure that's a red herring.


On Aug 31, 9:41 am, "no_spam_paque...@xxxxxx" <paque...@xxxxxx> wrote:
First, my sincere thanks to both of you for thoughtful and thought-
provoking responses!

With respect to Paul's suggestions I spent some time last night
looking carefully at Table 10 and especially at the footnotes to that
table as well as reviewing what seem to be pertinent parts of the
manual. In the wake of that exercise I've done several things though
I've not yet had the time to pursue in detail all of the threads Paul
raised. I did do a couple of things early this morning, however, that
seemed modestly promising to me after reflecting on Paul's comments
and the manual's content. First, I re-enabled legacy USB support
which I had disabled for reasons I won't bore you with. I also
downloaded from Intel and flashed in the most recent BIOS dated
today. One observation that troubles me is that the "Wake on LAN from
S5" option in the power tab of BIOS is inaccessible-both in the BIOS
that I had previously downloaded and in the one released today.
Scrolling down through the power options simply skips over that
option. That seems odd to me although the possibility of this being
some kind of wake-up-from-LAN effect seems very remote given that I
physically removed the LAN cable with no impact at all on the restart
behavior.

w_tom's points raised a couple of seemingly pertinent observations in
my mind. First, this is a dual-boot machine (Vista 32 and XP Pro) and
this behavior occurs on shutdown from BOTH systems. Second, the
history of this particular machine is that I installed XP Pro while
waiting (and waiting, and waiting, and waiting) to receive my copy of
Vista. Unless my memory is playing tricks with me-which is possible
of course, shut down worked normally for several weeks from the
original XP Pro installation and then stopped working for some unknown
reason which leads me back to Paul's hypothesis about the possibility
of some sort of hardware problem. That behavior, of course, has
survived into the new dual-boot installations!

Do these observations lead anywhere, I wonder?

On Aug 30, 8:13 pm, w_tom <w_t...@xxxxxxx> wrote:

On Aug 30, 7:57 am, "no_spam_paque...@xxxxxx" <paque...@xxxxxx> wrote:

I FINALLY got around to opening the box--to put in some new RAM.
While I was in the box, I tried disconnecting the power switch
connector from the motherboard while Vista was running and then tried
a shutdown. No luck--restarted as always! I then tried the same with
the "restart sw" connector and still no luck. Furthermore, when I
took it back to the retailer, one of their techies said he was able to
do a shutdown successfully from BIOS.

First appreciate how a power supply system gets turned off. The
operating system must understand what power supply controller is being
used AND therefore how to talk to it. Things such as removing power
switch were recommended on wild speculation; not based upon how
hardware works.

Second, if the OS does not know how to talk to that power supply
controller, then it cannot command power off. BIOS, obviously, would
know how to issue those same commands.

So your objective is to install the appropriate software (probably
in HAL) for that particular motherboard. The rub. You cannot do
that. That information is simply withheld from or completely
mysterious to most techs. Sometimes that software for that
motherboard does not even exist. That software would be unique to a
motherboard chip set AND should be available from motherboard
manufacturer. That manufacturer should have provided correct software
for Microsoft to include in Vista. Often information is not
available unless you make yourself enough of a pain. Most motherboard
manufacturers are dealing with people who don't know how electricity
works, did not even know about the power supply controller, and did
not know why the power switch would be completely irrelevant. Better
from them is to say nothing; claim that information is not available.

I can only point you in the right direction. BIOS could power off
the computer suggesting computer hardware can talk to power supply
controller AND power supply controller can turn off power supply.
That implies Windows has installed the wrong software for your power
supply controller.


.



Relevant Pages

  • Re: P5N32-SLI DL
    ... I am on my third motherboard an 6th set of ram, I also tried patriot DDR 2G8000 and this fails as well. ... In all cases the system locks up after a while and when I run Microsoft's Ram tester I get errors on the LDAP test on the third pass and every pass after that. ... I have loaded the latest beta bios and that has improved things slightly but the system still locks up and the memory tester fails again on the random LDAP test but less frequently. ... Good stability once you get enough power and cooling. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Boot process not starting
    ... with a new motherboard, cpu and video adapter and I can't get it to ... This repeats for as long as the power is on. ... the cooler fan pushpins but I will have to have another look at this. ... and the memory controller is set up. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: P5E MB slow POST
    ... You can go into the BIOS, ... Some boards, you press the power button, and no fans spin or anything. ... this has turned out to be because the motherboard ... A PCI port 80 card can be used, ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Computer will not wake up after power down
    ... > computer, under Power Mgmt, I can set to turn monitor off, say 10> minutes ... > will bring it back, mouse action, keyboard, etc., nothing. ... > Have had Motherboard replaced, had Hard Drive replaced, reinstalled OS ... Does the motherboard have the most current BIOS? ...
    (microsoft.public.windowsxp.general)
  • Re: P5N32 SLI DeLuxe not starting up
    ... Video - NVidia Quadro P231 DVI PCI Express ... Power supply: ... I cleared up the bios setting by moving the jumper, ... it could be the motherboard that is ...
    (alt.comp.periphs.mainboard.asus)

Quantcast