Hi Sean,

thanks for your suggestion.
In this case the undesirable behaviour of 'rebooting after hibernating'
could be solved by changing the value of the boolean parameter
DisableWakeEvent of the function SetSuspendState from FALSE to TRUE.

Kind regards
Bernd



"Sean Liming (MVP)" wrote:

> Try taking a look at the BIOS settings to see if S1 or S3 is set.
>
> Regards,
>
> Sean Liming
> www.sjjmicro.com / www.seanliming.com
> Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
>
>
>
> "Bernd" <Bernd@discussions.microsoft.com> wrote in message
> news:C7B5844F-1393-4B12-9992-FE82C472A1B1@microsoft.com...
> > HORM is used on the previous target PC with Intel 915 chipset and
> > 'Standard
> > PC'-HAL. Initiating hibernation (= generating a hibernate file showing the
> > progress bar) is realized by a tool which is calling the function
> > SetSuspendState ( Hibernate, ForceCritical,DisableWakeEvent ) as described
> > in
> > the MSDN article 'Dismounting Volumes in a Hibernate Once/Resume Many
> > Configuration' (http://msdn.microsoft.com/en-us/library/aa460084.aspx) and
> > works without problems.
> >
> > But the new target PC with Intel 945 chipset and 'ACPI Multiprocessor
> > PC'-HAL performs a reboot instead of power off after having written the
> > hibernate file with the same tool as described above!
> >
> > What is the reason? How can this the automatic reboot be avoided?
> >
> > Thanks in advance
> > Bernd
> >
>