Portmon for Windows v3.03

By Mark Russinovich

Published: January 12, 2012

Download Portmon (226 KB)
Run now from Sysinternals Live.

Introduction

Portmon is a utility that monitors and displays all serial and parallel port activity on a system. It has advanced filtering and search capabilities that make it a powerful tool for exploring the way Windows works, seeing how applications use ports, or tracking down problems in system or application configurations.

Portmon 3.x

Version 3.x of Portmon marks the introduction of a number of powerful features.

• Remote monitoring: Capture kernel-mode and/or Win32 debug output from any computer accessible via TCP/IP — even across the Internet. You can monitor multiple remote computers simultaneously. Portmon will even install its client software itself if you are running it on a Windows NT/2K system and are capturing from another Windows NT/2K system in the same Network Neighborhood.
• Most-recent-filter lists:Portmon has been extended with powerful filtering capabilities and it remembers your most recent filter selections, with an interface that makes it easy to reselect them.
• Clipboard copy: Select multiple lines in the output window and copy their contents to the clipboard.
• Highlighting: Highlight debug output that matches your highlighting filter, and even customize the highlighting colors.
• Log-to-file: Write debug output to a file as its being captured.
• Printing: Print all or part of captured debug output to a printer.
• One-file payload:Portmon is now implemented as one file.

The on-line help-file describes all these features, and more, in detail.

Installation and Use

Simply execute the Portmon program file (portmon.exe) and Portmon will immediately start capturing debug output. To run Portmon on Windows 95 you must get the WinSock2 update from Microsoft. Note that if you run Portmon on Windows NT/2K portmon.exe must be located on a non-network drive and you must have administrative privilege. Menus, hot-keys, or toolbar buttons can be used to clear the window, save the monitored data to a file, search output, change the window font, and more. The on-line help describes all of Portmon’s features.

Portmon understands all serial and parallel port I/O control (IOCTLs) commands and will display them along with interesting information regarding their associated parameters. For read and write requests Portmon displays the first several dozen bytes of the buffer, using ‘.’ to represent non-printable characters. The Show Hex menu option lets you toggle between ASCII and raw hex output of buffer data.

How it Works: WinNT

The Portmon GUI is responsible for identifying serial and parallel ports. It does so by enumerating the serial ports that are configured under HKEY_LOCAL_MACHINE\Hardware\DeviceMap\SerialComm and the parallel ports defined under HKEY_LOCAL_MACHINE\Hardware\DeviceMap\Parallel Ports. These keys contain the mappings between serial and parallel port device names and the Win32-accessible names.

When you select a port to monitor, Portmon sends a request to its device driver that includes the NT name (e.g. \device\serial0) that you are interested in. The driver uses standard filtering APIs to attach its own filter device object to the target device object. First, it uses ZwCreateFile to open the target device. Then it translates the handle it receives back from ZwCreateFile to a device object pointer. After creating its own filter device object that matches the characteristics of the target, the driver calls IoAttachDeviceByPointer to establish the filter. From that point on the Portmon driver will see all requests aimed at the target device.

Portmon has built-in knowledge of all standard serial and parallel port IOCTLs, which are the primary way that applications and drivers configure and read status information from ports. The IOCTLs are defined in the DDK file \ddk\src\comm\inc\ntddser.h and \ddk\src\comm\inc\ntddpar.h, and some are documented in the DDK.

How it Works: Windows 95 and 98

On Windows 95 and 98, the Portmon GUI relies on a dynamically loaded VxD to capture serial and parallel activity. The Windows VCOMM (Virtual Communications) device driver serves as the interface to parallel and serial devices, so applications that access ports indirectly use its services. The Portmon VxD uses standard VxD service hooking to intercept all accesses to VCOMM’s functions. Like its NT device driver, Portmon‘s VxD interprets requests to display them in a friendly format. On Windows 95 and 98 Portmon monitors all ports so there is no port selection like on NT.

Download Portmon (226 KB)

Run now from Sysinternals Live.

Free Virtual Serial Ports

Free Virtual Serial Ports Overview

Free Virtual Serial Ports is a Windows user-mode application, which allows you to create software virtual serial ports and emulate physical serial ports behavior. It operates exclusively in user-mode, therefore it is more stable and uses less memory, processor and operating system resources than any competitive products. It behaves exactly like hardware serial port with full serial port functionality, providing baud-rate emulation, configuration of data bits, parity (odd, even, mark, space) and stop bits, XON/XOFF software and hardware flow control, etc.

Our free virtual com port drivers allow you to emulate custom Plug-and-Play (PnP) serial ports and I/O ports interfaced by 16550 UART: COM1, COM2, COM3, COM4… COM255 correctly registered and visible in Windows device manager under standard Ports (COM & LPT) device class.

Our free com port null-modem emulator allows you to create virtual null-modem cable in order to emulate hardware null-modem cable with DB-25 or DE-9 connectors and Serial (Modem) control lines: Transmitted Data TxD, Received Data RxD, Data Terminal Ready DTR, Carrier Detect DCD, Data Set Ready DSR, Ring Indicator RI, Request To Send RTS, Clear To Send CTS. Virtual serial lines behaves exactly as real hardware serial lines.

Freeware virtual serial ports may be applicable as some kind of serial port redirector/COM port redirector which uses network interface to create and pair virtual serial communication ports on the same PC. It allows two legacy serial applications to communicate using created ports instead of using named pipes or any other modern inter-process communication mechanisms. Unlimited number of virtual COM port pairs may be created and used by COM port based applications to establish interconnection.

Virtual comm ports may be even more suitable for several serial applications than a HW serial ports. Virtual serial ports connection is much faster than physical null-modem cable connection and it depends only on your CPU, RAM and overall system performance.

Free Virtual Serial Ports OS support:

Free Virtual Serial Ports supports Windows desktop and server platforms starting from Windows Vista (x86 and x64), including Windows 8/8.1 32-bit and 64-bit operating systems.

Free Virtual Serial Ports Features

Free Virtual Com Port driver:

• Supports all standard bit rates of 75, 110, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600 and 115200 bit/s.
• Does not require any physical connections
• Joins virtual ports in pairs using virtual null modem cable
• Provides GUI and console application control
• Provides serial interface for device emulators
• Supports all modern Windows x86 and x64 platforms
• Uses only user-mode OS API calls, making program and system much more stable.
• Supports Windows WMI, Power Management, PnP and more technologies.

This product is popular free com0com alternative with signed drivers and probably best virtual serial port kit for developers.

Serial Devices supported by Free Virtual Com Ports

Our Free Virtual Serial Port driver may be used with software designed to control the following RS232, RS422, RS485 equipment and peripherals:

Dial-up modems, terminals, printers, RS-232, RS-422 and RS-485 test instruments, industrial equipment and automation systems, PLCs, VFDs, servo drives, CNC RS-232 controllers, laboratory automation equipment, scientific instruments, Serial device servers, NPort servers, multiport serial boards, Serial to fiber converters, RS-232 to RS-422/485 converters.

Our Free Virtual Serial Port emulator may be used to simulate connection of various equipment in the following areas:

• Network configuration and management equipment: routers, switches, multiplexers, hubs, firewalls, load balancers, console ports, WAN equipment, wireless LAN equipment;
• Diagnostic, controlling and measuring tools: digital multimeters, oscilloscopes, manometers, sensors;
• Telecommunication equipment: Fax-Modems, mini-ATS, Cell Phones, GSM mobile phones, GPS receivers (typically NMEA 0183 at 4,800 bit/s), satellite phones, low-speed satellite modems and other satellite based transceiver devices
• Shop fitting and retail equipment: EPOS and POS terminals, bar code scanners, card readers, weighing systems, door entry and HVAC systems, bar code readers.
• Consumer electronics: MIDI-serial devices, Digital Cams, entertaining equipment, simulators

FVSP Usage Scenarios

This is useful tool for testing, development, debugging and analysis of serial hardware and software applications. FVSP utility allows you to establish unlimited number of virtual serial connections and use it to exchange traffic and data streams between different serial applications. You may also emulate packet loss and connection breaks in order to test and analyze serial device failures.

Download this Free Virtual Serial Ports kit and start to emulate Serial Port communications in just few seconds!

Win32_SerialPort class

The Win32_SerialPort WMI class represents a serial port on a computer system running Windows.

The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties. Properties are listed in alphabetic order, not MOF order.

Syntax

Members

The Win32_SerialPort class has these types of members:

Methods

The Win32_SerialPort class has these methods.

Method	Description
Reset	Not implemented. To implement this method, see the Reset method in CIM_SerialController.
SetPowerState	Not implemented. To implement this method, see the SetPowerState method in CIM_SerialController.

Properties

The Win32_SerialPort class has these properties.

Availability

Data type: uint16

Access type: Read-only

Qualifiers: MappingStrings («MIF.DMTF|Operational State|003.5», «MIB.IETF|HOST-RESOURCES-MIB.hrDeviceStatus»)

Availability and status of the device.

Other (1)

Unknown (2)

Running/Full Power (3)

Running or Full Power

Warning (4)

In Test (5)

Not Applicable (6)

Power Off (7)

Off Line (8)

Off Duty (9)

Degraded (10)

Not Installed (11)

Install Error (12)

Power Save — Unknown (13)

The device is known to be in a power save mode, but its exact status is unknown.

Power Save — Low Power Mode (14)

The device is in a power save state but still functioning, and may exhibit degraded performance.

Power Save — Standby (15)

The device is not functioning, but could be brought to full power quickly.

Power Cycle (16)

Power Save — Warning (17)

The device is in a warning state, though also in a power save mode.

Paused (18)

The device is paused.

Not Ready (19)

The device is not ready.

Not Configured (20)

The device is not configured.

Quiesced (21)

The device is quiet.

Binary

Data type: boolean

Access type: Read-only

If TRUE, the serial port is configured for binary data transfer. Because the Windows API does not support nonbinary mode transfers, this property must be TRUE.

Capabilities

Data type: uint16 array

Access type: Read-only

Array of chip-level compatibility for the serial controller. This property describes the buffering and other capabilities of the serial controller that may be inherent in the chip hardware. The property is an enumerated integer.

Other (1)

Unknown (2)

XT/AT Compatible (3)

16450 Compatible (4)

16550 Compatible (5)

16550A Compatible (6)

8251 Compatible (160)

8251FIFO Compatible (161)

CapabilityDescriptions

Data type: string array

Access type: Read-only

Array of free-form strings providing more detailed explanations for any of the serial controller features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.

Caption

Data type: string

Access type: Read-only

Short description of the object.

ConfigManagerErrorCode

Data type: uint32

Access type: Read-only

Win32 Configuration Manager error code.

This device is working properly. (0)

Device is working properly.

This device is not configured correctly. (1)

Device is not configured correctly.

Windows cannot load the driver for this device. (2)

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (3)

Driver for this device might be corrupted, or the system may be low on memory or other resources.

This device is not working properly. One of its drivers or your registry might be corrupted. (4)

Device is not working properly. One of its drivers or the registry might be corrupted.

The driver for this device needs a resource that Windows cannot manage. (5)

Driver for the device requires a resource that Windows cannot manage.

The boot configuration for this device conflicts with other devices. (6)

Boot configuration for the device conflicts with other devices.

Cannot filter. (7)

The driver loader for the device is missing. (8)

Driver loader for the device is missing.

This device is not working properly because the controlling firmware is reporting the resources for the device incorrectly. (9)

Device is not working properly. The controlling firmware is incorrectly reporting the resources for the device.

This device cannot start. (10)

Device cannot start.

This device failed. (11)

This device cannot find enough free resources that it can use. (12)

Device cannot find enough free resources to use.

Windows cannot verify this device’s resources. (13)

Windows cannot verify the device’s resources.

This device cannot work properly until you restart your computer. (14)

Device cannot work properly until the computer is restarted.

This device is not working properly because there is probably a re-enumeration problem. (15)

Device is not working properly due to a possible re-enumeration problem.

Windows cannot identify all the resources this device uses. (16)

Windows cannot identify all of the resources that the device uses.

This device is asking for an unknown resource type. (17)

Device is requesting an unknown resource type.

Reinstall the drivers for this device. (18)

Device drivers must be reinstalled.

Failure using the VxD loader. (19)

Your registry might be corrupted. (20)

Registry might be corrupted.

System failure: Try changing the driver for this device. If that does not work, see your hardware documentation. Windows is removing this device. (21)

System failure. If changing the device driver is ineffective, see the hardware documentation. Windows is removing the device.

This device is disabled. (22)

Device is disabled.

System failure: Try changing the driver for this device. If that doesn’t work, see your hardware documentation. (23)

System failure. If changing the device driver is ineffective, see the hardware documentation.

This device is not present, is not working properly, or does not have all its drivers installed. (24)

Device is not present, not working properly, or does not have all of its drivers installed.

Windows is still setting up this device. (25)

Windows is still setting up the device.

Windows is still setting up this device. (26)

Windows is still setting up the device.

This device does not have valid log configuration. (27)

Device does not have valid log configuration.

The drivers for this device are not installed. (28)

Device drivers are not installed.

This device is disabled because the firmware of the device did not give it the required resources. (29)

Device is disabled. The device firmware did not provide the required resources.

This device is using an Interrupt Request (IRQ) resource that another device is using. (30)

Device is using an IRQ resource that another device is using.

This device is not working properly because Windows cannot load the drivers required for this device. (31)

Device is not working properly. Windows cannot load the required device drivers.

ConfigManagerUserConfig

Data type: boolean

Access type: Read-only

If TRUE, the device is using a user-defined configuration.

CreationClassName

Data type: string

Access type: Read-only

Name of the first concrete class to appear in the inheritance chain used in the creation of an instance. When used with the other key properties of the class, the property allows all instances of this class and its subclasses to be uniquely identified.

Description

Data type: string

Access type: Read-only

Description of the object.

DeviceID

Data type: string

Access type: Read-only

Unique identifier of the serial port with other devices on the system.

ErrorCleared

Data type: boolean

Access type: Read-only

If TRUE, the error reported in LastErrorCode is now cleared.

ErrorDescription

Data type: string

Access type: Read-only

Free-form string supplying more information about the error recorded in LastErrorCode, and information about any corrective actions that may be taken.

InstallDate

Data type: datetime

Access type: Read-only

Date and time the object was installed. This property does not need a value to indicate that the object is installed.

LastErrorCode

Data type: uint32

Access type: Read-only

Last error code reported by the logical device.

MaxBaudRate

Data type: uint32

Access type: Read-only

Maximum baud rate (in bits per second) supported by the serial controller.

MaximumInputBufferSize

Data type: uint32

Access type: Read-only

Maximum size of the serial port driver’s internal input buffer. A value of 0 (zero) indicates that no maximum value is imposed by the serial provider.

MaximumOutputBufferSize

Data type: uint32

Access type: Read-only

Maximum size of the serial port driver’s internal output buffer. A value of 0 (zero) indicates that no maximum value is imposed by the serial provider.

MaxNumberControlled

Data type: uint32

Access type: Read-only

Maximum number of directly addressable entities supportable by this controller. A value of 0 (zero) should be used if the number is unknown.

Name

Data type: string

Access type: Read-only

Label by which the object is known. When subclassed, the property can be overridden to be a key property.

OSAutoDiscovered

Data type: boolean

Access type: Read-only

If TRUE, the instances of this class were automatically discovered by the operating system. If, for example, hardware was added through Control Panel, the operating system finds instances of this class by querying hardware from the instances of this class.

PNPDeviceID

Data type: string

Access type: Read-only

Windows Plug and Play device identifier of the logical device.

PowerManagementCapabilities

Data type: uint16 array

Access type: Read-only

Array of the specific power-related capabilities of a logical device.

This property is inherited from CIM_LogicalDevice.

Unknown (0)

Not Supported (1)

Disabled (2)

Enabled (3)

The power management features are currently enabled but the exact feature set is unknown or the information is unavailable.

Power Saving Modes Entered Automatically (4)

The device can change its power state based on usage or other criteria.

Power State Settable (5)

The SetPowerState method is supported. This method is found on the parent CIM_LogicalDevice class and can be implemented. For more information, see Designing Managed Object Format (MOF) Classes.

Power Cycling Supported (6)

The SetPowerState method can be invoked with the PowerState parameter set to 5 (Power Cycle).

Timed Power On Supported (7)

Timed Power-On Supported

The SetPowerState method can be invoked with the PowerState parameter set to 5 (Power Cycle) and Time set to a specific date and time, or interval, for power-on.

PowerManagementSupported

Data type: boolean

Access type: Read-only

If TRUE, the device can be power-managed (can be put into suspend mode, and so on). The property does not indicate that power management features are currently enabled, only that the logical device is capable of power management.

ProtocolSupported

Data type: uint16

Access type: Read-only

Protocol used by the controller to access «controlled» devices.

This property is inherited from CIM_Controller. The following list shows the possible values.

Other (1)

Unknown (2)

EISA (3)

ISA (4)

PCI (5)

ATA/ATAPI (6)

Flexible Diskette (7)

1496 (8)

SCSI Parallel Interface (9)

SCSI Fibre Channel Protocol (10)

SCSI Serial Bus Protocol (11)

SCSI Serial Bus Protocol-2 (1394) (12)

SCSI Serial Storage Architecture (13)

VESA (14)

PCMCIA (15)

Universal Serial Bus (16)

Parallel Protocol (17)

ESCON (18)

Diagnostic (19)

I2C (20)

Power (21)

HIPPI (22)

MultiBus (23)

VME (24)

IPI (25)

IEEE-488 (26)

RS232 (27)

IEEE 802.3 10BASE5 (28)

IEEE 802.3 10BASE2 (29)

IEEE 802.3 1BASE5 (30)

IEEE 802.3 10BROAD36 (31)

IEEE 802.3 100BASEVG (32)

IEEE 802.5 Token-Ring (33)

ANSI X3T9.5 FDDI (34)

MCA (35)

ESDI (36)

IDE (37)

CMD (38)

ST506 (39)

DSSI (40)

QIC2 (41)

Enhanced ATA/IDE (42)

AGP (43)

TWIRP (two-way infrared) (44)

FIR (fast infrared) (45)

SIR (serial infrared) (46)

IrBus (47)

ProviderType

Data type: string

Access type: Read-only

Communications provider type.

«FAX Device» «LAT Protocol» «Modem Device» «Network Bridge» «Parallel Port» «RS232 Serial Port» «RS422 Port» «RS423 Port» «RS449 Port» «Scanner Device» «TCP/IP TelNet» «X.25» «Unspecified»

FAX Device («FAX Device»)

LAT Protocol («LAT Protocol»)

Modem Device («Modem Device»)

Network Bridge («Network Bridge»)

Parallel Port («Parallel Port»)

RS232 Serial Port («RS232 Serial Port»)

RS422 Port («RS422 Port»)

RS423 Port («RS423 Port»)

RS449 Port («RS449 Port»)

Scanner Device («Scanner Device»)

TCP/IP TelNet («TCP/IP TelNet»)

X.25 («X.25»)

Unspecified («Unspecified»)

SettableBaudRate

Data type: boolean

Access type: Read-only

If TRUE, the baud rate can be changed for this serial port.

SettableDataBits

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwSettableParams|SP_DATABITS»)

If TRUE, data bits can be set for this serial port.

SettableFlowControl

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwSettableParams|SP_HANDSHAKING»)

If TRUE, flow control can be set for this serial port.

SettableParity

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwSettableParams|SP_PARITY»)

If TRUE, parity can be set for this serial port.

SettableParityCheck

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwSettableParams|SP_PARITY_CHECK»)

If TRUE, parity checking can be set for this serial port (if parity checking is supported).

SettableRLSD

Data type: boolean

Access type: Read-only

If TRUE, Received Line Signal Detect (RLSD) can be set for this serial port (if RLSD is supported).

SettableStopBits

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwSettableParams|SP_STOPBITS»)

If TRUE, stop bits can be set for this serial port.

Status

Data type: string

Access type: Read-only

Current status of the object. Various operational and nonoperational statuses can be defined. Operational statuses include: «OK», «Degraded», and «Pred Fail» (an element, such as a SMART-enabled hard disk drive, may be functioning properly but predicting a failure in the near future). Nonoperational statuses include: «Error», «Starting», «Stopping», and «Service». The latter, «Service», could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is online, yet the managed element is neither «OK» nor in one of the other states.

Values include the following:

OK («OK»)

Error («Error»)

Degraded («Degraded»)

Unknown («Unknown»)

Pred Fail («Pred Fail»)

Starting («Starting»)

Stopping («Stopping»)

Service («Service»)

Stressed («Stressed»)

NonRecover («NonRecover»)

No Contact («No Contact»)

Lost Comm («Lost Comm»)

StatusInfo

Data type: uint16

Access type: Read-only

State of the logical device. If this property does not apply to the logical device, the value 5 (Not Applicable) should be used.

Other (1)

Unknown (2)

Enabled (3)

Disabled (4)

Not Applicable (5)

Supports16BitMode

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_16BITMODE»)

If TRUE, 16-bit mode is supported on this serial port.

SupportsDTRDSR

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_DTRDSR»)

If TRUE, data terminal ready (DTR) and data set ready (DSR) signals are supported on this serial port.

SupportsElapsedTimeouts

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_TOTALTIMEOUTS»)

If TRUE, elapsed time-outs are supported on this serial port. Elapsed timeouts track the total amount of time between data transmissions.

SupportsIntTimeouts

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_INTTIMEOUTS»)

If TRUE, interval time-outs are supported. An interval timeout is the amount of time allowed to elapse between the arrival of each piece of data.

SupportsParityCheck

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_PARITY_CHECK»)

If TRUE, parity checking is supported on this serial port.

SupportsRLSD

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_RLSD»)

If TRUE, Received Line Signal Detect (RLSD) is supported on this serial port.

SupportsRTSCTS

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_RTSCTS»)

If TRUE, ready to send (RTS) and clear to send (CTS) signals are supported on this serial port.

SupportsSpecialCharacters

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_SPECIALCHARS»)

If TRUE, serial port control characters are supported. These characters signal events rather than data. These characters are not displayable and are set by the driver. They include EofChar, ErrorChar, BreakChar, EventChar, XonChar, and XoffChar.

SupportsXOnXOff

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_XONXOFF»)

If TRUE, XON or XOFF flow-control is supported on this serial port.

SupportsXOnXOffSet

Data type: boolean

Access type: Read-only

Qualifiers: MappingStrings («Win32API|Communication Structures|COMMPROP|dwProvCapabilities|PCF_SETXCHAR»)

If TRUE, the communications provider supports configuration of the XONor XOFF flow-control setting.

SystemCreationClassName

Data type: string

Access type: Read-only

Value of the scoping computer’s CreationClassName property.

SystemName

Data type: string

Access type: Read-only

Name of the scoping system.

TimeOfLastReset

Data type: datetime

Access type: Read-only

Date and time this controller was last reset. This could mean the controller was powered down, or reinitialized.

Remarks

The Win32_SerialPort class is derived from CIM_SerialController.

Examples

For an alternate method of retrieving serial port information (from the registry), see the Enumerate Ports Visual Basic sample.

The List Serial Port Properties PowerShell example returns information about the serial ports installed on a computer.

The following VBScript sample returns information about the serial ports installed on a computer.