Login

Enable cams menu paltalk 11.x

Chike

Someone thout it’s smart to disable the menu in cam windos because it makes life too easy.
Or could be he just don’t now what’s what and does what he shouldn’t.
Anyways this is ultra annoying so I made a little application that re-enable them.
It’s just small tray up with a timer, based on Create a System Tray Application in VB.NET

9 thoughts on “Enable cams menu paltalk 11.x”

  2. Very good.. Bro,

    Chike, bro I am Getting an Error when I run the Program! Any Ideas why?…. Windows 7 Professional 32 / Service Pack 1. I also then tried to Download the Project and see if I could build it and run it afterwards, but that throws an error at the Timer function! I also changed the Any CPU to x86, but still getting the same error,

    I have attached an for both of the errors…. Any solution maybe why?

  4. Yes bro! Both of them.

    I tried a lot, Changing the options and the Stringbuilder, still the same. I gave up at the end :D. If you need to check it on Teamviewer just let me know, if thats better for you!

  5. @ChiNa-Man wrote:

    Yes bro! Both of them.

    I tried a lot, Changing the options and the Stringbuilder, still the same. I gave up at the end :D. If you need to check it on Teamviewer just let me know, if thats better for you!

    Post the whole exception text.
    Does it get inside EnumCamWindows, set a breakpoint at first line.

    They fixed the menu in 546 but introduced a new one, sorta LOL.

  7. OK, it’s my fault, not all declarations were consistant, failed for me too if I changed to x86.
    Change all Enum functions and enum procs to have lparam byref

  8. Sorry for Late Reply… OK thanks bro Chike. I will go a head and do that by tomorrow! Heading towards my bed 😀 and up again early morning for work!

  9. omg looooooooll, haha how funny.

    So here I will post the exceptions I’ve got when I tried to run thr program:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

     

    ************** Exception Text **************
System.Runtime.InteropServices.InvalidOleVariantTypeException: Specified OLE variant is invalid.
at CWE.Windows.EnumThreadWindows(Int32 dwThreadId, WNDENUMPROC lpfn, Object& lParam)
at CWE.Main.AppContext.myTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

CWE
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/DevTeam/Downloads/CWE.exe

System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

     

    For example:

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    And when I try to Build or Debug the Project (Visual Studio 2012), I get 3 Different Break Point Errors:

    1st Break Point Error:

    Additional Information: An invalid VARIANT was detected during a conversion from an unmanaged VARIANT to a managed object. Passing invalid VARIANTs to the CLR can cause unexpected exceptions, corruption or data loss.

    2nd Break Point Error:
    A first chance exception of type ‘System.Runtime.InteropServices.InvalidOleVariantTypeException’ occurred in Unknown Module.
    Additional information: Specified OLE variant is invalid.
    If there is a handler for this exception, the program may be safely continued.

    3rd Break Point Error:
    An unhandled exception of type ‘System.Runtime.InteropServices.InvalidOleVariantTypeException’ occurred in Unknown Module.
    Additional information: Specified OLE variant is invalid.
    If there is a handler for this exception, the program may be safely continued.

    Good luck Chike. And by the way, it the first time I have ever seen this Exception Error on my Computer! Usually I have never had problems running any C or NET Programs on my Computer!

Leave a Reply

You must Register or Login to comment on Enable cams menu paltalk 11.x