Re: Riddle me this...
HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Alwil Avast 4.8 Seamonkey 1.1.14 XP-Pro SP3. I had to uninstall Avast AV 4.8 and reinstall it. As a result of this activity, three changes happened to Seamonkey. 1) ALL my stored passwords disappeared; 2) ALL my stored and perpetual cookies disappeared; 3) My SSL settings were reset to give all warnings. Riddle me that? What does Avast have to do with Seamonkey (and why/how could it make those changes)? I was able to restore passwords/cookies by pulling up last night's backup for the xx.s file, rename the current file, rename the restored file with the current .s file name. All was returned to normal. why don't you ask them?: http://forum.avast.com/index.php I asked and was answered: Simply - avast does not make these changes to browsers, and avast never has a clue what POP mail client is being used and does not make any changes to them. avast's interaction with browsers is limited to intercepting the http calls it makes at the network level and the same goes for the unsecured POP/SMTP calls of mail clients, again at the network level. avast knows nothing of the internal working of any given browser or mail client. I think that there is a probability during the changes you were making to get the USB drive installed SeaMonkey may have had difficulty getting to the stored profile information for your browser and email client and created a new clean profile. So, if Avast did not cause this, and the timing was just coincidental, what would cause Seamonkey to burp as it did? how are we supposed to know. You gave one story to the SM support group, and another to the avast forum. Whats this all about: you were making to get the USB drive installed. Peter, Always happy to have your input. I uninstalled Avast to troubleshoot whether Avast was scanning a new USB hang-on HDD during the boot-up sequence. When connected, Windows was taking an additional minute to boot to the desk top. There was no change in the boot-up behavior with the USB HDD whether or not Avast was installed. With all respect, anything related to the hang-on drive is a red herring. The new drive had been connected for 10 days with no issues with Seamonkey. I uninstalled Avast to see if I could find the source of the elongated boot-up. Avast was not involved. Western Digital tech support stated it was Windows XP recognizing the drive and loading drivers that caused the expanded boot-up. All of this has no apparent bearing on loosing the passwords, cookies, and sll settings. So, if uninstall-install Avast is coincidental, I won't argue. Still, I'd like to understand why/how Seamonkey got scrambled. I am not sure this has some relevance but two AV I recently tried (should have noted their names) considered Seamonkey.exe as a virus and unceremoniously deleted it, with no possibility to recover it! Deleted cookies could have been considered spyware. But I have no explanation for the missing xx.s. Are you sure you did not do something to your profiles, and did you actually search all partitions for the missing files? Sometimes, Windows gets confused when you insert an external drive, and drive letters can get changed without you realizing it immediately. -- John Doue ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Riddle me this...
John Doue wrote: HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Alwil Avast 4.8 Seamonkey 1.1.14 XP-Pro SP3. I had to uninstall Avast AV 4.8 and reinstall it. As a result of this activity, three changes happened to Seamonkey. 1) ALL my stored passwords disappeared; 2) ALL my stored and perpetual cookies disappeared; 3) My SSL settings were reset to give all warnings. Riddle me that? What does Avast have to do with Seamonkey (and why/how could it make those changes)? I was able to restore passwords/cookies by pulling up last night's backup for the xx.s file, rename the current file, rename the restored file with the current .s file name. All was returned to normal. why don't you ask them?: http://forum.avast.com/index.php I asked and was answered: Simply - avast does not make these changes to browsers, and avast never has a clue what POP mail client is being used and does not make any changes to them. avast's interaction with browsers is limited to intercepting the http calls it makes at the network level and the same goes for the unsecured POP/SMTP calls of mail clients, again at the network level. avast knows nothing of the internal working of any given browser or mail client. I think that there is a probability during the changes you were making to get the USB drive installed SeaMonkey may have had difficulty getting to the stored profile information for your browser and email client and created a new clean profile. So, if Avast did not cause this, and the timing was just coincidental, what would cause Seamonkey to burp as it did? how are we supposed to know. You gave one story to the SM support group, and another to the avast forum. Whats this all about: you were making to get the USB drive installed. Peter, Always happy to have your input. I uninstalled Avast to troubleshoot whether Avast was scanning a new USB hang-on HDD during the boot-up sequence. When connected, Windows was taking an additional minute to boot to the desk top. There was no change in the boot-up behavior with the USB HDD whether or not Avast was installed. With all respect, anything related to the hang-on drive is a red herring. The new drive had been connected for 10 days with no issues with Seamonkey. I uninstalled Avast to see if I could find the source of the elongated boot-up. Avast was not involved. Western Digital tech support stated it was Windows XP recognizing the drive and loading drivers that caused the expanded boot-up. All of this has no apparent bearing on loosing the passwords, cookies, and sll settings. So, if uninstall-install Avast is coincidental, I won't argue. Still, I'd like to understand why/how Seamonkey got scrambled. I am not sure this has some relevance but two AV I recently tried (should have noted their names) considered Seamonkey.exe as a virus and unceremoniously deleted it, with no possibility to recover it! Deleted cookies could have been considered spyware. But I have no explanation for the missing xx.s. Are you sure you did not do something to your profiles, and did you actually search all partitions for the missing files? Sometimes, Windows gets confused when you insert an external drive, and drive letters can get changed without you realizing it immediately. The only subdirectory that .s files reside is in the .slt subdirectory. There are several *.s files with several dates, one going back two years, one four years old. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Riddle me this...
HeavyDuty wrote: Mark Hansen wrote: On 01/12/09 18:26, BeeNeR wrote: On or about 1/12/2009 3:58 PM, HeavyDuty typed the following: Alwil Avast 4.8 Seamonkey 1.1.14 XP-Pro SP3. I had to uninstall Avast AV 4.8 and reinstall it. As a result of this activity, three changes happened to Seamonkey. 1) ALL my stored passwords disappeared; 2) ALL my stored and perpetual cookies disappeared; 3) My SSL settings were reset to give all warnings. Riddle me that? What does Avast have to do with Seamonkey (and why/how could it make those changes)? I was able to restore passwords/cookies by pulling up last night's backup for the xx.s file, rename the current file, rename the restored file with the current .s file name. All was returned to normal. Since I'm using Avast 4.8 SM 1.1.14 and Windows 5.1 (XP-Pro) Service Pack 3 also and having none of the above programs, I would look elsewhere for a solution. It's not a Avast or SeaMonkey problem. Since you're using SeaMonkey and don't see the problem, it can't be a problem with SeaMonkey? Right. That's what I meant by anecdotal. If it does not happen to you, it can't be happening to anyone else. Very poor science and illogical. Mr. Spock would be disappointed. This is not fair. Some problems have been experienced by several users, so it is possible to better assess their causes. In the case of a problem like yours, it sounds logical to go to what appears to be the most probable causes first. Then, if the problem is not solved, people have to make educated guesses, try to get more precise information from the poster who sometimes feels offended. But often, useful info comes from facts the OP in good faith, did not think he should have mentionend. And in other cases, we have to hope the answer will come from unexpected places. Nothing to get offended about. -- John Doue ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Riddle me this...
HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Peter Potamus the Purple Hippo wrote: HeavyDuty wrote: Alwil Avast 4.8 Seamonkey 1.1.14 XP-Pro SP3. I had to uninstall Avast AV 4.8 and reinstall it. As a result of this activity, three changes happened to Seamonkey. 1) ALL my stored passwords disappeared; 2) ALL my stored and perpetual cookies disappeared; 3) My SSL settings were reset to give all warnings. Riddle me that? What does Avast have to do with Seamonkey (and why/how could it make those changes)? I was able to restore passwords/cookies by pulling up last night's backup for the xx.s file, rename the current file, rename the restored file with the current .s file name. All was returned to normal. why don't you ask them?: http://forum.avast.com/index.php I asked and was answered: Simply - avast does not make these changes to browsers, and avast never has a clue what POP mail client is being used and does not make any changes to them. avast's interaction with browsers is limited to intercepting the http calls it makes at the network level and the same goes for the unsecured POP/SMTP calls of mail clients, again at the network level. avast knows nothing of the internal working of any given browser or mail client. I think that there is a probability during the changes you were making to get the USB drive installed SeaMonkey may have had difficulty getting to the stored profile information for your browser and email client and created a new clean profile. So, if Avast did not cause this, and the timing was just coincidental, what would cause Seamonkey to burp as it did? how are we supposed to know. You gave one story to the SM support group, and another to the avast forum. Whats this all about: you were making to get the USB drive installed. Peter, Always happy to have your input. I uninstalled Avast to troubleshoot whether Avast was scanning a new USB hang-on HDD during the boot-up sequence. When connected, Windows was taking an additional minute to boot to the desk top. There was no change in the boot-up behavior with the USB HDD whether or not Avast was installed. With all respect, anything related to the hang-on drive is a red herring. The new drive had been connected for 10 days with no issues with Seamonkey. I uninstalled Avast to see if I could find the source of the elongated boot-up. Avast was not involved. Western Digital tech support stated it was Windows XP recognizing the drive and loading drivers that caused the expanded boot-up. All of this has no apparent bearing on loosing the passwords, cookies, and sll settings. So, if uninstall-install Avast is coincidental, I won't argue. Still, I'd like to understand why/how Seamonkey got scrambled. I have an USB Western Digital disk. Sometimes XP did not recognize my external HDD. The only good way of connecting it is to: 1. Power/On PC and HDD(not connected to the usb pc port) 2. Let all boot sequences to finish. 3. Plug the HDD into the usb slot. To disconnect: 1. Power down the pc 2. Disconnect the usb plug 3. Power off the HDD if needed 4. Disconnect the HDD of the power outlet. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
