no_spam_paquette@uwo.ca wrote:
> 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.
It could be controlled from the NIC properties in Windows. Waking features
can be controlled there.
For example, I have an Intel networking chip. I go to Device Manager,
select "Network Adapters", click on the instance of the adapter
"Intel Pro 1000/CT", do "Properties". A panel appears. Click
"Advanced". Scroll down the list, until you can see "Wake On LAN".
Select the "Wake On LAN" entry. Click "Properties" button.
Enable PME: OS Controlled (or enabled or disabled)
Wake on Link Settings: Disabled! (not forced or OS controlled)
Wake on Settings: OS Controlled (has several Magic Packet settings)
You can hammer your Ethernet chip into submission using those three
settings. I think the "Link" setting is the one you want Disabled.
"Link" means, if the light is lit, wake the computer. In other words,
as soon as another device is at the other end of the link, wake
me up (which would normally be always...). Very annoying. Magic
Packet is a bit more sane, because it takes a properly formatted
Magic Packet to wake the chip. The chip uses pattern matching for
that one.
HTH,
Paul
>
>
> On Aug 31, 9:41 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> 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...@usa.net> wrote:
>>
>>> On Aug 30, 7:57 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> 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.
>
>