thebeer

I like opera too, but I am using FF for the last 2 years, just installing opera from time to time, on newer releases. In the end, Opera is to unstable for me! And the it has many options, but also many that I don't use, so I prefer the plugins in FF! Just a personal opinion!

Well.. wpa.dbl doesn't work by itself. You have to consider other few stuff, mostly regarding hardware changes. Also, the Volume ID of the C hard drive. Wpa reads that too, and if you format the drive to install windows, it will get changed. You can use "Change Harddisk Volume ID" (search on google for the program) to find that out before installing, and then restore the original value. If you don't do major hardware changes... then there should be no problem, if you use the initial wpa file. Also, for OEM versions, wpa.dbl checks for few oem*.* files in system32 folder (oembios.bin, oembios.sig, oembios.cat, etc), because these files are specially created considering the hardware (in my case, my laptop's motherboard). Actually today I did an experiment, installing a n-lited win version, made from my OEM version, backing-up initially wpa.dbl and the oem files, and restoring them afterwards, and it is working now (only problem was during setup, asking for a oembios.cat, that I forgot to copy to the kit... but it's ok. I think oembios.bin is the most important, along wpa.dbl). It even worked without restoring the original volume ID. (in my previous attempts, without the oem* files, it kept asking for activation) Hope this helps! sorry for my english...