Known Issues
Any issues with screwed up colours can usually be sorted by typing /syssetup or going into the setup dialog in any other method.
VIRUS SCANNERS - Important
Some bright souls have hard-coded the name "moo.dll" as a virus in their virus scanners, some versions of norton pick it up as a virus, The Cleaner does, and some russian named one :D This dll is not a virus, I have scanned it myself with Norton Anti-virus 2002 and have always downloaded the dll from the official moo.dll site www.influenced.net . The best way to check if your dll is a virus, is by scanning it, renaming it and scanning again, and then running it through another ANTI-VIRUS not trojan hunter :) If a virus is still detected, please contact me @ irchs@btinternet.com with what virus was detected, the web site you downloaded the dll from and I will try and deal with it. I assure you that when I upload the dll, that it is as virus free as my anti virus says it is :)
darkenginepro.dll issue
An issue has been noticed with the darkenginepro.dll, it tends to cause an error message relating to line xxxx in systeminfo.mrc. You need to update your version of DirectX to be able to use the new SystemInfo.
Uptime Issues
Some issues have been discovered, symptons are that the uptime just appears as a blank or $null value. To fix this, go into the Options 2 tab and check "Use alternative method to retrieve uptime" and it should sort it straight away.
Peripheral Detection
On "older" operating systems, I could not find a generic registry key that holds the information about the current hardware in the machine. Auto detect works fine on 2000/XP :). If it does detect your hardware incorrectly, you can change it easily via the dialog setup.
Intelligent Custom Line
If too many options are selected, "line too long" errors are likely to occur for obvious reasons :D
Motherboard Monitor
If you experience any problems at all with this program, you can either deactivate it completely from the script in the setup, or make sure its set up properly by checking for your motherboard @ http://mbm.livewiredev.com
All other issues can usually be resolved by using the /uninstallSystemInfo function and then reinstalling it using the correct procedure.
Do not try and edit the script in anyway, it will prolly f*ck up :)