Idea激活2022.1.4(安装ideaIU-2022.1.4报错问题解决办法)

Bus Hound 5.0 Copyright (C) Perisoft 2000-2003. All rights reserved worldw
ide. Bus Hound is a powerful software bus analyzer for capturi
ng I/O and protocol from devices. Features include:  Supports every version of
IDE, SCSI, USB, 1394  Supports all devices such as hard drives, DVD, mice, scanners, web cams, and everythi
ng else  Supports Windows 95, 98, Me, NT 4.0, 2000, 2003, XP and XP Embedded  Capture megabytes of I/O limited only by available memory  Automatically stop the capture upon a trigger condition  Measure individual read, write, and isochronous device performance  Captures device driver packets such as IRP’s  Filter what type of phases are captured  Run on an unlimited number of machines at the same time  Capture any number of devices in parallel, regardless of bus type  Fits on a diskette for easy transportability and quick downloads  Drag and drop captured
data to other products in html format  Save captured
data to a text file or zip file  Simple device selection from a graphical tree of devices  Capture the system startup process  Arra
nge captured
data to user preferences such as the byte width per line  View low level protocol includi
ng SCSI sense
data and USB setup packets  View microsecond resolution timi
ng of each phase  Watch I/O on screen in real time as it happens  Pure software solution–no extra hardware or system cha
nges needed The Capture Window Commands sent to devices consist of one or more phases. Examples of phases are command bytes,
data bytes, and status bytes. Bus hound logs each phase complete with timi
ng information and a description of the content. Capture columns Below are descriptions of information in each column of the Capture Window: Device Device ID. Each device is assigned a number which can be matched up with devices in the Devices Window. The first detected device on the system is Device ID 0, the second is Device ID 1, and so on. This field is useful in the event multiple devices are bei
ng captured in parallel. For USB devices, the endpoint is also displayed (eg: 4.1 = device 4, endpoint 1). Phase Phase type. Please refer to the table for details of each phase type. Phase Description ADDR 8 byte 1394 transfer address ATI 7 byte ATA task file returned from an
IDE device ATO 7 byte ATA task file sent to an
IDE device ATP Windows ATA_PASS_THROUGH
data structure CDB SCSI command descriptor block (Known as a packet command for ATAPI devices) CTL 8 byte setup packet of a USB control transfer DI
Data In (Device to PC transfer) DO
Data Out (PC to device transfer) IOR Windows VXD I/O Request
data structure IRB Windows 1394 I/O Request Block
data structure IRP Windows I/O Request Packet
data structure ISOC Isochronous transfer
data bytes LEN
Data transfer le
ngth of a DI,DO, or ISOC phase in decimal units. This field is off by default and can be turned on from the setti
ngs Window LOCK 1394 lock transaction NSTS Windows 4 byte kernel mode NTSTATUS field RSET Bus or device reset RSTS Windows VXD IOR status SNS SCSI request sense
data SPT Windows SCSI Pass Through
data structure SRB Windows SCSI Request Block (SRB)
data structure SSTS Windows 1 byte SCSI Request Block (SRB) status STAK Windows IO_STACK_LOCATION
data structure URB Windows USB Request Block (URB)
data structure USTS Windows 4 byte USBD_STATUS code 
Data 
Data bytes associated with the phase. Examples are command bytes,
data transfer bytes, and status bytes. Description A text description of this phase prov
ided for your convenience. Delta Elapsed time from the previous phase to the current phase. The followi
ng table describes the units of the time format. Name Units us Microseconds ms Milliseconds sc Seconds mn Minutes hr Hours dy Days Cmd.Phase.Ofs(rep) This unique tag
identifies the exact position within the captured
data. All values are in decimal. Cmd is the command number. Commands start at 1 and increment for each new command sent to a device. Phase is the phase number within this command. A command is usually composed of multiple phases such as
data transfer and status. This value starts at 1 and increments for each new phase within the command. Ofs is the byte offset of the
data within this phase. This value starts at 0 and increments for each byte of
data in the
data transfer. Rep is the number of
identical commands issued back to back. The repeat count feature can be turned off by deselecti
ng the “Merge Repeated Commands” check box in the setti
ngs Window. Date Date the phase occurred in year/month/day format. Time Time the phase occurred in hour:minute:second.millisecond format. The hour ra
nges from 0 to 23 (military time). Capturi
ng the system startup process If the Bus Hound application is exited while the Run button is pressed, the device driver portion of Bus Hound continues capturi
ng
data. In the event the system is restarted, it will start capturi
ng
data early in the system startup process. If Bus Hound is exited while stopped, no capture will occur until returni
ng to the product and pressi
ng Run. Customizi
ng the capture display The column order can be modified by draggi
ng the column headers to the desired position. The byte width per line can be 1, 2, 4, 8, 16, or 32 bytes and is based on the width of the window. These setti
ngs are respected for S
avi
ng and drag & drop. Searchi
ng Searchi
ng can be performed from the capture window in either the up or down direction by typi
ng the search stri
ng in the lower left edit box followed by pressi
ng the up or down arrow to search up or down respectively. If the search stri
ng is not found, the trace position is not cha
nged. Searchi
ng is not case sensitive. Drag and Drop To use drag and drop, first select the desired ra
nge of lines by clicki
ng on the starti
ng line, then hold down shift and click the endi
ng line. The
data can now be dragged usi
ng the mouse to another product. Pressi
ng control-c copies the selected lines to the clipboard. Command Overlap Overlapped commands are
identified when a command starts before previous commands to the same device have completed. It is possible for Commands to be overlapped at the I/O subsystem level (which Bus Hound displays), but not at the hardware level. Multiple DI/DO phases Windows 9x only: if multiple DI/DO phases are listed for the same command, it indicates the transfer was split across multiple memory address ra
nges PS2 Mouse
data format Below is the format of the
data returned in the
data in phase for PS/2 mice. This is known as the MOUSE_INPUT_
DATA structure in the Windows DDK: Offset Le
ngth Content 0 2 Not used 2 2 Position type: 0000h = relative position 0001h = absolute position 4 2 Button flags: 0001h = left button down 0002h = left button up 0004h = right button down 0008h = right button up 0010h = middle button down 0020h = middle button up 0040h = button 4 down 0080h = button 4 up 0100h = button 5 down 0200h = button 5 up 0400h = mouse wheel 6 2 Mouse wheel
data 8 4 Not used 12 4 X position 16 4 Y position 20 4 Device specific information PS2 Keyboard
data format Below is the format of the
data returned in the
data in phase for PS/2 keyboards. This is known as the KEYBOARD_INPUT_
DATA structure in the Windows DDK: Offset Le
ngth Content 0 2 Not used 2 2 Scan code of key 4 2 Flags: 0000h = key pressed 0001h = key released 0002h = extended scan code E0 0004h = extended scan code E1 6 2 Not used 8 4 Device specific information The Save Window The Save button saves all captured
data to the specified file. The format of the file can be either a text file containi
ng standard ASCII characters or a Zip file. The
data will be saved in the same column order and byte width as seen on the screen. A comment can be prov
ided that will be placed into the header of the captured
data. The current date and time can be included in the comment by inserti
ng %c anywhere ins
ide the comment. If s
avi
ng to a zip file, the comment is also used for the zip file comment. The Setti
ngs Window This Window allows you to customize the capture process. Checkbox options in this window are applied instantly. Numeric entries are applied by pressi
ng the apply button, switchi
ng to another window, or exiti
ng Bus Hound. Buffer Size Specifies the number of kilobytes of RAM to use for capturi
ng
data. The size is limited only by system RAM. If not enough RAM is available to satisfy the requested size, the size is reduced to available RAM. If you need to get as much space as possible, bes
ides addi
ng more RAM to a system you can also try setti
ng the buffer size before starti
ng other applications. Note: allocati
ng a very large buffer size under Windows 95/98/Me can take a minute. Max Phase Specifies the maximum number of bytes that will be captured on each phase. Example: if Max Phase is set to 32 bytes and a 64K read operation occurs, only the first 32 bytes of the read will be captured. This option is useful for keepi
ng the size of the captured
data to a minimum. Stop When… These are triggers that allow the capture to automatically stop when the specified condition is met. Any combination of triggers may be selected. When a trigger condition is met, the capture stops and the trigger text is highlighted in red. Any Other
Error stops the capture when an
error occurs that does not fall into any of the other categories. Buffer Full stops the capture when Bus Hound’s buffer is full. If Buffer Full is deselected, capturi
ng continues after the buffer is full, keepi
ng the most recently captured
data. Bus Reset stops the capture when a bus reset occurs. 
Data Overrun stops the capture when a
data overrun or
data underrun occurs. Hardware
Error stops the capture when a hardware
error occurs. Invalid Command stops the capture when an invalid command is issued. Media
Error stops the capture when a device reports a media
error such as a bad sector. No Media stops the capture when a device reports no media is present. Not Ready stops the capture upon a not ready, timeout, or busy condition. Text Pattern / Hex Pattern stops the capture when the specified
data pattern is detected in the captured
data. For text patterns, the match is case sensitive. The pattern is checked against the
data transferred in any phase includi
ng commands,
data, and status. Vendor
Error stops the capture when a vendor unique
error occurs. Windows
Error stops the capture when an operati
ng system type
error occurs. Phases to Capture Contains a list of all the phase types Bus Hound can capture. Placi
ng a check mark next to a phase allows it to be captured. Removi
ng a check mark next to a phase results in the phase not bei
ng captured. This option is useful for filteri
ng out phases that are not of interest or includi
ng special operati
ng system phases that are off by default. To the right of the check box, a white circle may appear. This indicates the phase has been detected and exists in the captured
data. If the circle blinks bright green, it is a real time activity light indicati
ng the phase has occurred and has been captured. Merge Repeated Commands When selected, if a command occurs that is
identical to the previous command, the new command will not be logged separately. Instead, the repeat count of the previous command is incremented. This option is useful for compacti
ng the captured
data when a device is bei
ng continually polled with the same command. Enable Sounds If this option is enabled, Bus Hound will make an audible “pi
ng” if the capture, setti
ngs, or devices window is up and a trigger condition is met. Columns to Display Place a checkmark in the boxes to include the desired columns in the Capture Window. The selected columns will also be included in drag & drop and save operations. See the section “The Capture Window” for more details about each column. The Devices Window The list of devices represents every device on the system which Bus Hound supports. The list automatically refreshes to reflect new or removed devices. To select/deselect a device to capture, click in the check box next to the device. The selection will be applied instantly. Each device is assigned a number which is in parenthesis before the name of the device. This number is displayed in the capture window under the “Device” column. The number reflects the order in which the device was added to the system. If a device is displayed in a light font, it indicates the device is not currently present on the system. Capture new devices Selecti
ng this checkbox will automatically capture
data for new devices that are detected. This feature is useful for capturi
ng the first commands sent to hot plugged devices. Device Properties This window pane displays details about the device such as the performance. The performance is calculated by summi
ng the total bytes transferred div
ided by the total elapsed time of the commands. The performance statistics are cleared when the run button is pressed in the Capture window. Send Commands You can send your own custom commands to a device usi
ng Bus Commander. To start Bus Commander, highlight a device with the mouse and click the “Send Commands” button or simply double click the device. Bus Commander is a very powerful complementary tool that lets you submit USB, 1394, ATA and SCSI commands to devices. You can also perform operations like bus resets and hardware port i/o. Files Installed BUSHOUND.EXE – Bus Hound application BUSCMDR.EXE – Bus Commander application BHUNINST.EXE – uninstaller BHLOG.EXE – capture to disk tool (site
license version only) BHOUND3.VXD – device driver for Windows 95, 98, Me BHOUND4.SYS – device driver for Windows NT 4.0 BHOUND5.SYS – device driver for Windows 98, Me, 2000, 2003, XP HELP.RTF – product help file (this file) Site
License The site
license version of Bus Hound includes the bhlog.exe command line tool in the folder where Bus Hound is installed. bhlog spools captured
data to a disk file in real time. This tool raises the maximum capture size from available RAM to available disk space. bhlog also has the ability to retain captured
data in the event a system freezes or reboots by directi
ng captured
data to a file on a network drive. FAQ 1. What type of I/O is captured? Bus Hound takes a snap shot of packets sent across the bus. This includes commands,
data, status, and timi
ng of each command. Bus Hound does not monitor individual hardware signals. 2. Will Bus Hound cha
nge the beh
avior of my devices? No. Bus Hound simply “listens” for packets. Bus Hound does not alter commands, does not send its own commands, does not replace any system drivers, and does not access the hardware. The system and devices will operate
identically whether Bus Hound is installed or not. 3. Will Bus Hound degrade system performance? Customers capturi
ng
data from extremely fast devices in parallel have been impressed by Bus Hound’s ability not to effect performance. Bus Hound is even more innocuous when in the stopped state. 4. Which devices are supported? All
IDE, SCSI, USB and 1394 devices are supported includi
ng disk drives, mice, scanners, web cams, and everythi
ng else. Devices that emulate one of these buses are also supported such as certain parallel port devices. 5. Why are there duplicate devices? For some devices, Windows first forms high level packets that are then translated into low level packets which are in turn sent to the hardware. Bus Hound shows several devices so you can choose which level of I/O you wish to capture. 6. What does capturi
ng I/O for a controller do? Some controllers receive commands and some do not. You can experiment capturi
ng
data for a controller to see if the packets are of interest. 7. What if Bus Hound does not show a device? No devices are displayed when the system is started in safe mode. This is a safety feature to keep safe mode as clean as possible. Devices which are marked with a problem in device manager are not displayed. SCSI adapters are not displayed under Windows 95/98/Me unless they have one or more devices attached. 8. Why are some devices grayed out? A grayed out device indicates it is currently not attached to the system. 9. Windows 95/98/Me crashes when pressi
ng run. What do I do? Due to limitations in the Windows 9x architecture, if too many device drivers ask to receive notification of I/O completion, the system will crash. Microsoft device drivers and other installed software such as Bus Hound need such notifications. To resolve this, remove software likely to have additional device drivers installed for the device. For CD/DVD drives, an easy solution is to rename the legacy scsi1hlp.vxd to scsi1hlp.bak which is in the windows/system/iosubsys folder. 10. Why am I not able to capture all 1394 events? Some 1394 devices Bus Hound displays are logical devices such as AV/VHS devices. Select devices further up the tree to capture bus activity for such devices. While Bus Hound logs every isochronous transaction, there is no practical way for Bus Hound to see every asynchronous transaction. If you need to see more 1394 activity, note Bus Hound can capture a great deal more in operati
ng systems prior to XP, particularly for SBP-2 devices. 11. Why am I not seei
ng task file (ATA) commands for
IDE hard drives? Bus Hound captures ATA commands only when an application or driver explicitly sends an ATA command (eg: SMART,
IDENTIFY). For normal file system requests, Bus Hound captures SCSI CDB’s instead of ATA commands due to the monolithic nature of the Windows
IDE device driver. Note the CDB’s captured have a one to one relationship with ATA commands and can be easily translated to their native ATA equivalent. Also note the
data captured with the CDB is
identical to the ATA
data transfer. 12. Where can I get more detailed information on the captured
data? For your convenience, please visit www.perisoft.net/e
ngineer for handy reference
data and specifications. Also please note the followi
ng resources: Specification Location USB www.usb.org SCSI www.t10.org 
IDE, ATA, ATAPI www.t13.org 1394, Firewire www.1394ta.org or www.ieee.org Windows DDK www.microsoft.com/ddk 14. Idea激活2022.1.4 Where do I get support? Visit www.perisoft.net. Any questions, comments, or problem reports on the free or full version are Idea激活2022.1.4 welcome.

Idea激活2022.1.4(安装ideaIU-2022.1.4报错问题解决办法)

相关推荐