Wiird Error

[Igglyboo]

If you can't see that it says, access violation at address 004D33CD in module 'WiirdGUI.exe'. Read address of 00000001.

I got this after switching the gecko into COM mode but i can't switch it back, any ideas?

[Romaap]

I've had this error a couple of time, don't know what I did.

[Igglyboo]

Does anyone know how to fix this?
I really don't want to reformat my computer, system restore did not work.

[Romaap]

maybe if you re-download WiiRD and WiiRD GUI

[Igglyboo]

I tried that, no luck.
Also, gecko load, and gecko rip(dvd ripping) both work.
Wiird does not tho.

[Jassim]

thats really wiird, lol.

k enough of my lame jokes for now. anyway try re-installing USBgecko, uninstall the drivers then install them again, see if that helps. if u dont know how to just tell me and ill let u know how, its really simple

[Igglyboo]

Yea...
That was the first thing i did, i uninstalled them from the device manager and then manually.
It didn't work either time...

[Link]

Please:

-empty your wiird directory.. or create a new one
-does the WiiRd console (wiirdw32.exe) work properly?
-what operating system do you use? other settings?

[Igglyboo]

-I've done that several times.
-Yes.
-XP

Everything worked fine until I changed it to VCP mode and then changed it back.

[hetoan2]

when i clicked on this thread i thought i got an error again..... was ready to kill my computer but yea i hate that thing i got it about 5 times but i don't know how... might have been a different error....

[Igglyboo]

I couldn't fix it and I got really pissed off so i just reformatted.
I'll leave this open because it seems to be a semi-common problem.

[Romaap]

I got an acces violation error when I was searching in MEM1 and want to do a new search in MEM2 but accidentally forgot to start a NEW search.

[Link]

I checked that in the WiiRd GUI source code.. strange to admit.. that address is not part of the WiiRdGUI.exe assembly it is caused by a Win32 call.

[Igglyboo]

Yea, i thought so.
It's because of the driver, Wiird is not actually causing the error.

[agrs700]

try reinstalling the drivers