
well, it’s a fine conclusion of the last 4 years here on blog.skaelede.hu

well, it’s a fine conclusion of the last 4 years here on blog.skaelede.hu

well, it’s a fine conclusion of the last 4 years here on blog.skaelede.hu
I always missed the “view image in full screen” mode in my Vista installation, because out of the box it does not work with my Intel 950 video chip – when I clicked the Slide Show button it switched video mode back to something below 1024×768 (I’m using a 19″ LCD with 1440×900 resolution), and created a horrible performance and huge artifacts while switching pictures.
After some goggling, I’ve found the Microsoft KB article id #930102, dealing with “choppy image transition” quality. At the end of the article, you can find the solution: hack the registry, and set the WinSATScore to 500, to use the native video resolution. The transitions will be painstakingly slow, but you can press the Pause button to stop it, BUT going back and forth manually does not include transitions!
I always missed the “view image in full screen” mode in my Vista installation, because out of the box it does not work with my Intel 950 video chip – when I clicked the Slide Show button it switched video mode back to something below 1024×768 (I’m using a 19″ LCD with 1440×900 resolution), and created a horrible performance and huge artifacts while switching pictures.
After some goggling, I’ve found the Microsoft KB article id #930102, dealing with “choppy image transition” quality. At the end of the article, you can find the solution: hack the registry, and set the WinSATScore to 500, to use the native video resolution. The transitions will be painstakingly slow, but you can press the Pause button to stop it, BUT going back and forth manually does not include transitions!
If you want to get all images (and other fancy stuff like scripts, css) from a website (even if the files referenced in the Html source are hosted on other domains), you can do it with the following wget command:
wget -E -H -k -K -p -U "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" http://the.domain/file.name
note: if you don’t specify the browser type, the server possibly will think of you as a Crawler, a search engine bot, and will only serve you the robots.txt file.
If you want to get all images (and other fancy stuff like scripts, css) from a website (even if the files referenced in the Html source are hosted on other domains), you can do it with the following wget command:
wget -E -H -k -K -p -U "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" http://the.domain/file.name
note: if you don’t specify the browser type, the server possibly will think of you as a Crawler, a search engine bot, and will only serve you the robots.txt file.
When rolling out ChromeMailer to the people on the wild internets, some reported problems with missing mailto: handlers in registry. If ChromeMailer redirected you here, please see the steps below to repair your mailto handlers.
NOTE: YOU ARE RESPONSIBLE FOR THE CHANGES YOU MAKE IN YOUR REGISTRY!
There’s two ways to fix the issue:
1) Download fix_mailto.reg , (right click -> save as…) then double click it to install. It will recreate all required nodes.
2) Manually. Open Regedit (Start / Run… or in Vista type Regedit into search)
click on HKEY_CLASSES_ROOT. right click on it, New > key, rename it to “mailto”, then select mailto, New > key, create “shell”, in shell, create “open”, in open create “command”, in command: New > string value .it will create a key named (Default), double click on the (Default), and enter the following:
a) on Vista: C:Program FilesWindows MailWinMail.exe /mailurl:%1
b) on XP: C:Program FilesOutlook Expressmsimn.exe /mailurl:%1
This will reset the mailto: protocol handler to Windows default settings. If you now want to use ChromeMailer, simply run it, press ‘Install as Default Mailer’ and it will work as expected.
People keep asking me, why do they need to use ChromeMailer, how it differs from the good old registry hacks?
Here’s the technical information: ChromeMailer modifies the default mailto: handler in the registry (HKEY_CLASSES_ROOT || HKEY_CURRENT_USER mailtoshellopencommand), as the good old registry hacks do.
If a computer is a stand-alone one, it will use the HKEY_CLASSES_ROOT,if it’s in a domain it will use HKEY_CURRENT_USER. (others’ settings will not be affected – only if the user is logged in as a Domain Administrator.)
The true difference between the other registry-hacks and ChromeMailer is, that it sets the handler to itself, and rewrites the mailto: parameters.
A valid mailto: is like:
mailto:balint@skaelede.hu?subject=Hello&body=Message&cc=info@skaelede.hu&bcc=hidden@skaelede.hu
If you pass Gmail URL + mailto: params directly to Chrome (or any other browser) in the registry, with %1 parameter, it will truncate some parts of it, because 2 question marks will be in the URL, and it’s not permitted without UrlEncode: so anything after the second will miss.
For example: https://mail.google.com/mail/?extsrc=mailto&url=mailto:balint@skaelede.hu?subject=Hello would show up a window with the to address filled, but subject missing.
Parameter rewrite is the reason for UAC error on Vista, i don’t have $399 to to buy code authentication for my *free* app.
So for a user request, in version 0.2 I added the possibility to use this “truncated” mode, so it will not show up any messages, and will work in 80%…