WowReader Issues and HelpFollow

I can't get WOW Reader to get my stuff to upload to show my character. It says it uploads it on the program but not here.

I need to ask you this. I have some inter-process protection installed because of some spyware/malware problems we've been having, and it reports when programs try to mess with other programs on the PC. Your WowReader program was recently "busted" for trying to read stuff in an unrelated process. I told the protection suite "no, deny" and WowReader apparently went on about its business and uploaded my character profiles normally.

What are you looking for and what are you doing reading other processes? Why is this necessary to perform WowReader's function and can you stop it?

Thanks for the (probable) explanation that the read-access violation is happening because of EnumProcesses() or a similar call. You might possibly want to add a checkbox option to prevent this process search, lest people get worried.

The funny thing is, though, I can run other process listers and not get that same error from my protection suite.

So you might want to check to see whether you're trying to do anything else (or the library you're calling is inadvertently trying to do something else) as it walks the process list.

How do i add a Character. Sent email have a post on main form. Help plz. I dont have my add character button i used to have.

Edited, Sun Jan 29 17:29:31 2006 by DISU

Edited, Sun Jan 29 19:29:14 2006 by DISU

Is there any plugin/addon available that can show character stats like this through in a VB3 forum??

This had been bugging me for a while. Everything seems to be working fine but I never seen anything in the "uploaded" column when I run the program to upload and I get the feeling that nothing is getting sent.

I did a forum search and the last update I found on the status of a Wowreader version for the macintosh was back from August 2005. I've also found the FAQ answer, but I was just curious if there was any news. I use the hell out of Allakhazam and would like to contribute raw data as well as have my profiles available (and keep my membership paid up). Any hope for us mac types at all?

I fired up WOWReader today, it patched, and now it just endlessly loops throwing up "test" dialog boxes. If I try to kill it via hitting the X button on the window frame, it just pops itself right back up. I have to go to task manager to kill it.

What's going on here?

Got the same problem, endlessly loops throwing up "test" dialog boxes. Worked just fine yesterday

Edited, Fri Feb 3 19:00:06 2006 by Dazanus

as mentioned above, set boni such as Prayer of the Primal
or the 4mana/5sec from the Priests' ZG enchant are not added
as can be seen here:
http://wow.allakhazam.com/profile.html?72012

edit: also reputation seems to be read incorrectly.

Edited, Fri Feb 3 23:18:14 2006 by Unther

Several versions later and I still get the following error if I try to restore WowReader after it is minimized to the system tray.


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

************** Exception Text **************
System.ComponentModel.Win32Exception: Error creating window handle.
at System.Windows.Forms.
NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.
Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at System.Windows.Forms.Control.
RecreateHandleCore()
at System.Windows.Forms.Form.
RecreateHandleCore()
at System.Windows.Forms.Control.
RecreateHandle()
at System.Windows.Forms.Form.
set_ShowInTaskbar(Boolean value)
at wowreader.MainWindow.
menuRestore_Click(Object sender, EventArgs e)
at System.Windows.Forms.MenuItem.
OnClick(EventArgs e)
at System.Windows.Forms.MenuItemData.
Execute()
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.NotifyIcon.
WndProc(Message& msg)
at System.Windows.Forms.NotifyIconNativeWindow.
WndProc(Message& m)
at System.Windows.Forms.NativeWindow.
Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/
v1.1.4322/mscorlib.dll
----------------------------------------
wowreader
Assembly Version: 1.0.2225.36007
Win32 Version: 1.0.2225.36007
CodeBase: file:///C:/Program%20Files/WowReader/
wowreader.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/
system.windows.forms/1.0.5000.0__b77a5c561934e089/
system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/
system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/
system.drawing/1.0.5000.0__b03f5f7f11d50a3a
/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/
system.xml/1.0.5000.0__b77a5c561934e089/
system.xml.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.6.0.0
Win32 Version: 0.6.0.0
CodeBase: file:///C:/Program%20Files/WowReader/
ICSharpCode.SharpZipLib.DLL
----------------------------------------
LuaInterface
Assembly Version: 1.3.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/WowReader/
LuaInterface.DLL
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
[/code]

Darn, mine is still doing it :(