It said 1.0.2.28 was the driver version next to it. Just as the author of the above video said to, I downloaded the second to last driver listed on that page. So I downloaded the recommended files from The video above does have a link in the description for where to download drivers for Windows 10. But there are no drivers for it on that site. This seems to be it, or some revision of it, on the Macro Silicon website. I wasn't sure if those were all "0s" (as in zero) or "o" (as in the letter oh). The number on the main chip says "MS2100E PBA-GKFLG0F 1835". When I opened up the case of my Eas圜AP (you can just pry it open) I noticed that the circuit board said V 2.0. I noticed that the disc that came with my Eas圜AP says it's Windows 10 compatible, and it says "Version 4.0a" while in the video above it says Version 2. I would love it if the solution was as easy as using a different USB cable. I rebooted my laptop into Windows 10 to test this out. "Easycap not working on windows 10." Super User. That is it just purchase a quality top of the line usb cable and your good to go. I thought it was the driver for a long time until it hit me try a quality usb cable. Get your self a top of the line usb cable and you are good to go.I had one lying around my home and tried it and it works great. The usb cable that attaches to it and then you plug the other end to the computer. It's not the drivers I finally figured it out. On a Stackexchange discussion, one user wrote: The lsusb command lists the device id as 534d:0021.Ī quick Google search for the device id yielded some results which I may refer to later.Īnother search for 534d:0021+windows also returns some promising looking information that I'll return to. Note that it does this (install "wrong" edition) even if it later in the process shows that Microsoft will find and use the license for the other edition without logging in on an MS account, it does it by looking up various hardware serial numbers but this happens much later in the install process and only works if you've forced it to the right edition.I plugged the Eas圜AP into my computer at home running Ubuntu 18.04. Windows install bypass the Edition selection when it finds that key in BIOS storage, the workaround for this is to edit one of the file on the install media which forces it to always ask. OTOH this stored BIOS license key can be a problem if you're trying to do a clean install of a DIFFERENT edition of Windows (like Pro while the machine came with Home). If it does have the stored key it goes up to 100%. So you might as well use the most well-known one, Magical Jelly Bean KeyFinder.Īnd in my experience Microsoft will 99 times out of 100 automatically detect and apply the correct key (as long as you select the right Windows Edition) even when doing clean installs on existing hardware even if you don't use a MS account for login and it doesn't have a BIOS stored license key. So really, only the first method should ever be used, there are other programs and tools that will work but there's no reliable methods that doesn't use tools! If there's no Windows OEM key in the BIOS it will be empty and if you've reinstalled using a different key it will give you the wrong key! It is useful as a way to access the key that comes with the hardware on most newer OEM machines but is no substitute for actually checking what license key Windows actually use.Īnd the third method usually? sometimes? returns a "digital key" that's only valid for the specific install - there's no real use for this since it can't be used even on the same hardware after a reinstall! The OA3xOriginalProductKey method returns the Windows OEM license key stored in the BIOS for pre-installed machines where they used that method to store it - most OEMs do this because this is the only way where they DON'T need to physically affix a sticker with the key on the machine which saves them time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |