Monday, May 6, 2013

USB to Serial (Prolific 2303) Device Cannot Start (Code 10) in Windows 8/8.1/10

Is this a rare situation where a piece of legacy hardware works fine in Linux and is broken in Windows??

The Prolific 2303 works perfectly fine in Linux Mint.  Yet, for some reason, Prolific says that some of these chips have reached the end of life and won't be 'supported' under Windows 8.  Prolific suggests that you purchase their updated chipset (PL2303HX Rev D):


So, what is different about the newer chips that they *can* be supported in Windows 8, while the older ones can't?  What has changed in Windows 8 that makes this support different?

Here's the yellow triangle with exclamation point that you'll see:


And here is the "Code 10" error:


Fixing it:  Some clever people have figured out workarounds for this issue.

Get this file: Profilic_Win8_x64_x86.zip   (Google Drive link here.)

Extract the contents of this file somewhere and examine the contents:


Right click the .inf file, and select "Install".


I didn't notice that anything happened when I ran it.  Probably because I've tried so many different drivers and installations; maybe it was already installed, I don't know.

Got back to the device manager and right click the Prolific USB to Serial comm port, and click "Update Driver Software".


In the resulting dialog, click "Browse my computer for driver software":


Select "Let me pick from a list of device drivers on my computer":


Select the Prolific driver version 3.3.2 from 2008:


Win.


If all went well, you'll no longer see the yellow triangle:


h/t to the original post at Microsoft's Technet forum by user drtedrted.

Saturday, May 4, 2013

Windows 8 + Linux Mint UEFI Dual Boot Follow Up: When things go wrong.


Your BIOS setup may look different from this, but this is what mine looks like when it works the way I want (dual boot via Grub):

My BIOS "Boot" Configuration
Notice the first item called "mint".  This guy disappeared once after a Windows update.  In order to get it back, you may have to add it again.  Notice the option "File Browser Add Boot Option" in the screen above?  Select that option and you should get something that looks like this:

Dell file chooser
This is just a primitive file picker.  Above is a list of partitions on my machine.  You can select any one you want and see what is in there.  Then one you're looking should have contents like this:


Under <linuxmint> you should see this:


The grubx64.efi file is the one you want, this one will start Grub on boot.  Once you've selected this file, you will probably be asked to name the new boot configuration.  You can call it whatever you want.  Once you've given it a name (I called it "mint"), you will want to make it the first boot priority as in the first photo of this article.

Another problem I ran into once (again after a Windows 8 'update') was messed up partition flags.  Here is what my "working" partitions look like:


I've highlighted the partition flags at right.  You will of course need to know what you're doing if you start messing with these.  The important flags are "boot", which is on /dev/sda1 here, and the "msftres" flag which is on an 'unknown' chunk of the disk.  Make sure these are set properly.

Finally, when things really go wrong and you can't boot into Windows 8 anymore, you may need a Windows 8 rescue image.  This can be generated from a working copy of Windows -- even a working copy from a friend that has Windows 8.  If you can't find a friend that has it, maybe you can go to a local computer store and get one made...  You just need an 8GB USB memory stick.  I had to borrow one one from a friend of mine in order to use the utility called "bootrec".  The general procedure was something like:
  1. Boot Windows 8 recovery from USB drive. 
  2. Get to a command prompt and run the following:
  3. bootrec /fixmbr
  4. bootrec /fixboot
  5. bootrec /rebuildbcd
I am not sure which of the last three commands was most effective in fixing my problem, but I ran all of them.

So that's it.  For any problem you may have, I think you've got the information here to solve it.


Monday, April 15, 2013

Search Mint.com Transactions by Date with Firefox or Chrome

 If you're a Mint.com user, you've probably noticed that the search interface isn't all that great.  For one thing, you can't search your transactions by date.  When tax season rolls around, it is absolutely necessary to search and display only the transactions from the previous year.

It seems I'm not the only one to have noticed this oversight.  Look at the discussion on the Mint.com help blog here.  At that time (2009!) Mint representative Matt Snider posted the following response:



You can, but currently only by modifying the URL directly. We intend to someday expose this functionality in the user interface, but have not been able to agree on a minty enough design. Anyway, go to the transaction page, and you should see "https://wwws.mint.com/transaction.event" in the URL. Add the following "?startDate=06/01/2009&endDate=06/30/2009" at the end of the URL and hit enter. Change the start and end date to the dates you want to search. The complete URL should look something like this:

https://wwws.mint.com/transaction.eve...

Here Mint admits that they've been unable to come up with a "Minty enough" design in four years time!  In addition, this post reveals a semi-official interface to do this filtering yourself.  With this information, at least we are somewhat equipped to fix this problem ourselves.
  • If you use the Chrome browser, check out this extension in the Chrome Web Store.  I'm not a Chrome user so I can't comment more on this solution but it looks pretty sweet.
  • If you use Firefox, you can use my Greasemonkey script.
The basic interface.  Both dates are OK, so they're colored mint green.
Prerequisites:
Using the script:
  • Load the "Transactions" view on Mint.com.
  • Two input fields will appear below the search box. 
  • Set the start date and end date.  
  • If both dates are valid dates the page should reload automatically click the "Go" button.
  • If either of the dates are invalid the invalid date will be marked as pink.
  • You can get pretty crazy with the input date.  Try "Jan 1 2013" or "12-Jan-13" or whatever you want.  This functionality comes from the awesome datejs library.  Read more about that here.
  • It is possible that you get into a situation where the dates aren't updating, in this case you may need to start from "Transactions" again.
Here are some more clips of what the interface looks like:

Hover over either date to get more information.  Note "yesterday" works fine.

...just using a different entry format.


Here is an invalid entry.

It isn't perfect, but better than nothing!  Check out the source at github, change it, and push it back to me!