Showing posts with label Windows xp. Show all posts
Showing posts with label Windows xp. Show all posts

Monday, July 12, 2021

Obscure ways to get an old hp printer driver for Windows XP

So, some people are stuck on Windows xp, as may be some computers. But files do need printing. This set of instructions is good for other hardware connected to a computer with Windows xp, but with that operating system no longer supported by the hardware manufacturer.

The combo printer, scanner and copier is hp LaserJet Pro MFP M28w.

Officially, hp no longer supports Windows xp, so they no longer offer drivers for it. Microsoft also seems to have shut off Windows Update support for Windows xp. Otherwise, it would have been possible to use Windows Update to automatically download and install the necessary drivers.

32-bit drivers meant for Windows 7 might not work. In my case, the installation failed because of a file certificate error.

On attempting to launch one of the files extracted from the downloaded printer driver installer for Windows 7, the said file required Microsoft .NET Framework 4.0. To be safe, download and install that component first, as did I.

When using Internet search, I discovered, that there are slightly older versions of basic hp drivers for that model of device, but download locations offering that driver version were not particularly trustworthy.

But knowledge of older basic drivers for Windows xp got me the bright idea to check out the Windows Update Catalog.

First, on connecting the printer combo via USB showed me the display name of the printer's model:
HPHP LaserJet MFP M28-M31
("HPHP" is not a mistake; this is how it was actually displayed.)

This proved useful when searching the catalog:

As with any other obscure driver, go to catalog.update.microsoft.com, and search for
m28-m31 xp
in the case of this printer combo. "m28-m31" is the device model range, as displayed in the Found New Hardware wizard. "xp" should be self-explanatory, but searching without it will yield over a hundred results, which would be cumbersome to look through in search for a driver meant for only one major version of Windows.

A helpful demonstration link for this search is here.

The search yielded 14 results with the same file size, so this meant, that the printer combo is made up of several discreet integrated devices, with a driver for each, but in one and the same package.

To be safe, pick the package that does not mention "Windows XP 64-bit" in the table row.

On clicking "Download", I downloaded a 32.8 MB .cab file with a long file name made up of hexadecimal symbols.

Using 7-Zip, I extracted the CAB file into a new folder, and browsed to that folder in Windows Explorer.

Keep in mind, that I usually have set Windows Explorer to show system files, including .inf files.

The extracted folder contains several .inf files, and these and other .inf files in the extracted bunch of files are driver installation files.

Other subfolders were the following:
  • amd64
  • drivers
  • i386
  • XPV
Right-click on all the .inf files, and click Install for each of them.

The .inf files should have correct information built-in as to bitness, so, that 32-bit drivers are installed in a 32-bit system.

The XPV folder also contains .inf files, and these pertain to the printing function. Right-click on those, too, and click 'Install' for their context menus.

Restart Windows.

On restart and login, most drivers for the affected hardware should install correctly, but getting the printer to be recognised may require more work, if the printer happens to be not listed in the Printers and Faxes Control Panel folder.

My memory is iffy here, but the basic gist is this:

In that same Printers and Faxes folder, click on "Add a printer" in the left-side Printer Tasks Explorer sidebar, or select File > Add a printer from the menu bar.

This launches the Add Printer wizard. There, click Next.

Select the 'Local printer attached to this computer' radio button. The checkbox to automatically detect the Plug and Play printer is optional (this function might not work).

Click Next to select a printer port.

The "Use the following port:" radio button must be checked. From the drop-down menu, pick the port that displays as "USB00x (Virtual printer port for USB)" (x is a number). Click Next.

After that, installation should commence, and one would then be provided with printer options.

The printer test page printed correctly, and I was happy.

Caveat: If there are two or more listed virtual printer ports for USB, repeat Add Printer routine, and click next. If the printer is already listed and shown as 'not connected' (faded out), right-click on the item, click on Properties.

In the Properties window for that printer, click on the Ports tab. In the list, pick the USB port that works.

A few hours after that, I discovered the driver installation CD for that same printer/scanner/copier combo, but if memory serves, it did not contain drivers for Windows xp when I first wanted to install drivers on Windows XP for that printer several years ago.

The thought of trying Windows Update did not come to mind, because: Microsoft had stopped issuing updates for Windows xp, and there were serious performance issues with Windows Update in that computer, as Windows Update had at times stopped working properly, and was taking up huge CPU resources. Had I not had issues with Windows Update on that computer, I'd have probably tried Windows Update, as it still supported Windows XP at the time.

Monday, August 24, 2020

Как быстро скачать современный браузер для "свежего" Windows xp

У, первый пост на русском :-)

Тут более-или-менее копия реплая

Итак, на этом видео видно, что у автора SuperGTOR не удалось сразу скачать Google Chrome с браузером Internet Explorer 6.0, версия которая уже очень устарела (скоро 20 лет будет), и ему надо было сначала скачать обновления для операционной системы, чтоб скачать Internet Explorer 8.0, а тем уже Chrome.

Вместо Chrome возможно так быстро (без обновлений) с браузером Internet Explorer 6.0 скачать Firefox, аж с официального FTP-сайта Мозиллы, так как тот сайт доступен и без https протокола, с простым протоколом http — http://ftp.mozilla.org/pub/firefox/releases/ — и скачать версию 52.9.0esr.
Тем же методом возможно скачать на старые версии Андройда APK-пакеты браузера Firefox для Android, из папки /pub/mobile/releases/ (пакеты под именем Fennec): Firefox 31.0 последний для Android 2.2, Firefox 47.0 для Android 2.3 (Android API 9), Firefox 55.0.2 для Android 4.0 (но Firefox 31.3.0esr, если архитектура процессора ARMv6). Расширение NoScript Anywhere, скачаемый с официалного сайта NoScript, очень поможет.
52.9.0 самая последняя версия Firefox для Windows XP, и та поддерживает криптографический протокол TLS 1.2. Существует и поддержка TLS версии 1.3, но та по умолчению не вклюычена. Чтоб влкючить (а надо), тогда на странице настроек about:config у настройки security.tls.version.max ставить цифру 4 (вместо 3).

Ещё надо (т.е. очень рекомендую) скачать расширение NoScript для защиты от скриптов, тракеров, рекламы, фонтов, и подобного хлама. Для классического Firefoxa подходит и классическая версия расширения NoScript 5.1.9. Чтоб инсталлировать эту версию, надо на странице настроек about:config менять настройку xpinstall.signatures.required на false (неверен / неверный), чтоб Firefox на заблокировал бы инсталляцию расширения из-за отсутсвия цифровой сигнатуры. Вот и всё.

А оттуда с Firefox-ом возможно скачать другие браузеры: New Moon или MyPal и/или что угодно.

Отдельно, в настройках Internet Explorer надо выключить SSL 2.0, SSL 3.0, и включить TLS 1.0. Иначе все сайты с протоколом https с браузера IE совсем недостижимы.

Thursday, November 1, 2018

The two forks of Pale Moon for Windows XP

This was posted as a reply at Google Product Forums. This concerned video stopping every 25 minutes on YouTube during HTML5 playback.

I got to test a long-form YouTube video with New Moon 27.6.0a1, and the 25-minute video lag still happens.

At that point (when video stops during playback), I pause, or move the video progress indicator back a little to keep the video going.
I treat the breaks every 25 minutes like the breaks during tv ads

I'm most likely stuck with that video lag stoppage, as I've chosen to keep a fork of Pale Moon Moon 27.6.x, because that branch still supports cookie prompting.

There are two forks of Pale Moon for Windows XP:

* New Moon — available at RT's Free Soft blog at Blogspot.
This browser is not my main driver.
* MyPal. Of the two, MyPal 27.6.2 is a somewhat later release than New Moon 27.6.0a1, so I just might consider replacing New Moon with MyPal.

The positive side is, that unlike Firefox, the forks support H.264 video, which should play most videos on YouTube, and clips on twitter.

To switch on support for WebM/VP9 in New Moon 27.6.0a1, one can uncheck "Use MSE asynchronously", and then check "Enable MSE for WebM video" in the Content section of the Options window.

Newer versions of forks most likely have H.264 support as built-in. Older versions of New Moon require extracting the lav extension file(s) from lav.7z into the folder where the browser is installed in Program Files.

It should be noted, that New Moon and MyPal 27.6.x are older versions, but support a few bits more functionality than a comparable version of Firefox (38.8).

Saturday, April 7, 2018

Delfi Flash-põhine video, Firefox ja privaatne lehitsemine

Niisiis tekkis hiljuti vajadus vaadata Delfis artikli juurde käivat videot, aga video kohe tööle ei läinud.

Tingimused olid järgmised:
* Inteli integreeritud videoadapteriga (videokaardiga) sülearvuti, mis ei toeta OpenGL-i seda versiooni, kus Firefoxis mängiks HTML5 video;
* Windows XP SP3;
* Mozilla Firefox 38.8 (eestikeelne);
* VLC Media Player (see osutub hiljem oluliseks);
* Flash Player, mida selle vanema versiooni tõttu automaatselt ei aktiveerita;
* Firefoxi privaatse lehitsemise režiim;
* Samuti annab Firefox veebilehtedele teada, et jälitamist ei soovita (küpsised jne.).

Video mitte-esinemisel osutusid peamisteks põhjusteks teatud Delfi jt. domeenidel pluginate ja küpsiste õigused, ehk nende puudumine.

Protsessi kirjeldus


Kuna HTML5 video mängimine ei tööta videoadapteri draiveris OpenGL 2.0 toetuse puudumisel, langeb Delfi pleier tagasi Flashile, mille põhjal hakkab tööle JWPlayer.

Firefox kuni versioonini 43.x (k.a.) toetab küpsiste salvestamise kohta küsimist, kuid see süsteem ei tööta privaatse veebilehitsemise režiimis, ning eeldatavasti ka siis, kui Firefox annab veebilehtedele teada, et jälitamist ei soovita. Viimane võib tähendada, et ei võeta vastu küpsiseid, aga selle protsessi hingeelu ma täpselt ei tunne.

Lahendus


Kuna aga videomängijat ei tulnud ette, selgus lähemal uurimisel, et Flash ja küpsised oleksid teatud domeenidel lubatud.

Muuhulgas asub Flashil põhinev JWPlayer näiteks g3.nh.ee domeenil.

Küpsiste ja pluginate õiguste muutmiseks tuleb teha järgmist:
  • Mine aadressile

    http://g1.nh.ee/ct/ej/arrow_250.png

    Ette tuleb PNG-formaadis olev noolepilt, ning väljaspoolt pilti tee lehitseja (musta värvi) vaatealale paremklikk ja vali hüpikmenüüst "Vaata veebilehe teavet".
  • Uues aknas "Veebilehe teave" mine vahekaardile Õigused, ning erinevate õiguste nimekirjas tee järgmised muudatused:
    • Sektsioonis Pluginate aktiveerimine vali raadionupp "Lubatud" igal real, kus on "VLC Web", sh. ka see VLC rida, kus võib olla kirjas "Plugin võib sisaldada turvaauku!" Seletuseks niipalju, et peale VLC installimist on Flash-plugin märgitud mingil põhjusel VLC-ks.
    • Keri nimekirjas alla, kuni jõuad eraldiseni Küpsiste salvestamine.
      Seal vali "Lubatud" või "Lubatud selleks seansiks".
    • Korda sama asja järgmistel aadressidel:
      • Delfi koduleht (www.delfi.ee) või vajadusel mõni muu Delfi alamleht, mille artiklis näidatakse videot, nagu näiteks Delfi Publik (publik.delfi.ee)
      • Delfit toetavad domeenid:
        • http://g1.nh.ee/ct/ej/arrow_250.png
        • http://g3.nh.ee/m/dd/nupp.png
      • JWPlayeri domeen:
        https://ssl.p.jwpcdn.com/6/12/logo.png
      • Video lähtedomeen aadressil eeds.babahhcdn.com või mõni muu babahhcdn.com alamdomeen:
        http://eeds.babahhcdn.com/crossdomain.xml
  • Videot sisaldav artikli lehekülg tuli uuesti laadida.
Suurema osa näitefailide asukohad sain kätte klikkides näiteks Delfi artiklil "Vaata veebilehe teavet" ja siis selle akna sektsioonist "Meedia". Ülejäänud asukohad sain teada Firefoxi veebiarendaja Network tööriista ja Internetiotsinguga. (Nii või teisiti olid failide asukohtad avalikult kättesaadavad.)

Saturday, October 8, 2016

Windows: Creating a shortcut to select a file in a folder

I often need to find out which version of Skype installer was automatically downloaded into the local temp folder.

While the Windows UI makes it possible to create simple shortcuts, then there is no UI for more complex stuff.

After some searching, the correct Target line in the shortcut properties must be this:

C:\WINDOWS\explorer.exe ,/select="C:\Documents and Settings\A User's Account Name\Local Settings\temp\SkypeSetup.exe"

It is important to separate the executive and its options from each other with a space, after which the comma starts in that line.

This also works from the command prompt.

Applies to Windows XP, but should also work in other Windows versions. YMMV.

Tuesday, August 12, 2014

Android telefoniga mobiil-Interneti jagamine läbi Wi-Fi

Seadmete opsüsteemid:
• Samsungi telefonis Android 2.3.6 (eestikeelse kasutajaliidesega);
• arvutil Windows XP SP3, mis on ingliskeelse kasutajaliidese ja Windowsi enda Wi-Fi tööriistadega ühendumiseks.
Mida teha, kui arvutil on ThinkVantage Access Connections

Artikkel eeldab juba nii Androidi-nutitelefoni kui ka Windowsi kasutamise oskust teataval tasemel.

Niisiis selgus kõige alguses, et nutitelefonis peab Wi-Fi ise samal ajal välja lülitatud olema.

Kõigepealt tuleb kindlaks teha, et mobiil-Interneti võrguseaded on enam-vähem korras:
    Seaded  
  • Juhtmevaba võrk ja võrk >
    • Mobiilsidevõrgud >
        Pääsupunktide nimed >
      • Elisa:
        (•) internet.elisa.ee
        wap.elisa.ee või mms.elisa.ee vms asemel.
         
      • EMT:
        (•) internet.emt.ee
        wap.emt.ee või wap2.emt.ee või mms.emt.ee asemel.

        Android nutitelefon võimaldab kasutada nii tavalisi Interneti-lehekülgi kui ka lehitseda wap-lehtedel. Nendel juhtudel, kus mobiiliteenuse paketis on mobiil-Internetile mahupiirangud, mille ületamisel tuleb oluliselt rohkem maksta, on wap-lehtedel lehitsemine odavam. Soodsa paketita kõnekaardi omanikele Android-nutitelefonis mobiil-andmeside ei soovita, kuna paljud teenused ja programmid soovivad automaatselt ühenduda ja kohe andmeid vahetada. Niisugused kõnekaardid sobivad rohkem WAP-lehitsejatega funktsioonitelefonidesse (sh Nokia mitte-Windows nutitelefonid), millega on oluliselt kergem oma Internetiliiklust reguleerida.

Edasi tuleb seadistada Wi-Fi hotspoti (Android 2.3.6-s värdsõna "kuumkoht") juurdepääsupunkt (AP ehk access point) —
    Seaded  
  • Juhtmevaba võrk ja võrk >
    • Modem ja kaasaskantav kuumkoht >
      • Konfig. kaasask. Wifi kuumkohta >

        Võrgu SSID (nimi, mille järgi leiad võrgu üles)
        [Kirjuta oma võrgu nimi. Lubatud on numbrid 0-9 ja tähed A-Z, a-z, sidekriips - ja allkriips _]

        Turvalisus
        Vali [WPA2-PSK]

        Parool
        [Kirjuta tühikuteta vähemalt 8 tähemärki, lubatud on numbrid 0-9 ja tähed a-z (küll mitte suurtähed)]

        [\/] Näita parooli
        — on valik näidata võrguparooli, mille võib Windowsi Notepadis üles kirjutada ja kohe mällu kopeerida (Ctrl+C).

        Vajuta [Salv.] nupule
         

Siiski otsustasin, et enne hotspoti aktiveerimist oleks kasulik mobiilivõrk (pakettandmeside) enne sisse lülitada (võib ka tagurpidi) —

    Seaded  
  • Juhtmevaba võrk ja võrk >
    • Mobiilsidevõrgud >
      • Kasuta pakettandmeside [\/]
        — Kui seda parasjagu vaja pole, ei pea see sees olema.
Nüüd aktiveeri hotspot:
    Seaded  
  • Juhtmevaba võrk ja võrk >
    • Modem ja kaasaskantav kuumkoht >
      • Kaasaskantav Wi-Fi kuumkoht [\/]

        Windowsis otsi Wi-fi võrk ja leia oma võrgu SSID. Vali see ja ühendu.

        Võrguga Ühendumiseks küsib Windows võrguparooli, tihtipeale kahe sisestusväljaga samas dialoogiaknas.
        Sisesta seesama võrguparool, mille oma Wi-Fi võrgu tarvis. Kui tuleb teine väli, siis sinna sama parool uuesti.
        Üleskirjutatud parooli saab kopeerida ja asetada (kleepida) võrguparooli väljale (Ctrl+V).

Ühendumine siis, kui Wi-Fi tööriistaks on ThinkVantage Access Connections

Tingimusteks Windows XP SP3 ja ThinkVantage Access Connections 6.01 (2013, ingliskeelne).

ThinkVantage Access Connections on suurepärane võrguühenduste haldamise programm, mille algselt arendas välja IBM, ning mille arendamist jätkab Lenovo. Access Connectionsi eelis on põhjalik seadistatavus, võimalus luua ja hallata asukohaprofiile ning neid eksportida ja importida ühest arvutist teise. Lisaks kergendab see võrguühenduste haldamist, eriti kui kasutusel on erinevad Windowsi opsüsteemid (XP, Vista, 7, 8, 8.1).

Niisiis järgnev eeldab, et arvuti peamiseks võrguühenduste haldajaks on Windowsi enda asemel ThinkVantage Access Connections (tavaliselt ingliskeelne), mis tuleb kaasa peamiselt ThinkPad sülearvutitega, aga võib-olla ka teiste Lenovo sülearvutitega. Teine eeldus on see, et näiteks kui on Inteli Wi-Fi adapter, siis Inteli Wi-Fi tarkvara ei ole aktiivne ja on maha installitud, kuid adapteri draiverid alles.

Kui hotspotiga nutitelefonil on kõik muud tingimused edukalt täidetud, siis üldine probleem on see, et ThinkVantage Access Connections programmiga ei ole võimalik peale võrguparooli sisestamist Interneti-ühendust saada.

Access Connections on küll palju funktsionaalsem, kuid teatud olukordades mitte nii paindlik kui Windowsi enda võrguhaldustööriistad.

Et kui juba läbi Access Connectionsi oli alguses püütud ühendust võtta, siis Access Connections on juba salvestanud asukohaprofiili, mis kannab mobiiltelefoni AP (access point-i) nimetust. Antud Access Connectionsi versiooniga (6.01) miskipärast ei õnnestunud toimetada äsjaloodud asukohaprofiili, millega ei saanud ühendust (selle ühenduse valiku puhul oli Edit-nupp tuhm). Seega äsjaloodud edutu asukohaprofiil tuli kustutada; Access Connectionsis on sellisel juhul efektiivsem käsitsi uue asukohaprofiili tegemine.

Lahendus seisneb selles, et Wi-Fi seadetes peab konkreetse ühenduse krüpteerimine olema AES ja mitte TKIP.

Kui avada Access Connections põhiaken (tegumiriba märkuste alal must arvuti, mille all juhtmed), siis minna Location Profiles (asukohaprofiilid) vahekaardile, millel ilmub asukohaprofiilide nimekiri.

Eeldusel, et vana ja mittetoimetatav asukohaprofiil on juba kustutatud ning käsitsi uuesti loodud, tuleb seadetes suhteliselt hoolikalt näpuga järge ajada.

Kui Location Profiles vahekaardi nimistus on leitud telefoni AP, valida asukohaprofiil ja klikkida Edit nupule. See kehtib siis asukohaprofiili kohta, mis on saanud eduka ühenduse ja mida saab toimetada.

Aknas Edit Profile: (asukohaprofiili nimi) valida "Wireless Settings" vahekaart.

Et kõik oleks kindel, siis ühenduse tüüp (Connection type) peab olema infrastruktuur (Infrastructure), "Wireless mode" on tavaliselt "Auto". Teisi seadeid (v.a. allolevad) tavaliselt muuta pole vaja.

Kui AP juhtmevabaks turvastandardiks on telefonis valitud WPA2-PSK (Android 2.3.6-s ainuke turvaline valik), siis Access Connections telefoni-wifi asukohaprofiili Wireless Settings vahekaardil on allatulev menüü "Wireless Security Type", kus valida
"Use Wi-Fi Protected Access - Pre Shared Key (WPA-PSK)". Lisaks klikkida Properties nupule, mille järel tuleb ette "Wi-Fi Settings" aken. Seal on järgmised võimalused:
Access point authentication, kus valitud peab olema WPA2-PSK
Data encryption: — Valitud peab saama AES ja mitte TKIP.
Pre-shared key on "Use 8-63 alphanumeric characters (0-9, a-z)"
• Edasi vajadusel sisestada uuesti võrguparool ja vajutada OK.

"Edit Profile" akna "Additional Settings" (täiendavad seaded) vahekaardil on tavaliselt linnuke
\/ Network security juures. Kui vajutada [Settings...] nupule, siis vastutustundlikul kasutajal on tavaliselt välja lülitatud failide ja printerite jagamine, Interneti-ühenduse jagamine, ning sisse on lülitatud Windowsi tulemüür.

Wednesday, July 10, 2013

Windows Update not working, error 0x8DDD0018

This can happen with Windows XP (Service Pack 3), but may not be ruled out for Vista and 7.

Windows Update error 0x8DDD0018, by which the Microsoft Update website now very helpfully explains that one or more of these services are not running:
* Automatic Updates
* Background Intelligent Transfer Service (BITS);
* Event Log

Even if all these services are running, and Windows Update refuses to run, then the culprit is the Windows Installer service not being active.

Run services.msc and then start Windows Installer. Refresh the Windows Update website. #worksforme

Wednesday, September 14, 2011

Lynx: Associating filetypes with a program in Windows

After a few hours of trying and failing in lynx.cfg and searching the Internet, I found a reasonably good collection of ideas (kudos to Kenneth Kwok), which served me with inspiration for a working solution.

• The version of Lynx is 2.8.7rel1, unfortunately it doesn't support SSL (gonna work on getting Lynx with that some day...).
N., 15.09.2011. update: A fully functional and SSL-enabled, albeit an older, 2.8.5rel1, version of the browser is available at Claudio Santambrogio's (csant) website (beware that export and other restrictions may still apply to the downloader's country).

As I needed an SSL-based browser, then out of curiosity I started comparing both Lynx browsers' config files and to my great delight found that csant's external app configuration was more elegant than my previous discovery. Jump to a description of how to implement the better solution.

And yes, the options inspired by Kenneth Kwok are still valid, but there are now less scenarios to use them.
• The operating system is Windows xp SP3, other Windows operating systems may also apply, but exact instructions on how to change environment variables were gleaned from this version of Windows.

Unlike in the linked article, it turned out that I didn't need to use a .mailcap file to associate a helper app.

The interesting part is that Windows Lynx (still) requires batch files to send requests for an external application and a path to them must be set as a global or user environment variable.
  • Create a folder that will hold batch files. I created one in
    C:\Program Files\Lynx\Batches
  • Create an environment variable pointing to that path:

    In My Computer/System Properties > go to Advanced tab > click "Environment Variables" button > in the relevant window's "System variables" section > scroll down to Path, select it, click the Edit button;

    In the path editing window, the Path string is long, but you can add a semicolon to the end of the string (if it's missing), then right after the semicolon add

    C:\Program Files\Lynx\Batches

    and that's it. (No additional semicolon required.)

    Click OK to close the window, click OK in Environment Variables window — This will save and update the path in Windows xp (maybe 2000, too) or newer; click OK for System Properties window.

    You won't need to restart unless it's a Windows 9x OS, for which you'd need to edit autoexec.bat, enter a short-form path à la C:\PROGRA~1\Lynx\Batches and restart the system for changes to take effect.
  • Now, in the C:\Program Files\Lynx\Batches folder itself, assuming you only want an image viewer program to be associated, create paint.bat, edit it as follows:
    @ECHO OFF
    C:\WINDOWS\SYSTEM32\Mspaint.exe %1
    ^ In addition, you may wish to add %2 %3 %n — if you know that there may be more arguments passed from Lynx, but there's usually one.
    Save the batch file.
  • In lynx.cfg (opened either via WordPad or Notepad2 or something that supports both CR & LF newlines), go to a certain place in the file by searching for the image/png pattern. There, you will see which MIME types you must activate for each filetype suffix.

    I uncommented (deleted a hash # from the start of the line) all that were web images, such as those concerning .png, .gif, .jpg and .jpeg.
  • Then in lynx.cfg, go to part of the file using the VIEWER: search pattern. There, you will see a list of program commands associated with a particular MIME-type (they are short by default, because they're typically UNIX-specific).
    N., 15.09.2011.:
    Uncomment, or rather, copy, paste, and uncomment those for image formats, and modify the commands to look like this:
    VIEWER:image/gif:start mspaint %s
    VIEWER:image/png:start mspaint %s
    VIEWER:image/jpeg:start mspaint %s
    VIEWER:image/tiff:start gimp-2.6.exe %s #special case
    • The superb catch ^ is where one must use the start command to invoke a program that's located in the Windows Path environment variable.
    mspaint is the command-line name of the Windows Paint program, which is located in C:\WINDOWS\SYSTEM32 and that address is typically set as one of the locations in the Path environment variable.
    gimp-2.6.exe is a different case, where I separately had to include C:\Program Files\GIMP-2.0\bin in the Path environment variable to make it launch, as for some reason it was impossible to use the full program path in the Lynx config file.
    Uncomment, or rather, copy, paste, and uncomment those for image formats, and modify the commands to look like this:
    VIEWER:image/gif:paint.bat %s&:NON_XWINDOWS
    VIEWER:image/png:paint.bat %s&:NON_XWINDOWS
    VIEWER:image/tiff:gimp.bat %s&:NON_XWINDOWS
    VIEWER:image/jpeg:paint.bat %s&:NON_XWINDOWS
    • Up here ^, add paint.bat right after a colon that follows the mimetype;
    %s is the wildcard for the filename to be entered;
    • The ampersand & is there to leave the program in the background. It can be there in Windows, but it's useful in Unix-like systems.
    :NON_XWINDOWS [sic] basically specifies that the targetted application is not an X Window System program and this option can be there, too. In Windows it may mean that the batch program is not exactly a graphical program either.
  • Save the configuration file and I think you should be done.
    Launch Lynx, go to a page with an image file, then on it, press Enter/Return or the left key to activate.
Similar steps can be made for other filetypes and MIME-types (which can be added, btw, since the list in lynx.cfg is non-exhaustive) and you can add programs different than Paint for other filetypes. Above, I have setup a batch file to run The GIMP for the TIFF filetype.

Saturday, September 3, 2011

Microsoft Security Essentials teeb arvuti aeglaseks?

Kommentaar PM/Tarbija24 artiklile ja selle kommentaaridele

Microsoft Security Essentials[:w:en] programmiga on see jama, et see uuendab väga mahukat moodi ja uuendamise ajal võtab liialt palju arvutiressurssi.

Teine jama on see, et kui arvuti töötab, kuid kui seda ei kasutata, siis hakkab MSE skannima — kujuta ette näiteks ETV-d veebist vaadates ja arvutit otseselt samal ajal mitte kasutades, kui pilt ka väärikal arvutil hakkima ja arvuti aeglaseks läheb.

Lahendus (ingliskeelses Windows XP-s) on järgmine:
Start > Programs > Accessories > System Tools > Scheduled Tasks — seal lülitasin mina välja MPIdleTask eseme.

Soovitan seda teha kogenud kasutajatel näiteks juhtudel, kui nad on sunnitud MSE-ga olema, kuid programmi sellist käitumist ei salli.

K., 15.02.2012. täiendus:
Microsoft Security Essentials programmi uuendamine toimub automaatselt ja sedasi poolenisti eraldi Windows Update teenusest. (Tingimus on, et Windows Update automaatsed uuendused on sisse lülitatud.)

Uuenduste kontrollimine ja automaatne uuendamine toimub iga kord kui Windowsisse sisse logida, sh. peale arvuti sisse lülitamist, peale arvuti "talveunest" sisse lülitamist, peale arvuti unerežiimist sisse lülitamist.

Absoluutselt iga kord. Uuenduste kontroll ja uuendamine võtab endale kogu arvuti tähelepanu ja midagi produktiivset sellel ajal teha ei saa.

Võimalik, et toode oligi mõeldud kodukasutajatele lisaks ka väikeettevõtetes kuni kümnele arvutile (aga ainult seda tüüpi organisatsioonides), seega näiteks väikeettevõtte tööarvutites ei peaks selline uuendamistuhin väga problemaatiline olema, sest väikeettevõtted on tavaliselt väga kitsaste eelarvevõimalustega ja sellises olukorras jääb MSE ainsaks legaalseks tasuta valikuks residentse skanneriga antiviiruste seas.

Tavalisele kodukasutajale, kes arvutit äriks ei kasuta, on olemas ka teistsuguseid variante, nii et MSE-d väga soovitada ei oska.

Wednesday, August 18, 2010

Recap on SeaMonkey 1.1 > 2.0 migration: Add-on caveats

Themes

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.

Extensions (this is the difficult part)

  • Extensions must be installed anew.

  • The whitelist of servers where extensions and themes can be installed from might not be migrated.

  • Globally installing an extension requires administrative rights.

    Unlike with Mozilla Firefox, whereby globally installing an extension installs it into every private user profile for all users of an operating system (so that there are multiple copies around of the same extension), doing this for SeaMonkey actually installs the extension into SeaMonkey's extensions folder that resides in the program's install directory.

    The pitfall is that a limited Windows xp user would then be unable to update a required extension for compatibility. I had that with two spelling dictionaries.

    The quick-and-dirty solution in my case was to temporarily set the user as administrator, update the extension for compatibility and then remove the user's administrator credentials. Bah.

    While global extension installation could potentially be very convenient in terms of getting to install only one extension at once for all profiles (=different SeaMonkey users), it does introduce a number of security and other considerations:

    1. One is that, for example, in Windows xp, SeaMonkey is installed into the Program Files folder, where limited users have limited rights, which means that they cannot update the extension, even for compatibility (can't modify folder contents).

    2. If SeaMonkey were installed into a public directory — such as
      C:\Documents and Settings\All Users\Documents — then the whole suite would be left vulnerable to tampering either by its users or a malicious program (both would have to have awareness of the program's different location).

    3. Change user access rights for relevant extensions' folders where they are in
      Program Files\SeaMonkey\extensions.

      A few words of caution: I have not tried this myself, but some of the user support forum topics related to SeaMonkey have suggested that limited users should be given rights to the whole SeaMonkey install directory, so that they would be able to update their extensions. I do not recommend giving rights to the whole program directory, but giving rights to limited users for only the extensions directories.

      While this would make SeaMonkey reasonably tamper-proof, the extensions would be the few to remain vulnerable to tampering.


      To easily see which add-on is installed into which folder, install the MR Tech Toolkit extension. It extends the Add-on Manager with lots of useful tools, but the function you need is "Browse install directory" when right-clicking an extension.

      Once the Windows Explorer folder for the extension is open, click on the folder whitespace, and on the Properties command. This should open the Properties window for the current folder. There, in the Security tab, click on Users from the Group or User names list and click on the Modify checkbox in the "Allow" column. Click the Apply button, but don't leave the window yet. Click the Advanced button and in the "Advanced Security Settings for extensionfoldername" list, verify that the set permissions for separate user(s) or a group of users apply to "This folder, subfolders and files".

      This action thus leaves SeaMonkey more-or-less tamper-proof, but may leave directories of specific extensions vulnerable to tampering.

    4. Best to install extensions separately into every profile? What if there are more than five users and what if a few of those users have more than one SeaMonkey profile?

  • 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 automatically. 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.

It has always been the developers' intention for Mozilla (later SeaMonkey, which became Mozilla's successor; and a branched-off Mozilla Firefox) to have global and per-user extensions.

Mozilla 1.0 finally came out on 05.06.2002. Seeing what Mozilla 1.0's (minimum) system requirements were (modest by nowadays' standards) can give a helpful glimpse into what kind of hardware and software people were using at that time.

This was an era when single-user operating systems in computers were still a norm: four years after the release of Windows 98 and two years after Windows Me was released. Hard disk capacity then (2001–2002) — well, roughly ten years back — was about 10% of what it is now (2010) and there wasn't any lack of people who used much older computers. It's duly possible that hard disk capacity was seen as a premium back then, because after Mozilla 1.0 was released, it was criticized for its bloat.

Mozilla 1.0's full installer for Windows was 9.8 Mb, releases for Linux were between 11.6–13.9 Mb, and release sizes for exotic operating systems ranged between 16–26 Mb. The size of the Windows installer was actually normal, because the installers for Netscape Communicator 4.x and Internet Explorer 5 weren't all that much more smaller, as both included bundled software.

I guess the bloat factor was two-pronged:

Those who lived through those times, can remember how Internet Explorer reigned supreme.

Actual software bloat

IE users eager to try out something new would probably perform a 'normal' install of Mozilla (or Netscape 6.X) and only thereafter discover that Mozilla wasn't only a browser, but an application suite with an extensive feature set, while Internet Explorer was duly perceived as a stand-alone program. And that the typical installs of Netscape 6.X would also bundle a number of other tag-along apps, like RealPlayer and AOL Instant Messenger.

In all actual fact, Outlook Express, Windows Media Player, Microsoft NetMeeting and various other bits were just as well bundled with large ('Normal'/'Typical') Internet Explorer installations, only that Internet Explorer was marketed by Microsoft as an inalienable part of the Windows operating system; other said programs were bundled as parts of Windows 95OSR2.x, Windows 98/Me and newer. Yet people launching Internet Explorer both on Windows and Mac knew and saw that they were only launching a browser and not a whole suite of applications (e-mail, newsgroups, chat/IM) they probably didn't have any need for.

Slow user interface responsiveness

Much of Mozilla's user-facing behaviour was based on Netscape Communicator 4.x, but its cross-platform user interface toolkit was completely new.

Netscape 6.X and newer were subsequently based on Mozilla's underlying code base. People used to Internet Explorer or even Netscape 4.x found Mozilla 1.0 as not particularly responsive compared to IE and Netscape 4.x and I know I can attest to that when seeing SeaMonkey 1.1.xx work on older hardware.

In terms of system resource usage, Mozilla 1.0 would run more-or-less properly on the kind of metal specified in its system requirements. Nevertheless, the new cross-platform user interface toolkit (intended to ease development, which I believe it did) was not native to any existing operating system and thus imposed a performance penalty on any hardware that wasn't top-of-the line. Hence the talk of bloat.

All this gave plenty of impetus for Mozilla developers to create a separate browser which eventually came to be Mozilla Firefox. And lo and behold, Mozilla Firefox 1.0 ran well and faster on even older hardware (CPU considerations aside).

To continue soon?


What is so great about SeaMonkey, is that the underlying technology didn't change much throughout the great ten years between Mozilla 1.0 and SeaMonkey 1.1.19, which really is proof of the package's superiour design considerations.

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:
  • 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.
Just in case, copy all SeaMonkey 1.1 profile data over to a backup location. Move the SeaMonkey (1.1) Program Files folder to another location. Quit all instances of SeaMonkey 1.1, including the QuickLauncher (removed in 2.0).

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 be

C:\Documents and Settings\Username\Application Data\Mozilla\Profiles\default\g1bb3r1sh.slt

Note that your actual profile folder contains other letters and numbers than g1bb3r1sh.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.
Delete the existing new default profile in SeaMonkey 2.0, quit Profile Manager.

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.
Everything else should be relatively easy. Well, almost.
  • 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 hotkey does.
  • If you use a separate profile for private browsing, re-check your preferences and settings to see that they are all correct.
Otherwise, things should should work the same, just that all this careful migration work takes time.

Wednesday, September 24, 2008

ScanDisk tulemused (eestikeelses) Windows XP-s

Märkus: ScanDisk programm on Windows xp-s CHKDSK nimega.

Event Viewer > Application > Source: Winlogon, ava tulemuste vaatamiseks (peaks olema kõige varasem sissekanne peale restarti).

    Event Viewer'i (sündmustelogi) avamise eri moodused:
     
  • Start > Juhtpaneel > Haldusriistad > Event Viewer
  • Töölaual või Start-menüüs paremklikk Minu arvuti ikoonil > Manage > laienda puumenüüst Event Viewer
  • Start > Käivita..., kirjuta eventvwr.msc ning vajuta OK/Enter.
Abimaterjali sain siit.

Friday, August 29, 2008

Showing exe files' extensions in Windows

Regedit HKCR\exefile, add new string AlwaysShowExt.

The same applies to other filetype descriptions, like exefile, some of which might be more elaborate than that.

Restart.

Saturday, July 26, 2008

gimp-win-remote and Windows Vista

In Windows Vista, opening a file in the same instance of GIMP (2.4.6 is currently the latest) appears to be much trickier than in Windows XP (well, I have yet to try that out there..).
R., 28.09.2012. update:

Turns out that it can be just as tricky on Windows XP, so the same solution applies.
First off, I used to try opening a file through the Open With... command, but that didn't work, because it yielded an error message. Nevertheless, the program was added to the registry and the Open With list, so it was easier to tweak it after that.

To access the Windows Registry, click the Windows button and then the Run... command, type regedit, press Enter, give permission to continue. You can also launch Regedit from the Command Prompt; the principle is the same.

The key that you need to navigate to is

HKEY_CLASSES_ROOT\Applications\gimp-win-remote.exe\shell\open\command

The (Default) string in the right-side view of the key's contents already has the non-working command in it (the format of which usually works with most other apps to open files). Double-click (Default) to modify, and then between the app path and "%1" add with quotes and separate with one space on either size:

"gimp-2.4.exe"

The resulting command should look like this:

"C:\Program Files\GIMP-2.0\bin\gimp-win-remote.exe" "gimp-2.4.exe" "%1"

Click OK, quit the Registry Editor, and now try opening an image file with gimp-win-remote, if an instance of GIMP is open already.

I got the tip from here.

R., 28.09.2012. update

In addition, here's a registry solution to change the gimp-win-remote.exe program name in the Open With list (both in the shortcut menu and the dialog) to something less cryptic, once you're already using the registry to resolve the above situation.

(I tried this out in Windows XP, and I don't know if it will work the same in Windows Vista.)

Move up to

HKEY_CLASSES_ROOT\Applications\gimp-win-remote.exe\shell\open\

— and create a FriendlyAppName string in it:
right-click in empty space of the right pane for the shortcut menu,
choose New > String Value, then write FriendlyAppName for the new value.

Now, that's only a parameter. To change it, double-click on it or press the Enter/Return key for it and write the friendly app name.
Because the Open With dialog sorts programs alphabetically, then GIMP and GNU Image Manipulation Program will appear near the top of the list. The GIMP, which sounds cooler, will then be near the bottom of the list, and reaching it when choosing a program to open a file may require scrolling (at least for the first time). In any way, GIMP 2.6 should already allow adding the Edit with GIMP command to an image file's context menu upon installation or when editing preferences.

In a computer that is used by an average user who understands English, I chose GNU Image Manipulation Program (GIMP) as the friendly app name.

The simple reason was the the long name is self-explanatory and (GIMP) in parentheses is there for future name recognition.