[ 30 October 2001: Message edited by: Bill Bowker ]

A good idea, but we think it is not so easy to implement. New hardware requires new releases of software. You can see it with 3rd party utils.
Total diskspace calculation can be done in an easy way by kixtart. For us is dir command not a 3rd party utility.
greetings.

a small example.

code:

---

$drives = GetObject("WinMgmts:").InstancesOf("Win32_LogicalDisk")
for each $drive in $drives
	? $drive.name
	? "Total drive size = " + $drive.size
	? "freespace        = " + $drive.freespace
	select
		case $drive.drivetype = 0
			? "Drive type       = Unknown"
		case $drive.drivetype = 1
			? "Drive type       = No Root Directory"
		case $drive.drivetype = 2
			? "Drive type       = Removable Disk"
		case $drive.drivetype = 3
			? "Drive type       = Local Disk"
		case $drive.drivetype = 4
			? "Drive type       = Network Drive"
		case $drive.drivetype = 5
			? "Drive type       = Compact Disc"
		case $drive.drivetype = 6
			? "Drive type       = RAM Disk"
	endselect
	? ""
next

---

code:

---

? "----===== Drives =====----"
$drives = GetObject("WinMgmts:").InstancesOf("Win32_LogicalDisk")
for each $drive in $drives
	? $drive.name
	? "Total drive size = " + $drive.size
	? "freespace        = " + $drive.freespace
	select
		case $drive.drivetype = 0
			? "Drive type       = Unknown"
		case $drive.drivetype = 1
			? "Drive type       = No Root Directory"
		case $drive.drivetype = 2
			? "Drive type       = Removable Disk"
		case $drive.drivetype = 3
			? "Drive type       = Local Disk"
		case $drive.drivetype = 4
			? "Drive type       = Network Drive"
		case $drive.drivetype = 5
			? "Drive type       = Compact Disc"
		case $drive.drivetype = 6
			? "Drive type       = RAM Disk"
	endselect
	? ""
next

? "----===== CPU's =====----"
$CPUs = GetObject("WinMgmts:").InstancesOf("Win32_Processor")
for each $cpu in $cpus
	? $cpu.Manufacturer + ":" + $cpu.CurrentClockSpeed + "Mhz"
next
? "----===== Memory =====----"
$Memory = GetObject("WinMgmts:").InstancesOf("Win32_PhysicalMemory")
for each $mem in $memory
	? $mem.Capacity + " bytes"
next

---

You see it is already there. Code is very simple. You only need to learn some object
programming.
Greetings.

Do you know what these values are based on? None of them are close to anything I have. The CPU was correct. The disk space might be right if you were to /1024 maybe? The RAM is way off both Physical as well as available the Cached memory was the only one right. The physical and swap combined still don't make what it says I have. Is there documentation somewhere that explains how this call is interpredted?

i got all of that stuff out of the WMI SDK the other night. Aside from that.....?

Bryce

MCA has a script that can take care of this for you. Great stuff. The CPU is not very reliable though becuase of time slice issues that the auther knows about, but seems he appears to be gone from school now and not updating the program anymore. But the other stuff works good.

Thanks again for that kind of work MCA.

WMI works just as well on Win9x machines, just install the WMI-core.
The WMI-core has to be installed on all OS'es prior to W2K.

The same goes for the ADSI-inteface, this can also be installed on all platforms from Win95 and upwards.

Erik

We doesn't know what a script can do also. But we find out that some
manufactories doesn't support Windows 95 anymore. A simple installation
with own risk isn't possible. Even Microsoft programs doesn't always work in a correct way.
Same experience with new hardware.

Possible that everybody should migrate to Windows XP, which means:
- we can use it for a long time.
- new hardware and software will be compatible with this version also
for a long time.
- we have the possibility to find new problems and microsoft have the
challenge to fix them.
greetings.

btw: NTDOC, we will look at your remark about CPU.