Great Quality Zx-5360 Drivers
2.2.4, 23 September 2012) (ver. 1.1.8, 14 June 2012) (ver. 2.3.8, 18 August 2012) (ver. 1.1.7, 22 January 2011) (ver. 2.2.3, 11 June 2011) (ver. 1.0.8, 20 September 2012) (ver. 1.5.8, 18 March 2013) (ver.
1.2.5, 30 December 2011) (ver. 2.2.3, 10 January 2011) (ver. 1.0.6, 05 December 2011) (ver. 1.0.4, 09 January 2011) (ver. 1.0.1, 26 November 2013) (ver. 2.2.7, 15 June 2012) (ver. 1.2.9, 30 October 2012) (ver.
2.3.1, 07 May 2012) (ver. 1.3.8, 19 April 2011) (ver. 1.5.4, 24 July 2012) (ver. 2.0.4, 29 January 2012) (ver. 2.2.6, 13 January 2013) (ver.
DRIVER NEEDED: Great Quality ZX-5360 (Windows XP Home) [IDE] Bios / Motherboard Request Board.
1.1.3, 26 August 2013) (ver. 1.5.8, 23 August 2013) (ver. 2.2.4, 25 August 2011) (ver.
2.4.6, 28 November 2011) (ver. 2.2.7, 23 November 2012) (ver.
1.4.3, 23 August 2011) (ver. 2.0.1, 23 November 2011) (ver. 1.3.8, 28 January 2013) (ver.
1.1.3, 30 August 2011) (ver. 2.3.8, 14 July 2012) (ver. 1.1.4, 12 March 2013) (ver. 2.4.2, 19 September 2011) (ver. 2.2.6, 10 April 2013) (ver. 2.5.3, 18 April 2013) (ver. 2.0.1, 24 April 2012) (ver.
2.2.8, 03 March 2013) (ver. 2.3.2, 15 September 2012) (ver. 2.4.5, 25 May 2012) (ver.
2.5.3, 08 April 2012) (ver. 1.2.5, 25 January 2011) (ver. 1.4.6, 09 June 2013) (ver. 2.2.5, 11 August 2011) (ver. 1.1.5, 19 September 2013) (ver. 1.4.5, 24 March 2013) (ver. 2.0.4, 09 April 2011) (ver.
2.5.8, 12 February 2013) (ver. 2.0.2, 08 March 2012) (ver. 2.0.8, 12 December 2012) (ver. 1.1.3, 27 November 2011) (ver. 1.4.8, 04 March 2011) (ver. 1.1.8, 18 February 2012) (ver.
2.3.9, 18 February 2012) (ver. 1.5.4, 28 April 2011) (ver.
2.5.5, 16 June 2013) (ver. 1.3.9, 06 May 2013) (ver. 1.2.2, 15 May 2011) (ver. 1.4.5, 23 June 2011) (ver. 2.5.9, 21 September 2013) (ver.
1.1.2, 30 March 2011) (ver. 1.5.5, 30 August 2011) (ver.
1.3.6, 09 August 2012) (ver. 1.4.9, 14 April 2011) (ver. 1.0.7, 24 September 2012) (ver. 1.1.6, 13 February 2013) (ver. 2.4.8, 31 August 2012) (ver.
1.1.9, 12 March 2013) (ver. 2.2.7, 23 March 2011) (ver. 2.1.9, 02 July 2011) (ver. 1.5.7, 28 May 2013) (ver.
1.4.3, 31 July 2012) (ver. 2.1.1, 30 August 2012) (ver. 2.5.5, 15 January 2012) (ver.
2.0.3, 06 February 2011) (ver. 2.1.9, 30 August 2011) (ver. 1.2.5, 15 June 2011) (ver.
1.4.2, 01 August 2011) (ver. 2.5.5, 06 September 2011) (ver. 2.0.2, 18 February 2012) (ver. 1.3.7, 21 April 2012) (ver. 1.3.4, 17 November 2013) (ver. 2.2.1, 19 April 2012) (ver. 1.1.5, 19 August 2011) (ver.
2.3.3, 13 March 2011) (ver. 2.1.1, 06 September 2012) (ver. 1.2.5, 03 September 2013) (ver. 1.0.8, 08 August 2013) (ver.
1.0.9, 07 August 2012) (ver. 1.0.7, 26 February 2012) (ver. 1.1.4, 16 May 2012) (ver. 1.3.7, 07 November 2011) (ver. 1.1.7, 19 April 2012) (ver.
2.4.6, 17 June 2012) (ver. 1.3.6, 22 January 2012) (ver.
1.4.9, 14 September 2011) (ver. 1.5.9, 13 November 2013) (ver. 1.5.1, 18 June 2011) (ver. 2.4.2, 05 September 2012) (ver. 1.4.7, 20 September 2012) (ver. 2.5.7, 19 May 2013) (ver. 2.0.3, 16 June 2013) (ver.
2.2.7, 12 January 2011) (ver. 1.2.7, 23 April 2013) (ver. 1.3.3, 12 June 2012) (ver. 1.1.8, 18 May 2013) (ver. 2.4.6, 11 April 2013) (ver. 1.1.6, 05 December 2012) (ver. 1.5.4, 03 January 2011) (ver.
1.3.2, 31 October 2011) (ver. 1.1.4, 20 August 2011) (ver. 2.5.7, 24 June 2011) (ver. 2.3.5, 06 July 2011) (ver. 1.1.8, 18 March 2011) (ver. 1.0.7, 14 May 2011) (ver.
1.0.9, 04 August 2012) (ver. 1.2.9, 16 May 2013) (ver. 1.5.2, 07 November 2013) (ver. 1.2.4, 20 January 2013) (ver. 2.3.7, 06 October 2013) (ver. 2.0.1, 15 August 2013) (ver. 2.1.4, 18 July 2012) (ver.
1.1.2, 27 October 2011) (ver. 1.3.5, 23 August 2012) (ver. 1.5.4, 06 January 2011) (ver.
1.4.2, 20 September 2013) (ver. 1.1.4, 10 March 2012) (ver. 2.5.1, 06 March 2011) (ver.
2.4.4, 15 March 2011) (ver. 1.1.5, 24 February 2011) (ver. 1.3.9, 04 May 2012) (ver. 1.3.3, 10 December 2011) (ver. 1.0.9, 26 November 2012) (ver. 1.2.1, 25 May 2013) (ver. 2.0.1, 07 March 2012) (ver.
1.4.9, 18 February 2012) (ver. 2.1.3, 01 September 2011) (ver. 2.4.2, 02 December 2012) (ver. 1.1.6, 10 May 2012) (ver. 2.2.9, 20 April 2012) (ver. 2.3.9, 18 December 2011) (ver. 1.0.6, 21 June 2013) (ver.
2.2.5, 17 January 2012) (ver. 1.3.7, 28 May 2011) (ver. 1.2.5, 11 June 2012) (ver. 1.0.1, 04 May 2012) (ver. 2.5.4, 21 June 2012) (ver. 2.0.9, 11 June 2013) (ver. 1.4.4, 14 October 2012) (ver.
2.2.8, 07 May 2013) (ver. 1.1.4, 25 September 2011) (ver. 1.5.2, 04 November 2013) (ver. 2.2.7, 23 February 2012) (ver. 1.3.5, 02 July 2011) (ver. 1.3.3, 13 August 2012) (ver. 1.4.9, 10 December 2011) (ver.
2.1.6, 04 November 2011) (ver. 1.3.1, 07 May 2012) (ver. 2.4.4, 02 December 2012) (ver. 2.3.2, 28 March 2012) (ver. 2.5.9, 20 October 2011) (ver.
1.5.5, 27 January 2012) (ver. 1.3.4, 08 August 2013) (ver. 2.3.2, 18 September 2012) (ver.
1.1.7, 23 May 2013) (ver. 1.5.5, 19 August 2013) (ver. 1.5.3, 13 September 2012) (ver. 2.2.1, 24 April 2012) (ver.
1.1.5, 09 November 2013) (ver. 1.5.7, 23 April 2013) (ver. 1.4.6, 27 October 2012) (ver. 1.4.7, 28 July 2011) (ver. 2.0.3, 04 May 2013) (ver. 1.4.5, 12 June 2013) (ver. 2.0.6, 12 August 2011) (ver.
2.0.7, 21 March 2011) (ver. 2.3.8, 12 October 2012) (ver. 1.4.6, 24 December 2012) (ver.
2.4.6, 25 February 2013) (ver. 2.2.2, 21 June 2012) (ver. 1.4.8, 24 January 2011) (ver. 2.2.6, 27 July 2012) (ver.
1.1.6, 22 November 2011) (ver. 1.4.1, 27 December 2012) (ver. 2.3.4, 01 August 2013) (ver. 1.2.5, 20 April 2012) (ver. 1.0.4, 05 November 2012) (ver.
2.4.6, 08 April 2012) (ver. 2.4.3, 05 December 2011) (ver.
2.2.7, 02 September 2012) (ver. 2.3.4, 27 December 2012) (ver.
2.2.5, 30 November 2011) (ver. 2.4.1, 11 July 2012) (ver. 2.1.9, 18 January 2013) (ver. 2.0.3, 03 September 2013) (ver. 1.2.5, 20 May 2012) (ver.
1.0.2, 30 November 2012) (ver. 2.2.2, 08 September 2012) (ver.
2.1.7, 16 November 2013) (ver. 2.5.1, 25 November 2012) (ver.
1.4.8, 06 July 2011) (ver. 1.3.1, 21 September 2012) (ver. 1.1.3, 27 September 2011) (ver. 1.3.3, 09 December 2012) (ver.
2.3.6, 25 June 2011) (ver. 1.3.4, 19 May 2012) (ver. 2.0.6, 25 February 2012) (ver. 1.4.3, 19 September 2011) (ver. 1.4.4, 05 January 2012) (ver. 1.0.1, 10 December 2012) (ver.
2.0.8, 13 July 2012) (ver. 2.3.3, 26 August 2013) (ver. 1.4.2, 04 November 2012) (ver. 2.1.1, 25 October 2011) (ver. 1.4.6, 29 January 2011) (ver. 2.4.8, 14 July 2011) (ver. 1.5.9, 07 July 2013) (ver.
2.5.4, 13 May 2012) (ver. 2.4.6, 10 December 2012) (ver. 2.3.1, 15 December 2012) (ver. 1.1.9, 06 May 2012) (ver. 1.2.6, 20 March 2013) (ver. 2.3.5, 17 September 2012) (ver.
1.2.5, 04 July 2012) (ver. 1.4.1, 18 January 2012) (ver. 2.0.8, 18 February 2013) (ver.
2.4.1, 20 April 2011) (ver. 2.0.1, 06 April 2012) (ver. 1.4.5, 21 May 2012) (ver. 1.3.9, 13 March 2011) (ver. 2.4.5, 28 February 2012) (ver. 1.3.5, 18 July 2012) (ver. 2.1.4, 29 August 2011) (ver.
2.4.1, 19 August 2011) (ver. 2.5.3, 08 April 2012) (ver. 2.4.7, 26 April 2012) (ver. 1.0.5, 28 June 2013) (ver. 2.3.1, 05 March 2013) (ver.
2.3.1, 10 April 2013) (ver. 1.3.3, 26 June 2012) (ver. 2.0.9, 22 September 2013) (ver. 1.2.5, 25 September 2013) (ver.
2.1.8, 01 March 2013) (ver. 1.3.5, 06 May 2013) (ver. 2.3.8, 12 February 2011) (ver. 1.5.7, 19 August 2011) (ver.
1.1.2, 10 June 2011) (ver. 2.2.6, 27 February 2013) (ver. 2.3.4, 24 September 2012) (ver. 1.2.3, 22 July 2011) (ver.
1.0.8, 22 July 2013) (ver. 1.5.9, 20 July 2012) (ver. 1.0.2, 28 October 2013) (ver. 2.5.1, 28 March 2013) (ver. 2.5.6, 04 July 2011) (ver. 1.4.2, 30 September 2013) (ver. 2.5.5, 25 November 2012) (ver.
2.2.9, 26 November 2011) (ver. 2.0.1, 14 November 2012) (ver. 1.0.8, 25 February 2012) (ver. 2.3.6, 14 January 2012) (ver. 2.2.5, 04 September 2012) (ver. 2.2.6, 21 February 2013) (ver.
2.3.5, 16 July 2012) (ver. 2.2.7, 11 June 2013) (ver. 2.3.7, 19 June 2013) (ver. 2.2.9, 05 September 2012) (ver. 2.5.5, 20 July 2012) (ver. 2.5.7, 07 September 2013) (ver. 2.5.9, 25 January 2012) (ver.
2.2.3, 20 March 2011) (ver. 1.5.6, 16 February 2013) (ver.
2.2.2, 04 February 2013) (ver. 1.1.5, 02 May 2011) (ver. 2.2.2, 21 May 2012) (ver. 2.0.5, 16 November 2012) (ver. 2.5.7, 27 August 2013) (ver. 1.2.4, 21 June 2011) (ver. 1.4.8, 11 July 2013) (ver.
1.4.5, 10 December 2011) (ver. 2.5.2, 17 August 2012) (ver. 1.4.5, 03 June 2013) (ver.
1.5.7, 01 March 2012) (ver. 1.4.2, 14 November 2012) (ver. 2.3.2, 20 June 2011) (ver. 2.0.4, 17 February 2011) (ver. 2.3.9, 19 February 2011) (ver. 1.3.2, 25 March 2012) (ver.
2.4.8, 05 April 2013) (ver. 1.0.9, 06 January 2013) (ver.
1.4.6, 30 June 2011) (ver. 1.1.1, 13 September 2013) (ver.
1.5.1, 28 January 2012) (ver. 2.3.4, 04 August 2011) (ver. 2.4.8, 19 August 2013) (ver. 1.4.5, 17 February 2013) (ver.
2.2.6, 29 February 2012) (ver. 2.2.2, 15 April 2012) (ver.
1.4.9, 19 January 2011) (ver. 1.2.8, 07 October 2013) (ver. 1.3.7, 24 January 2011) (ver. 1.5.9, 20 March 2013) (ver. 2.4.5, 12 July 2013) (ver. 1.4.7, 01 April 2011) (ver.
2.1.6, 24 August 2012) (ver. 2.1.7, 13 February 2011) (ver. 1.3.5, 19 December 2012) (ver. 1.4.6, 08 June 2012) (ver.
1.3.9, 05 February 2013) (ver. 1.1.8, 09 September 2011) (ver. 1.5.5, 18 June 2011) (ver. 1.2.3, 28 June 2011) (ver.
2.0.7, 11 January 2011) (ver. 2.4.3, 09 June 2012) (ver. 2.3.4, 30 March 2012) (ver. 1.0.9, 25 September 2011) (ver. 2.0.8, 18 June 2012) (ver.
2.4.6, 07 August 2013) (ver. 2.1.9, 10 January 2011) (ver. 1.1.7, 10 October 2012) (ver. 1.0.9, 21 September 2012) (ver. 1.5.2, 18 June 2012) (ver. 2.2.7, 07 November 2013) (ver.
2.5.2, 31 March 2011) (ver. 2.1.2, 09 February 2013) (ver.
2.1.9, 03 January 2011) (ver. 2.5.6, 05 September 2013) (ver. 1.3.1, 03 February 2012) (ver. 1.5.7, 02 March 2013) (ver. 1.3.5, 08 March 2011) (ver. 2.0.2, 31 August 2012) (ver.
1.2.9, 24 October 2011) (ver. 1.4.2, 14 May 2013) (ver. 1.2.2, 22 November 2012) (ver. 2.4.4, 10 August 2012) (ver. 2.2.4, 09 May 2012) (ver. 1.1.9, 03 January 2011) (ver.
2.0.1, 06 February 2011) (ver. 2.5.4, 01 July 2013) (ver. 2.1.2, 04 April 2011) (ver. 1.3.1, 30 July 2012) (ver. 2.2.2, 12 May 2012) (ver. 2.2.1, 06 February 2011) (ver.
2.2.2, 24 April 2011) (ver. 1.1.5, 14 March 2013) (ver. 2.3.6, 09 August 2013) (ver. 1.2.2, 15 October 2012) (ver.
1.0.1, 23 September 2011) (ver. 1.4.3, 04 December 2011) (ver.
2.4.6, 30 March 2012) (ver. 2.0.9, 26 January 2011) (ver.
1.4.4, 31 August 2012) (ver. 2.5.5, 18 September 2011) (ver. 1.4.7, 19 October 2011) (ver. 2.3.8, 27 July 2011) (ver. 2.1.4, 12 August 2012) (ver. 2.3.6, 07 November 2011) (ver. 1.5.8, 08 April 2011) (ver.
Great Quality Zx 5532
2.4.1, 20 April 2013) (ver. 2.0.6, 17 May 2012) (ver. 2.3.6, 29 November 2011) (ver. 1.1.7, 22 January 2011) (ver. 1.1.9, 19 August 2011) (ver.
2.1.5, 07 July 2012) (ver. 2.2.5, 02 October 2013) (ver. 2.3.3, 27 February 2013) (ver. 2.2.9, 19 January 2013) (ver. 1.1.2, 16 November 2011) (ver. 1.2.2, 23 April 2012) (ver. 1.5.9, 03 August 2012) (ver.
1.5.8, 05 November 2013) (ver. 2.5.6, 28 February 2012) (ver.
2.1.6, 01 September 2011) (ver. 1.5.2, 02 February 2013) (ver. 2.3.5, 09 December 2011) (ver. 1.5.4, 09 December 2011) (ver. 2.3.4, 26 January 2013) (ver.
1.5.8, 15 February 2013) (ver. 1.5.9, 13 August 2013) (ver. 1.4.1, 26 August 2012) (ver. 2.5.7, 29 November 2012) (ver. 2.1.7, 10 February 2012) (ver. 1.1.6, 04 November 2011) (ver. 1.3.9, 01 February 2012) (ver.
1.2.8, 06 November 2013) (ver. 1.0.5, 16 September 2012) (ver. 2.1.2, 30 October 2011) (ver. 1.4.6, 08 October 2013) (ver. 2.2.4, 05 September 2012) (ver. 2.0.8, 02 February 2012) (ver. 2.3.6, 20 January 2011) (ver.
2.0.4, 27 October 2013) (ver. 2.0.5, 12 November 2011) (ver. 2.2.6, 19 March 2013) (ver.
1.2.7, 30 November 2012) (ver. 2.5.9, 23 March 2011) (ver. 2.5.5, 07 September 2012) (ver. 1.3.6, 18 July 2013) (ver. 1.3.4, 19 September 2011) (ver.
1.4.8, 13 July 2012) (ver. 2.5.7, 10 May 2013) (ver. 2.3.7, 25 December 2011) (ver. 1.3.2, 13 December 2011) (ver. 2.2.3, 16 March 2012) (ver.
2.3.1, 24 August 2013) (ver. 1.4.8, 23 February 2011) (ver. 2.3.4, 25 June 2012) (ver.
1.0.4, 26 September 2012) (ver. 2.0.6, 17 July 2013) (ver. 1.5.1, 26 January 2012) (ver.
2.4.4, 02 July 2011) (ver. 1.3.3, 27 July 2012) (ver. 1.5.6, 03 December 2012) (ver. 1.0.4, 22 July 2011) (ver. 1.2.5, 05 April 2011) (ver. 1.2.9, 03 January 2012) (ver.
1.1.7, 09 July 2011) (ver. 2.2.6, 30 September 2013) (ver. 1.3.4, 26 May 2013) (ver. 2.4.8, 18 March 2011) (ver. 2.4.3, 12 January 2012) (ver. 1.5.8, 03 October 2013) (ver. 2.3.9, 09 March 2013) (ver.
1.4.3, 18 November 2012) (ver. 2.1.2, 07 October 2013) (ver. 2.5.8, 02 February 2013) (ver.
1.4.7, 06 October 2012) (ver. 2.5.5, 10 April 2013) (ver. 1.1.7, 29 February 2012) (ver. 2.3.1, 11 May 2013) (ver.
1.0.2, 15 February 2012) (ver. 1.0.1, 24 October 2013) (ver. 1.4.8, 16 November 2013) (ver.
1.0.5, 15 April 2011) (ver. 2.4.8, 14 January 2012) (ver. 2.3.7, 23 April 2013) (ver. 2.2.9, 22 May 2011) (ver.
2.0.3, 25 February 2013) (ver. 1.5.2, 13 December 2012) (ver. 2.0.1, 05 January 2012) (ver. 1.5.9, 31 March 2013) (ver. 1.1.8, 08 March 2013) (ver. 1.1.2, 19 May 2011) (ver. 1.1.3, 14 March 2011) (ver.
1.4.2, 13 October 2013) (ver. 2.2.4, 11 March 2011) (ver. 1.0.7, 28 December 2011) (ver. 2.4.9, 31 January 2012) (ver. 2.0.5, 29 September 2011) (ver.
2.2.8, 20 October 2012) (ver. 1.5.6, 23 May 2011) (ver. 1.0.9, 06 December 2011) (ver. 1.4.5, 17 December 2012) (ver. 1.4.1, 31 August 2013) (ver.
2.0.1, 08 September 2011) (ver. 1.0.4, 15 March 2013) (ver.
2.3.9, 03 July 2012) (ver. 2.1.8, 09 November 2012) (ver. 2.3.6, 24 March 2012) (ver. 2.4.2, 26 February 2012) (ver. 2.3.7, 09 June 2011) (ver.
1.4.8, 01 April 2012) (ver. 1.1.6, 18 July 2013) (ver. 1.3.5, 13 July 2011) (ver. 1.5.6, 15 October 2011) (ver.
2.2.1, 25 July 2011) (ver. 2.1.3, 05 May 2013) (ver. 2.3.2, 16 August 2013) (ver. 1.1.9, 27 June 2012) (ver.
2.2.4, 07 November 2011) (ver. 2.3.2, 16 May 2011) (ver.
2.3.5, 05 October 2011) (ver. 1.1.3, 11 March 2012) (ver. 1.5.2, 01 September 2012) (ver. 2.3.9, 15 May 2012) (ver. 2.3.2, 16 January 2012) (ver.
1.1.3, 23 January 2013) (ver. 1.1.2, 30 March 2011) (ver. 2.2.9, 06 September 2011) (ver. 1.5.4, 10 July 2011) (ver. 2.1.8, 09 August 2013) (ver. 2.5.6, 23 May 2011) (ver.
2.0.7, 21 October 2012) (ver. 2.1.5, 13 April 2012) (ver. 1.1.8, 16 November 2012) (ver. 1.5.6, 06 January 2012) (ver. 2.5.2, 31 October 2013) (ver. 1.0.7, 12 May 2011) (ver.
2.1.2, 06 September 2011) (ver. 2.0.8, 05 November 2013) (ver. 2.1.2, 13 June 2012) (ver. 2.0.8, 05 January 2011) (ver. 2.4.8, 16 September 2011) (ver. 2.4.7, 23 January 2013) (ver.
1.1.3, 24 January 2013) (ver. 1.5.2, 20 May 2013) (ver. 1.4.4, 21 March 2012) (ver. 2.3.7, 27 March 2013) (ver. 1.2.1, 09 April 2012) (ver.
2.3.8, 08 July 2012) (ver. 1.4.1, 17 August 2013) (ver.
2.5.3, 20 September 2012) (ver. 1.2.7, 07 July 2013) (ver. 1.3.4, 03 November 2012) (ver. 1.0.1, 25 November 2012) (ver. 1.4.3, 03 February 2012) (ver. 2.4.9, 27 May 2012) (ver. 2.5.8, 11 September 2011) (ver.
1.3.2, 12 June 2011) (ver. 1.0.6, 24 March 2012) (ver. 2.5.8, 15 April 2011) (ver. 2.5.9, 11 December 2011) (ver. 2.5.3, 16 February 2013) (ver.
1.4.8, 24 September 2013) (ver. 1.4.4, 17 January 2011) (ver.
2.4.3, 20 August 2012) (ver. 2.4.7, 01 November 2012) (ver. 1.4.1, 12 September 2013) (ver. 1.3.7, 14 August 2012) (ver.
2.4.5, 17 July 2011) (ver. 2.2.4, 23 March 2012) (ver.
2.1.2, 01 May 2012) (ver. 2.0.1, 04 October 2011) (ver. 1.5.4, 23 February 2011) (ver.
2.4.7, 13 August 2011) (ver. 2.2.4, 01 April 2013) (ver. 1.3.2, 13 March 2013) (ver.
1.1.7, 01 January 2013) (ver. 1.1.4, 08 June 2011) (ver.
1.5.8, 18 September 2011) (ver. 2.4.6, 04 August 2012) (ver.
1.5.5, 17 August 2012) (ver. 2.0.5, 09 May 2012) (ver.
2.1.2, 07 November 2012) (ver. 2.2.9, 15 January 2013) (ver. 2.4.1, 29 January 2012) (ver. 1.5.7, 29 August 2011) (ver. 2.5.3, 09 May 2011) (ver.
2.3.5, 01 February 2011) (ver. 2.0.5, 25 January 2013) (ver. 2.4.2, 21 April 2013) (ver.
2.4.7, 21 April 2012) (ver. 1.0.2, 27 July 2011) (ver. 1.1.9, 24 February 2013) (ver.
2.2.3, 27 October 2011) (ver. 2.0.5, 07 June 2012) (ver. 2.4.3, 15 January 2011) (ver.
1.5.1, 05 March 2013) (ver. 2.3.3, 09 March 2012) (ver. 1.2.1, 07 September 2013) (ver. 2.3.6, 03 January 2012) (ver. 1.1.3, 17 September 2013) (ver. 2.5.7, 11 September 2012) (ver.
1.5.4, 19 July 2013) (ver. 2.4.3, 31 October 2011) (ver. 2.1.6, 30 June 2012) (ver. 2.3.4, 09 November 2011) (ver. 2.5.8, 02 May 2013) (ver. 1.5.1, 02 September 2011) (ver.
1.3.2, 08 October 2011) (ver. 2.2.8, 23 July 2012) (ver. 1.5.6, 04 May 2012) (ver. 2.2.6, 24 January 2013) (ver. 1.1.9, 29 April 2012) (ver. 1.0.6, 04 June 2012) (ver. 1.3.5, 19 March 2011) (ver.
2.0.2, 03 May 2012) (ver. 1.3.8, 23 December 2012) (ver. 1.3.7, 28 October 2011) (ver. 2.4.2, 02 March 2012) (ver.
1.2.3, 08 July 2013) (ver. 1.1.2, 21 April 2012) (ver. 2.5.5, 06 November 2011) (ver. 1.4.9, 27 February 2013) (ver. 2.4.7, 21 January 2012) (ver.
2.0.9, 04 August 2011) (ver. 2.4.3, 21 June 2011) (ver. 1.4.4, 23 September 2012) (ver. 2.4.8, 19 September 2012) (ver.
2.1.9, 29 April 2013) (ver. 1.4.1, 17 April 2011) (ver. 2.5.6, 27 February 2011) (ver. 1.5.8, 15 March 2012) (ver.
2.3.8, 20 September 2012) (ver. 1.2.1, 17 June 2013) (ver. 2.3.1, 01 April 2013) (ver. 1.0.3, 26 August 2011) (ver. 1.4.3, 19 November 2011) (ver.
1.4.3, 04 February 2012) (ver. 1.3.7, 22 May 2013) (ver. 2.1.1, 30 December 2012) (ver. 1.5.2, 25 April 2013) (ver. 2.2.4, 06 March 2012) (ver.
Great Quality Zx-5580
1.4.4, 05 August 2013) (ver. 1.1.6, 29 October 2013) (ver. 1.1.8, 06 December 2012) (ver. 1.0.8, 14 July 2011) (ver. 1.4.2, 10 July 2011) (ver. 2.0.7, 02 February 2013) (ver.
2.4.6, 16 October 2012) (ver. 1.4.5, 08 September 2013) (ver. 1.0.3, 16 July 2012) (ver. 2.4.1, 02 September 2013) (ver. 2.2.1, 18 October 2011) (ver. 2.4.6, 04 March 2011) (ver. 1.4.4, 04 December 2011) (ver.
1.1.3, 06 May 2013) (ver. 1.2.9, 10 June 2013) (ver. 2.3.6, 26 August 2011) (ver. 1.0.3, 12 March 2011) (ver.
1.3.5, 10 September 2012) (ver. 2.4.3, 09 June 2013) (ver. 1.2.2, 21 January 2013) (ver. 2.4.4, 01 April 2011) (ver. 1.2.7, 20 November 2013) (ver.
2.5.5, 11 November 2011) (ver. 1.5.1, 16 July 2011) (ver. 1.3.2, 01 May 2013) (ver. 1.2.6, 25 August 2012) (ver.
2.3.8, 17 July 2013) (ver. 2.5.5, 03 January 2012) (ver. 2.5.5, 13 November 2012) (ver. 2.0.1, 06 September 2013) (ver.
1.3.7, 21 June 2013) (ver. 2.2.6, 15 August 2013) (ver. 1.3.2, 24 April 2011) (ver.
2.1.5, 09 January 2012) (ver. 2.3.8, 21 April 2011) (ver. 1.2.1, 18 November 2012) (ver. 2.1.8, 27 October 2013) (ver.
2.3.9, 11 February 2011) (ver. 1.5.8, 23 March 2013) (ver. 1.0.2, 17 June 2013) (ver. 1.3.8, 27 March 2013) (ver. 1.5.8, 11 February 2013) (ver. 1.2.7, 16 June 2011) (ver.
1.2.5, 20 December 2011) (ver. 2.0.5, 11 November 2012) (ver. 2.1.8, 01 February 2011) (ver. 2.3.5, 02 December 2011) (ver. 1.0.4, 31 July 2011) (ver. 1.0.3, 15 July 2011) (ver. 1.0.2, 16 September 2011) (ver.
1.3.4, 23 November 2011) (ver. 1.3.7, 28 March 2013) (ver. 1.1.8, 24 May 2013) (ver.
2.2.2, 01 May 2013) (ver. 1.0.1, 20 January 2011) (ver. 2.5.3, 16 September 2012) (ver.
2.5.9, 06 December 2011) (ver. 2.0.1, 22 August 2012) (ver. 1.0.9, 07 May 2012) (ver.
2.1.1, 25 February 2012) (ver. 2.1.4, 02 April 2011) (ver. 2.1.3, 05 July 2013) (ver. 2.4.9, 22 June 2013) (ver. 2.2.2, 18 April 2011) (ver. 1.2.2, 09 July 2011) (ver.
2.3.1, 19 October 2013) (ver. 2.0.6, 26 January 2012) (ver. 2.5.7, 30 October 2011) (ver. 2.3.9, 25 September 2013) (ver. 1.4.8, 06 September 2011) (ver. 1.1.2, 20 May 2011) (ver.
1.4.8, 08 August 2013) (ver. 1.3.1, 30 August 2011) (ver. 2.2.4, 31 March 2013) (ver. 1.2.6, 14 March 2013) (ver.
2.2.8, 23 August 2013) (ver. 1.3.1, 03 November 2011) (ver. 2.2.7, 18 November 2012) (ver. 2.0.2, 30 July 2013) (ver. 1.3.3, 24 June 2012) (ver. 1.5.5, 13 October 2012) (ver. 1.4.6, 12 March 2013) (ver.
1.0.6, 14 July 2013) (ver. 1.2.4, 27 July 2011) (ver.
1.2.8, 26 January 2012) (ver. 1.5.7, 15 February 2011) (ver. 2.1.5, 07 September 2011) (ver. 2.0.1, 21 June 2011) (ver. 1.0.9, 26 May 2012) (ver. 2.1.6, 05 January 2013) (ver.
2.5.1, 04 May 2013) (ver. 2.1.2, 03 June 2012) (ver. 1.0.6, 30 April 2011) (ver. 2.1.5, 13 June 2011) (ver.
1.3.6, 12 June 2012) (ver. 1.0.3, 01 April 2013) (ver. 2.2.7, 09 October 2011) (ver. 2.4.8, 25 January 2012) (ver.
2.5.3, 19 April 2012) (ver. 1.5.4, 07 September 2012) (ver. 1.4.5, 26 December 2011) (ver. 2.4.1, 09 June 2011) (ver. 1.2.5, 19 May 2011) (ver.
2.3.4, 18 February 2013) (ver. 1.1.7, 15 June 2011) (ver. 2.2.2, 21 July 2011) (ver.
2.4.7, 21 January 2011) (ver. 2.4.8, 20 March 2013) (ver. 2.3.9, 26 April 2011) (ver.
1.2.4, 08 July 2011) (ver. 2.0.2, 13 February 2013) (ver. 2.3.7, 01 July 2013) (ver.
1.4.1, 18 August 2011) (ver. 1.0.1, 26 September 2012) (ver. 2.4.8, 28 March 2011) (ver.
1.0.5, 28 May 2011) (ver. 2.1.3, 10 April 2013) (ver. 2.0.7, 26 January 2012) (ver. 2.5.8, 12 January 2011) (ver. 1.2.4, 23 January 2012) (ver. 2.0.5, 03 August 2011) (ver.
1.4.8, 10 September 2013) (ver. 1.3.4, 16 February 2013) (ver. 1.0.1, 24 July 2012) (ver. 1.4.3, 18 June 2013) (ver. 2.0.4, 25 October 2013) (ver. 1.1.8, 16 August 2012) (ver. 2.4.2, 17 August 2012) (ver.
2.1.2, 08 July 2011) (ver. 1.2.3, 31 December 2012) (ver. 2.2.4, 09 July 2012) (ver. 2.3.5, 26 April 2013) (ver.
1.3.9, 05 August 2012) (ver. 2.5.4, 18 April 2012) (ver. 2.5.6, 30 April 2011) (ver.
1.2.2, 19 October 2012) (ver. 1.4.3, 10 May 2013) (ver. 2.5.7, 17 April 2011) (ver.
1.2.4, 28 July 2011) (ver. 1.2.7, 19 March 2011) (ver. 1.1.7, 09 February 2011) (ver. 1.3.2, 26 July 2013) (ver. 1.1.1, 16 March 2011) (ver.
1.1.9, 12 November 2013) (ver. 2.3.8, 08 January 2011) (ver. 1.1.3, 04 September 2013) (ver. 2.5.7, 27 May 2013) (ver.
2.4.4, 06 August 2011) (ver. 2.3.4, 30 March 2012) (ver.
2.3.7, 19 March 2011) (ver. 2.1.4, 21 July 2013) (ver. 2.5.8, 10 December 2012) (ver.
1.0.2, 11 August 2013) (ver. 2.4.3, 14 September 2012) (ver. 2.0.8, 14 February 2012) (ver. 1.3.7, 06 November 2013) (ver.
2.2.2, 20 January 2012) (ver. 2.1.8, 07 August 2011) (ver. 2.4.8, 04 August 2011) (ver. 2.4.3, 14 June 2011) (ver. 2.2.8, 23 March 2011) (ver.
1.3.8, 19 January 2012) (ver. 2.3.7, 21 July 2013) (ver. 1.3.9, 09 September 2012) (ver. 1.0.1, 08 February 2012) (ver. 2.1.3, 12 July 2011) (ver.
2.4.9, 01 March 2011) (ver. 2.3.8, 07 April 2013) (ver. 1.4.8, 06 June 2013) (ver. 1.1.1, 10 September 2013) (ver. 2.3.6, 12 June 2011) (ver. 2.2.8, 05 August 2013) (ver.
1.5.6, 10 March 2012) (ver. 1.1.7, 15 April 2011) (ver. 1.4.4, 21 July 2013) (ver. 2.2.8, 10 November 2011) (ver. 2.4.5, 17 October 2012) (ver. 2.5.3, 23 November 2013) (ver.
2.1.2, 14 April 2013) (ver. 1.5.8, 24 April 2011) (ver. 1.0.8, 17 July 2011) (ver. 2.0.5, 14 December 2011) (ver. 1.4.4, 10 February 2012) (ver. 1.0.3, 21 August 2011) (ver. 1.2.9, 25 November 2011) (ver.
2.2.2, 03 May 2011) (ver. 1.3.9, 11 May 2011) (ver. 1.4.5, 25 January 2012) (ver. 1.4.9, 19 September 2012) (ver. 1.2.5, 20 June 2011) (ver. 1.2.5, 08 May 2011) (ver.
2.2.1, 11 September 2011) (ver. 2.3.1, 20 March 2013) (ver. 1.3.3, 31 January 2011) (ver. 1.3.7, 08 April 2011) (ver. 1.1.7, 14 August 2013) (ver. 1.3.1, 10 September 2013) (ver.
1.4.8, 29 March 2012) (ver. 1.0.3, 25 August 2013) (ver. 2.0.9, 15 September 2012) (ver.
2.5.5, 07 March 2013) (ver. 1.1.9, 15 January 2012) (ver.
2.4.2, 07 June 2013) (ver. 1.3.5, 22 March 2011) (ver. 2.0.7, 07 February 2012) (ver. 2.2.9, 20 August 2012) (ver. 1.3.4, 18 July 2013) (ver. 1.5.9, 25 July 2012) (ver. 1.0.2, 28 October 2012) (ver.
1.4.6, 09 November 2012) (ver. 1.0.9, 19 October 2013) (ver. 1.2.1, 05 January 2011) (ver. 1.2.9, 14 April 2013) (ver. 2.4.2, 02 April 2013) (ver.
2.5.6, 20 September 2011) (ver. 2.1.8, 29 February 2012) (ver.
1.2.9, 05 August 2013) (ver. 1.4.3, 26 October 2011) (ver.
1.3.3, 31 May 2011) (ver. 2.5.8, 19 February 2011) (ver. 2.4.1, 02 July 2012) (ver. 2.2.3, 14 October 2013) (ver. 1.3.9, 22 August 2013) (ver. 2.4.3, 16 June 2013) (ver. 1.0.1, 22 March 2011) (ver.
1.3.2, 30 September 2011) (ver. 1.4.1, 06 January 2013) (ver. 1.0.6, 18 April 2013) (ver. 1.1.8, 07 January 2011) (ver. 1.0.2, 09 November 2011) (ver.
2.2.5, 08 July 2013) (ver. 1.3.2, 07 January 2011) (ver. 1.2.2, 10 December 2011) (ver.
2.4.2, 18 November 2013) (ver. 2.2.2, 12 January 2011) (ver. 2.1.5, 28 June 2013) (ver. 1.2.2, 04 June 2013) (ver. 1.5.9, 22 February 2012) (ver.
1.1.1, 13 March 2012) (ver. 2.2.6, 23 February 2013) (ver.
1.1.2, 27 June 2012) (ver. 2.0.8, 13 January 2013) (ver.
2.1.6, 29 October 2011) (ver. 2.4.1, 26 November 2012) (ver. 1.1.9, 02 June 2012) (ver.
2.0.9, 16 April 2013) (ver. 2.2.2, 06 August 2012) (ver. 2.2.9, 30 January 2013) (ver. 2.2.6, 08 January 2013) (ver. 1.0.4, 17 October 2013) (ver. 2.0.4, 02 April 2013) (ver.
2.4.5, 24 January 2011) (ver. 1.4.8, 30 August 2013) (ver. 1.3.6, 30 May 2011) (ver.
1.1.3, 18 September 2013) (ver. 2.0.3, 21 February 2012) (ver. 1.3.2, 23 May 2013) (ver. 1.3.6, 28 July 2013) (ver.
2.5.6, 26 November 2013) (ver. 2.5.5, 26 November 2013) (ver.
1.1.1, 01 August 2011) (ver. 2.0.6, 22 November 2011) (ver. 2.1.4, 19 March 2013) (ver. 2.2.4, 20 September 2012) (ver. 2.0.6, 15 August 2012) (ver. 2.4.5, 07 October 2012) (ver.
1.0.2, 20 September 2013) (ver. 2.5.7, 06 April 2012) (ver. 2.1.4, 29 March 2011) (ver.
1.3.8, 06 April 2013) (ver. 2.3.5, 08 October 2012) (ver.
2.1.9, 27 February 2012) (ver. 1.0.1, 10 January 2011) (ver. 1.4.3, 15 May 2013) (ver. 1.3.6, 08 July 2013) (ver. 1.0.3, 28 May 2012) (ver.
1.1.2, 17 February 2011) (ver. 1.4.6, 18 January 2012) (ver. 2.1.5, 19 June 2013) (ver. 2.2.5, 05 March 2013) (ver. 2.0.7, 27 August 2011) (ver. 1.2.8, 30 September 2012) (ver.
2.2.4, 05 August 2011) (ver. 1.2.1, 12 June 2012) (ver. 1.2.3, 25 February 2011) (ver. 1.3.3, 28 January 2011) (ver. 2.2.5, 27 August 2011) (ver.
1.3.8, 23 April 2011) (ver. 2.4.5, 01 October 2012) (ver. 1.4.8, 29 October 2012) (ver. 2.5.6, 28 July 2012) (ver. 2.3.2, 31 August 2011) (ver. 2.1.5, 12 May 2013) (ver.
2.4.6, 15 July 2013) (ver. 2.3.3, 14 December 2011) (ver. 2.0.2, 22 November 2012) (ver.
1.0.2, 11 February 2012) (ver. 1.3.6, 10 January 2013) (ver. 2.5.1, 17 April 2011) (ver. 1.1.4, 21 August 2013) (ver.
2.5.7, 17 November 2012) (ver. 1.4.7, 27 December 2012) (ver. 1.4.9, 22 May 2012) (ver.
1.2.3, 06 February 2012) (ver. 2.0.3, 13 July 2012) (ver. 2.3.9, 02 April 2011) (ver. 2.4.1, 02 November 2012) (ver. 2.2.9, 20 May 2012) (ver. 1.3.2, 06 April 2011) (ver.
2.1.2, 01 February 2011).
I have a Jetway K8M8MSR2 motherboard. It has 6 total USB ports on the rear, none on front.
4 ports are on-board, whilst 2 ports are on a separate mounting connected to a motherboard header. The computer is connected to a IOGEAR GCMP1764 4-computer KVM. It has a keyboard, mouse and a EPSON R300 printer connected to its USB's. This is what Device Manager displays: UNIVERSAL SERIAL BUS CONTROLLERS GENERIC USB HUB USB COMPOSITE DEVICE USB COMPOSITE DEVICE USB MASS STORAGE DEVICE USB PRINTING SUPPORT USB ROOT HUB USB ROOT HUB USB ROOT HUB USB ROOT HUB USB ROOT HUB VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA USB 2.0 ENHANCED HOST CONTROLLER I understand which entry signifies that I have USB2, although I do not know if all USB ports are USB2.
I fail to comprehend how I have five 'USB ROOT HUB' entries - I think I should have six. Interestingly, when I turned off the Epson R300 printer, these entries disappeared: USB COMPOSITE DEVICE USB MASS STORAGE DEVICE USB PRINTING SUPPORT How is it that a printer is 'mass storage'? What is the other 'USB COMPOSITE DEVICE'? What is the 'GENERIC USB HUB'? Are the four 'VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER' entries for the four on-board USB's? Why them and not the other two?
Thank you George. Paul wrote: Is there any way to FORCE the computer to use the usb 2.0 enhanced host controller? I've got a Fry's Great Quality ZX-5360 laptop. Has the VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER I don't have the recovery disks. Fry's can't support it. ECS can't support it.
VIA drivers don't help. I've even tried several other related drivers with no success.
I get no ENHANCED in the device manager list. No usb 2.0 speed.
'this device can perform faster' dialog when plugging in a 2.0 device. I have not reloaded XP because there's licensed software on it that I don't want to lose. Is there any way to FORCE the computer to use the high speed drivers?
Thanks, mike. Paul wrote: Is there any way to FORCE the computer to use the usb 2.0 enhanced host controller? I've got a Fry's Great Quality ZX-5360 laptop. Has the VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER I don't have the recovery disks. Fry's can't support it. ECS can't support it.
VIA drivers don't help. I've even tried several other related drivers with no success. I get no ENHANCED in the device manager list. No usb 2.0 speed. 'this device can perform faster' dialog when plugging in a 2.0 device. I have not reloaded XP because there's licensed software on it that I don't want to lose.
Is there any way to FORCE the computer to use the high speed drivers? Thanks, mike. Paul wrote: Is there any way to FORCE the computer to use the usb 2.0 enhanced host controller? I've got a Fry's Great Quality ZX-5360 laptop. Has the VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER I don't have the recovery disks. Fry's can't support it. ECS can't support it.
VIA drivers don't help. I've even tried several other related drivers with no success. I get no ENHANCED in the device manager list. No usb 2.0 speed.
'this device can perform faster' dialog when plugging in a 2.0 device. I have not reloaded XP because there's licensed software on it that I don't want to lose. Is there any way to FORCE the computer to use the high speed drivers? Thanks, mike. Click to expand.Also, you can test with an alternate OS, to verify whether the hardware is visible or not.
I use Knoppix (knopper.net), a Linux LiveCD, for doing maintenance. If you boot such a CD, then use dmesg, lsusb, lspci you can get info on what hardware is detected on the motherboard. That would be a way of seeing whether USB2 was available in Linux. If Linux detected USB2, then you'd know it was more of a software problem on Windows. If you get VEN and DEV info, from things like those Linux commands, you can look up the codes here. In the first of those files, I can see. 1106 VIA Technologies, Inc.
3104 USB 2.0 That is how you map from some numbers you may have found, to what device they may have come from. The numbers in this case are hex. Device Manager also has those numbers. In WinXP, they added 'Details' as a tab in the device entry, and if you select 'Hardware Ids' from the pulldown menu, you can see the numbers for a device. For example, a VIA Rev 5 (USB 1.1) block would be Vendor 1106 and Device 3038. Paul wrote: Is there any way to FORCE the computer to use the usb 2.0 enhanced host controller? I've got a Fry's Great Quality ZX-5360 laptop.
Has the VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER I don't have the recovery disks. Fry's can't support it. ECS can't support it. VIA drivers don't help.
I've even tried several other related drivers with no success. I get no ENHANCED in the device manager list. No usb 2.0 speed. 'this device can perform faster' dialog when plugging in a 2.0 device. I have not reloaded XP because there's licensed software on it that I don't want to lose. Is there any way to FORCE the computer to use the high speed drivers? Thanks, mike.
Click to expand.Thanks, Device manager says the usb port is vendor 1106 device 3038 which is listed as a usb1.1 controller. But the computer spec swears that the ports are usb2.0. There's even a FAQ entry on the Fry's site that confirms that the ports are USB2.0 but you have to set the USB mode in the bios to Auto, which I have done. Tried all possible usb settings in the bios. The obvious conclusion is that Fry's lied about the spec. I can't make Knoppix run on this system. It doesn't like the display and I'm too inexperienced to know why.
But Puppy Linux runs. When I plug in a usb2 flash drive, dmesg says 'new usb full speed device detected'. Puppy doesn't have lsusb. Thanks, mike. Thanks, Device manager says the usb port is vendor 1106 device 3038 which is listed as a usb1.1 controller. But the computer spec swears that the ports are usb2.0.
There's even a FAQ entry on the Fry's site that confirms that the ports are USB2.0 but you have to set the USB mode in the bios to Auto, which I have done. Tried all possible usb settings in the bios. The obvious conclusion is that Fry's lied about the spec. I can't make Knoppix run on this system.
It doesn't like the display and I'm too inexperienced to know why. But Puppy Linux runs. When I plug in a usb2 flash drive, dmesg says 'new usb full speed device detected'.
Puppy doesn't have lsusb. Thanks, mike. Click to expand.In your first post, you claimed Device Manager had VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA REV 5 OR LATER USB UNIVERSAL HOST CONTROLLER VIA USB 2.0 ENHANCED HOST CONTROLLER The last entry, means all ports should have USB 2.0 capability. If you check details on that last entry, is the device working? These are things to check 1) BIOS setting.
And since you have an 'Enhanced' entry, we know that is OK. 2) Properly installed USB stack. That is harder to check. If you check the 'setupapi.log' file, you may see pci ven1106&dev3104 being installed somewhere in that file. Usually there are two entries next to one another, as it looks to me like the driver installation happens in two stages. If you see installations happening on different dates, that could happen if you 'reset' the USB stack. Doing a 'reset' of the stack is detailed here.
By removing the entries in Safe Mode, the idea is, that Windows will reinstall the drivers for USB on the next regular boot. 3) USB2 undoubtedly works at the motherboard level. But any custom cable assemblies with USB connectors at the end, or even external hubs or KVMs or the like, may not have USB2 compatible components. Some wiring assemblies have filter components, which prevent USB2 from working properly. I have a couple Antec computer cases, for example, where the front ports won't run at USB2 rates (even though the motherboard does run at USB2). If the hardware attempts it, all the hardware will see, is CRC errors on the USB packets.
So it would switch back to USB 1.1. I'd probably agree with calling Fry some bad names, if it weren't for the fact you have one of these in Device Manager. This tells me your problem is fixable. They could be totally inept, and install filtering components on the computer, which prevent proper USB2 signal transmission, but what are the odds of that happening? I mean, if they managed to make the computer work, then they'll also manage to route the USB signals properly on the motherboard. The motherboard design has a lot of controlled impedance tracks, and there are lots of other things they could screw up, which would have caused the computer to crash.
VIA USB 2.0 ENHANCED HOST CONTROLLER HTH, Paul. 2) Properly installed USB stack.
That is harder to check. If you check the 'setupapi.log' file, you may see pci ven1106&dev3104 being installed somewhere in that file. Usually there are two entries next to one another, as it looks to me like the driver installation happens in two stages. If you see installations happening on different dates, that could happen if you 'reset' the USB stack.
Doing a 'reset' of the stack is detailed here. By removing the entries in Safe Mode, the idea is, that Windows will reinstall the drivers for USB on the next regular boot. 3) USB2 undoubtedly works at the motherboard level. But any custom cable assemblies with USB connectors at the end, or even external hubs or KVMs or the like, may not have USB2 compatible components.
Some wiring assemblies have filter components, which prevent USB2 from working properly. I have a couple Antec computer cases, for example, where the front ports won't run at USB2 rates (even though the motherboard does run at USB2).
If the hardware attempts it, all the hardware will see, is CRC errors on the USB packets. So it would switch back to USB 1.1. Click to expand. Do programs like Everest actually interrogate the hardware?
Or do they just ask the OS what it installed? I downloaded the Everest trial and will install it. I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge. Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Click to expand.
Do programs like Everest actually interrogate the hardware? Or do they just ask the OS what it installed? I downloaded the Everest trial and will install it. I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge. Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Click to expand.
Do programs like Everest actually interrogate the hardware? Or do they just ask the OS what it installed? I downloaded the Everest trial and will install it.
I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge. Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Paul wrote: spamme0 wrote: Nope, I don't.that was George's system.
OK, so start with a hardware inventory of your ZX-5360. What chipset does it use? What does Everest tell you?. OK, I can see your system here. VIA K8N800+VT8235M-CE 4- USB 2.0 ports would be on VT8235M-CE Check with Everest, and see if it agrees. HTH, Paul Do programs like Everest actually interrogate the hardware? Or do they just ask the OS what it installed?
I downloaded the Everest trial and will install it. I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge. Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Click to expand.There is no point deleting the USB stack just yet. I believe you should be able to see 'pci ven1106&dev3104', the identity of the USB2, in Everest, even before a driver is installed.
There would not be much point in trying to install it, unless it claims to be present. This is the Everest I use (it is old, but for newer hardware which isn't identified, I can still use the ven/dev info). For example, on my VIA chipset, if I look in Devices CI Devices, I can see the VIA USB 2.0 Enhanced Host Controller, with Device ID 1106-3104. If I saw that, then I'd know that efforts to install it could succeed. If the device is still not listed, then the problem (as described by Fry's), is still in the BIOS.
Also, have a look in 'setupapi.log' file, and search for '3104'. See if at any point, the OS has attempted to deal with that hardware. Maybe a partial explanation is already in setupapi.log. Spamme0 wrote: Paul wrote: spamme0 wrote: Nope, I don't.that was George's system.
OK, so start with a hardware inventory of your ZX-5360. What chipset does it use? What does Everest tell you?. OK, I can see your system here.
VIA K8N800+VT8235M-CE 4- USB 2.0 ports would be on VT8235M-CE Check with Everest, and see if it agrees. HTH, Paul Do programs like Everest actually interrogate the hardware? Or do they just ask the OS what it installed? I downloaded the Everest trial and will install it. I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge.
Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Mike I was not able to find a specific product page for VT8235M-CE.
Great Quality Zx 5580 Drivers
What I did do, is check the specs for a few other things that use VT8235M-CE, and they claim to have 4 USB2 ports as well. OK, I went back to the Fry's site, and they've already answered this question Have a look.
'please make sure the “Legacy USB support” option in the bios advance setup is set to AUTO'. Click to expand.There is no point deleting the USB stack just yet. I believe you should be able to see 'pci ven1106&dev3104', the identity of the USB2, in Everest, even before a driver is installed. There would not be much point in trying to install it, unless it claims to be present.
This is the Everest I use (it is old, but for newer hardware which isn't identified, I can still use the ven/dev info). For example, on my VIA chipset, if I look in Devices CI Devices, I can see the VIA USB 2.0 Enhanced Host Controller, with Device ID 1106-3104.
If I saw that, then I'd know that efforts to install it could succeed. If the device is still not listed, then the problem (as described by Fry's), is still in the BIOS. Also, have a look in 'setupapi.log' file, and search for '3104'. See if at any point, the OS has attempted to deal with that hardware.
Maybe a partial explanation is already in setupapi.log. Click to expand.Ok, I blew away windows and did a fresh install of XPHomeSP3. I installed everest 220. It gives me more detail of the same info. The USB Controller is pci/ven1106&dev3038&SUBSYS0F601019&REV80 PCI Devidce is VIA VT83C572 PCI-USB Controller IRQ is 21 There are three instances of USB host controller sharing INT21.
Nothing else. Port is E400-E41F The chipset now shows as VIA K8M800/K8N800 Chipset Still no mention of 'enhanced' in device manager.
Still get 'this device can perform faster.' When inserting my flash drive. I searched setupapi.log for 3104. I get many instances of 3038 in the usb section. Searching for 'enhanced' gets two hits in the keyboard section. No hits on 'ehci'.
Your comments suggest that the device ID's are read from the bios and not the chips themselves??? That gets me back to my very first question. Is there any way to override that info and FORCE windows to use the enhanced driver? I've already blown away the OS. As long as I don't actually write anything to CMOS, I've got nothing to lose.
I guess I should mention that I did find a BIOS update for the ECS-536. I'm afraid to apply it lest I brick the Fry's variant 536S. I'd rather have a working computer with USB1.1. If the Fry's machine shipped with USB2.0, the existing BIOS should at least load the right drivers.
I tried to edit the hardware ID strings in regedit, but it won't let me. Probably just as well;-) Color me frustrated. I also feel like I'm wasting a bunch of your time.
I appreciate the effort. Any other ideas? Thanks, mike. Paul wrote: spamme0 wrote: Paul wrote: spamme0 wrote: Nope, I don't.that was George's system.
OK, so start with a hardware inventory of your ZX-5360. What chipset does it use? What does Everest tell you?. OK, I can see your system here. VIA K8N800+VT8235M-CE 4- USB 2.0 ports would be on VT8235M-CE Check with Everest, and see if it agrees.
HTH, Paul Do programs like Everest actually interrogate the hardware? Or do they just ask the OS what it installed? I downloaded the Everest trial and will install it. I've been using SIW and PC Wizard SIW gives me these answers: Under USB ports it finds Via Rev 5 or greater 1106/3038 Under hardware info, it says it's a K8M400 CPU to PCI bridge and VT8235 PCI to ISA bridge.
Under PCI, it claims to have a VT82xxxxx UHCI USB 1.1 Controller (All VIA chipsets) Fry's and SIW disagree over what USB support is provided. Mike I was not able to find a specific product page for VT8235M-CE. What I did do, is check the specs for a few other things that use VT8235M-CE, and they claim to have 4 USB2 ports as well. OK, I went back to the Fry's site, and they've already answered this question Have a look. 'please make sure the “Legacy USB support” option in the bios advance setup is set to AUTO' Yes, that was the first thing I tried. I previously said that I'd tried that more than once. Tried on/off/auto nothing works.
Still haven't had a chance to retry deleting drivers in safe mode. I'll get on it. I'm wondering if I might have to set the legacy support to auto mode BEFORE windows gets installed. PITA to try it, but I don't have a better idea. Mike HTH, Paul. Click to expand.There is no point deleting the USB stack just yet.
I believe you should be able to see 'pci ven1106&dev3104', the identity of the USB2, in Everest, even before a driver is installed. There would not be much point in trying to install it, unless it claims to be present.
This is the Everest I use (it is old, but for newer hardware which isn't identified, I can still use the ven/dev info). For example, on my VIA chipset, if I look in Devices CI Devices, I can see the VIA USB 2.0 Enhanced Host Controller, with Device ID 1106-3104. If I saw that, then I'd know that efforts to install it could succeed. If the device is still not listed, then the problem (as described by Fry's), is still in the BIOS. Also, have a look in 'setupapi.log' file, and search for '3104'. See if at any point, the OS has attempted to deal with that hardware.
Maybe a partial explanation is already in setupapi.log. Click to expand.Ok, I blew away windows and did a fresh install of XPHomeSP3.
I installed everest 220. It gives me more detail of the same info. The USB Controller is pci/ven1106&dev3038&SUBSYS0F601019&REV80 PCI Devidce is VIA VT83C572 PCI-USB Controller IRQ is 21 There are three instances of USB host controller sharing INT21. Nothing else. Port is E400-E41F The chipset now shows as VIA K8M800/K8N800 Chipset Still no mention of 'enhanced' in device manager. Still get 'this device can perform faster.'
When inserting my flash drive. I searched setupapi.log for 3104. I get many instances of 3038 in the usb section. Searching for 'enhanced' gets two hits in the keyboard section. No hits on 'ehci'.
Your comments suggest that the device ID's are read from the bios and not the chips themselves??? That gets me back to my very first question. Is there any way to override that info and FORCE windows to use the enhanced driver? I've already blown away the OS. As long as I don't actually write anything to CMOS, I've got nothing to lose. I guess I should mention that I did find a BIOS update for the ECS-536.
I'm afraid to apply it lest I brick the Fry's variant 536S. I'd rather have a working computer with USB1.1.
If the Fry's machine shipped with USB2.0, the existing BIOS should at least load the right drivers. I tried to edit the hardware ID strings in regedit, but it won't let me. Probably just as well;-) Color me frustrated. I also feel like I'm wasting a bunch of your time.
I appreciate the effort. Any other ideas? Thanks, mike.
Click to expand.Enumerations are read directly from the hardware. Or at least I hope they are, because it would be pretty useless if Everest was just mining WinXP for info.
In the lab, on embedded computers, our startup code probes each PCI slot address, and says 'anybody home?' If a device responds, and further probes in the config space, extract information, then you know there is a device present. A methodical probing, checking everywhere, ensures that everything that can be detected, is detected.
A number of hardware buses support that kind of probing. Some bus standards provide less info than others (which makes it a bit harder to be sure what is sitting on the bus - an example is the kind of thing Speedfan does, when it looks for fan controllers - the enumeration recipe is rather complicated). Your evidence suggests, the Fry's BIOS is leaving USB2 disabled.
Hardware devices may have a mechanism, where the BIOS can set a bit in the registers of the device, to prevent it from responding to later probes. The Fry's BIOS could be doing that.
And that could be why the '3104' is not responding. Having the BIOS fiddle with the controls, is not absolute. For example, on my motherboard, I can disable the IDE devices in the BIOS (in an attempt to make my hard drive invisible), and Linux can still find the disk drives. So Linux could turn the interfaces back on again, which I didn't want.
In the case of the Windows ATI video driver, the ATI software is able to change AGP settings on the fly (so attempts to set the BIOS to AGP 4X, could be met by the ATI driver setting the AGP slot to AGP 8X). It is not, like what the BIOS is doing, is absolute. If that bit is flipped later, and the hardware rescanned, the hardware could then be discovered. My conclusion at this point, is the BIOS is to blame. I don't see this as a hardware problem as such. There are other methods, for the BIOS to pass info about hardware, to the operating system.
For example, for 'standard' hardware devices, the BIOS passes 'ACPI objects' via ACPI data tables. At least some of the Everest entries you see, will be of that type. Your USB entries however, are sitting on the bus (sort of a PCI bus, but internal to the chipset), and they should be detectable via bus probes that return four instances of 1106-3038 and one instance of 1106-3104. The fact that the 1106-3038 is fully working, suggests the problem is that 1106-3104 is turned off by the BIOS. Is there a tool to fix this?
Yes, there is. A number of years ago, people used WPCREDIT by H.Oda, to change the registers in their chipset. You need someone to map out the chipset for you, and tell you.exactly. which byte to change. Changing any adjacent bytes, can cause the computer to crash instantly.
So there is a tool - but it is a lot like playing with dynamite in a dark room. You would flip a bit to turn on USB2, then rescan in Device Manager and see if new hardware was detected. That would be the basic method.
Example of hacking with WPCREDIT, back in the day. (There is a companion tool called WPCRSET, to apply the changes each time the OS starts up. It is mentioned in this article.
This isn't important right now, because you're not likely to get a PCR file with register definitions to make editing in WPCREDIT easy.) Modern OSes make this kind of hacking more difficult, by requiring something to punch through 'Ring 0' protection, so you can edit the hardware values. As a consequence, I wouldn't want to guess as to which OSes WPCREDIT currently works with. If the program is prepared for this possibility, it may have a copy of 'giveio' or the like, to allow the program to edit hardware.
Normally, software programs don't control hardware directly, they go through restrictive drivers. The only danger from spontaneously crashing your OS, is the possibility that the file system will be corrupted. As long as you have a good backup plan, or recovery media, then you should be good-to-go.
For example, if you somehow wiped out the partition table on the hard drive, you'd want a restoration method, which can put every byte of the hard drive, back in place. The level of danger, depends on the reliability of the chip register map you've got to work with. Intel makes this simple, as Intel offers datasheets, so you can do all the work yourself. Companies like VIA, don't give out datasheets to just anyone. You need a business card, and a pesky salesman will call on you, and so on. BIOS flashing is equally dangerous. It can be made less dangerous, with devices such as 'BIOS Savior' from ioss.com.tw.
But for a laptop, that isn't an option (no room physically). Installing one of these, gives you an extra BIOS flash memory chip. It allows flashing experimental BIOS files, and if the flash fails, you flip a selector switch, and return to the 'good working' BIOS chip.
This is how people used to work with Nforce2 boards, to test out BIOS files. (Now that many desktop boards use smaller serial BIOS chips, this product is physically no longer compatible.
But in its time, if you were a BIOS hacker, it was money well spent.). I get the impression, you know the Fry's machine is the same as some ECS machine.
You need to find a forum where people have experimented with the machine, and know the ECS BIOS will 'take' if you flash it. You also need to know what the odds are of 'bricking' the machine, with the tools provided. At the very least, when playing with the BIOS, your very first step, is to archive the existing BIOS contents, then place that file somewhere, where you can find it in an emergency. For example, a backup of my original motherboard BIOS, is sitting on the root of my C: drive, (which I made a FAT32 volume on purpose). If necessary, I can boot using my DOS floppy, and the original BIOS is there if I need to flash back to factory conditions. So bare minimum, don't use any flashing tool, unless it has an option to archive the existing BIOS file.
Lionel richie encore rar. In some cases, once you flash the new BIOS (like the ECS), you may not be able to go back to the 'Fry's' BIOS. That depends on the identity string. Some flasher tools have a 'force' option, to flash regardless of identity. If Fry's is simply shipping an ECS barebones, with their name on it, it may be using the ECS BIOS provided with the product, rather than rewriting or changing it. So it could just be an ordinary ECS BIOS all along. Note that, when you flash a BIOS, then restart the computer at least once, the 'image' inside the BIOS chip, won't match what you burned.
A couple small sections of the BIOS chip are writable at the startup of the computer, and DMI/ESCD live there. Thus, if attempting to 'compare' BIOS files, remember that for two BIOS to be 'equal', not all the bytes have to match. Only the executable code sections would have to match, for the BIOS to be 'equal'. Anything which is regularly updated, should not be part of an equivalence check. I learned this the hard way, by experimenting, and finding my new BIOS didn't seem to be the same any more Good luck, Paul.