Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 29 Jan 2020 08:03:53 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00TFnZio026617; Wed, 29 Jan 2020 10:53:11 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00TFnY1n026614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 29 Jan 2020 10:49:34 -0500 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 00TFnOnN026580 for ; Wed, 29 Jan 2020 10:49:25 -0500 Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 29 Jan 2020 10:49:19 -0500 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by oc11expo23.exchange.mit.edu (18.9.4.88) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 29 Jan 2020 10:49:33 -0500 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.171) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 29 Jan 2020 10:49:33 -0500 Received: from MN2PR01CA0012.prod.exchangelabs.com (2603:10b6:208:10c::25) by MWHPR0101MB3005.prod.exchangelabs.com (2603:10b6:301:31::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.26; Wed, 29 Jan 2020 15:49:31 +0000 Received: from CO1NAM03FT016.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::206) by MN2PR01CA0012.outlook.office365.com (2603:10b6:208:10c::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.20 via Frontend Transport; Wed, 29 Jan 2020 15:49:31 +0000 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (40.92.20.106) by CO1NAM03FT016.mail.protection.outlook.com (10.152.80.170) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Wed, 29 Jan 2020 15:49:30 +0000 Received: from BN8NAM11FT017.eop-nam11.prod.protection.outlook.com (10.13.176.58) by BN8NAM11HT173.eop-nam11.prod.protection.outlook.com (10.13.177.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.25; Wed, 29 Jan 2020 15:49:29 +0000 Received: from BYAPR02MB4055.namprd02.prod.outlook.com (10.13.176.55) by BN8NAM11FT017.mail.protection.outlook.com (10.13.177.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.25 via Frontend Transport; Wed, 29 Jan 2020 15:49:28 +0000 Received: from BYAPR02MB4055.namprd02.prod.outlook.com ([fe80::f964:6ae7:834b:8fa7]) by BYAPR02MB4055.namprd02.prod.outlook.com ([fe80::f964:6ae7:834b:8fa7%5]) with mapi id 15.20.2665.027; Wed, 29 Jan 2020 15:49:28 +0000 From: Bob Blick To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 29 Jan 2020 07:49:28 -0800 Subject: Re: [PIC] PICkit 2 Thread-Topic: [PIC] PICkit 2 Thread-Index: AQHV1fuOSDKyEpfpd0eIdcm2Fk/eVKgAisqAgAE+QgE= Message-ID: References: , List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: acceptlanguage: en-US received-spf: Pass (protection.outlook.com: domain of outlook.com designates 40.92.20.106 as permitted sender) receiver=protection.outlook.com; client-ip=40.92.20.106; helo=NAM11-BN8-obe.outbound.protection.outlook.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RBZUywuXeoUA0uzrZUjRU/0vOoe3jjT+TwsPX3/oiJo=; b=OxH7SWo+jivDMPQBbdfb6ot8cxVZIeHWKbukSsD8nbVO8//erVQHYq4542WjKDcF8DuaLYCpwXZAWxhGxCViGLfI52opdXxmBojsZh0s/6F2qz3yJWI8AvB83cAFT24UCc8rJW66px6G9Gbc9th7u1cU+79cyVw4QPp71qlCsYZQHPokifzjkpNWd7zZgKxiuZ0tkOUTl2auAZZcV6Odjnmh7a0eE5SkpwyI/1NwfLgc4LhjVPWex0eZz8G0GhC3/va7p5rJBfu7ADDzt0lr/vYcfCZLWwSTJoooKSat0kqLyt4MNF1K9QMjlfh6g/gBKfshqsFNfT7zZLezvCer4A== authentication-results: spf=pass (sender IP is 40.92.20.106) smtp.mailfrom=outlook.com; mit.edu; dkim=pass (signature was verified) header.d=outlook.com;mit.edu; dmarc=pass action=none header.from=outlook.com;compauth=pass reason=100 errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-topics: [PIC] x-mime-autoconverted: from quoted-printable to 8bit by PCH.mit.edu id 00TFnY1n026614 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Wouter, Interesting. If it doesn't need a driver, and it does show in Device Manage= r as the correct items, perhaps the PICkit2 application software is confuse= d by the 36 other items listed as HID-compliant devices(whatever they may b= e) as opposed to Win7 only showing the entries associated with PICkit2. I suppose nobody uses the PICkit2 anymore, otherwise I would expect more pe= ople would be having the same problem as me. Since I don't do any new devel= opment with PICs, I'm not going to go out and buy a new programmer. Thanks for the reply! Best regards, Bob ________________________________________ From: Wouter van Ooijen=20 Sent: Tuesday, January 28, 2020 12:41 PM To: Bob Blick Subject: Re: [PIC] PICkit 2 Op 28-Jan-20 om 6:00 PM schreef Bob Blick: > I am trying to use a PICkit 2 and the PICkit 2 v2.61 application under Wi= ndows 10. I got it to work once. Now it is invisible to the PICkit2 softwar= e. In Device Manager I believe it is showing up as a USB input device. I tr= ied removing that device but when I plug the PICkit2 back in it shows up th= e same way. Due to my poor understanding of Windows directory structure I c= an't seem to find the actual driver folder for the PICkit2 to try to force = a particular driver. > > I've got two PICkit2's and cables and they both do the same thing. They w= ork on a Windows 7 machine but that machine has a dying hard drive so I rea= lly can't use it very much longer. > > Anyone been here before and gotten their PICkit2 to work? > > Thanks! > > Bob Not been there, but my pcikit2 (might be a Chinses clone) works like a charm on W 10. It shows as a "HID-compliant vendor-defined device". IIRC a HID device on W doesn't need a driver. -- Wouter "Objects? No Thanks!" van Ooijen --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .