application hangs with 2.7

Chuck Braden jcbraden at
Fri Jun 25 09:40:32 EDT 2010

I get nothing when I double click on the .bat file.  If I try it from a open command prompt window I still get nothing - the command prompt window disappears. 

>>> Daniel Atallah <datallah at> 6/25/2010 8:32 AM >>>
On Fri, Jun 25, 2010 at 09:07, Chuck Braden <jcbraden at> wrote:
> So does the batch file get launched when the application is started and does it just sit and wait for an event? Is it intended to be started after a hang has occurred and the application had to be killed? What is the process to access the file (which I guess is debug.log?)

The batch file is what starts the application - all it does is to
start the application and redirect the debug output to the
%LOCALAPPDATA%\.purple\debuglogs\2010-06-25_08.44.53.40.log (date/time
at which process started) file.  Instead of running Pidgin using your
normal shortcut, it is launched using the pidgin.vbs file.

That debug log file is just a text file that you can open in any text editor.

The idea is that we can look at that debug log and see if there is
anything there that can give us an indication of why it is hanging.


>>>> Daniel Atallah <datallah at> 6/24/2010 3:14 PM >>>
> On Thu, Jun 24, 2010 at 14:59, Chuck Braden <jcbraden at> wrote:
>> So is the creation of a pidgin.vbs file supposed to be able to start the application in the mode that will generate the debug log? I get nothing when I double-click on a file with the following attributes.
>> Set WshShell = WScript.CreateObject("WScript.Shell")
>> obj = WshShell.Run("pidgin.bat", 0)
>> It is associated with a Microsoft Windows based script host. Does it need to be associated with a different application/program?
> That is correct - it is just a MSSH script to launch the pidgin batch
> file and hide the console window.
> -D
> _______________________________________________
> Support at mailing list
> Want to unsubscribe?  Use this link:

More information about the Support mailing list