WiiRD dump loops

[Nuke]

the older and newer version of WiiRD is in the download area.

[Link]

The old one is still online.. http://wiird.l0nk.org/wiird-pbeta.rar

The main problem with the old one is the fact that unfortunately it boots into an immediate crash on Windows Vista x64 or Windows Server 2008 x64. I tried installing Delphi 6 (which was used by kenobi to compile the GUI) on these platforms but it seems to be unable to handle them forcing me to install Delphi 2006. While Delphi 2006 was able to compile the code just fine it brings new features and unfortunately also new bugs.

What I personally like to always ask for: bug reports WHATEVER happens.. so for example the newest release I did has some new bug fixed which was related to the memory viewer: the problem was simple, for some reason the text mode was set to right to left - and Delphi 6 didn't have complete support for that yet, while Delphi 2006 has and well.. it showed memory data backwards. Kinda annoying!

The bug you experience is defenitely not WiiRd GUI related! And the console has always been built with Delphi 2006 and there were no changes to the dump command done! All I did was adding PAL50 support which was kinda overdue as Gecko OS had support for this for long. The GUI was also simply adjusted to support it but that's all. Dump commands were never changed.

My recommendations are:
-check your USB Gecko with another PC or notebook.. try it on another USB port.. and well, believe it or not, I had problems when I was putting the cable under tension.. if it's hanging loose things are working much better for me! Otherwise a simple enlongement would do the job.

Please tell a little bit about your PC configuration. Please note that officially Windows 2000 and XP are supported, I know that Windows 98 and ME did run in my tests but I can't offer complete support. For Vista: we would like to have it supported though there seem to be many problems on Vista with both the console and the GUI and we currently do not have too good in-sight information on these problems.


And as mentioned: please always do bug reports, things like "Can I have the old version" neither help kenobi, me nor you! We are interested in fixing everything, we really are!

[Mouse]

I am on win xp sp1 and I have long usb cable.
I installed latest driver manually thru device manager.
the one that I got from usbgecko download area.

what happened is that the wiirdgui runs and stuck in a loop.
I cant change tabs or click on buttons.  

I run wiirdw32.exe and I was able to get a screen capture ok.  

wiirdgui is only problematic here.

[Mouse]

How can I kill wiirdw32.exe from my process list?  
I wonder if it is causing that problem.  
I tried killing it by many ways.  

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>
D:\wiird>
D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>taskkill /IM wiirdw32.exe /F
SUCCESS: The process "wiirdw32.exe" with PID 3768 has been terminated.

D:\wiird>pskill wiirdw32.exe

PsKill v1.10 - Terminates processes on local or remote systems
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - //www.sysinternals.com

Process wiirdw32.exe killed.


D:\wiird>
D:\wiird>pskill wiirdw32.exe

PsKill v1.10 - Terminates processes on local or remote systems
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - //www.sysinternals.com

Process wiirdw32.exe killed.


D:\wiird>
D:\wiird>pskill wiirdw32.exe

PsKill v1.10 - Terminates processes on local or remote systems
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - //www.sysinternals.com

Process wiirdw32.exe killed.


D:\wiird>
D:\wiird>pskill wiirdw32.exe

PsKill v1.10 - Terminates processes on local or remote systems
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - //www.sysinternals.com

Process wiirdw32.exe killed.

[Link]

If you're running wiirdw32.exe using WiiRd GUI (meaning you open the GUI), the GUI will try everything to not allow wiirdw32.exe to be killed.. the GUI and the console have to be killed together.

For mouse:

Please save your console log and lemme have a look at it!

[Mouse]

I killed wiirdgui first.
I dont see any logs here.