Posted by
Pate in
Help, News, Troubleshooting, Updates and fixes
Oct 7th, 2010 |
5 Comments
Campus-wide reports tell that a new McAfee definition file detects and removes RooiHub as a trojan. Except for all the bugs, RooiHub does not contain any trojan that we know of.
The generic misclassification is most likely due to the software’s ability to replace itself when a new update is released via the official RooiHub website. We are working on releasing a fix, possibly excluding the auto-updater, to solve the problem.
In the meantime, if you want to try a sane virus-scanner instead, use AVG. You can remove McAfee like so (though we don’t recommend going without anti-virus) with instructions provided by the community (we didn’t test this):
Posted by
Pate in
Help, Troubleshooting
Jul 27th, 2009 |
14 Comments
Cause
- You need the latest ApexDC++ software or it is not installed properly.
Solution
Permanent link to this post (20 words, estimated 5 secs reading time)
Posted by
Pate in
Help, Troubleshooting
Jul 27th, 2009 |
12 Comments
Causes
- Windows Firewall is blocking RooiHub communications.
- No one else on your local area network (LAN) is running rooihub.
Solutions
Any one of the following solutions will suffice. Start with the simplest: the first.
- Open the Control Panel in Windows (or run control from the Run prompt). Disable Windows Firewall.
- Create an exception for the RooiHub executable (RooiHub.exe) in Windows Firewall.
- Allow UDP traffic on port 13000 and TCP traffic on port 6667 and 8067 for chat servers.
- Get other people on your LAN to run RooiHub.
Permanent link to this post (88 words, estimated 21 secs reading time)
Posted by
Pate in
Troubleshooting
Jul 27th, 2009 |
31 Comments
Causes
- RooiHub is already running or did not close properly.
- Another application may be trying to use the RooiHub ports (unlikely).
Solutions
- Close RooiHub it by right-clicking on the RooiHub tray icon and selecting Exit.
- If there is no icon, run taskmgr.exe from the Run prompt and end the “RooiHub.exe” task. Run RooiHub again.
Permanent link to this post (55 words, estimated 13 secs reading time)