+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: General Forum (/forum-4.html)
+--- Thread: Getting rid of wrong Windows10 drivers (Clonix/Nov) (/thread-15429.html)
Pages: 1 2
Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-05-2020 01:01 AM
Hi all,
Since Windows 8 showed up and currently under Win10, most (if not all) Clonix/NoV users with a K149/150 USB programmer have suffered the dreaded "driver auto upgrade". Rendering their programmers useless until they take corrective action: a not always easy workaround to get the previous Win7 driver re-installed.
Further more, in many cases this is just a "temporary fix" and Windows managed to "re-upgrade" the offending Prolific driver. Really frustrating as I know first hand. :-(
Since I've been having quite a lot of spare time lately, I decided to design a simplified version of the popular PicKit2 USB programmer.
(I've tried to insert a render image, without success. Here is the link)
Image.
Originally developed by Microchip it can handle the programming task in a far more efficient way:
- About 50% faster
- No USB cable required.
- No module adapter either (PCB has its own gold plated pads to plug the module)
- No drivers required. Runs on the HID native Windows controller. (Quite like a mouse.)
- Open to new µControllers to handle new applications.
A new version of the configuration utility including the required controls to use this new programmer is also available: ClonixConfig61.exe.
There is a short demo YouTube video: here.
Feel free to comment or share.
Best wishes from the Canary Islands and keep safe.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Didier Lachieze - 08-05-2020 07:52 AM
Thanks Diego, great little device ! A neat design improvement compared to the previous ones.
Is it available for purchase?
(08-05-2020 01:01 AM)Diego Diaz Wrote: (I've tried to insert a render image, without success. Here is the link)
Image.
To embed an image stored on Google drive and make it zoom-able you can refer to this discussion.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - HP-Collection - 08-05-2020 08:14 AM
Same question like Didier: 2 pieces for me, please
Matthias
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-05-2020 01:54 PM
Hi,
Thanks for your interest, (and thanks for the image insertion hint Didier. :-)
Regarding availability, I'll place an ad in the corresponding MoHPC section as soon as the first batch is ready. (Hopefully, by end next week.)
Still working on the manual for the Config61 utility.
Stay healthy. ;-)
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - CY-CL - 08-05-2020 03:42 PM
Great News! Thanks Diego!
I will also buy two devices.
Regards,
Patrik
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - rprosperi - 08-07-2020 01:02 AM
Cool development Diego!!
This should breath new life into the various CLONIX/NoV modules out there and help avoid a lot of hassles for people. I suspect a lot more folks have trouble than actually report it, so this should help a lot!
2 for me too please (if your keeping notes, and if not, I'll order after you post the announcement)
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Ángel Martin - 08-07-2020 04:54 AM
Great news and very timely - Other two for me as well...
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - MeindertKuipers - 08-07-2020 08:21 AM
Good work Diego, count me in for one as well!
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-07-2020 10:50 AM
Hi all,
And thanks for your kind words and interest.
First batch will be limited to about 30 units. Which I think will be enough for now.
So far I've taken down requests for 12 units.
The Config61 utility does not handle previous (pre-2013) devices: Clonix-41(d), NoVRAM & NoV-32; based on 32K µControllers.
The programmer itself is able to deal with these though, but the GUI may become a bit messy if all that backwards compatibility is included.
However a simple workaround allows to build the .HEX file using current Config42 and launching PicKit2 SW manually to complete the module programming.
Should enough demand rise, I could dig into the Config42 utility and modify the code to handle the new programmer (Config51?). Time will tell.
Best wishes from Spain.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - aurelio - 08-07-2020 04:29 PM
(08-07-2020 08:21 AM)MeindertKuipers Wrote: Good work Diego, count me in for one as well!Hi Diego, good work, +1,
I bought my Clonix41 in the 2013 so I think the Config61 will handle it without problem, for the Nov64 and USB41, no problem as well.
regards
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-07-2020 08:06 PM
Hello Aurelio,
The pre-2013 reference extends to every Clonix-41(d), NoVRAM and NoV-32.
They were all discontinued on Dec. 15 2013 after the 10th. Anniversary.
However, although the new Config61 will not handle these modules, the pogrammer itself can be used to configure them with the .HEX files generated under the Config42 utility.
Hope this doesn't pose a big handicap.
Best from Canary Islands and keep safe.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Mark Hardman - 08-08-2020 02:49 AM
(08-07-2020 08:06 PM)Diego Diaz Wrote: The pre-2013 reference extends to every Clonix-41(d), NoVRAM and NoV-32.
They were all discontinued on Dec. 15 2013 after the 10th. Anniversary.
However, although the new Config61 will not handle these modules, the pogrammer itself can be used to configure them with the .HEX files generated under the Config42 utility.
In our email communication, I was left with the impression that the new programmer is not compatible with my NoV-64d that was part of the 10th Anniversary bundle. Could you please clarify if it is or is not compatible? If it is, I would love to place an order for one of the new programmers.
Warmest regards,
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-08-2020 05:12 AM
Hi Mark,
And sorry about the misunderstanding.
To clarify the point: The new programmer and the new configuration utility (ver. 6.2) are both compatible with Clonix-D, NoV-64, NoV-64d and USB-41 modules. (any manufacturing date)
The programmer itself is in fact compatible with all the modules I've built from 2003 to date, including the "pre-Dic. 2013" modules: Clonix-41 (silver or gold label), Clonix-41d (the ones exclusive in the Anniversary bundle), NoVRAM and NoV-32.
It is just the Config62 utility which doesn't include these previous modules, hence the need of a workaround creating the .HEX file on Config42 and programming afterwards with the new USB PicKit2 programmer SW: "PicKit2v2p06.exe"
I'll make a new video showing this on an old Clonix-41d module.
Hope this to be a clearer explanation.
Best wishes.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-08-2020 08:34 AM
Here's the link to the video I mention on the previous post.
Viedo.
As usual, feel free to comment/question as required.
Best.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Massimo Gnerucci - 08-08-2020 01:03 PM
(08-08-2020 08:34 AM)Diego Diaz Wrote: Here's the link to the video I mention on the previous post.
Viedo.
As usual, feel free to comment/question as required.
Best.
Diego.
Thanks Diego, since I am the owner of your very first Clonix module, and one of the first NoVram, I am glad to see that I can use this new programmer with them!
Please put me in for one of these.
Thank you.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Mark Hardman - 08-08-2020 06:34 PM
(08-08-2020 05:12 AM)Diego Diaz Wrote: Hi Mark,
To clarify the point: The new programmer and the new configuration utility (ver. 6.2) are both compatible with Clonix-D, NoV-64, NoV-64d and USB-41 modules. (any manufacturing date)
Best wishes.
Diego.
Thank you for for taking the time to answer; everything is perfectly clear now. I'll confirm my order via email.
Mark
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-08-2020 11:07 PM
Hi Massimo, good to see you here! ;-)
Mark, thanks for your message. You've got mail too.
Best.
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - aurelio - 08-09-2020 09:51 AM
Thanks, do you know already how much will cost the programmer, is already on Clonix site?
regards
Aurelio
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - Diego Diaz - 08-09-2020 10:40 AM
Hi Aurelio,
Still waiting for the µControllers and some other parts to arrive.
The parcel is still pending Customs clearance, so final price will depend on the taxes (if applicable).
Once I get them (hopefully early next week) I will confirm the price and place the corresponding ad on this very site.
I'm confident to keep it in the same range as the previous K150 and adapter (40Eur) and don't go beyond 45 in the worst case.
Hope you find this info useful.
Best
Diego.
RE: Getting rid of wrong Windows10 drivers (Clonix/Nov) - aurelio - 08-09-2020 11:53 AM
(08-09-2020 10:40 AM)Diego Diaz Wrote: Hi Aurelio,Thank-you Diego, you will ship from the Carribean or from Spain?
Still waiting for the µControllers and some other parts to arrive.
The parcel is still pending Customs clearance, so final price will depend on the taxes (if applicable).
Once I get them (hopefully early next week) I will confirm the price and place the corresponding ad on this very site.
I'm confident to keep it in the same range as the previous K150 and adapter (40Eur) and don't go beyond 45 in the worst case.
Hope you find this info useful.
Best
Diego.