You may look at / try the Open Source Software:
https://github.com/radiomanV/TL866
This doesn't look like a programmer, just a program how to flash the original firmware. But it is nice to see that the schematic is included, someone could write a new firmware with it.
[...]
Hi,i'm using the programmer in a windows 7 x64 virtual machine using vmware and it works without any problem...
Maybe some problem with virtualbox?
Programmer works in Win10 64 bit and so I believe it should work in Win7 too. Might be something in your settings and not the programmer software. Why not D/L a new copy of the Windows programmer driver software and reinstall it.
Hi,i'm using the programmer in a windows 10 x64 VM on a MacBook Pro using Parallels and it works great...
Hi,i'm using the programmer in a windows 10 x64 VM on a MacBook Pro using Parallels and it works great...
Yes, I am doing same and working perfectly. However recently, I have created a multimeter blog
https://bestmultimeterreviews.org/. I am trying to write multimeter review and how mulitmeter works. I need some feedback from you guys.
I tried it again and now it works. Host system: Debian 64 bit, VM: Oracle VirtualBox 5.0.40 r115130, guest system: Windows 7, 64 bit and later tested with Windows 10, 64 bit. I guess the USB stack somewhere got confused when I updated the firmware and the host system needed a reboot, which I don't do often since I use Linux as my main system.
Hello everybody.
Now beta testing of the Android shell for the programmer TL866.
A video with a brief overview of working with soft WizardProg Mobile.
Write feedback, now you can affect how the program will look and work.
https://play.google.com/apps/testing/com.wizardprog.mobileTL866 has become unique, it works in both Windows and Android.
Hello everybody.
Now beta testing of the Android shell for the programmer TL866.
TL866 has become unique, it works in both Windows and Android.
Interesting, thanks for the update.
Hello everybody.
Now beta testing of the Android shell for the programmer TL866.
...
TL866 has become unique, it works in both Windows and Android.
That's very cool. Another good project for old Android phones -- make a standalone TL866.
Google Play says my Android phone (Alcatel One Touch Evolve 2) is not supported. Oh well. Great looking project though!
Thanks Radioman and everyone else here who have contributed to this forum.
I just got the MiniPro TL866CS off Amazon, and it looks good so far. It works fine on my desktop pc running Windows 7
The only issue I have is probably "DotNet" related, but I am not sure. Other software (Autodesk, and some others) have the same error caused by the type of installation inf file used or the setup file itself.
I can't install the USB driver on either of my 2 WinXP laptops. The programmer software installs, it thinks it installed the USB driver, but after I connect the TL866CS to the cable when instructed to, the "Found New Hardware Wizard" retrieves the device name (MiniPro TL-866 Programmer" then "MiniProWdf".
After a while of the red light staying solid and yellow flashing, the wdfcoinstaller runs from the .inf file and I get an error from the "Found New Hardware Wizard" window saying something about "no signature found". Screenshot attached:
Anyone else have this problem? Any solutions? Thanks.
Well, I ran the separate driver installer in the DRV folder, and it says the driver is unsigned, that's why it won't install on my XP machines. Certificate expired in 2012.
I will just try to find some older sw version to try with XP.
Well, I ran the separate driver installer in the DRV folder, and it says the driver is unsigned, that's why it won't install on my XP machines. Certificate expired in 2012.
I will just try to find some older sw version to try with XP.
Why is your XP machine not just asking you if you're okay with installing an unsigned driver?
Sent from my SM-N9005 using Tapatalk
Well, I ran the separate driver installer in the DRV folder, and it says the driver is unsigned, that's why it won't install on my XP machines. Certificate expired in 2012.
I will just try to find some older sw version to try with XP.
Why is your XP machine not just asking you if you're okay with installing an unsigned driver?
Sent from my SM-N9005 using Tapatalk
It did ask, I told it to install anyway. Then it fails. I will get a new screen shot. If I can find a different driver install or xp registry file to import, that would be great....
Screenshots. Incidently, MiniProWDF.sys in the DRV folder has no digital certificate, but the one in DRV\WIN64 is signed. I tried both, no luck in XP.
Sorry, but Windows XP 64bit is known to have issues like this.
If you have access to another system with a newer Windows of even Windows XP 32bit, try it again.
My laptops are only 32 bit. I was ust saying the 64 bit file is signed so it installs on Win7 x64 fine, but the 32 bit one is messed up. This is version 6.6 that is current. Incidentally my CD that came with it is also version 6.6. CRC check shows identical 32 bit files (I use "Hashtab" for crc checks).
If I can find an older version with a good driver install for win32 somewhere, then I can still use the current program.
Most of the old uploads people did to rapidshare, etc, are no longer there. Maybe someone here has an older cdrom with a working win32 usb driver install?
I should have mentioned that I have tested the current v6.60 version
on a old Windows XP SP3 laptop here. It installed and works well.
You can't use the 64bit driver on a 32bit OS version. You need to use
the MiniProWDF.inf in the installed drv folder. Normally it should have
done it automagically when installing the MiniPro software.
My normal used systems are all Windows 10 64bit, but for the sake
of some awfull cases and testing purposed, I kept the old notebook.
I only checked 64 bit folder for comparison. I ran the regular full install, tried importing the inf, tried installing certificates, nothing fixed the unsigned driver error.
It must be something I am missing, but Microsoft is silent about. Like I originally posted, other software had similar issues according to my Google searches... DotNet4 had it, I think an autocad version did as well. They said it had to do with using a devcon install with a coinstaller. Deleting temp files and the Cat2 folder didn't work.
I give up for now. Maybe I can install or remove sometyhing in Windows XP that clashes with the driver install.
Thanks for trying though: :-)