As promised, Opera 10 final was released on Sep 1st
|
|||||
|
As promised, Opera 10 final was released on Sep 1st Problem(s):
Explanation:I’m not sure of the exact details, but this is what I think I’ve found. Perhaps someone at Microsoft would correct or elaborate on this. Previously, actxprxy.dll (ActiveX Interface Marshaling Library) was used as the proxy for a multitude of system interfaces, such as IShellFolder and IServiceProvider. In Windows 7 (and probably Vista also), the GUID of this library has changed from {B8DA6310-E19B-11D0-933C-00A0C90DCAA9} to {C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6} Secondly, there is also a new Proxy/Stub provider found in ieproxy.dll of Internet Explorer (IE ActiveX Interface Marshaling Library). Some interfaces that previously used actxprxy.dll are now registered to use ieproxy.dll. Now various problematic software (such as Vault 3.x) will try to register against actxproxy using the old GUID, and for interfaces now proxied by ieproxy.dll. SolutionYou must use regsvr32 to re-register the two proxy DLLs, then reboot You can use the below batch file to do this. You must run this batch file with administrative privileges (right click on the file and choose Run as administrator): If you don’t run the batch file as an administrator, you will get an error as pictured: [Download RegisterActxprxyAndIeproxy.cmd] RegisterActxprxyAndIeproxy.cmd source: @echo off :: 32 bit and 64 bit IF EXIST "%SystemRoot%\System32\actxprxy.dll" "%SystemRoot%\System32\regsvr32.exe" "%SystemRoot%\System32\actxprxy.dll" IF EXIST "%ProgramFiles%\Internet Explorer\ieproxy.dll" "%SystemRoot%\System32\regsvr32.exe" "%ProgramFiles%\Internet Explorer\ieproxy.dll" :: 64 bit only (32bit on 64 bit) IF EXIST "%WinDir%\SysWOW64\actxprxy.dll" "%WinDir%\SysWOW64\regsvr32.exe" "%WinDir%\SysWOW64\actxprxy.dll" IF EXIST "%ProgramFiles(x86)%\Internet Explorer\ieproxy.dll" "%WinDir%\SysWOW64\regsvr32.exe" "%ProgramFiles(x86)%\Internet Explorer\ieproxy.dll" Don’t forget to reboot after re-registering the DLLs! Edit: The script has been updated to support 64-bit Windows Opera 10 Beta 3 is out! The timing is uncanny because the last time I did a clean install of Windows 7, Beta 2 came out hours after I had done a new install. Today I installed Windows 7 RTM on my machine at work, and then hours later, a new beta of Opera 10. What the? I had a bit of trouble getting WC3Banlist (mainly due to its dependency on WinPcap) on Windows 7 This is working on Windows 7 RC1, with User Acount Control (UAC) on (set to Default) I did quite a few things when troubleshooting so it’s hard to replicate the exact steps, but here’s some instructions on how I have it set up now: Install WinPcap
Install WC3Banlist
Run Wc3Banlist
Verify
TroubleshootingIf this still isn’t working, I would recommend turning off UAC and trying again.
Opera 10 Alpha last night prompted me to automatically update, and lo and behold it installed the Beta 1. The most noticeable change is the default skin, which is lighter and more consistent, using some new etching effects and icons everywhere. More changes are on the horizon for this for Beta 2, from the skin designer John Hicks. A cool new enhancement is you can drag down the tab bar to get thumbnails for all the tabs, known as Visual Tabs:
There’s now an interface to customize the Speed Dial (rather than manually editing ini files) Opera Turbo, the Opera proxy service that offers compression of web pages (suitable for low-bandwidth connections) is built in and can be switched on or off or set to auto mode (turning itself on if it detects you’re on a slow internet connection). I have tested this out while I’m on 64kbps, and it’s ok but it’s probably not worth it unless Opera have some New Zealand or Australia proxies. I suspect it would work great in Europe. I’ve been writing some unit tests recently that test some multi-threaded functionality. Typically this involves hooking up some event handlers then waiting for some asynchronous code to fire the event before proceeding with the unit test and assertions. The ManualResetEvent class (MSDN) seems a good choice for this, and this post has a small example of using it in a unit test:
This details how you can debug an application running on a remote machine from Visual Studio on your local machine, as if the remote application was running on your local machine. The keys are:
Create local machine account
Create remote machine account
Run Visual Studio 2008 Remote DebuggerYou have several options for launching the Remote Debugger.
It’s a good idea to run this as a Windows application as recommended by the Visual Studio 2008 Remote Debugger Configuration Wizard (and in my opinion easier to troubleshoot). At this point if you’re not logged in as the new user you created, you might want to do that now so that you can run the Remote Debugger under them. Once you’ve followed instructions for installing, run the remote debugger if it isn’t already by going to Start > Programs > Microsoft Visual Studio 2008 > Visual Studio Tools > Visual Studio 2008 Remote Debugger. It should say that it’s running an instance similar to DebugUser@RemoteMachineName Connect to the remote machine with Visual Studio
uTorrent is one of the most popular BitTorrent clients out there. In my opinion it’s the best. You can set up IP filtering in uTorrent to block bad seeds and peers from a list maintained by the community. How to set up IP filtering in uTorrent
How to get and update the ipfilter.datI’ve written a simple program that will download the ipfilter.dat from SourceForge and copy it into the file where uTorrent expects it. uTorrent IPFilter Updater [ Requires .NET 3.5 ]
How to get uTorrent to pick up the new ipfilter.datYou have two options:
Looking in the Log should show a message similar to “Loaded ipfilter.dat xxxxxx entries)” Because IP ranges and addresses change often, it’s a good idea to update your filter list often too. In some of the work I’m doing right now, I’m manipulating an assembly after compile time – having it disassembled into IL, tweaked, then re-compiled back into an assembly. The assembly is signed and what is being done to the assembly is breaking the strong name. This is quite comforting to know; the strong name wouldn’t be so strong if it was that easy to hack an assembly with a strong name. When trying to load the hacked assembly, I am getting an exception (FileLoadException in this case but I’m guessing this may differ depending on your assembly load method) with the message “Could not load file or assembly ‘MyAssemblyName’ or one of its dependencies. Strong name validation failed.”. The first interesting thing here is that the assembly named in the error message isn’t the hacked assembly; the hacked assembly is one of MyAssemblyName’s dependencies and is what’s triggering the error. Make sure that you check the dependencies of the assembly named in the exception message when troubleshooting. The problem may be with one of the dependencies. In my case the exception isn’t a surprise because of what’s being done to the assembly. But until I resolve that, how can I get around this for now? You can exclude an assembly from strong name validation for development purposes using the Microsoft (R) .NET Framework Strong Name Utility tool aka sn.exe:
Make sure you change the sn.exe path depending on which version of the .NET Framework SDK you have installed. If you’re having trouble, get into the ”%ProgramFiles%\Microsoft SDKs\Windows” dir and search for sn.exe, and use the newest one you can find. You might find it handy to add this as a Post-build event command-line for your project from within Visual Studio in Project Properties > Build Events:
So how do you switch the strong name validation back on for your assembly? Use the -Vu switch:
|
|||||
|
Copyright © 2010 David's Blog - All Rights Reserved |
|||||