TestIDs
---------
1
2
3

TestData
--------
A
B

What I want is a join that produces:

Result
--------
1 A
1 B
2 A
2 B
3 A
3 B

This is essentially a join without an "on" clause, however the trick in SQL is that the "join" keyword isn't needed either.  The select statement is simply:

select * from TestIDs, TestData

Notice that there is a comma seperating the tables to select from, and no join keyword anywhere.  Handy!

Things to gather:

• Your Evo, when you're ready to wipe all data (write down apps to reload, backup anything you don't want to lose, etc)
• Your USB cable
• SimpleRoot OTA 1.47.651.1 Edition

Ideal Steps:

1. Try following the instructions on the SimpleRoot thread, ideally you won't have any issues and will result in a rooted stock firmware (note: this will leave your Evo in a state where you can install an alternative firmware--but SimpleRoot *is not* an alternative firmware).
2. If things don't go so smoothly, try my customized steps:

My Extra Steps

• Check the version of HTC Sync on your PC, it should be the same version that was included on the SD Card of your phone. ( 2.0.31)
• Perform a Factory reset on the phone, either through the System menu or from the bootloader (hold the volume-rocker when powering up)
• Mount your MicroSD card as a USB drive and Format it (FAT32)
• Repeat the SimpleRoot steps

At the end of this process my phone entered a reboot-loop; which definately made me nervous.  I pulled the battery and SD card, then replaced the battery and powered up (without the SD card) and it booted successfully.  I verified the firmware had been successfully downgraded (to 1.17.x.x), which indicates the process was successful, and resumed.

My next step was a custom recovery--I tried using SimpleRoot's Extras menu, but my phone would boot to a red triangle with an exclamation and make it no further (this is the recovery screen)--so I grabbed evorecovery from here and (with the phone still at the red-triangle) unzipped evorecovery and successfully ran recovery-windows.bat.  Upon completion I had my customized recovery screen running and took the opportunity to partition my SD-card for apps2sd (not sure if this will be relevant since I'm going to cyanogenmod 6/froyo/android 2.2--which includes an official form of apps2sd), and ran a nand + ext backup.

Apparently UPS can ship so fast that they wind back time.  Which would be awesome, if only they got it to the right address (I like in Kentucky, not Missouri).

At work we are writing a .NET 2.0 application that has its roots back in 1.1.  Some ancillary applications were also written in 1.1, and shared some common libraries; so when it came time for this application to be upgraded to 2.0 some libraries had to be left behind for compatibility reasons.

One such library has the task of loading data from databases, and was designed to read from MS Access, SQL Server, or MSDE; however in the ongoing development of our application we are scraping the MS Access use in favor of SQL Compact Edition.  For those familiar with SQL CE, you'll know it's not compatible with the 1.1 framework--so we were faced with the issue of either duplicating the functionality of the 1.1 DLL in a 2.0 DLL, so that old applications could be left alone, or with doing massive work to overhaul the old applications and try to bring them all up to 2.0...  neither option was terribly appealing (although the first option was obviously preferable).

Our project architect put the task to me, and had a plan of attack that he figured would let us make the 1.1 DLL talk to the SQL CE database via a 2.0 DLL proxy--however you'll know that 1.1 projects cannot reference 2.0 projects.  Here's where a little trickery comes in...

For a quick recap we have: A Framework 2.0 application, which calls a 1.1 Library to retrieve data.  We need: A Framework 2.0 application to call the 1.1 Library to call a 2.0 Library to retrieve the data from SQL CE.

To achieve this we added an interface to the 1.1 Library, and implemented that interface in the new 2.0 library which uses the interface to fetch the needed data from the database.  The 1.1 library uses reflection to late-load the 2.0 library and instantiates it by its interface.

So the workflow is:

• 2.0 Application makes a call to the 1.1 Library
  •  1.1 Library uses an Assembly.Load() call to late-load the new 2.0 Library and casts it to the 1.1's interface definition.
  • 1.1 Library then can call the Interface member, which...
    • Talk through the 2.0 framework to our SQL CE database.

To install XP I had to convert my SATA controller to run under Compatibility-mode, which allows XP to recognize the drive without a 3rd party driver during installation. After installing XP, Vista, and Ubuntu Gutsy Gibbon on the drive in this mode I flipped the BIOS switch back to AHCI, and both versions of Windows crashed hard.

Here's the path to recovery:

1. Go to Lenovo\IBM's site and lookup the driver-download page for your machine, this page is under Support.
2. Find "Intel Storage Matrix" on the driver page and download it. Then run this file, which will extract other files.
3. Open a command prompt, and go to C:\Drivers\Win\IMSM\Prepare (created by the above step). Then run "Install.cmd" which will install the Intel drivers.
4. Reboot, flip the BIOS switch to AHCI, and you should be all set.

This works for both XP and Vista; although Ubuntu was happy without any work

dmidecode will output lots of details about your motherboard and the devices connected to it, including BIOS information as well as some upgradability info (usually).