Windows 7: Windows Media Encoder: No Specified Device Driver Is Present

I had downloaded Microsoft Windows Media Encoder (WME) 9.0.  I was aware that it was unsupported and otherwise limited in comparison against Microsoft Expression Encoder 4 Pro ($199).  I was trying to use it to do video screen capture in 64-bit Windows 7.  I went into New Session > Capture Screen > Specific Window and Capture Audio from the Default Audio Device > designate the window > name the output file > high quality > diplay information (blank) > Finish.  At that point, I got this error:

Windows Media Encoder

No specified device driver is present.(0xC00D0072)

A search led to a Microsoft webpage that said this occurred because DirectX Media 6.0 was not installed.  Unfortunately, the page to which they directed me for the appropriate download was defunct.  Wikipedia said that DirectX 6.0 was released in August 1998, that the current version was DirectX 11, and that DirectX had been included in Windows ever since Windows 95 SR2.  (I also saw an indication that this problem might arise only when trying to record audio along with the video.  I didn't investigate that; I was only interested in video plus sound at this point.)

My theory was that DirectX had grown and that WME had not been maintained to keep up with it, and therefore I needed to install an older version of DirectX for that purpose.  I was not sure that this would work without screwing up the more recent DirectX.  I made a System Restore point and then downloaded DirectX 8.1 Runtime for Windows 2000, released in November 2001.  I wasn't sure whether that was the right thing; I also downloaded the DirectX Media Platform SDK Redistributable (June 2001).  Both were around 6-8MB.

Before installing them, I looked at a few more posts.  One post said that what was missing was actually a WDM (Windows Driver Model?) driver for the microphone.  The plausible theory in this case was that I would gain nothing by installing a retrograde version of DirectX; instead, I just needed a current driver.  But I was using onboard audio; I had only installed the motherboard recently; and I had made sure to get the latest drivers at that point.  I guessed that the motherboard drivers were no longer attempting compatibility with WME.

There was always the option of using a handheld audio recorder to record sound from the speakers.  Or if I didn't mind risking blowing up my handheld recorder, I could try running a cable directly from the computer's headphone output to the recorder's microphone input.  I would still have the hassle of synchronizing audio with video in a video editor.  That would be more difficult if the video showed lip motion or other things that would become bothersome if they weren't closely aligned.

There was also the possibility of doing further research into who was using WME on Win7 successfully at this point, and what hardware they were using, and buying the appropriate sound card.  I was out of time for this project, but it could also develop that further research would turn up a solution I had overlooked.  But good video capture had been elusive.  I had bought Debut and had been using it with good results; the question only arose because there was a hopefully temporary licensing snafu where Debut didn't work for me in the middle of the night.  Debut was now working again, so I shelved this question for the time being.

PUSBLANXAD01 AD-LAN01 PC USB Network Adapter Driver Blues

On Amazon.com, I bought an item described as "NEW USB to LAN RJ45 Ethernet 10/100 Network Adapter Card."  The purpose was to see if I could use USB to connect to the Internet, where I did not have a working ethernet connector for the usual cable connection.  The device was cheap -- about $7 with shipping -- and when I plugged it in, it lit right up.  The problem was, contrary to the ad, it did not come with a driver CD.  And since the Windows Vista computer I wanted to use it on was, of course, not able to go online, I could not download and install the drivers automatically.

The device came in a little box with a label on it that read, "16254 PUSBLANXAD01[J133] PC USB Network Adapter."  The UPC product number on the box was 8-77083-03542-3 (or 877083035423).  The device itself had a label that said, "Model:  AD-LAN01."  Both stickers said, "Made in China."

Buy.com had a review that I didn't see before buying, in which the buyer said that s/he had the same problem -- no driver CD.  That Buy.com webpage said the item was made by eForCity.  I went to the eForCity webpage.  It had no link for driver downloads.  There were several reviews.  Some said they had no problem; some said it didn't work.  I wondered whether it mattered if you used it on Windows XP or Vista.  I plugged it into a WinXP machine and tried that.  Windows recognized it as a "USB Network Controller," but the Found New Hardware Wizard said, "The wizard could not find the software on your computer for USB Network Controller."  I chose the option of connecting and searching for the software on the Internet -- using the existing ethernet connection on that computer to do so.  A minute later, it said, "Cannot Install This Hardware.  The hardware was not installed because the wizard cannot find the necessary software."  I verified that my online connection was working OK, tried again, and got the same thing.

Some of these reviews said something about downloading drivers from other websites.  Good way to get a virus.  I tried a search for AD-LAN01 instead of the previous search for PUSBLANXAD01.  That turned up only a couple of hits, one of which was a thread on which the person said they had tried downloading drivers and still had no luck, and another of which was a driver download page for some kind of graphics device that was apparently also called the AD-LAN01.  I tried a search for the UPC.  This gave me a post from someone who said the CD did come with theirs, but it was nonreadable and they had to reinstall the driver weekly.  So, OK, toss it in the parts box and maybe someday I'll find a computer that it works on.  Junk.  Should have bought a brand-name product.  And that was my next step.