|
Newbie |
Joined: Tue Mar 09, 2010 3:02 am Posts: 32
|
[quote="jpa"]OK. I've now replicated this. I think you're running the 32-bit version of cscript from c:\Windows\SysWOW64 rather than the 64-bit version from c:\Windows\System32. If you're just calling cscript without any path then your path search order is different than mine. What do you have in your PATH environment variable?
Well, I just ran it on my system and checked the path using Process Explorer from Sysinternals and it is using the syswow64 path. (this when running the simple command 'cscript.exe audit_windows.vbs')
Interesting stuff.
I just manually specified the system32 path and it does work, pulling the 64bit info as it should, just as you suggested.
Yeesh, is this stuff fun or what? Thanks a bunch for the help. That'll answer that question. Now I'll just specify c:\windows\system32\cscript.exe specifically, as all machines will have it in that path, and it should function correctly for all machines from that path (whether XP, 7, 32-bit, or 64-bit).
|
|