HolidayBuyer's Guide

Windows Legacy OS forum

General discussion

Standby and Hibernate Failure with PGP 6.x

by talkinghorse / January 21, 2006 12:59 AM PST

Looking for work-around solution standby/hibernate failure in WinXP system after installation of PGP 6.x.

Problem is completely described in Microsoft KB
article Q-314118 http://support.microsoft.com/kb/314118/en-us

I am presently using PGP 6.5.1 and want to keep it.
I'm using it for the PGPdisk features with encrypted
volumes (directories). It works fine in WinXP with
both existing PGD volumes that I have (from previous
systems) and it also works fine with newly created
PGD volumes. The only problem is that it prevents
WinXP from entering Standby modes when I attempt this
power down feature in WinXP for my laptop.

Uninstalling PGP 6.5 is not an acceptable option for
me (suggested by the MS KB article 314118). I want
to use PGP 6.5 with WinXP and not have to pay $100
for the new PGP 9.0 Desktop Home software. I would
like to see if there is a work-around in WinXP that
I could use to allow me to use PGP 6.5 and also
retain the Power Standby and Hibernate features of
WinXP (which are important to me for laptop usage).

Renaming the PGP drivers (PGPDisk.sys and
PGPmemlock.sys) to a different filename in the
system32/drivers directory works (after a WinXP reboot),
but this just restores Standby features of WinXP
(which proves that I have the problem in Q-314118).
But this solution of course disables PGPdisk from
working - which is not acceptable either.

Any WinXP hacks or registry tricks / suggestions would be appreciated.

thanks.....John

Discussion is locked
You are posting a reply to: Standby and Hibernate Failure with PGP 6.x
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Standby and Hibernate Failure with PGP 6.x
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Link.
by R. Proffitt Forum moderator / January 21, 2006 3:12 AM PST
http://www.mccune.cc/PGPpage2.htm looks interesting in that it noted this issue and suggests not using a screen saver password or the password on resume.

Other than that, I know nothing.

Bob
Collapse -
Password Removal doesn't help with Q-314118
by talkinghorse / January 21, 2006 1:39 PM PST
In reply to: Link.

Password removal does not help with this particular
problem. Of course even if it did, it would render
my laptop totally unsecure, which I certainly don't
want.

According the MS Knowledge Base article for 314118
PGP 6.5.1 is installing it's kernel-mode drivers
(pgpdisk.sys pgpmemlock.sys) and they are attaching
themselves to the the standard keyboard driver
(I8042prt.sys) and the PGP drivers do not support
Plug and Play I/O request packets (IRPs).

Other than my brute force method of physically
renaming the PGP system32/drivers to a different
set of filenames and rebooting WinXP, I was hoping
for a trick or hack that would allow a user to
remove the association to the keyboard driver from
the PGP drivers, or simply terminate the PGP drivers
(assuming the user is finished with using them
for a WinXP session) prior to attempting the power
standby functions from WinXP.

Collapse -
Since paying up seems to cure it, why not?
by R. Proffitt Forum moderator / January 21, 2006 1:44 PM PST

I only offered the link as a possibility. Looks like there is no other known cure.

Happy hunting,

Bob

Popular Forums
icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

HOLIDAY GIFT GUIDE 2017

Cameras that make great holiday gifts

Let them start the new year with a step up in photo and video quality from a phone.