Author Topic: Unable to Use System After Extended Time in Standby  (Read 6912 times)

0 Members and 1 Guest are viewing this topic.

Hornus Continuum

  • Guest
Unable to Use System After Extended Time in Standby
« on: August 16, 2003, 11:03:57 AM »
While logged on with a limited account, I used the machine eight to ten hours.  All was normal.  When finished, I put the machine in standby.  Upon returning several hours later, it was no longer in standby; the power button indicator was no longer flashing, and there was light but repeated disk activity.  However, the monitor was still in its low power mode; cycling its power had no effect, as expected since the monitor enters this mode when there is no signal from the video card.  The computer could not be restored to normal operation with either the keyboard or the mouse.  As I didn't think at the time to turn on the printer, which has a USB 2.0 connection, the only option I saw was to force a shut down by pressing and holding the power button.  Upon booting and logging on with an administrator account, all appeared normal.

Examination of the application, security, and system logs revealed nothing useful; however, the scheduled tasks log showed that Symantec NetDetect ran at 08:13:28, ten to fifteen minutes before I noticed the computer was no longer in standby.  This task is only scheduled to run weekly at 01:14 on Saturdays, repeating every 6 hours for up to 48 hours; the option to wake the computer to run the task was disabled.  I saw no reason why it ran at 08:13 on Wednesday.  Also, according to the Avast! Log Viewer, the Virus Chest was accessed at 08:12:59.

I put the computer in standby a second time, checking on it in ten to thirty minute intervals.  After about 6 hours, the same as before, I saw that it was out of standby again and had to be forcibly restarted.  The scheduled tasks log showed that Symantec NetDetect did not run this time, but again, the Avast! Log Viewer indicated that the Virus Chest was accessed around the time that the computer came out of standby.  Having reconfigured the Standard Shield provider shortly before putting the computer in standby the first time, selecting the blocked operations opening file for writing, deleting file, renaming file, and formatting along with the option to deny the operations that should be blocked when Avast! cannot prompt for a response, I changed the latter to allow the operations.  I repeated the test for the second time with the same results, including the Virus Chest access.  Perhaps coincidentally, 6 hours is the power management setting for hibernation.  Since changing the option to allow operations resulted in no joy, I restored its former setting, deny the operations, changed the hibernation power management setting to NEVER, and repeated the test.  8 hours later, the computer was still in standby, and it returned to normal when I moved the mouse.

In addition to the three tests listed here, where I left the computer alone during the test, there were some intermediate tests in which I deliberately brought the computer out of standby.

Theories or suggestions appreciated.   8)


System Configuration:

Intel Celeron @ 2.0 GHz; 256 MB DDR RAM; 60 GB hard drive, two partitions (NTFS bootable partition, FAT32 recovery partition); HP CD-writer/DVD (40x/8x/x8/16x)
HP v70s 17" monitor; HP PS/2 mouse and keyboard; HP Deskjet 3320 printer; HP Scanjet 3500c flatbed scanner

Windows XP Home Edition Version 2002 SP1 with all critical and security updates applied, and DirectX 8.1

Agnitum Outpost Firewall free edition version 1.0.1817.1645; Avast! 4 version 4.0.235; Finjan Software SurfinGuard Pro Version 5.70 (Build 281); Script Sentry v2.7.1; Spybot Search & Destroy 1.2
Internet Explorer 6.0 SP1 with all updates applied; Outlook Express 6.0 SP1 (version 6.00.2800.1123 with all updates applied
Norton SystemWorks 5.0 (2002)

Phoenix BIOS - core version 4.06, BIOS revision 3.11 09/25/02; Intel i845G chipset, Intel Extreme Graphics, updated with current graphics driver; Lucent WinModem - 56k v.92, updated with current modem driver; Realtek RTL8139 Family PCI Fast Ethernet integrated NIC

Stand-alone machine with NIC disabled, two modem connections (only one actively used) each with TCP/IP enabled and NetBIOS over TCP/IP, File and Printer Sharing, and Client for Microsoft Networks disabled
« Last Edit: August 18, 2003, 07:38:47 PM by Hornus Continuum »

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re:Unable to Use System After Extended Time in Standby
« Reply #1 on: August 18, 2003, 11:07:10 AM »
Could you please post the logs regarding Virus chest ?

whocares

  • Guest
Re:Unable to Use System After Extended Time in Standby
« Reply #2 on: August 18, 2003, 12:03:20 PM »
do you have Norton Monitor and Avast shield both active  ?

could be also a problem with Outpost not shutting down (fast enough)

also search MS-Knowledge base or google

what non-critical windowsupdates are not applied ?

Hornus Continuum

  • Guest
Re:Unable to Use System After Extended Time in Standby
« Reply #3 on: August 18, 2003, 07:36:10 PM »
vojtech,

Here are the entries you requested.  Since the entries just prior to my noticing that the system had come out of standby were made under the System account, I've included only similar entries.  Otherwise, there are far too many of them.

13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestAddSystemFiles.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestOpenListLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestNextFileLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestNextFileLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestNextFileLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestCloseListLoc.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestInit.
13.08.2003 08:12:59   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestGetValueLoc.

out of standby.

13.08.2003 10:53:03   NT AUTHORITY\SYSTEM   1092   Info from aswChestS: chestStop.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestAddSystemFiles.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestOpenListLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestCloseListLoc.
13.08.2003 10:54:01   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestInit

13.08.2003 11:07:43   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStop.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestOpenListLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestNextFileLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestNextFileLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestGetValueLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestCloseListLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestNextFileLoc.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestInit.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
13.08.2003 11:08:40   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestAddSystemFiles.

13.08.2003 13:08:51   NT AUTHORITY\SYSTEM   1088   Info from aswChestS: chestStop.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestCloseListLoc.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestInit.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestAddSystemFiles.
13.08.2003 13:09:49   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestOpenListLoc.

out of standby

13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestCloseListLoc.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestInit.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestAddSystemFiles.
13.08.2003 19:18:54   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestOpenListLoc.

out of standby

14.08.2003 03:35:20   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStop.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestOpenListLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestNextFileLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestGetValueLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestCloseListLoc.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestStart TcpIp=0 Lrpc=1.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestAddSystemFiles.
14.08.2003 03:36:18   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chestInit.
14.08.2003 04:33:42   NT AUTHORITY\SYSTEM   1084   Info from aswChestS: chest s_GetList 0017C878.

still in standby

Regards.
Hornus

Hornus Continuum

  • Guest
Re:Unable to Use System After Extended Time in Standby
« Reply #4 on: August 18, 2003, 08:50:34 PM »
whocares,

do you have Norton Monitor and Avast shield both active  ?

If by Norton Monitor you're referring to Norton AntiVirus, then no; it's been uninstalled.  If you're referring to something in Norton SystemWorks: Norton System Doctor was not running.  The Speed Disk service was running, which monitors file accesses so that the optimizer can defrag the drive based on the files' frequency of access, how long it's been since the last access, and whether they were read or write accesses.  The Norton Unerase Protection service was also running, providing the Norton Protected Recycle Bin and Unerase Wizard functionality.  Norton Clean Sweep and Internet Sweep were not running when the problem first occurred.  They only run under an administrator account, not under a limited account like I was using.  However, while I was testing, I was running under an administrative account, and so they were running at that time.

could be also a problem with Outpost not shutting down (fast enough)

Outpost may indeed have shutdown issues; occasionally I find entries indicating that its service terminated unexpectedly.  However, I've never tried to correlate them with what's going on with the system, like Explorer hanging for example.  Be that as it may though, there's no reason for Outpost to shut down when the system enters or exits either standby or hibernation.

also search MS-Knowledge base or google

I did search the knowledge base, but I didn't find anything relevant.  Granted though, I might have given up too easily.  It's tough to be dedicated enough to do a  thorough KB search.  Its search engine frequently returns numerous duplicates and articles that have absolutely nothing to do with anything -- you know, wrong OS, wrong application, wrong topic, FCOL -- along with the obligatory invitations to use the other available support options.   ???  I subscribe to 19 of the Microsoft forums, and I have up to 8 months of posts downloaded.  (I've got tons-o-disk-space --  they take up only 3/4's of a GB.  The forum search and display capabilities are so crude, they can suck-start a Harley.   ;D  It's far easier and faster to search in Outlook Express.)  There's nothing in their forums about it either.

what non-critical windowsupdates are not applied ?

282010:   Recommended Update for Microsoft Jet 4.0 Service Pack 7 (SP7) - Windows XP
The database engine is installed, but no database application is installed on this system.

322011:   You Cannot Preview a Fax in the Fax Console
Microsoft recommends installing this patch only on machines experiencing this specific problem.

815021:   Security Update (Windows XP)
This patch only applies to IIS and the WebDAV protocol, neither of which is installed.

815485:   Wireless (-Fidelity) Protected Access (WPA) support
817778:   Recommended Update for Windows XP SP1  (Advanced Networking Pack for Windows XP)
This is a stand-alone system.

820291:    Recommended Update (Windows XP)
This functionality was made available in SP1, excepting the help button in the diaglog box.  I can live without the button, LOL.

822343:   MS03-022: Flaw in ISAPI Extension for Windows Media Services Could Cause Code Execution
Windows XP is unaffected by this bug.

DirectX 9.0a and 9.0b End-user Runtime
I have no applications or games requiring DirectX 9.0.   :-[

More crap either I don't need and/or want.   ::)
Euro Conversion Tool
Microsoft .NET Framework
Microsoft Windows Journal Viewer (Windows XP viewer for Windows CE Journals)
Windows Messenger 4.7
Windows MovieMaker 2

Regards,
Hornus

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re:Unable to Use System After Extended Time in Standby
« Reply #5 on: August 18, 2003, 10:15:40 PM »
The scheduled tasks log showed that Symantec NetDetect did not run this time...

Perhaps coincidentally, 6 hours is the power management setting for hibernation.  Since changing the option to allow operations resulted in no joy, I restored its former setting, deny the operations, changed the hibernation power management setting to NEVER, and repeated the test.  8 hours later, the computer was still in standby, and it returned to normal when I moved the mouse.


Do you have Norton Antivirus and avast instaled at the same computer?
For hibernation problems, see http://www.microsoft.com/downloads/details.aspx?displaylang=pt-br&FamilyID=4cbc68d2-09e1-4511-af14-03f357180135

Or download the file (patch):
http://download.microsoft.com/download/f/5/5/f553754f-6846-4917-8675-bbf1103362a7/Q330909_WXP_SP2_x86_PTB.exe

This patch correct my hibernation problems...  ;)


The best things in life are free.

Hornus Continuum

  • Guest
Re:Unable to Use System After Extended Time in Standby
« Reply #6 on: August 19, 2003, 12:22:31 AM »
Technical,

Thanx for your reply and for digging up the link to the KB article.

No, NAV isn't installed, but I still use LiveUpdate to update Norton SystemWorks.

I checked out KB 330909.  I do stress my system heavily, not to the extreme mentioned in the article but more than the average I'll bet.  ::)  It's not uncommon for me to have a dozen or more applications running simultaneously.  Is this patch only for systems with 1 GB or more of memory, or does it help with less beefy machines?  Are you aware of any problems resulting from installing it on a computer with less RAM?  I'm interested but concerned because the article didn't state that the patch can be uninstalled.

Will you tell me about the hibernation problems you were having?  I haven't, until now perhaps, had any trouble entering hibernation, but I normally do it manually.  Typically it's because I've a half dozen or so Internet Explorer windows open following several threads on the web, and I want to pick up where I left off.  I did notice, however, about 2, maybe 3 months back, that Internet Explorer and/or Explorer were prone to eventual failures afterward, not coming out of hibernation mind you, but 1 - 3 hours later.  I wouldn't bet any favorite body parts on it :o, but it seems that this started after installing some critical updates.

Regards,
Hornus

whocares

  • Guest
Re:Unable to Use System After Extended Time in Standby
« Reply #7 on: August 19, 2003, 12:38:18 AM »
I wouldn't bet any favorite body parts on it :o, but it seems that this started after installing some critical updates.

Regards,
Hornus

Hi ,
could be XP-kernel / WebDAV-updates..
numerous posts on this for XP.

I'm not an XP-ert, so either wait for some Xp-Pro here,or search some more.

 ;)

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re:Unable to Use System After Extended Time in Standby
« Reply #8 on: August 19, 2003, 04:27:21 AM »
Technical,

No, NAV isn't installed, but I still use LiveUpdate to update Norton SystemWorks.

I checked out KB 330909.  I do stress my system heavily, not to the extreme mentioned in the article but more than the average I'll bet.  ::)  It's not uncommon for me to have a dozen or more applications running simultaneously.  Is this patch only for systems with 1 GB or more of memory, or does it help with less beefy machines?  Are you aware of any problems resulting from installing it on a computer with less RAM?  I'm interested but concerned because the article didn't state that the patch can be uninstalled.

Will you tell me about the hibernation problems you were having?  I haven't, until now perhaps, had any trouble entering hibernation, but I normally do it manually.  Typically it's because I've a half dozen or so Internet Explorer windows open following several threads on the web, and I want to pick up where I left off.  I did notice, however, about 2, maybe 3 months back, that Internet Explorer and/or Explorer were prone to eventual failures afterward, not coming out of hibernation mind you, but 1 - 3 hours later.  I wouldn't bet any favorite body parts on it :o, but it seems that this started after installing some critical updates.

Regards,
Hornus

I´m happy you don´t have Norton Antivirus  :D But if you installed it anytime in the past please, read DOS under XP / NAV http://www.avast.com/forum/index.php?board=1;action=display;threadid=259;start=0

There are lots of post describing the incompatibility between avast and Norton (because of Norton  >:(). A few weeks ago, jv16 PowerTools was a good Registry Cleaner but now it´s shareware (see Freeware completely compatible with avast! on XP Pro http://www.avast.com/forum/index.php?board=1;action=display;threadid=834;start=new).

For RAM memory trouble, try RAMBooster or MemTest (see http://www.avast.com/forum/index.php?board=1;action=display;threadid=834;start=new) is completely compatible with avast and XP Pro

My troubles with hibernation were simple: the computer just shutdown (even if you try Restart or Hibernation), it´s just Power off. Now, it´s working. What did I do? I suppose that I clean backgroud applications (specially from Start Menu and Run) but I´m not sure till today...  :'(

I install the Microsoft patch and have no problems and I have much less than 1 Gb of RAM so I don´t know why the article says that is just for "large RAM users".

Good luck! Cheers.  ;)
The best things in life are free.