Check adsweep an adblock extension for chrome
other alternatives to my original solution:
I love the new Google Chrome Browser, especially theâ€¦:
- – really fast render speed,
- – new tab page
- – and the ability to create a new window from a tab that you drop outside chrome.
Naturally, I am missing all my nice add-ons from Firefox, mainly the adblock add-on!
So I found an alternative solution: using Privoxy. Privoxy is a small web proxy that runs locally and has the ability to filter ads.
- 1. Download & install http://www.privoxy.org/
- 2. And then set Google chromeâ€™s proxy options:
Options->Under the hood->change proxy settings->Lan Settings
Check: “Use a proxy server for your LAN”
And under advanced add proxy address 127.0.0.1 port 8118 for http and secure but leave ftp blank.
Now you can surf the web with Google Chrome and a lot less ads!
Here is the list of add-ons I use to make my Mozilla Thunderbird Mail client more usefull.
- Folder Account
Lets you associate user accounts and identities with specific folders.
- Remember Mismatched Domains
Adds a “Don’t warn me again about this certificate for this domain” checkbox to the Domain Mismatch and Expired Certificate warning windows.
Minimizes Thunderbird windows into the system tray.
gives the possibility to import and export in vCard and vcf format;
- Sync Kolab 1.0.1
SyncKolab reads a selected Imap folder and synchronizes it with the local address book and calendar
Integrates web site based email accounts in to Mozllia Thunderbird: Yahoo, Gmail, Hotmail,…
Suddenly Mozilla Thunderbird started crashing on me. I found out that it was the webmail addon “Hotmail 1.2.15 (live)” which creates the problem. The solution is to upgrade to the newer version 1.2.17, but unfortunately this has to be done manually:
- 1) download the new version of the addon http://webmail.mozdev.org/installation.html (right-click save as).
- 2) start mozilla thunderbird in safemode.
- 3) drag & drop the downloaded extension into the addon manager.
- 4) restart Thunderbird.
There is a new CRM/ERP/BUSINESS web app in town and itâ€™s free (as in beer, for 5 users): Iceberg.
There are two versions a standalone and a server install to be deployed on (MS Sql Server 2005 express & ASP.NET (IIS 5 or 6), but since I have IIS7 and windows 2008 there was some pluming needed before everything worked.
Here is what I configured in IIS 7 to make it work:
- Set the Managed pipeline mode property of the application pool that is running iceberg to Classic
- Under Handler Mappings add a new Script Map
Request path: *.asmx
- For the SQL connection I uncommented the string provided in the web.config file but check that the SQL server is running in SQL mixed authentication mode.
- If there are still problems use the Event Viewer to look at the detailed error log.
While testing seaside when loading the pages locally in firefox I had a long delay. After some digging,
it turns out that the slowness is caused by an IPv6 issue with DNS and can easily be resolved by turning IPv6 support off in Firefox while doing localhost testing. To make the change, type about:config in the address bar, locate the network.dns.disableIPv6 setting and double-click on it to set it to true. This does the trick for the Firefox localhost issue on Vista and everything is running fast again.
as it turns out other people had the same issues but not in relation with seaside, therefore I found it in google only after having discovered the solution by myself.
I am hopping that blogging it under seaside/squeak will help someone save some time.
The loading will get to the point where you click to continue [Mission Splash screen] once you click, the screen goes blank and you hear what sounds like an explosion then nothing. Only a black screen.
I found a solution in the relic forums
Fix for this issue:
Go to this folder:
My documents\My Games\Company of Heroes\Savegames\RelicCOH\Campaigns\cxp2\
Find the file
“oosterbeek_crossing – counterattack.cohsav”
Move this file out of the folder and onto your desktop or delete it.
Run the game, hit continue campaign.
NOTE: This worked for me
J’ai mis en ligne des vidÃ©os, ainsi qu’une description d’un projet de dashboard que j’avais crÃ©e pour le cours de “SystÃ¨me d’Infromation et d’Aide Ã la DÃ©cision”.
A consulter sur mon wiki HEC
Advanced Topics in Programming Languages: Java Puzzlers, Episode VI – Google Tech Talks July 23, 2007
Many other interesting talks at: Google Video Tech Talks
HTC4260xxG9AT00 Firmware A0L2 (May 2, 2007)
The firmware update is only available on a bootable ISO CD-ROM, but the laptop has neither a floppy drive, nor a CD-ROM drive. The update is quiet important since it reduced the noise made by an annoying clicking sound of the hard drive.
If you are in a hurry go directly to Setting up the PXE server
My first attempt was trying to boot on an USB pen drive, but the only time it booted successfully was with a size of a floppy. Unfortunately it is impossible to copy the 18mb content from the CD onto it. Every attempt to expand the size of the bootable dos partition on the USB pen drive resulted in a failure to correctly boot the dos environment.
Second attempt was booting a large disk image over PXE network boot, but that failed, as well.
The final solution that worked was booting a dos floppy with network support from PXE or USB pen drive and then connect to a network share with the content of the firmware updating CD.
Creating the network boot floppy with the right driver (optional)
Creating the driver (optional)
What you will need:
- Extract makev3 to a folder
- In makev3\source create Ã folder name b57
- Extract B57.dos and Protocol.ini from the ibm dos drivers (NDIS2/DOS ) to your makev3\source\b57 folder
- Rename protocol.ini to B57.ini
- Open the file in notepad and remove or comment the line [B57]
- Create a new text file named ndis.txt in the same folder and put a description in it like:
B57 Broadcom NetXtreme Gigabit Ethernet NDIS2 Driver 8.28
- Open a command prompt and go into the makev3 folder and execute make b57
You now have a working b57.cab file under makev3\cabs
Creating the boot floppy
What you will need:
- Extract Batâ€™s Network Boot Disk creator into a folder (for example bfd107)
- Copy the b57.cab into \bfd107\cabs\drivers\ndis\
- Open a command prompt on the folder bfd107 and run bfd â€“i netboot.img
You should have a netboot.img file in your network boot disk creator folder (bfd107)
What you will need:
- Extract TFTP into a folder (tftp)
- Extract pxelinu.0 and memdisk\memdisk from the syslinux-xx.zip file into your tftp directory.
- Copy your netboot.img file into the tftp directory
- Create a folder named pxelinux.cfg (yes, with a .cfg)
- In the pxelinux.cfg folder create a file named default containing this:
- Configure TFTP Settings
Other sites that will help you to configure tftpd
Sharing, Connecting, Patching
What you will need:
- Utility to extract the files from the iso image 7-zip
- The bootable iso image with the firmware files www-307.ibm.com/…
Before we boot we have to configure the share that hosts the files from the iso image
- Extract the content of the image with 7-zip or another program into a folder and share it.
- Network Boot your laptop by pressing F12 at startup
- Choose PCI LAN (you should now be booting via PXE onto netboot.img)
- At the first selection screen I used Boot with emm386 (max memory)
- Running Network Config -> ok
- Auto detect PCI adapter -> Manual -> B57
- Configure your network settings
- TCP/IP or NwLink (IPX/SPX)
If you use TCP/IP be sure that your pc or/and your domain allows login in with the deprecated security levels for dos.
Or you can install the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, under properties of your network connection on your windows machine.
- When you have successfully connected to the network you can type:
net use c: \\your-server\yourshare to connect to the share
- Then you change to the drive and run the firmware updating program:
Warning!, I give you no warranty that it will work correctly for you! The dos environment is not the same as the one booted by the official CD-ROM, but the patching worked for me.
From the readme
Important Notice: Please REMOVE hard drive password.
Otherwise firmware can't be updated with error message.