PS/2 mice pause in 32-bit Windows XP Pro. SP3 (safe mode too) and 7 PE liveCD...
Ant
Does anyone know why my PS/2 mice, with its USB adapter (Logitech and
eMachine), like to pause on my new EVGA X58 SLI (132-BL-E758; BIOS date
5/11/2010; v6.00 PG; release number IX58SZ64) motherboard in 32-bit
Windows? I never had this problem with my other older motherboards with
pure PS/2 connections, but this new motherboard only has a PS/2 keyboard
port so I was forced to use a USB adapter for the mouse. The reason for
a PS/2 mouse is because I use a KVM to share my monitor, mouse, and
keyboard. I already eliminated the cables and KVM switch box to see
where the pauses are coming from. They're not from KVM and its cables. :(
My PS/2 mice likes to pause in 32-bit Windows. Rear ports seems to pause
way more than the front. The pauses can cause randomly and every few
seconds. I also tried different adapter cables beside different PS/2
mice. I can reproduce this in both 32-bit Windows XP Pro. SP3 (safe mode
too) and 7 PE liveCD.
I was not able to reproduce it with a KNOPPIX v6.4.4 liveCD, but I did
notice these USB errors in dmesg command:
a_codec_realtek cx24123 cx24113 i7core_edac snd_hda_intel r8169 mii
s5h1420 edac_core snd_hda_codec i2c_i801
[ 14.355804] Pid: 2102, comm: modprobe Tainted: G W 2.6.37 #13
[ 14.355807] Call Trace:
[ 14.355812] [<c0133505>] warn_slowpath_common+0x77/0x8c
[ 14.355816] [<c01fd12c>] ? __xlate_proc_name+0x99/0xa0
[ 14.355820] [<c01fd12c>] ? __xlate_proc_name+0x99/0xa0
[ 14.355824] [<c0133596>] warn_slowpath_fmt+0x2e/0x30
[ 14.355827] [<c01fd12c>] __xlate_proc_name+0x99/0xa0
[ 14.355831] [<c01fdb67>] __proc_create+0x46/0xea
[ 14.355835] [<c01fdd8b>] proc_mkdir_mode+0x23/0x47
[ 14.355839] [<c01fddbe>] proc_mkdir+0xf/0x11
[ 14.355844] [<c01751e8>] register_handler_proc+0xce/0xde
[ 14.355849] [<c01734af>] __setup_irq+0x216/0x277
[ 14.355854] [<c02f1fc2>] ? __pci_request_region+0xb0/0xf8
[ 14.355858] [<c017390d>] request_threaded_irq+0x109/0x12e
[ 14.355865] [<f839a109>] ? flexcop_pci_isr+0x0/0xf0 [b2c2_flexcop_pci]
[ 14.355871] [<f839a363>] flexcop_pci_probe+0x16a/0x281
[b2c2_flexcop_pci]
[ 14.355875] [<c02f329f>] local_pci_probe+0x3e/0x81
[ 14.355879] [<c02f3d63>] pci_device_probe+0x43/0x66
[ 14.355884] [<c0380d7b>] driver_probe_device+0x97/0x128
[ 14.355887] [<c0380e4f>] __driver_attach+0x43/0x5f
[ 14.355892] [<c0380532>] bus_for_each_dev+0x3d/0x67
[ 14.355896] [<c0380c13>] driver_attach+0x19/0x1b
[ 14.355899] [<c0380e0c>] ? __driver_attach+0x0/0x5f
[ 14.355902] [<c03808fb>] bus_add_driver+0x9e/0x1e3
[ 14.355906] [<c03810a2>] driver_register+0x84/0xeb
[ 14.355910] [<c02f3f45>] __pci_register_driver+0x38/0x95
[ 14.355916] [<f839d017>] flexcop_pci_module_init+0x17/0x19
[b2c2_flexcop_pci]
[ 14.355920] [<c0101174>] do_one_initcall+0x87/0x13d
[ 14.355925] [<f839d000>] ? flexcop_pci_module_init+0x0/0x19
[b2c2_flexcop_pci]
[ 14.355930] [<c015df40>] sys_init_module+0xcd4/0xe74
[ 14.355936] [<c057df05>] syscall_call+0x7/0xb
[ 14.355940] ---[ end trace 5a0003f5d005a066 ]---
[ 14.366953] DVB: registering new adapter (FlexCop Digital TV device)
[ 14.368564] b2c2-flexcop: MAC address = 00:d0:d7:30:19:c1
[ 14.369171] CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
[ 14.369173] CX24123: wrong demod revision: 87
[ 14.570685] nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a,
err == -121)
[ 14.570689] Unknown/Unsupported NXT chip: 00 00 00 00 00
[ 14.571177] lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02
error (ret == -121)
[ 14.571514] bcm3510: Revision: 0x1, Layer: 0xb.
[ 14.583081] b2c2-flexcop: found 'Broadcom BCM3510 VSB/QAM frontend' .
[ 14.583085] DVB: registering adapter 1 frontend 0 (Broadcom BCM3510
VSB/QAM frontend)...
[ 14.583191] b2c2-flexcop: initialization of 'Air2PC/AirStar 2 ATSC
1st generation' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
[ 14.612931] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 15.874030] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 15.894649] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 16.272853] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 20.818513] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 22.974664] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 26.511687] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 28.707741] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 31.679122] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 33.183186] [drm] Initialized drm 1.1.0 20060810
[ 33.412969] [drm] radeon kernel modesetting enabled.
[ 33.413014] radeon 0000:02:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 33.413018] radeon 0000:02:00.0: setting latency timer to 64
[ 33.413881] [drm] initializing kernel modesetting (RV770 0x1002:0x9440).
[ 33.414052] [drm] register mmio base: 0xF3BE0000
[ 33.414055] [drm] register mmio size: 65536
[ 33.414275] ATOM BIOS: WEKIVA
[ 33.414290] radeon 0000:02:00.0: VRAM: 512M 0x0000000000000000 -
0x000000001FFFFFFF (512M used)
[ 33.414292] radeon 0000:02:00.0: GTT: 512M 0x0000000020000000 -
0x000000003FFFFFFF
[ 33.417099] [drm] Detected VRAM RAM=512M, BAR=256M
[ 33.417101] [drm] RAM width 256bits DDR
[ 33.417163] [TTM] Zone kernel: Available graphics memory: 440070 kiB.
[ 33.417166] [TTM] Zone highmem: Available graphics memory: 1291818 kiB.
[ 33.417168] [TTM] Initializing pool allocator.
[ 33.417185] [drm] radeon: 512M of VRAM memory ready
[ 33.417187] [drm] radeon: 512M of GTT memory ready.
[ 33.417232] radeon 0000:02:00.0: irq 44 for MSI/MSI-X
[ 33.417237] radeon 0000:02:00.0: radeon: using MSI.
[ 33.417263] [drm] radeon: irq initialized.
[ 33.417265] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 33.417525] [drm] Loading RV770 Microcode
[ 33.564928] radeon 0000:02:00.0: WB enabled
[ 33.611699] [drm] ring test succeeded in 1 usecs
[ 33.611807] [drm] radeon: ib pool ready.
[ 33.611902] [drm] ib test succeeded in 0 usecs
[ 33.611904] [drm] Enabling audio support
[ 33.611909] failed to evaluate ATIF got AE_BAD_PARAMETER
[ 33.612360] [drm] Radeon Display Connectors
[ 33.612362] [drm] Connector 0:
[ 33.612363] [drm] DVI-I
[ 33.612364] [drm] HPD2
[ 33.612365] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68
0x7e6c 0x7e6c
[ 33.612366] [drm] Encoders:
[ 33.612368] [drm] DFP1: INTERNAL_UNIPHY
[ 33.612369] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 33.612370] [drm] Connector 1:
[ 33.612371] [drm] DIN
[ 33.612372] [drm] Encoders:
[ 33.612373] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 33.612374] [drm] Connector 2:
[ 33.612374] [drm] DVI-I
[ 33.612375] [drm] HPD1
[ 33.612377] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28
0x7e2c 0x7e2c
[ 33.612378] [drm] Encoders:
[ 33.612379] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 33.612380] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
[ 33.718954] [drm] Internal thermal controller with fan control
[ 33.719028] [drm] radeon: power management initialized
[ 33.852563] [drm] fb mappable at 0xD0142000
[ 33.852565] [drm] vram apper at 0xD0000000
[ 33.852566] [drm] size 5242880
[ 33.852567] [drm] fb depth is 24
[ 33.852568] [drm] pitch is 5120
[ 34.278659] Console: switching to colour frame buffer device 160x64
[ 34.285293] fb0: radeondrmfb frame buffer device
[ 34.285294] drm: registered panic notifier
[ 34.285297] [drm] Initialized radeon 2.7.0 20080528 for 0000:02:00.0
on minor 0
[ 40.114035] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 42.180338] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 46.612427] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 49.680232] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 54.654704] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 62.480716] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 64.463835] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 67.049219] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 69.844227] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 79.277358] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 89.652149] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 94.872817] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 95.632505] NET: Registered protocol family 10
[ 95.633185] lo: Disabled Privacy Extensions
[ 97.062232] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 103.108100] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 108.446748] lp: driver loaded but no devices found
[ 108.470690] ppdev: user-space parallel port driver
[ 108.498813] r8169 0000:07:00.0: eth0: link down
[ 108.498899] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 108.534227] r8169 0000:08:00.0: eth1: link up
[ 108.534238] r8169 0000:08:00.0: eth1: link up
[ 114.008620] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 116.387697] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 119.036273] eth1: no IPv6 routers present
[ 124.183759] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 130.093198] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 151.614751] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 159.354201] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 164.897676] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 181.125314] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 189.863026] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 198.287969] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 212.765426] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 220.704585] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 223.333203] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 226.407712] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 228.899943] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 231.086014] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 234.935796] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 239.201473] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 243.450576] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 259.398739] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 264.829034] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 269.820114] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 292.173511] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 328.791420] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 351.024955] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 353.221014] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 370.343766] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 378.465890] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 381.101197] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 393.678725] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 404.699026] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 413.905902] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 433.114917] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 436.019723] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 451.412212] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 462.702018] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 468.012513] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 472.431309] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 479.049477] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 483.508131] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 490.518934] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 505.102857] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 506.906330] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 511.571328] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 514.143401] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 516.888492] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 521.649982] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 526.105354] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 541.391366] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 543.713877] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 550.631512] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 553.107087] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 555.832232] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 557.812012] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 560.294241] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 570.406189] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 577.017682] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 581.619455] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 587.688625] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 594.386637] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 600.938226] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 607.060651] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 620.799395] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 631.533556] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 645.668278] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 653.797110] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 656.409120] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 668.930050] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 698.959723] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 715.084235] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 720.348117] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 732.822526] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 768.655149] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 799.909251] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 829.942268] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 840.277108] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 843.261804] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 851.121066] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 858.581075] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 860.727237] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 868.579872] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 882.252097] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 886.833925] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 894.956061] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 897.857542] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 904.013170] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 909.147360] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 934.831444] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1012.020116] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1019.303808] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1038.076903] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1040.961754] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1088.001000] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1094.046886] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
[ 1105.762590] usb 7-1: reset low speed USB device using uhci_hcd and
address 2
Does Windows not reset USB device or something? I also tried Logitech
Mouseware, but that didn't seem to help either.
Thank you in advance. :)
FYI on my PC specifications: Intel i7 950 CPU, three 2 GB of Kingston
HyperX T1 Series 240-Pin DDR3 SDRAM 2000 (PC3 16000) Desktop Memory
Model KHX2000C9AD3T1K3/6GX DDR3 RAM (6 GB total; 2.5 GB shown; will
install a 64-bit OS later on to use it all) in 32-bit old, updated
Windows XP Pro. SP3 (Internet Explorer [rarely used] v6.0 SP3 and
DirectX 9.0c [June 2010]), EVGA X58 SLI (132-BL-E758; BIOS date
5/11/2010; v6.00 PG; release number IX58SZ64) motherboard, MSI
R4870-T2D512 OC Radeon HD 4870 512 MB (S-video+composite cables and
adapter connected to Toshiba W-627 VCR to a January 1996 20" Sharp CRT
TV), an used mid-tower Antec P180 ATX case, five 120 mm case fans, a
side dual cooler fan to cool PCI cards, two onboard RealTek Gigabit
Ethernets and onboard RealTek sound, Corsair CMPSU-650TX 650 watts
ATX12V/EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC
power supply, two Broadband Technologies Air2PC-ATSC-PCI HDTV tuner
cards (DVB; revision 2; connected to a DB2 bowtie antenna), LG HL-DT-ST
DVDRAM GH24NS50 burner drive, Sony NEC Optiarc DVD-RW AD-7220S SATA
burner drive, two internal 7200 RPM Seagate SATA hard disk drives (HDDs)
[ST3320620AS 320 GB and ST3500320AS 500 GB], and Logitech Z-2300
speakers (2.1 setup and analog).
--
"... [Let us inquire] what glory there was in an omnipotent being
torturing forever a puny little creature who could in no way defend
himself? Would it be to the glory of a man to fry ants?" --Charlotte
Perkins Gilman
/\___/\ Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
Ant
an optical laser type. They didn't make any differencs.
On 4/26/2011 6:34 AM PT, Ant typed:
"Ah. Those club kids did eat those ants up like popcorn." --CSI: Miami
(Wannabe episode; #218)
/\___/\ Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
--
"Ah. Those club kids did eat those ants up like popcorn." --CSI: Miami
(Wannabe episode; #218)
Nobody > (Revisited)
have you tried using that Logitech mouse as USB? Does it do the same?
(and I'm a Logi-freak, Trackman Wheel here, logi setpoint drivers on
Win7 32)
I think Logitech builds their micey-type stuff as both PS/2 and USB
from the ground up. All the green adapter does is just a connector
change as far as I can tell. I've carved one open and could not find
*any* active componentry inside.
In reality, i don't think the USB vs PS/2 has anything to do with it.
Methinks we share the same concept on using ports, if I can use the
keyboard and/or mouse as PS/2 (depending on mobo), I will.
1) avoids the uncommon but real 'can't do BIOS w/USB KB' issue
2) saves a hi-power USB mobo port for other uses.
From my own experience on mouse-halts and such, most have been
malfunctioning apps. Mozilla FF and TB do it often, but not to the
level that *any* version of IE does.
I had it happen today with T-Bird 3.1.9.
The pointer just totally disappeared. I could somewhat find it by waving
around blindly until something dimmed or changed.
Killing and restarting T-bird fixed it.
Another 'methinks'... I've been around the Ant long enough to know he's
got possibly more than normal paranoia on security. That often leads to
many strange security apps running in the background. (Ben Dere,Dun
Dat). This ends up doing the same instability as loading up a bunch of
TSRs in DOS/Win3X.
I'd try going thru the 'selective startup' troubleshoot game on this.
--
"Shit this is it, all the pieces do fit.
We're like that crazy old man jumping
out of the alleyway with a baseball bat,
saying, "Remember me motherfucker?"
Jim “Dandy” Mangrum
Ant
> Ant, I think you have a hex that leads to strange fails.
It happens all the time. :( One of my friends teased me that ants
shouldn't be using computers. :P
> have you tried using that Logitech mouse as USB? Does it do the same?
What do you mean as USB? It has a PS/2 connector. I use PS/2 mice and
keyboards because of KVMs to share with other PCs. I really don't want
to have to replace them with USB ones since they are costly.
>
> (and I'm a Logi-freak, Trackman Wheel here, logi setpoint drivers on
> Win7 32)
>
> I think Logitech builds their micey-type stuff as both PS/2 and USB
> from the ground up. All the green adapter does is just a connector
> change as far as I can tell. I've carved one open and could not
> find *any* active componentry inside.
>
> In reality, i don't think the USB vs PS/2 has anything to do with it.
>
> Methinks we share the same concept on using ports, if I can use the
> keyboard and/or mouse as PS/2 (depending on mobo), I will.
> 1) avoids the uncommon but real 'can't do BIOS w/USB KB' issue
> 2) saves a hi-power USB mobo port for other uses.
>
> From my own experience on mouse-halts and such, most have been
> malfunctioning apps. Mozilla FF and TB do it often, but not to the
> level that *any* version of IE does.
It happens everywhere in Windows even in safe mode, login screens, etc.
:(
> I had it happen today with T-Bird 3.1.9.
> The pointer just totally disappeared. I could somewhat find it by
> waving around blindly until something dimmed or changed.
> Killing and restarting T-bird fixed it.
>
> Another 'methinks'... I've been around the Ant long enough to know
> he's got possibly more than normal paranoia on security. That often
> leads to many strange security apps running in the background. (Ben
> Dere,Dun Dat). This ends up doing the same instability as loading up
> a bunch of TSRs in DOS/Win3X.
>
> I'd try going thru the 'selective startup' troubleshoot game on this.
Yeah, that is what I am doing. No problems in KNOPPIX v6.4.4's liveCD
(Linux/Debian)!
Quote of the Week: "The foreign policy aim of ants can be summed up as
follows: restless aggression, territorial conquest, and genocidal
annihilation of neighboring colonies whenever possible. If ants had
nuclear weapons, they would probably end the world in a week." --Journey
to the Ants, page 59. Bert Holldobler & Edward O. Wilson
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Paul
> Hello!
>
> Does anyone know why my PS/2 mice, with its USB adapter (Logitech and
> eMachine), like to pause on my new EVGA X58 SLI (132-BL-E758; BIOS date
> 5/11/2010; v6.00 PG; release number IX58SZ64) motherboard in 32-bit
> Windows? I never had this problem with my other older motherboards with
> pure PS/2 connections, but this new motherboard only has a PS/2 keyboard
> port so I was forced to use a USB adapter for the mouse. The reason for
> a PS/2 mouse is because I use a KVM to share my monitor, mouse, and
> keyboard. I already eliminated the cables and KVM switch box to see
> where the pauses are coming from. They're not from KVM and its cables. :(
>
> My PS/2 mice likes to pause in 32-bit Windows. Rear ports seems to pause
> way more than the front. The pauses can cause randomly and every few
> seconds. I also tried different adapter cables beside different PS/2
> mice. I can reproduce this in both 32-bit Windows XP Pro. SP3 (safe mode
> too) and 7 PE liveCD.
>
> I was not able to reproduce it with a KNOPPIX v6.4.4 liveCD, but I did
> notice these USB errors in dmesg command:
> a_codec_realtek cx24123 cx24113 i7core_edac snd_hda_intel r8169 mii
> s5h1420 edac_core snd_hda_codec i2c_i801
<< snipped valuable trace data >>
> [ 67.049219] usb 7-1: reset low speed USB device using uhci_hcd and address 2
> [ 69.844227] usb 7-1: reset low speed USB device using uhci_hcd and address 2
> [ 79.277358] usb 7-1: reset low speed USB device using uhci_hcd and address 2
...
> [ 1094.046886] usb 7-1: reset low speed USB device using uhci_hcd and address 2
>
> Does Windows not reset USB device or something? I also tried Logitech
> Mouseware, but that didn't seem to help either.
>
> Thank you in advance. :)
>
> FYI on my PC specifications: Intel i7 950 CPU, three 2 GB of Kingston
> HyperX T1 Series 240-Pin DDR3 SDRAM 2000 (PC3 16000) Desktop Memory
> Model KHX2000C9AD3T1K3/6GX DDR3 RAM (6 GB total; 2.5 GB shown; will
> install a 64-bit OS later on to use it all) in 32-bit old, updated
> Windows XP Pro. SP3 (Internet Explorer [rarely used] v6.0 SP3 and
> DirectX 9.0c [June 2010]), EVGA X58 SLI (132-BL-E758; BIOS date
> 5/11/2010; v6.00 PG; release number IX58SZ64) motherboard, MSI
> R4870-T2D512 OC Radeon HD 4870 512 MB (S-video+composite cables and
> adapter connected to Toshiba W-627 VCR to a January 1996 20" Sharp CRT
> TV), an used mid-tower Antec P180 ATX case, five 120 mm case fans, a
> side dual cooler fan to cool PCI cards, two onboard RealTek Gigabit
> Ethernets and onboard RealTek sound, Corsair CMPSU-650TX 650 watts
> ATX12V/EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC
> power supply, two Broadband Technologies Air2PC-ATSC-PCI HDTV tuner
> cards (DVB; revision 2; connected to a DB2 bowtie antenna), LG HL-DT-ST
> DVDRAM GH24NS50 burner drive, Sony NEC Optiarc DVD-RW AD-7220S SATA
> burner drive, two internal 7200 RPM Seagate SATA hard disk drives (HDDs)
> [ST3320620AS 320 GB and ST3500320AS 500 GB], and Logitech Z-2300
> speakers (2.1 setup and analog).
Your motherboard comes in a couple models, but it's possible the same
manual covers the A1 and TR versions.
http://www.evga.com/support/manuals/files/132-BL-E758.pdf
On page 49, you can try disabling
"USB Keyboard Function [Disable]
USB Mouse Function [Disable]
Use this function to enable or disable support under DOS."
Some of those functions are documented here. It's possible for
the BIOS in SMM/SMI mode, to pull information from USB devices,
and stuff that info into PS/2 space. I doubt you need that right now.
http://www.techarp.com/freebog.aspx
"USB Keyboard Support
USB Legacy Support
USB Mouse Support
USB Port 64/60 Emulation"
*******
When you're in Windows, fire up Device Manager (devmgmt.msc) and
look at the USB entries. For example, your USB Root Hubs may have:
"Allow the computer to turn off this device to save power."
Disable that, so that the USB Root Hub remains powered consistently.
I hope that's enough to sort the Windows problem.
*******
In some cases, a BIOS update may be needed to fix things like that.
http://www.evga.com/support/drivers/
Mainboards, EVGA X58 Series, E758 - X58 SLI BIOS
I took a look at the release notes, but don't see an item there
that suggests your problem is fixed via BIOS update. At this point,
all I suggest you do, is look at the release notes for hints.
EVGA may also have a forum, and you can try looking there.
*******
Also, in your description, you should be careful to state what actual
interface is being used.
I have a Logitech mouse (M-BQ85)
http://www.drivers.ru/images/catalog/logitech_Click.jpg
and it comes with a turquoise colored adapter. The adapter is passive,
and has a PS/2 male end (for the computer) and a USB female end (for the
mouse). The mouse comes with a USB connector on the end. But if you
fit the turquoise colored adapter, the mouse then has a PS/2 end, and
that plugs into a PS/2 equipped computer. I used to use the turquoise
adapter with my older computers, because they had PS/2 mouse ports.
My latest computer is like your machine - there is a PS/2 keyboard port,
but no mouse port. Therefore, I had to remove the adapter, and now the
mouse uses its (native) USB connector instead.
You've been connecting your mouse via USB, so it's effectively a USB mouse,
as far as the technical details of this problem are concerned.
The turquoise adapter is passive. There is no chip inside. The mouse in
fact, is dual protocol. It senses the voltages on the various wires,
and figures out whether it is installed on a PS/2 port (via adapter) or
on a USB port (no adapter). This adapter won't work, if the mouse is
not inherently dual protocol - if the mouse came with such an adapter,
that is proof it is dual protocol. Otherwise, I doubt the instructions
in this article would work, if you used a mouse which was USB only.
http://www.ehow.com/how_6898911_run-mouse-through-ps2-port.html
This is an example of an "active" adapter. The "blob" contains a single
chip, which contains an actual 8 bit microcontroller and firmware. It
converts PS/2 protocol input, into USB packets. Usage of this device,
will not change your symptoms one bit, so don't bother. Older versions
of this design used to freeze after ten minutes usage, but that
was a firmware issue. As far as I know, they fixed that. But even if
this thing is working, it's not going to change your "USB bus disconnect"
symptoms.
http://www.newegg.com/Product/Product.aspx?Item=N82E16812156019
It's not clear to me, how you're going to connect mixed generations
of computers to your KVM. Not many KVMs support both PS/2 and USB
or any combination thereof. If all the KVM supports is PS/2,
then you're not going to be able to use that with your X58 (missing mouse port),
unless you use an active adapter. The active adapter would solve the
connection problem, but would not necessarily change the symptoms
of your bus disconnect. But using the active adapter, may make it
possible to wire up the KVM again.
So first:
1) Solve the bus disconnect problem.
2) Consider an active adapter as a work-around for the shortcomings
of your average KVM. (There is no reason to believe, combining a
KVM with an active adapter is going to work - because they both
are playing around with the interface, and these technologies
aren't exactly "transparent". They both may involve hacks of
various sorts. If such a combination actually worked, I'd consider
it a miracle. It's really a "$5 gamble", not a sure thing.)
Paul
Ant
PS/2+USB adapter splitter. It was working for about 30 minutes and then
both devices started pausing. When I type on my PS/2 keyboard and pauses
occur, it either doesn't register my keys or gets stuccccccccccccccck
like that. :(
On 4/26/2011 6:50 AM PT, Ant typed:
"The ant has made himself illustrious; Through constant industry
industrious.; So what? Would you be calm and placid; If you were full of
formic acid?" --Ogden Nash (The Ant)
Ant
> Your motherboard comes in a couple models, but it's possible the same
> manual covers the A1 and TR versions.
>
> http://www.evga.com/support/manuals/files/132-BL-E758.pdf
>
> On page 49, you can try disabling
>
> "USB Keyboard Function [Disable]
> USB Mouse Function [Disable]
>
> Use this function to enable or disable support under DOS."
> Some of those functions are documented here. It's possible for
> the BIOS in SMM/SMI mode, to pull information from USB devices,
> and stuff that info into PS/2 space. I doubt you need that right now.
>
> http://www.techarp.com/freebog.aspx
>
> "USB Keyboard Support
> USB Legacy Support
> USB Mouse Support
> USB Port 64/60 Emulation"
I tried that and it didn't help. I even tried disabling controllers, but
disabling 1.0 resulted losing all of my USB. :D So I just disabled 2.0
controller and still same problems. I also tried changing USB speeds in
CMOS. Basically I changed all values to their opposites. Same problem. Bleh!
> *******
>
> When you're in Windows, fire up Device Manager (devmgmt.msc) and
> look at the USB entries. For example, your USB Root Hubs may have:
>
> "Allow the computer to turn off this device to save power."
>
> Disable that, so that the USB Root Hub remains powered consistently.
>
> I hope that's enough to sort the Windows problem.
OK, they were all enabled so I disabled all eight of them. I didn't see
any power options for Intel ICH10 Family USB Host controllers. However,
I did see each one using 10% of the bandwidth used. Is that OK? But then
I don't see options to change those values. Also, do I have to reboot?
Windows XP didn't tell me.
Also, doesn't XP's safe mode and Windows 7 PE have these always powered
on? I don't think they even do power savings at all.
> In some cases, a BIOS update may be needed to fix things like that.
>
> http://www.evga.com/support/drivers/
>
> Mainboards, EVGA X58 Series, E758 - X58 SLI BIOS
>
> I took a look at the release notes, but don't see an item there
> that suggests your problem is fixed via BIOS update. At this point,
> all I suggest you do, is look at the release notes for hints.
>
> EVGA may also have a forum, and you can try looking there.
Yeah, I posted my issue in my old forum thread:
http://www.evga.com/forums/tm.aspx?high=&m=750057 ... So far, we're all
stomped! :)
> Also, in your description, you should be careful to state what actual
> interface is being used.
>
> I have a Logitech mouse (M-BQ85)
>
> http://www.drivers.ru/images/catalog/logitech_Click.jpg
I am just using basic PS/2 mices (eMachine ball and Logitech optical;
both have two buttons with their middle scrollwheels).
> and it comes with a turquoise colored adapter. The adapter is passive,
> and has a PS/2 male end (for the computer) and a USB female end (for the
> mouse). The mouse comes with a USB connector on the end. But if you
> fit the turquoise colored adapter, the mouse then has a PS/2 end, and
> that plugs into a PS/2 equipped computer. I used to use the turquoise
> adapter with my older computers, because they had PS/2 mouse ports.
> My latest computer is like your machine - there is a PS/2 keyboard port,
> but no mouse port. Therefore, I had to remove the adapter, and now the
> mouse uses its (native) USB connector instead.
>
> You've been connecting your mouse via USB, so it's effectively a USB mouse,
> as far as the technical details of this problem are concerned.
So PS/2 mice connected to USB adapters is considered a USB device?
Interesting. Both basic mice have green PS/2 connectors (male IIRC).
I also tried old Logitech's Mouseware from Logitech's web site which did
not help.
Well, I reproduced the pause problems without KVMs and cables. So that's
a good start to narrow down the sources. It seems like my motherboard
doesn't like USB+PS/2 adapters. :(
> So first:
>
> 1) Solve the bus disconnect problem.
Yeah. I wonder why Linux/KNOPPIX liveCD's session didn't pause, but
still show messages about USB connections in its dmesg. I think I will
try an Ubuntu liveCD next.
> 2) Consider an active adapter as a work-around for the shortcomings
> of your average KVM. (There is no reason to believe, combining a
> KVM with an active adapter is going to work - because they both
> are playing around with the interface, and these technologies
> aren't exactly "transparent". They both may involve hacks of
> various sorts. If such a combination actually worked, I'd consider
> it a miracle. It's really a "$5 gamble", not a sure thing.)
Someone suggested me to try hooking both PS/2 mouse and keyboard to the
PS/2+USB adapter splitter. It was working for about 30 minutes and then
both devices started pausing. When I type on my PS/2 keyboard and pauses
occur, it either doesn't register my keys or gets stuccccccccccccccck
like that. :(
--
"When many work together for a goal, great things may be accomplished.
It is said a lion cub was killed by a single colony of ants." --Saskya
Pandita
Paul
> Someone suggested me to try hooking both mouse and keyboard to the
> PS/2+USB adapter splitter. It was working for about 30 minutes and then
> both devices started pausing. When I type on my PS/2 keyboard and pauses
> occur, it either doesn't register my keys or gets stuccccccccccccccck
> like that. :(
>
Is this an adapter of some sort, on the KVM ?
Are you referring to the PS/2 plus dual USB stack on the back of the computer ?
Or do you own one of these ?
http://images17.newegg.com/is/image/newegg/12-119-237-S02?$S640W$
*******
If it's the latter kind of device, this is the chip inside the "blob"
in the center of the cable.
http://www.chesen.com.tw/p3-products-CSC0101A.asp
"The CEC CSC0101A is an integral micro-controller for converting
PS/2 interface signal to USB applications, which includes 8 bits
high performance micro-controller core, combined USB1.1 low-speed
interface and dual PS/2 handler module."
That product has firmware inside. Either that chip, or one similar in
design, had some kind of firmware bug when it came out. It would "go nuts"
after about ten minutes. That kinda sounds like your symptoms. On later
devices, I stopped seeing complaints.
http://www.chesen.com.tw/images/p3-products/CSC0101A.jpg
The chip draws 20mA, so should even work with a USB hub. The keyboard
or mouse plugged into it, would increase the load. So you'd have to
sum the three of them, to see if they exceeded the power limits
of the USB port used. If a 100mA keyboard, a 100mA mouse, and the
20ma chip drew power from a USB port, you'd need a 500mA port on the
back of the computer for that. A bus powered USB hub port (with 100mA
limit) would not be enough for it.
http://www.chesen.com.tw/download/pc/CSC0101A/R_CSC0101A_160.rar (PDF inside)
Since it has a processor inside, and uses its own internal firmware,
that can help explain why it can go nuts (if badly designed). The
implication is the device doesn't have a fixed function as such,
and relies on its own internal program running in the 6502, to
transfer bytes from the PS/2 interface, into USB packets.
Paul
Ant
> Ant wrote:
>> Someone suggested me to try hooking both mouse and keyboard to the
>> PS/2+USB adapter splitter. It was working for about 30 minutes and
>> then both devices started pausing. When I type on my PS/2 keyboard and
>> pauses occur, it either doesn't register my keys or gets
>> stuccccccccccccccck like that. :(
>>
>
> Is this an adapter of some sort, on the KVM ?
No. I tried without KVMs and their cables, and was still able to
reproduce the symptoms/problems/.
> Are you referring to the PS/2 plus dual USB stack on the back of the
> computer ?
What is a dual USB stack? I am just using a basic USB+PS/2 adapter cable.
>
> Or do you own one of these ?
>
> http://images17.newegg.com/is/image/newegg/12-119-237-S02?$S640W$
Yes, I have that splitter type and without a splitter type (just for
mice -- green color PS/2 end). Both have the same problems.
> If it's the latter kind of device, this is the chip inside the "blob"
> in the center of the cable.
>
> http://www.chesen.com.tw/p3-products-CSC0101A.asp
>
> "The CEC CSC0101A is an integral micro-controller for converting
> PS/2 interface signal to USB applications, which includes 8 bits
> high performance micro-controller core, combined USB1.1 low-speed
> interface and dual PS/2 handler module."
>
> That product has firmware inside. Either that chip, or one similar in
> design, had some kind of firmware bug when it came out. It would "go nuts"
> after about ten minutes. That kinda sounds like your symptoms. On later
> devices, I stopped seeing complaints.
Hmm, I have seen this problem right after Windows' boot ups too.
> http://www.chesen.com.tw/images/p3-products/CSC0101A.jpg
>
> The chip draws 20mA, so should even work with a USB hub. The keyboard
> or mouse plugged into it, would increase the load. So you'd have to
> sum the three of them, to see if they exceeded the power limits
> of the USB port used. If a 100mA keyboard, a 100mA mouse, and the
> 20ma chip drew power from a USB port, you'd need a 500mA port on the
> back of the computer for that. A bus powered USB hub port (with 100mA
> limit) would not be enough for it.
>
> http://www.chesen.com.tw/download/pc/CSC0101A/R_CSC0101A_160.rar (PDF
> inside)
>
> Since it has a processor inside, and uses its own internal firmware,
> that can help explain why it can go nuts (if badly designed). The
> implication is the device doesn't have a fixed function as such,
> and relies on its own internal program running in the 6502, to
> transfer bytes from the PS/2 interface, into USB packets.
So, are there any USB+PS/2 adapters that would work for my situation?
How come KNOPPIX v6.4.4 didn't have these pauses even though its dmesg
show USB messages ("usb 7-1: reset low speed USB device using uhci_hcd
and address 2")?
--
"Although you're a little ant, I won't bully you." --Sai Yuk from The
Legend of Fong Sai Yuk movie (English subtitles)
Paul
>
> So, are there any USB+PS/2 adapters that would work for my situation?
> How come KNOPPIX v6.4.4 didn't have these pauses even though its dmesg
> show USB messages ("usb 7-1: reset low speed USB device using uhci_hcd
> and address 2")?
The message tells you something is wrong. As far as I know, bus resets
are part of discovering new hardware. And that can happen, if a device
"disappears" from the bus and then comes back again. I proposed a
Power Management event as a cause for that, which you eliminated.
The device itself (like a Chesen chip) might do that on its own
(internal reset).
Maybe Linux takes a shortcut on the reset, using existing state information,
and isn't really doing very much, protocol wise ? It could be, that in
Windows they do a complete device reset, and all state is lost. You'd
need something like a USB protocol analyzer to guess at this.
As far as I know, your ICH10R has a conventional USB implementation.
It should behave like the chips before it.
Paul
Ant
> > How come KNOPPIX v6.4.4 didn't have these pauses even though its dmesg
> > show USB messages ("usb 7-1: reset low speed USB device using uhci_hcd
> > and address 2")?
> The message tells you something is wrong. As far as I know, bus resets
> are part of discovering new hardware. And that can happen, if a device
> "disappears" from the bus and then comes back again. I proposed a
> Power Management event as a cause for that, which you eliminated.
> The device itself (like a Chesen chip) might do that on its own
> (internal reset).
Yeah, I told my internal hubs to always be powered on (don't have any
external hubs). I still get pauses. :(
> Maybe Linux takes a shortcut on the reset, using existing state information,
> and isn't really doing very much, protocol wise ? It could be, that in
> Windows they do a complete device reset, and all state is lost. You'd
> need something like a USB protocol analyzer to guess at this.
Where would I get one of those? Is it software or hardware?
> As far as I know, your ICH10R has a conventional USB implementation.
> It should behave like the chips before it.
Strange. Someone told me that these adapters do not work well. Is that
true?
--
Quote of the Week: "The foreign policy aim of ants can be summed up as
follows: restless aggression, territorial conquest, and genocidal
annihilation of neighboring colonies whenever possible. If ants had
nuclear weapons, they would probably end the world in a week." --Journey
to the Ants, page 59. Bert Holldobler & Edward O. Wilson
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Paul
>
> Strange. Someone told me that these adapters do not work well. Is that
> true?
The active PS/2 to USB adapter, uses an internal 8 bit processor
and 8KB of firmware.
Which means, here is room for firmware bugs. And the firmware is likely
masked ROM. It can't be changed, once you've bought the chip.
As the revision of firmware changes (manufacturer makes improvements),
the behavior of the adapter could change. You'd only get those
improvements by buying a new one. And without release notes,
tracking what improvements were made, or bugs fixed, we aren't
in a position to say anything about an active adapter.
Devices with masked ROM can be relatively cheap to make. That's how
they can sell the active adapter for $5 to $10. If they had to support
an EEPROM, make the device reprogrammable, the cost would go up.
I would test your adapter on another computer, and see if there
are still bus resets coming from the interaction of the adapter
with the computer.
*******
USB bus protocol analysers are generally more expensive than a
consumer could afford. And pretty pointless if they don't find
anything. Only a USB hardware developer could justify owning
one, like the folks at Chesen.
http://www.lecroy.com/ProtocolAnalyzer/ProtocolOverview.aspx?seriesid=164
Paul
Ant
> Ant wrote:
> >
> > Strange. Someone told me that these adapters do not work well. Is that
> > true?
> The active PS/2 to USB adapter, uses an internal 8 bit processor
> and 8KB of firmware.
> Which means, here is room for firmware bugs. And the firmware is likely
> masked ROM. It can't be changed, once you've bought the chip.
> As the revision of firmware changes (manufacturer makes improvements),
> the behavior of the adapter could change. You'd only get those
> improvements by buying a new one. And without release notes,
> tracking what improvements were made, or bugs fixed, we aren't
> in a position to say anything about an active adapter.
There's no way to check this? Dang. What about when buying? I got mine
for cheap. Do you know which ones are the good ones?
> Devices with masked ROM can be relatively cheap to make. That's how
> they can sell the active adapter for $5 to $10. If they had to support
> an EEPROM, make the device reprogrammable, the cost would go up.
> I would test your adapter on another computer, and see if there
> are still bus resets coming from the interaction of the adapter
> with the computer.
Good idea! I will try it on my office test PCs.
> USB bus protocol analysers are generally more expensive than a
> consumer could afford. And pretty pointless if they don't find
> anything. Only a USB hardware developer could justify owning
> one, like the folks at Chesen.
> http://www.lecroy.com/ProtocolAnalyzer/ProtocolOverview.aspx?seriesid=164
Ah, high end fancy tools. Nevermind then. :)
Ant
> > they can sell the active adapter for $5 to $10. If they had to support
> > an EEPROM, make the device reprogrammable, the cost would go up.
> > I would test your adapter on another computer, and see if there
> > are still bus resets coming from the interaction of the adapter
> > with the computer.
> Good idea! I will try it on my office test PCs.
So far on one newer PCs (Acer AM3800), it works in its updated 64-bit W7
HP SP1 OS. I will keep it connected for a while.
John B. Smith
years. I call it the 'stuttering mouse'. I use it on USB as otherwise
it stays lighted after I shut the machine down. I think it stutters on
either connection. Motherboard is an Abit, now out of business, I sure
can pick them. I've looked for 3 years for something that would fix
the problem 'live', while running in WindowsXP. My only recourse has
been a reboot. When I run Core Temp with the problem active, I see one
core going back and forth from 0% to 20% activity.
Ant
>>> Devices with masked ROM can be relatively cheap to make. That's how
>>> they can sell the active adapter for $5 to $10. If they had to support
>>> an EEPROM, make the device reprogrammable, the cost would go up.
>
>>> I would test your adapter on another computer, and see if there
>>> are still bus resets coming from the interaction of the adapter
>>> with the computer.
>
>> Good idea! I will try it on my office test PCs.
>
> So far on one newer PCs (Acer AM3800), it works in its updated 64-bit W7
> HP SP1 OS. I will keep it connected for a while.
No problems as of yesterday's test. PS/2+USB splitter adapters should be
fine.
Yep, something is screwy with these USB ports on my motherboard with
PS/2 adapters... Overnight, I used an Ubuntu v11.04 desktop liveCD and
did get a frozen mouse that required a disconnection and reconnection:
http://pastebin.ca/2051975 ...
Maybe this/my motherboard hates these splitter PS/2 adatters? :(
--
"I'm not afraid of insects taking over the world, and you know why? It
would take about a million ants just to aim a gun at me, let alone fire
it. And you know what I'm doing while they're aiming it at me? I just
sort of slip off to the side, and then suddenly run up and kick the gun
out of their hands." --Jack Handy from Saturday Night Live
/\___/\ Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
So that mouse worked on other PCs without problems?
--
"If someone makes you angry, I think the thing to do is tie them down to
the ground, cover them in honey, and then release a swarm of killer ants
on them. That way, you can hit them over and over again and say, 'Hey!
I'm just trying to help!' and they can't really get mad at you." --R.M.
Weiner
John B. Smith
>On 4/29/2011 8:18 AM PT, John B. Smith typed:
>
>> I've been having a similar problem with my Microsoft mouse for 3
>> years. I call it the 'stuttering mouse'. I use it on USB as otherwise
>> it stays lighted after I shut the machine down. I think it stutters on
>> either connection. Motherboard is an Abit, now out of business, I sure
>> can pick them. I've looked for 3 years for something that would fix
>> the problem 'live', while running in WindowsXP. My only recourse has
>> been a reboot. When I run Core Temp with the problem active, I see one
>> core going back and forth from 0% to 20% activity.
>
>So that mouse worked on other PCs without problems?
Yes, when I was having EVGA problems I was switching back and forth
from my Abit machine to my older MSI machine with it. No problems on
the MSI.
Ant
Did you ever RMA that problamatic motherboard to see if it was a
defective port or something?
--
"If you're an ant, and you're walking along across the top of a cup of
pudding, you probably have no idea that the only thing between you and
disaster is the strength of that pudding skin." --Jack Handy from
Saturday Night Live
John B. Smith
>On 4/30/2011 5:23 AM PT, John B. Smith typed:
>
>>>> I've been having a similar problem with my Microsoft mouse for 3
>>>> years. I call it the 'stuttering mouse'. I use it on USB as otherwise
>>>> it stays lighted after I shut the machine down. I think it stutters on
>>>> either connection. Motherboard is an Abit, now out of business, I sure
>>>> can pick them. I've looked for 3 years for something that would fix
>>>> the problem 'live', while running in WindowsXP. My only recourse has
>>>> been a reboot. When I run Core Temp with the problem active, I see one
>>>> core going back and forth from 0% to 20% activity.
>>>
>>> So that mouse worked on other PCs without problems?
>>
>> Yes, when I was having EVGA problems I was switching back and forth
>> from my Abit machine to my older MSI machine with it. No problems on
>> the MSI.
>
>Did you ever RMA that problamatic motherboard to see if it was a
>defective port or something?
Too late, they went out of business. IF they are still doing RMAs I'd
be afraid of getting someone else's castoff.