Path:
eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.o
rg!.POSTED!not-for-mail
From: Paul 
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: Unable to "Standby" my ThinkPad T23 Laptop
Date: Sun, 19 Nov 2017 18:56:44 -0500
Organization: A noiseless patient Spider
Lines: 124
Message-ID: 
References: 
 
 
 

Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 19 Nov 2017 23:56:44 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
posting-host="298dd85610663aca11f6cf84d46cd01e";
 logging-data="841"; mail-complaints-to="abuse@eternal-september.org";
posting-account="U2FsdGVkX1+grw9muLXRDu1NpQQv9/xMvFPPqZKDoWw="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
In-Reply-To: 
Cancel-Lock: sha1:idHwRsYPqqGV3D2OooVWKusi9hA=
Xref: feeder.eternal-september.org microsoft.public.windowsxp.general:134632

jaugustine@verizon.net wrote:
> 
>> The "dumppo" tool is supposed to have two purposes.
>>
>> 1) List the currently supported ACPI states
>> 2) Issue an override, in an attempt to re-enable missing
>>    state support, when any associated hardware mis-configurations
>>    have been corrected.
>>
>> It doesn't help to do an override, if the underlying problem
>> is still present.
>>
>> Say, for example, in WinXP, you look at Device Manager,
>> look under Computer, and it doesn't say "ACPI Multiprocessor PC".
> 
> Hi Paul,
> 
>     It DOES show "ACPI....." under "Computer" via "Device Manager".
> 
>     BTW,  I forgot to mention that the FN & F4/Sleep keys combo does
> NOT work with WinXP,  but DOES (put to "sleep") with Win98.
> 
>   Here is the results of using command, "dumppo admin cap":
> 
> Admin policy overrides
> Min sleep state......: S3
> Max sleep state......: S4 - hibernate
> Min video timeout....: 0
> Max video timeout....: -1
> Min spindown timeout.: 0
> Max spindown timeout.: -1
> power capabilities
> System power capabilities
> Power Button Present....: TRUE
> Sleep Button Present....: TRUE
> Lid Present.............: TRUE
> System states supported.: S5 
> Hiber file reserved.....: FALSE
> Thermal control.........: TRUE
> CPU Throttle control....: TRUE
> Processor min throttle..: 64
> Processor trottle scale.: 100 (1%)
> Some disk will spindown.: TRUE
> System batteries present: TRUE 
> System batteries scale..: (G:0 C:0) (G:0 C:0) (G:0 C:0) 
> Ac on line wake ability.: Unspecified
> Lid wake ability........: Unspecified
> RTC wake ability........: S4 - hibernate
> Min device wake.........: Unspecified
> Default low latency wake: Unspecified
> 
> LEGACY DRIVER DETECTED
>  VgaSave
> 
>   Again, Thanks, John

I think that means something related to video, is
blocking the states. The system states supported is in
pretty poor shape, as it's missing S3 and S4.

A couple Googles show people are trying to re-install
their video driver. You might take a look in Device
Manager (devmgmt.msc) first, and see whether everything
is clean and there are no yellow marks and so on.

There are two kinds of video drivers. The VESA driver is
for when the OS has no proprietary video card driver
installed. The ATI/Nvidia/Intel driver is the real,
full-featured driver, which enables hardware acceleration.
For the display adapter listed in Device Manager, you
want to see whether the text string is "branded" or
not, with a proprietary string.

It's possible, once you resolve the driver issue, that
you won't even need dumppo. But time will tell.

I think you're the first person I've run into, with
things blocked on a driver. The possibility was mentioned
on the Bellamy site, but I'd never seen it "in the wild".

*******

I learned a valuable lesson about computer hygiene and
video cards, a long time ago. I used to rip out and install
different video cards, with hardly a care in the world. At
one point, the computer had ATI, NVidia, and Matrox drivers
of some description. I never bothered to remove the
drivers.

The proper way to handle video is:

1) Go to Add/Remove and uninstall the current video driver.
2) Shut down, power off (unplug), install new video card.
3) System comes up and uses VESA driver initially.
    That Microsoft VESA driver ensures you can see the screen.
    It's basically just making a dumb frame buffer.
4) User then installs the proper driver for the new
    brand of video card. Accelerated video returns to the
    system.

If you do it that way, there are fewer chances of
side effects.

I got my OS in question, in such bad shape, I could
no longer get DMA/DIME working and games weren't
accelerated. I had to re-install, having learned
that I should be more careful in future. No amount
of "driver cleaners" would restore DMA/DIME.

Obviously, you can have two different brands of
video cards in a computer at the same time. There are
likely to be some scenarios that are hard to resolve
(like one driver that has "taken" to two different
cards, when you really want some "newer" driver to
only be used for one of the cards). I don't know
all the answers to such complicated setups. I
did run two FX5200 AGP cards for a test once, and
that was enough "fun" with dual cards right there.
The cards would switch roles (who drive left monitor
and who drives right monitor), while the system
was running :-) I took that apart after
a couple days and returned to a single video card.

    Paul
--- Platinum Xpress/Win/WINServer v3.1