schworgj
asked on
VBScript - How much memory? Processor Info?
I need to get the RAM (total/free) and the processor info (speed/type) without using the WMI because this script will run on Win95/98 boxes that might not have WMI installed.
If it were me, I would script the installation of WMI (via login script) on those Win9x boxes since permissions aren't an issue. The vbScript could then check if WMI is present, collect the inventory. I have an old kixtart script I could post that installs WMI. I know your question was about vbScript, but you can lauch a kixtart script from within vbScript.
ASKER
I have been told that we are not to install anything on these computers. Scripting the install was my first thought too.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Can't use this code in VBScript. At least not the memory section. Thanks for the registry location of the processor. I'll leave the question open a bit longer to see if I can get the memory part answered too then split the points accordingly.
Yeah, if you're stuck with VBScript, your hands are kinda tied. However VBScript can use DLLs. For example, there are a lot of good CPU detection/speed tools available as COM-based DLLs.
Are you at least allowed to register a DLL on these PCs?
Are you at least allowed to register a DLL on these PCs?
ASKER
I got the CPU info out of the registry. It isn't as much info as we would like but it will do. I am amazed that there isn't a simple way to check total/free memory without some DLL or WMI. VBScript is pretty limited in what it can do without external tools.
I don't think we are supose to put anything beyond the single script on the user's PC. Actually, the script is sitting on a network drive and just gets called. Long story but we are trying not to actually install anything beyond a shortcut to this script.
Driving me nuts.
I don't think we are supose to put anything beyond the single script on the user's PC. Actually, the script is sitting on a network drive and just gets called. Long story but we are trying not to actually install anything beyond a shortcut to this script.
Driving me nuts.