If Windows 2000, WMI can pull this info directly out of BIOS - check-out Radimus and Kent's WMIQuery UDF in the UDF library - else SMBIOS.EXE can be used to get at this information as well. Check-out MCA's website site for that !

-Shawn

[ 28 December 2001: Message edited by: Will Hetrick ]

code:

---

:Hardware
	$Biosv=""	$Biosd=""	$Make=""	$Model=""	$SerNo=""	$Case=""
	$CPUfm=""	$CPUsp=""	$dimm1=""	$dimm2=""	$dimm3=""	$memory=""
	if @ras=0
		If exist("c:\smbios.exe")=0
			? "	Installing SMBIOS inspector"
			copy "$logon\smbios.exe" "c:\"
			endif
		endif
	go c:
	cd "c:\"
	del "c:\hardware.lst"
	shell "%comspec% /c c:\smbios.exe >nul"
	sleep 1
	$Biosv=readprofilestring("c:\hardware.lst","Bios","Version")
	$biosd=readprofilestring("c:\hardware.lst","Bios","Date")
	$Make =readprofilestring("c:\hardware.lst","System","Make")
	$Model=readprofilestring("c:\hardware.lst","System","Model")
	$SerNo=readprofilestring("c:\hardware.lst","System","Serial#")
	$Case =readprofilestring("c:\hardware.lst","Case","Type")
	$CPUfm=readprofilestring("c:\hardware.lst","Processor-4","Family")
	$CPUsp=readprofilestring("c:\hardware.lst","Processor-4","CurSpeed")
	if $CPUfm=""	
		$CPUfm=readprofilestring("c:\hardware.lst","Processor-400","Family")
		$CPUsp=readprofilestring("c:\hardware.lst","Processor-400","CurSpeed")
		endif
	select
		case $make="Dell Computer Corporation"
			$dimm1=readprofilestring("c:\hardware.lst","MemDev4352","Size")
			$dimm2=readprofilestring("c:\hardware.lst","MemDev4353","Size")
			$memory=val("$dimm1")+val("$dimm2")
		case $make="Compaq"
			$dimm1=readprofilestring("c:\hardware.lst","MemDev35","Size")
			$dimm2=readprofilestring("c:\hardware.lst","MemDev36","Size")
			$dimm3=readprofilestring("c:\hardware.lst","MemDev37","Size")
			$memory=val("$dimm1")+val("$dimm2")+val("$dimm3")
		endselect
	$freespace=getdiskspace("C:\")
	? "	Computer "color c+/n "Manufacturer " color w/n "is " color w+/n $Make color w/n
	? "	Computer "color c+/n "Model " color w/n "is " color w+/n $Model color w/n
	? "	Computer "color c+/n "Bios " color w/n "is " color w+/n $Biosv color w/n " dated " color w+/n $Biosd color w/n
	? "	Computer "color c+/n "Serial Number " color w/n "is " color w+/n $SerNo color w/n
	? "	Computer "color c+/n "Processor " color w/n "is a " color w+/n $CPUfm color w/n " running at " color w+/n $CPUsp color w/n
	? "	Computer "color c+/n "Memory " color w/n "is " color w+/n $memory " MB" color w/n 
	return
;********************************************* end of Hardware ***********************************************************

---

I've subsequently replaced this with the WMIQuery functions. This is more of an example of the same data in different locations...

This thread looks very interesting.

I also get the same result as Will Hetrick (on my Pentium II/330). It doesn't seem as if the HARDWARE.LST file is being created (anywhere).

However, if I execute from the DOS prompt...
SMBIOS /G >c:hardware.lst
I can see heaps of (valuable) information within the C:\hardware.lst file. The file however, won't be interrogated by Radimus' Kix script.

Radimus....
Can you perhaps elaborate on your comment "I've subsequently replaced this with the WMIQuery functions"

Best regards,
Michael

[ 28 December 2001: Message edited by: Ashpoint ]

Wilbur

Will, potentially Windows security 'might' be an issue, as well as Bios version (doubtful). WMI is build into the Win2k OS, and NT SP4 or better, and WinMe. for 9x you will have to DL and install the WMI components from MSDN

there are a few different versions of SMBIOS out there. The used to use dumped it's output into a INI file structure that readprofilestring can easilly read

I haven't seen it not work on one PC and work on another. As this is a function of the OS, you will need to determine that the function IS being called, and what parameters are being sent

the most likely suspect is something else in the script, perhaps a unmatched quote or a if/endif or a branching weirdness going on.

Are these all the same machine / same bios?
Same OS / Service Pack?
what about IE?

All the machines I've run this on (Compaq Despro EN, 400 & 600, Dell Latitude CPt) are running NT SP5 w/IE 5 or Win2k SP2 IE6.
My Dev machine at home is running XP

BTW, all the machines are picking up the Memory size and speed of processor.
Here is an example of the login data.
Find duplicates for CINFO
Computer, Date, IP Address, Mac Address, Make, Model, Serial Num
RVBIT4-20, 12/31/2001 9:06:36 AM, 10.101.4.20, 00B0D04BB848, , ,
RVBIT4-20, 12/27/2001 8:00:27 AM, 10.101.4.20, 00B0D04BB848, Dell Computer Corporation, OptiPlex GX110, HBIT4

[ 31 December 2001: Message edited by: Will Hetrick ]

If it doesn't consistently work on the same machine... well, it IS a microsoft product

I'd assume a new version of SMS to heavily rely on that for hardware and asset inventory.

As for your problems with the code, I really don't understand why you have these problems, perhaps the BIOS needs an update, or is is a permissions sort of thing.