After I migrated a Windows XP computer from SeaMonkey 1.1.19 to SeaMonkey 2.0.6, it turned out that the program experienced short, yet periodic slowdowns which were also evident in Process Explorer with CPU spikes that were related to the process.
The particular profile of SeaMonkey has the following extensions:
Flashblock 1.3.16, NoScript 2.0.1 and three spelling dictionaries.
As I surfed around to look for any kind of resolution, I stumbled upon the two most relevant forum threads, one in MozillaZine and the other on NoScript.
The best hint was given in this InformAction posting, where the workaround is to disable ABE (Application Boundaries Enforcer), which also disabled the holdups, but I hope for a better solution without sacrificing some on security.
Where to disable ABE:
NoScript Options > Advanced tab > ABE subtab > Remove checkbox at "Enable ABE (Application Boundaries Enforcer)"
Friday, August 13, 2010
Wednesday, August 11, 2010
Fun about Windows
The Guardian's Charlie Brooker:
“Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it.”Source: Microsoft's grinning robots or the Brotherhood of the Mac. Which is worse?
Monday, August 9, 2010
Migrating from SeaMonkey 1.1 to SeaMonkey 2.0
What motivated me to migrate was that YouTube and GMail now use standards that supersede those supported by SeaMonkey 1.1. Yes, the latter is still in many ways a modern browser and application suite and really the last one that still works in Windows 95.
Yet it's become difficult to browse websites, such as Gawker, New York Times and E24.ee, which are very script-heavy and I don't like seeing pop-up notifications about "this or that script taking too long to load" without necessarily losing useful site functionality with NoScript.
As it usually is standard practice when upgrading software from one major version to another, the older major version is typically uninstalled first and then a newer version installed. Windows users may want to restart...
Now, with SeaMonkey versions 1.1 and 2.0 it's far more trickier if a user wants to retain (in effect, migrate) their profile data. The trouble with SeaMonkey 2.0 is that its profile migration is not as elegant as it is, for example, in an upgrade from OpenOffice.org 2.x to 3.x.
Here's why: For profile migration to work, SeaMonkey 1.1 must be set as the default browser. If a user uninstalls it (and dutifully keeps profile data), SeaMonkey 1.1 will cease to exist as an installed application and thus it won't be the default browser. Even if SeaMonkey is installed, but not set as the default browser, SeaMonkey 2.0 will skip the migration routine and will default to creating a blank default profile.
The good points:
Install SeaMonkey 2.0. Don't launch it from the installer, but start the SeaMonkey 2.0 Profile Manager. If it shows the default profile, launch Sm 2.0 and see if it offers to migrate profile data. If not and if you won't see your old bookmarks, then profile data has not been migrated. Quit.
Start the SeaMonkey 2.0 Profile Manager again.
In a command line, go to SeaMonkey 2.0's installed directory, then follow instructions given in a MozillaWiki on SeaMonkey 2.0 profile migration:
Yet it's become difficult to browse websites, such as Gawker, New York Times and E24.ee, which are very script-heavy and I don't like seeing pop-up notifications about "this or that script taking too long to load" without necessarily losing useful site functionality with NoScript.
As it usually is standard practice when upgrading software from one major version to another, the older major version is typically uninstalled first and then a newer version installed. Windows users may want to restart...
Now, with SeaMonkey versions 1.1 and 2.0 it's far more trickier if a user wants to retain (in effect, migrate) their profile data. The trouble with SeaMonkey 2.0 is that its profile migration is not as elegant as it is, for example, in an upgrade from OpenOffice.org 2.x to 3.x.
Here's why: For profile migration to work, SeaMonkey 1.1 must be set as the default browser. If a user uninstalls it (and dutifully keeps profile data), SeaMonkey 1.1 will cease to exist as an installed application and thus it won't be the default browser. Even if SeaMonkey is installed, but not set as the default browser, SeaMonkey 2.0 will skip the migration routine and will default to creating a blank default profile.
The good points:
- SeaMonkey 1.1 and 2.0 can be installed side-by-side;
- In an administrator account, setting SeaMonkey 1.1 as the default browser should work throughout all Windows profiles;
- SeaMonkey 1.1 and 2.0 won't write to each other's profile data;
- I forgot what the fourth point was.
Install SeaMonkey 2.0. Don't launch it from the installer, but start the SeaMonkey 2.0 Profile Manager. If it shows the default profile, launch Sm 2.0 and see if it offers to migrate profile data. If not and if you won't see your old bookmarks, then profile data has not been migrated. Quit.
Start the SeaMonkey 2.0 Profile Manager again.
Just in case: Outside the Profile Manager, open the folder location of your old SeaMonkey 1.1 default profile. In Windows XP This should beDelete the existing new default profile in SeaMonkey 2.0, quit Profile Manager.C:\Documents and Settings\Username\Application Data\Mozilla\Profiles\default\g1bb3r1sh.slt
Note that your actual profile folder contains other letters and numbers thang1bb3r1sh.slt, just that this is a useful example.
Note what the name of your SeaMonkey's default profile directory is. The purpose of this is to see if it's different from SeaMonkey 2.0's and if it is, then it's all fine.
In a command line, go to SeaMonkey 2.0's installed directory, then follow instructions given in a MozillaWiki on SeaMonkey 2.0 profile migration:
- Create a profile with exactly the profile name of your old [default] profile
- and you should now get the migration dialog. Choose which profile to import data from.
- Extensions must be installed anew.
- The whitelist of servers where extensions and themes can be installed from might not be migrated.
- I had trouble installing Flashblock from addons.mozilla.org, so I had to add flashblock.mozdev.org to the whitelist and install from there. No trouble installing NoScript from addons.mozilla.org.
- As it usually is with SeaMonkey browsers, the Flashblock toolbar button will not show automatically. Instead of opening the Preferences window, click on any free space in the SeaMonkey toolbar, then on
Customize...A Firefox-like toolbar customization dialog should show up and the Flashblock toolbar item can be added wherever a user chooses in the toolbar (the standard location was next to the Home button in the Personal Toolbar). Because the computer where I installed SeaMonkey 2.0 does not have a printer, I dragged the printer button off the toolbar. - Server whitelists for Flashblock and NoScript do not migrate. I had to manually type in server names into the new Flashblock whitelist, but I think its file can be migrated (haven't checked how to do it). NoScript allows exporting the whitelist, so I did that from SeaMonkey 1.1 and imported the whitelist in SeaMonkey 2.0 after installing NoScript.
- Even if a profile is migrated, SeaMonkey 2.0 will default to its default theme. If you used a Modern theme (built-in), then you'll have to choose it from the Add-on Manager and restart SeaMonkey. The selection and amount of themes for SeaMonkey 2.0 is different than for SeaMonkey 1.x.
- Important: Since all cookie data is dutifully copied over during migration, then cookies which have it that a user is still logged in at some e-mail or other service, persist. This means that before migration, users should first log out from all of their services in SeaMonkey 1.1, if they haven't done so before.
- The F10 keyboard shortcut to activate the menu does not work.
Alt+menu hotkeydoes. - If you use a separate profile for private browsing, re-check your preferences and settings to see that they are all correct.
Labels:
cookies,
keyboard shortcut,
Migration,
profile migration,
SeaMonkey,
Windows xp
Wednesday, August 4, 2010
Ctrl+V, Ctrl+C, Ctrl+X disabled, but Shift+Del/Ins & Ctrl+F not?
As the title suggests, it was one day impossible to cut, copy and paste in Windows XP across apps using Ctrl+X, Ctrl+C, Ctrl+V and to use left-Ctrl+PgUp/PgDn to move around tabs in SeaMonkey. Shift+Del, Ctrl+Ins and Shift+Ins worked, so did Ctrl+F, Ctrl+Q and a few other keyboard shortcuts.
The keyboard was Logitech Internet Pro Keyboard (iTouch Pro or somesuch).
I did do my standard run through tech forums (even a keyboard driver change) and scans with software (Spybot Search & Destroy didn't find anything). MBAM found a few things, I deleted them (the scan log of this well below).
LATER it turned out that the non-standard www button on the keyboard was STUCK. I had it moved to normal position and then using the Ctrl+... keys worked like a charm, even after a restart. Trouble was that I failed to test if the Ctrl+ keys also worked after the MBAM scan and correction.
* Some text is in Estonian.
The keyboard was Logitech Internet Pro Keyboard (iTouch Pro or somesuch).
I did do my standard run through tech forums (even a keyboard driver change) and scans with software (Spybot Search & Destroy didn't find anything). MBAM found a few things, I deleted them (the scan log of this well below).
LATER it turned out that the non-standard www button on the keyboard was STUCK. I had it moved to normal position and then using the Ctrl+... keys worked like a charm, even after a restart. Trouble was that I failed to test if the Ctrl+ keys also worked after the MBAM scan and correction.
* Some text is in Estonian.
Malwarebytes' Anti-Malware 1.46
www.malwarebytes.org
Andmebaasi versioon: 4387
Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702
4.08.2010 10:19:46
mbam-log-2010-08-04 (10-19-46).txt
Kontrolli tüüp: Kiirkontroll
Kontrollitud objekte: 180205
Kulunud aeg: 9 minut(id), 31 sekund(id)
Nakatunud mälu objekte: 0
Nakatunud mälu mooduleid: 0
Nakatunud registrivõtmeid: 1
Nakatunud registri väärtusi: 1
Nakatunud registriandmeid: 0
Nakatunud kaustu: 2
Nakatunud faile: 0
Nakatunud mälu objekte:
(Pahavara ei tuvastatud)
Nakatunud mälu mooduleid:
(Pahavara ei tuvastatud)
Nakatunud registrivõtmeid:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{faad2038-c371-473d-86f1-5b11d39c3775} (Rogue.Multiple) -> Quarantined and deleted successfully.
Nakatunud registri väärtusi:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Network\uid (Malware.Trace) -> Quarantined and deleted successfully.
Nakatunud registriandmeid:
(Pahavara ei tuvastatud)
Nakatunud kaustu:
C:\Documents and Settings\All Users\Application Data\SalesMonitor (Rogue.Multiple) -> Quarantined and deleted successfully.
C:\Documents and Settings\All Users\Application Data\SalesMonitor\Data (Rogue.Multiple) -> Quarantined and deleted successfully.
Nakatunud faile:
(Pahavara ei tuvastatud)
Tuesday, April 27, 2010
ID-kaart ja Mozilla Firefox
Kuna ma väga palju ID-kaardi dokumentatsiooni lugenud pole, siis alles hiljuti selgus, et edukaks sisselogimiseks Internetipanka tuleb ID-kaart lugejasse pista veel enne lehitseja avamist.
Asja tuum seisneb nimelt selles, et inimese ID-kaardi sertifikaadid loetakse sisse veebilehitseja avamisel. Kui ID-kaart sisestada juba olemasoleva veebilehitseja sessiooni ajal, siis sertifikaate automaatselt sisse ei loeta. Imelik värk.
Selline olukord tekkis Mozilla Firefox 3.0.19-s Windows Vista SP2 all, kuid ei välista ka, et sama olukord on ka mujal (teistes modernsetes Windowsites ja Firefoxi versioonides. Teistsuguste lehitsejate ja opsüsteemidega ei tea veel). Kaardilugejaks oli OmniKey CardMan 1021.
Asja tuum seisneb nimelt selles, et inimese ID-kaardi sertifikaadid loetakse sisse veebilehitseja avamisel. Kui ID-kaart sisestada juba olemasoleva veebilehitseja sessiooni ajal, siis sertifikaate automaatselt sisse ei loeta. Imelik värk.
Selline olukord tekkis Mozilla Firefox 3.0.19-s Windows Vista SP2 all, kuid ei välista ka, et sama olukord on ka mujal (teistes modernsetes Windowsites ja Firefoxi versioonides. Teistsuguste lehitsejate ja opsüsteemidega ei tea veel). Kaardilugejaks oli OmniKey CardMan 1021.
Friday, April 2, 2010
pilet.ee-sse ei saa sisse
Juhtus selline lugu, et tegelikult päris modernse, kuid õige pisut aegunud Mozilla Firefoxiga (versioon 3.0.19) läksin pilet.ee kodulehele ning seal tekkis selline veateade:
"invalid security certificate".
Veateade annab võimaluse lisada pilet.ee domeen erandite nimekirja, kuid seda pole tegelikult vaja teha.
Sama veateade võib tulla ka teiste vanemate Gecko-põhiste lehitsejatega, nagu näiteks SeaMonkey (Mozilla edasiarendus), K-Meleon, Galeon, Epiphany jt.
Lahendus:
Tarvis on lehitsejale peale panna Sertifitseerimiskeskuse sertifikaadid siit või siit.
See on suhteliselt lihtne, sest sertifikaatidele tuleb peale klikkida ja siis ilmub programmidialoog, mille kaudu saab sertifikaadid lehitsejasse panna. Saab valida vähemalt, et nende sertifikaatidega saab ära tunda veebisaite.
Tuleb tähele panna, et see protseduur tuleb veateate esinemisel teha igas lehitsejas ja lehitsejaprofiilis eraldi. Lähtuda võib kasvõi sellest, kui lehitsejas niisugune veateade tekib.
Kui niisuguseid asju juhtub ka Internet Exploreriga, tuleb sertifikaat samamoodi peale panna.
"invalid security certificate".
Veateade annab võimaluse lisada pilet.ee domeen erandite nimekirja, kuid seda pole tegelikult vaja teha.
Sama veateade võib tulla ka teiste vanemate Gecko-põhiste lehitsejatega, nagu näiteks SeaMonkey (Mozilla edasiarendus), K-Meleon, Galeon, Epiphany jt.
Lahendus:
Tarvis on lehitsejale peale panna Sertifitseerimiskeskuse sertifikaadid siit või siit.
See on suhteliselt lihtne, sest sertifikaatidele tuleb peale klikkida ja siis ilmub programmidialoog, mille kaudu saab sertifikaadid lehitsejasse panna. Saab valida vähemalt, et nende sertifikaatidega saab ära tunda veebisaite.
Tuleb tähele panna, et see protseduur tuleb veateate esinemisel teha igas lehitsejas ja lehitsejaprofiilis eraldi. Lähtuda võib kasvõi sellest, kui lehitsejas niisugune veateade tekib.
Kui niisuguseid asju juhtub ka Internet Exploreriga, tuleb sertifikaat samamoodi peale panna.
Saturday, March 13, 2010
RegCure
Avastasin ühe sugulase arvutist programmi nimega RegCure, justkui oleks tarvis arvutis Windowsi registrit puhastada.
Ehkki Windowsi register on andmebaas, mille heaolust sõltub ka antud opsüsteemi töö, ei ole Windowsi aeglus alati tingitud sellest, et selle registri justkui mingid vead oleksid aegluses süüdi. Tihti põhjustab pikaldust mõni halvasti seatud või kirjutatud riistvara-draiver.
Et adekvaatset infot RegCure kohta on väga raske otsimootoritega leida, tuli mul seda tikutulega otsida.
Siin on siis vähe tasakaalukamat infot programmi kohta:
Complaints Board sait (inglise keeles, vt. kommentaarid)
Kuidas RegCure nimi liigagi tihti otsimootorites esineb (inglise keeles):
How to "Fix" Advertising Keywords
Peale selle soovib RegCure registreerimist, kus lehitsejas tuleb lahti programmi veebisait, mis küsib ees- ja perekonnanime ja e-posti aadressi.
Etem on tõmmata tasuta programm hea reputatsiooniga arendajalt. Kodusel tavakasutajal on hea renomeega arendaja äratundmisel tavaliselt raskusi, seega parim ressurss on Wikipedia (enamasti ingliskeelne, sest seal on kõige parem info).
Kiiruga leidsin CCleaner programmi, millega kohta on ka Wikipedia artikkel inglise keeles.
Kes Windowsi registri puhastamise tagamaadest inglise keeles rohkem lugeda soovib, saab seda siit.
Microsofti toodetest on olemas
Ehkki Windowsi register on andmebaas, mille heaolust sõltub ka antud opsüsteemi töö, ei ole Windowsi aeglus alati tingitud sellest, et selle registri justkui mingid vead oleksid aegluses süüdi. Tihti põhjustab pikaldust mõni halvasti seatud või kirjutatud riistvara-draiver.
Et adekvaatset infot RegCure kohta on väga raske otsimootoritega leida, tuli mul seda tikutulega otsida.
Siin on siis vähe tasakaalukamat infot programmi kohta:
Complaints Board sait (inglise keeles, vt. kommentaarid)
Kuidas RegCure nimi liigagi tihti otsimootorites esineb (inglise keeles):
How to "Fix" Advertising Keywords
Peale selle soovib RegCure registreerimist, kus lehitsejas tuleb lahti programmi veebisait, mis küsib ees- ja perekonnanime ja e-posti aadressi.
Etem on tõmmata tasuta programm hea reputatsiooniga arendajalt. Kodusel tavakasutajal on hea renomeega arendaja äratundmisel tavaliselt raskusi, seega parim ressurss on Wikipedia (enamasti ingliskeelne, sest seal on kõige parem info).
Kiiruga leidsin CCleaner programmi, millega kohta on ka Wikipedia artikkel inglise keeles.
Kes Windowsi registri puhastamise tagamaadest inglise keeles rohkem lugeda soovib, saab seda siit.
Microsofti toodetest on olemas
- Windows Malicious Software Removal Tool (Windowsi pahatahtliku tarkvara eemaldamise tööriist),
- Windows Defender, mis on edestatud
- Microsoft Security Essentials poolt. Viimast lubab litsents kasutada kodus ning ärilistel eesmärkidel vaid kodukontoris — seega välistatud on organisatsioonid ja nende kontorid.
Subscribe to:
Posts (Atom)