remote wonder rundll32 check-in/suspect

M

mahi

New member
i think i have it...

it seems that everyone (seems is the key word here) that the problem with run dll as an app crashing (during startup) rendering the remote useless, is related to hyperthreading/intel setups..

as a general check-in anyone with this problem post your specs..maybe someone who has some links in ati will look out for us and pass the word along..

maybe we can find a fix for ourselves...since i recieved in aiw 9800 pro the remote worked for 2 weeks (then again when i had to reformat)...

i remember during some searches reading about someone having problems with dual cpus and ati drivers/software..maybe there is a windows hotfix out there that with our collective energies we can come to some common solution..

the x10 driver install thing workd for this problem..but some of the buttons on the remote do not work after that..the regedit hack doesnt help at all (well the problems are different..the look similar but the run dll is a new one)

anyone with this problem (or who happen to have seen it before) check in and post your specs and drivers and give some feedback...lurking here for over a year convinced me to buy an aiw card..and i have seen the power of resolution in the rage community, so i believe (maybe foolishly) that we can get this bug kicked..

abit ic7-g [email protected] (3/2 divide)
corsair pc 3700 (2.5/3/3/6)
audigy2 zs (vanilla)
2 raptors (raid 0 32k stripe)
aiw 9800pro (ati)
bunch-o-junk and a dvd burner i have yet to use....
1 pci card (audigy) in pci slot 4..too many usb devices to count
xp pro/up to date drivers as soon as they look "stable"

seems normal...
but my remote doesnt work
discuss..
 
Re: remote wonder rundll32 check-in/suspect

mahi said:
run dll as an app
Click to expand...

I have the exact same problem. As matter of fact, the stupid msg box is opened right before me. As similar to you, my remote stopped working. I am running ASUS P4C800E Deluxe with ATI AIW 9800 PRO.

Here is more of my problem. Ever since upgrading to ATI AIW 9800 PRO, the MMC TV (version 8.5-8.8) keeps crashing the video adaptor in XP. XP tries to recover this and defaults to 800x600 res 4bit colour!(lol) and hence manual reboot. So I am running CAT 3.10(tried various version with same negative result) with MMC 8.1 . Now, my remote doesn't work! I suspect "ATI USB Wireless Remote Receiver v2.36" driver got to do with my problem. Been trying to uninstall this version 2.36 and install a lower version without much sucess. Everytime I uninstall this version, and install using SETUP of older version like REMOTE 1.4 to 2.0, the driver 2.36 keeps on poping up!!

Anyhow... still problem with REMOTE but TV from MMC 8.1 doesn't seems to crash my video card any more.

running :
ASUS P4C800E Deluxe
ATI AIW 9800 PRO
MMC 8.1
CAT 3.10
REMOTE 1.4-2.2 DOESN'T WORK!! "RUN A DLL AS AN APP PROBLEM"

PEACE.
 
thanks for decoding it..

and yeah the x-10 drivers "work" by stopping the message...
but all the buttons on the remote wont work as advertised..
plus..how many of us bought our cards to have 4 missing buttons (hit the config button with the x-10 drivers installed)

so, its cool that they stop the message..but i didnt pay 400 bucks for a card to not work..
its not a hardware issue..just a software issue that needs attention..i am so not the only one experiencing this problem!..and hyper threading is now mainstream..weather its an x-10 problem, ati problem, microsoft problem, its a problem that will crop up untill either its resolved but the said parties...or better yet i am forced into buying a new "updated" product that by default will solve the problem...

we shouldnt assume that by sitting back and letting ati ignore any problem with their drivers, and tech support tell us reformat is an answer...dont let ati become nvidia (their latest crop of drivers suck..and the mobo drivers dont work with safedisc)they used to be the sme exact thing..the underdog with good support..then morphed into a company that wouldnt support its hard core community (omega drivers were their saving grace for the 4x.xx driver line) but would rather invest time in confusing their bottom line (the innocent guy who wants to play a game and cant descide between a gf3 ir a gf 4mx..sad)..not to say ati is a saint by any means..but their drivers have come a long way from the late 90's till now..and they need to fix the issue...in the end, i figured that our collective minds can get together and maybe find a solution together (i thought i had it at one point..but it stopped in a few days and never worked again)....

i know we arent the only three with this problem...and i have tried everything..they work for a minute..then stop..whats happening to my remote?
 
i think iam the only one with this problem...

anyone here with a i875/865 or amp setup?

and has mmc/remote wonder installed and not having these problems?
 
okay it took me a while to write this post than my window i was typing in decided to FUKKING CLOSE!!!
and i dont feel like rewriting everything again... so ill keep this short


The first time it the RW drivers crashed i updated my CMOS BIOS to a newer version... ill post my specs on the bottom

i got so frustrated i reformatted and the first thing i did was install the RW 2.2 drivers... and it WORKED!!! well for a while anyway... i than installed The ATI MMC v8.8 program and RW crashed, but not before giving me an error saying something about my language pack was wrong or something... and it hasnt worked since

there.
okay heres the specs:
MSI 865 PE NEO2-LS (with bios v1.9)
AIW Radeon 9700 Pro
Logitech Cordless MX Duo
Audigy 2 Platinum Pro EX
Generic 512mb PC-3200 DDR Ram
P4 2.4C Processor
 
stockacura said:
After more decoding of your msg and seaching the forum... http://www.x10.com/support/support_soft1.htm site had the file x10drivers.exe which fixed my problem. Thanks!
Click to expand...

oh. my. god.


THIS SOLVED THE PROBLEM!!!! WOW!!!!!! GOOD JOB MAN!!!!!

i sent a reply to ATI support site and i suggest that you all do the same :) :) :)

okay: quick note, IF it does NOT work at startup, than you need to disable LOAD ON WINDOWS STARTUP... it does not work!! ALSO do NOT place a shortcut in the Start-up directory!! the fastest way to do it is have a desktop icon so its easy to find...

you will need to load the RW app manually AFTER windows does all its warm up crap. MAKE SURE THERE ARE NO INSTANCES OF RW.EXE prior to loading it!


someone should sticky THIS
 
Last edited:
I'm not impressed with this remote at all. This error still comes up after I did this and now I read that it doens't work with usb 2.0. Well that's all I have. Good by AIW.
 
I know this thread is ancient, but I just spent all night trying to get my RW to install fresh, and was getting the RunDLL32 errors constantly. I finally fixed it...what seemed to do the trick for me was as follows:

1) Unplug the receiver.
2) Completely uninstall the RW software via control panel and delete the RemCtrl folder from Program Files.
3) do a C: drive search for X10* and deleting all files & folders found. For me, this was the missing step that solved the problem.
4) Reboot and install the latest RW software version.
5) Reboot again if requested. Plug in the receiver. And it FINALLY worked.
 
Re: remote wonder rundll32 check-in/suspect

Cyber Dog said:
I know this thread is ancient, but I just spent all night trying to get my RW to install fresh, and was getting the RunDLL32 errors constantly. I finally fixed it...what seemed to do the trick for me was as follows:

1) Unplug the receiver.
2) Completely uninstall the RW software via control panel and delete the RemCtrl folder from Program Files.
3) do a C: drive search for X10* and deleting all files & folders found. For me, this was the missing step that solved the problem.
4) Reboot and install the latest RW software version.
5) Reboot again if requested. Plug in the receiver. And it FINALLY worked.
Click to expand...

What version of the RW wonder software are you using?
 
Cyber Dog said:
I know this thread is ancient, but I just spent all night trying to get my RW to install fresh, and was getting the RunDLL32 errors constantly. I finally fixed it...what seemed to do the trick for me was as follows:

1) Unplug the receiver.
2) Completely uninstall the RW software via control panel and delete the RemCtrl folder from Program Files.
3) do a C: drive search for X10* and deleting all files & folders found. For me, this was the missing step that solved the problem.
4) Reboot and install the latest RW software version.
5) Reboot again if requested. Plug in the receiver. And it FINALLY worked.
Click to expand...

Wow, you are excellent, man! I was just about to reinstall XP because of this error, did one last search and found your solution. Works perfectly! Thank you very much! :) I guess, when this error spontaneously appears, some file in the 'X10 Commander' folder must have gotten corrupt somehow. If this is the case, making a backup of this folder when everything works ok, and replacing the bad folder as soon as the error appears might also do the trick.

Cheers!

- spit
 
ati remote wander 1 works with driver v.1.4

ati remote wander 1 works with driver v.1.4

Cyber Dog said:
I know this thread is ancient, but I just spent all night trying to get my RW to install fresh, and was getting the RunDLL32 errors constantly. I finally fixed it...what seemed to do the trick for me was as follows:

1) Unplug the receiver.
2) Completely uninstall the RW software via control panel and delete the RemCtrl folder from Program Files.
3) do a C: drive search for X10* and deleting all files & folders found. For me, this was the missing step that solved the problem.
4) Reboot and install the latest RW software version.
5) Reboot again if requested. Plug in the receiver. And it FINALLY worked.
Click to expand...

:)if you are using ATI RW 1 on xp sp2, install drivers v. 1.4 and after install go to : device manager/usb/ati remote wander/ update driver/choose driver to install/ati wireless remote reciver v2.36. this works...
 
You must log in or register to reply here.
Back
Top