Hi, yes, yes & yes <g>
I agree, these Kernel32 errors are hard to track down. In fact I never really succeeded with this in the past. There are many different problem opportunities - like sloppy programming with (nearly) all kind of software, resulting in various kinds of conflicts, including timing errors and memory conflicts. Short of switching to an other operating system (which one does work better?) all that's left for us to do is eliminate all the other possibilities. Besides known and often reported problems with AV software which can be alleviate by changing versions, I have become used to cleaning my system on a regular basis. For instance from all unneccessary tmp, ff, etc. files and all those temp files my PC gathers during Internet activities. In addition I do clean up my registry - well, not that often, but every now and then. This seems to help a lot indeed. That said, from own experience over quite a long period I find that Win98 is quite stable (ok, I know there are still lots of weak spots <g>). For cleaning up all temp files I use a batch file I got from the Langa list, named CleanAll.bat. It does a really thorough job, and has saved my *** more than once. My favourite registry cleaner is integrated in Juoni Vuorio's jv16Power Tools. It works fast, and without ruining necessary settings like other cleaners used to do (MS's RegClean for instance). (BTW, both these are free tools!). FWIW Tilman ----- Original Message ----- From: "Dan Cline" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 09, 2002 5:41 AM Subject: Re: [LegacyUG] May have found fix-Kernel 32DLL Error > Well, yeah, it may depend on the program version you are running, but > years of experience with a Kernel32.dll fault tells me it's more than > likely system specific with older versions of Windoze and the > interference of one of Microsoft's own programs or a third party file > agitating in the background, anti virus software being one of the main > culprits. > > One classic (to me) was the introduction of advert.dll, a file installed > by a download client (Gozilla?) that raised havoc with browsers, causing > the blue screen of death. Gozilla's little payload (advert.dll) made > calls for advertisement banners while the download client was running, > which triggered an illegal operation on some systems but not others. The > result was, in part, that people made wide-ranging accusations about the > specific applications they were running as being buggy when in fact they > were not. Legacy may not be blameless, but could very well be. > > Kernel32.dll is the heart of the windows OS and these errors are very > hard to track down (according to people a lot smarter than me). > Likewise, a fix on one system may not apply on another. Just some > thoughts. To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
