? RW->RUNDLL32 Sticks (In Process List)

Synetech

Synetech

New member
Hi,

This problem has been around for as long as I can remember. :bleh:

Whenever I run the Remote Wonder software (the control panel), it starts an instance of RUNDLL32 which stays active (can be seen in the task manager) indefinitely, even if I close the app. I can manually kill RUNDLL32 and the remote continues to work properly.

I presume that this is just poor programming because it is clearly not nessecary since it works if RUNDLL is killed. The RW control app is the only program I have seen which uses RUNDLL32 and leaves it running; I hope that it can be fixed soon.
 
Does anyone know how to kill this process from loading up everytime ATIRW.EXE is started?!? I tried reinstalling RW and MMC a bajillion times and it still won't go away. I didn't have this problem before and I don't know how to fix it.

Edit: If this helps, I found this entry in Window's Registry, C:\WINDOWS\system32\rundll32.exe C:\PROGRA~1\ATIMUL~1\RemCtrl\x10net.dll,EntryPoint.
 
Last edited:
I went ahead and deleted the registry entry with no apparent ill effects and rundll32.exe doesn't start anymore.
 
Nope, no good. That seems to work if you've got a Remote Wonder II (and probably a Plus), but if you're using a Remote Wonder, then it won't work at all if you remove that entry. Even if you're using a newer remote, chances are that it uses some function or API from the base RW DLL that you just haven't used yet.

This is poor design, but worse is that it stays resident even after you quit the program.
 
Synetech said:
Nope, no good. That seems to work if you've got a Remote Wonder II (and probably a Plus), but if you're using a Remote Wonder, then it won't work at all if you remove that entry. Even if you're using a newer remote, chances are that it uses some function or API from the base RW DLL that you just haven't used yet.

This is poor design, but worse is that it stays resident even after you quit the program.
Click to expand...

I do have the remote wonder II. The registry entry I deleted may be used to install the rwII drivers, but once the rwII is installed it may not be needed anymore. I could be wrong and there is some loss of functionality with my rwII, but for now it's a solution I'm happy with at the moment. I know how fustrating this software is and I'm sorry this didn't work for you.
 
Actually, I rarely use them at all so I'm not concerned. I just wanted to warn people using the older remote.

The class interface in question seems to be a server component. I'm not sure where that comes in, but it doesn't affect the RWII that I can tell.
 
I’m still looking for a way to stop it from running, but in the meantime, it seems that rundll32.exe can safely be terminated (aka killed) after startup.
 
You must log in or register to reply here.
Back
Top