This is an update to the first packet sniffer. Raw Packet Sniffer (Bugs Fixed) Email: Submitted on. You will need a program like Winzip to decompress it.Virus note:All files are scanned once-a-day by Planet Source Code for viruses, but new viruses come out every day, so no prevention.
» » » Using ActiveXperts Serial Port Component with Visual Basic 6.x ActiveXperts Serial Port Component is a software development kit (SDK) that enables the user to communicate to a device over a serial interface. Such a device can be: a weight indicator, a modem, a scanner, or any other device that is equiped with a serial port. It can even be another PC, connected via a NULL modem cable. ActiveXperts Serial Port Component features the following: • Direct COM port support (like 'COM1') • TAPI (Windows Telephony Device) support (like 'Standard 56000 bps Modem'); • Support for RS-232/RS422/RS485, up to 256 simultaneous ports; • Support for all types of Hayes compatible modems; • Support for serial cable as well as USB cable or Bluetooth connections; • Support for Virtual COM ports (i.e. COM ports redirected through the network); • Hardware flow control (RTS/CTS, DTR/DSR) and software flowcontrol (XON/XOFF) support; • Configurable baudrate/parity/stopbits, full buffered data transfer, text/binary data transfer. Step 1: Download and install the ActiveXperts Serial Port Component Download the ActiveXperts Serial Port Component from the and start the installation.
The installation guides you through the installation process. Step 2: Create a new Visual Basic project Launch 'Microsoft Visual Basic' from the Start menu, and choose 'New' from the 'File Menu'. The 'New Project' dialog appears. Select 'Standard Exe' and click 'OK': (Click on the picture to enlarge) Step 3: Refer to the ActiveXperts Serial Port Component Library and create the objects A new Project is created, with a blank form. First, you must add a reference to Serial Port Component in the project to be able to use the object. To do so, choose 'References.'
From the 'Project' menu. In the 'References' dialog that pops up, enable the 'Serial Port Component 2.2 Type Library' reference as shown in the following picture: (Click on the picture to enlarge) Click 'OK' to close the 'References.'
Then, select the Project form and choose 'View Code' from the context menu: (Click on the picture to enlarge) On top of your code, declare the following object: Public objComport As AxSerial.ComPort Step 4: Create the object From the Code window, select 'Form'. The Private Sub 'Form_Load()' will be displayed now. In the 'Form Load' function, create the object in the following way: Set objComport = CreateObject('AxSerial.ComPort') Step 5: Send an AT command to a connected Hayes compatible modem You can now send and/or receive data to and/or from a serial device. The following code shows how to query a modem: '!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ' DO NOT FORGET: ADD A REFERENCE TO THE SERIAL PORT COMPONENT LIBRARY FROM THE PROJECT->REFERENCE '!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Sadhak bamakhyapa serial cast. After this incident, Bamakhepa was fed first in the temple before the deity and nobody obstructed him.
Well, as far as i know, IoGetDeviceObjectPointer() can not be used for all devices, specially when those devices already 'being opened' by another application. But there is another way to do 'attach and detach device', by creating a filter driver for those devices, modify some registry(ies) and let the PnP Manager and/or I/O Manager do that for you. For the detail how to do this, you can see the the sample in WDK, unfortunately i forgot what sample for specific, but i think (if i'm not mistaken) sample about disk performance.
Member 10398370 7-Jan-14 21:58 7-Jan-14 21:58 Hello,Good afternoon,I have a question need to ask you. In the filter driver development, when there is data in the data queue, using the event to notify the application.
Create an event in the application, It is passed to the driver via DeviceIoControl. While waiting for an event using threads in the application, there is a signal event, to fetch data.
Such a program structure, when the application is running, and the serial transceivers the data transceiver, PC happens blue screen. If the application and the serial are not both running, PC does not blue screen.what causes the problem? In your routine, the application uses the OVERLAPPED structure, does OVERLAPPED I / O in the filter driver is necessary?