Maybe you haven't used sockscap32.
it is an usefull utility that can add SOCKS support to the any application that uses MS TCP/IP functions.
You can try SocksCap32 Even application you are running have no support for proxies.
you can add desired application to the Application profile list.
when the application in this list is started in the " Cap" ,it can use a certain proxy automatically ,not needing be configured proxy manually,such as 127.0.0.1:9050 etc.
thus it'll be convenience to use a Application needing proxy.
are you get it?
Edited 1 time(s). Last edit at 10/23/2008 02:00PM by kevinnn.
Quote kevinnn it is an usefull utility that can add SOCKS support to the any application that uses MS TCP/IP functions.
Any application that uses MS TCP/IP functions is not any application.
Quote kevinnn You can try SocksCap32 Even application you are running have no support for proxies.
But km provides support for proxies. You just have to configure it accordingly.
Quote kevinnn you can add desired application to the Application profile list.
when the application in this list is started in the " Cap" ,it can use a certain proxy automatically ,not needing be configured proxy manually,such as 127.0.0.1:9050 etc.
thus it'll be convenience to use a Application needing proxy.
are you get it?
I think so. Is the behavior of km 1.5.1 different from the behavior of Firefox 2.0.0.17 or SeaMonkey 1.1.12 in regard to SocksCap32?
@kevinnn,
It is part of the bug finding and verifying procedure. We users not the devs do the initial tests. To test whether someting is a K-Meleon or GRE problem You use another Gecko browser with the same GRE (e.g. a Firefox or SeaMonkey with GRE 1.8.1.17).
If You find that only K-Meleon 1.5.1 does it - it is either a problem of sockscap32 or K-Meleon.
p.s. & You are the initial finder of the problem = You check it
But why bother? Or does K-Meleon 1.5.1 exist in Your language?
@kko, könnte dies etwa mit dem Sandboxie Problem zusammenhängen?
Mein Problem von neulich scheint von meiner Maus zu sein
Edited 1 time(s). Last edit at 10/24/2008 05:46AM by guenter.
Testing with firefox3.0.3,the problem didn't occur.
ff3.0.3 can worked in the sockscap32 normally,so it probably be a bug of km1.51.
Why can km1.16 and pre-version worked in the sockscap32 normally?
doubting……
Quote guenter Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.8.1.17) Gecko/20080829 Firefox/2.0.0.17 - but I do not know how to run Firefox 2 next to Firefox 3.
You can install them alongside each other - they can share the same profile.
That's irrelevant. I asked for Firefox 2.0.0.17. Firefox 3 is using Gecko 1.9 and is thus not comparable with km 1.5.
i erroneously thought the newest km1.51 used the same GKE as ff3.0.3.
I found ff2.0.0.17 & tested with it . ff2.0.0.17 can use sockscap32 normally .there didn't occur that problem.
Quote
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 Firefox/2.0.0.17
Quote
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080919 K-Meleon/1.5.1
so they should be comparable.probably be a bug of km1.51 self.
Quote kevinnn ff2.0.0.17 can use sockscap32 normally .there didn't occur that problem.
OK. Thank you kevinnn. We can now exclude that it is a problem with Gecko 1.8.1.17 - it's either km 1.5.1 or sockscap. I'll try to investigate this further and file a bug report...
i tested further with km1.5.0 , it can use sockscap32 likewise.
it seems that only km1.5.1 has this bug.
it is helpful for fixing the bug to analyze the change of proxy code between km1.51 and its pre-visions.
Quote
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17pre) Gecko/20080716 K-Meleon/1.5.0
Edited 1 time(s). Last edit at 10/25/2008 04:31PM by kevinnn.