Database Search
TechHome
 | |
|
- !Microsofts WMI Object Browser!
- !WMI Reference!
- !WMI Security!
- Add Key Qualifier
- Backup Event Log
- Best Way to Read Event Log via WMI
- Check if WMI is Installed
- Clear Event Log via WMI
- Close All but One Instance
- Detect If monitor is in Standby Mode
- Detect Resume From Standby
- Detect Standby or Hibernation Event
- Detecting Local Network Connectivity and Speed
- Determine Laptop or Destop System Enclosure
- Determine Machine Type
- Determining If a Machine is a Domain Controller
- Directory Watcher
- Display Refresh Rate
- Error 1261 on ConnectServer line
- Extract SN from Bios using WMI
- fileSizeEX returns 0 for the Pagefile.sys file
- Get Asset Tag From Dell Computers
- Get Daylight Savings Time
- Get Default Printer
- Get ipv6 IP Address via Host Name
- Get Owner of a Process
- Get Physical Memory
- Get Process List via WMI
- Get Remote Logged in User
- Get Specific Events
- Get Status of Network Adapter
- Get Win32_DiskDrive Data with DeviceID
- Install MSI apps
- Is Computer WMI Enabled UDF
- Last Reboot Time
- List Active Network Adapters
- List All Monitors
- List Available Screen Resolutions
- List Installed Modems
- List Namespaces
- List Processes on a Remote Computer
- List Scheduled Tasks
- Manufacturer Model and Serial from WMI
- Modify DNS Entries
- Monitor Events
- Obtain the Name of the Domain to which the Computer Belongs
- PCMCIA Card Detection
- Physical Memory Inspection
- Ping Status
- Remote Number of Drives
- Remote Process UDFs
- Run an Application on a Remote Computer
- Search Eventlog Example
- Set Adapter Speed Duplex
- SetDNSSuffixSearchOrder MisMatched Type Error
- System Restore Point
- Total CPU Usage
- Using WMI List Applications
- Win32_EncryptableVolume
- Win32_SerialPort Information via WMI
- Windows NT Schedule Service - AT
- WMI - Processor Info
- WMI and Arrays
- WMI and Get IPAddress Property
- WMI and Remote Interactive Desktop Scripts
- WMI and WinPE
- WMI causing LLSMGR to start
- WMI ExecQuery
- WMI Get Fan Speed
- WMI Get MAC Address and NIC info
- WMI hangs
- WMI ObjectOpen Problem on Windows 95
- WMI Query Paths Need Double Backslashes
- WMI Related Resources
- WMI Scriptomatic
- wntGetCon using WMI
- WQL LIKE Operator
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
WMI ObjectOpen Problem on Windows 95
Question:
I am getting a error when I try to open an object in Win95 or Win98.Can we provide a way for these OS's to find this? Win2k has no problem...
Locator = ObjectOpen("WbemScripting.SWbemLocator")
Service = Locator.ConnectServer()
Errors occur on the "Service = ... " line.
The difference between Win2k and Win95 was in this line:
modem = ObjectCollectionNext(hEnum) value => 0 .. for Win95, but for Win2k value => 33337Why would value = 0, on Windows 95?
Answer:
First, Make sure you have the WMI operating system core components installed.Here are the WMI System Requirements:
The WMI operating system core components are supported on Windows NT 4.0 with Service Pack 4 or later, including Windows 2000/XP, and on Windows 95 OSR2 and Windows 98.
The WMI infrastructure consists of the following components:
- The actual WMI software (Winmgmt.exe), a component that provides applications with uniform access to management data.
- The Common Information Model (CIM) repository, a central storage area for management data.
For Win95, 98, and NT 4.0, if WMI is not already installed, you can download the Windows Management Instrumentation (WMI) CORE 1.5 from Microsoft at: http://msdn.microsoft.com/downloads/sample.asp?url=/MSDN-FILES/027/001/576/msdncompositedoc.xml&frame=true
It is strange that on Win95 the ObjectCollectionNext is returning zero! The function ObjectCollectionNext returns an OLE object handle (i.e. 33337) representing the next item in the collection, or 0 (zero) when finished enumerating the collection.
User response:
Thanks a lot! That did it for Win98, but for Win95 I did not get anything in my list of modems though I have one sitting in the PCMCIA slot. Any idea why this might be?Reply:
Not really sure at this point. It would seem that there are no modem items in that collection.A quick search out at microsoft came up with this:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B285895
SYMPTOMS
When you attempt to retrieve instances from the Windows Management Instrumentation (WMI) Win32_POTSModem and
Win32_POTSModemToSerialPort classes in Windows 95 or Windows 98, no instances are returned.
CAUSE
This problem occurs because the WMI provider does not retrieve Telephony API (TAPI) information.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is
described in this article. Apply it only to computers that are experiencing this specific problem.
Article ID: W16279
File Created: 2004:03:30:15:43:44
Last Updated: 2004:03:30:15:43:44