Here’s a side-by-side comparison of my old HP rw6828 and my new HTC TyTN II.
| | HP iPAQ rw6828 | HTC TyTN II | | — | — | — | | Processor | Intel® PXA270 Processor 416MHz | Qualcomm® MSM 7200, 400MHz | | Operating System | Windows Mobile 5.0 | Windows Mobile® 6 Professional | | Memory | 45MB available for persistent user storage 64MB SDRAM for running applications | ROM: 256MB RAM: 128MB SDRAM | | Dimension | 102mm (L) x 58mm (W) x 19.5mm (D) | 112 mm (L) X 59 mm (W) X 19 mm (D) | | Weight | 140g | 190g with battery | | Display | 56 x 56mm (2.205 x 2.205 inches) transflective TFT QVGA color, 240 x 240 pixels,0.24mm dot pitch, 64K-color support, portrait and landscape support with touch screen | 2.8 inch, 240 X 320 QVGA TFT-LCD display with adjustable angle and backlight | | Network | GSM, GPRS, EDGE | HSDPA/UMTS: Tri-band 850, 1900, 2100 MHz HSDPA: Up to 384kbps for upload and 3.6Mbps for download UMTS: Up to 384kbps for upload and download GSM/GPRS/EDGE: Quad-band 850, 900, 1800, 1900 MHz (The device will operate on frequencies available from the cellular network) | | Device Control | | Finger scrolling and panning 5-Way navigation control | | Keyboard | None | Slide-out QWERTY keyboard | | Connectivity | Class II device; up to 4 dBm transmit, typical 10 meter range (approximately 33 feet) - High-speed, low-power, short-range wireless communication with other Bluetooth devices Serial IrDA SIR, data transfer up to 115.2 Kb per second, USB 1.1 Client - support via HP standard mini-USB cable 802.11b (WEP and WPA) | Bluetooth® 2.0 Wi-Fi®: IEEE 802.11 b/g (WEP, WPA, WPA2) HTC ExtUSB™ (11-pin mini-USB and audio jack in one) GPS antenna connector | | Camera | Built-in UXVGA 1.3MP with LED light, 1280 x 1024 resolution, JPEG and 3GP format, support for still image, and video playback, H.263 | Main camera: 3 megapixel CMOS color camera with auto focus Second camera: VGA CMOS color camera | | Audio | Integrated microphone, receiver, speaker and one 2.5mm stereo headphone jack, MP3 stereo (through headphone jack) Handsfree speakerphone | Built-in microphone and speaker | | Ringtone formats | Simple MIDI Type 0, WMA, WAV, MP3, polyphonic MIDI |
- MP3, AAC, AAC+, WMA, WAV, and AMR-NB
- 40 polyphonic and standard MIDI format 0 and 1(SMF)/SP MIDI
Headset 2.5mm jack with single earbud style headset (mute and volume control) mini-USB connector Battery Removable/rechargeable 1200 mAh, 3.7 Volt, Lithium polymer battery 1,350 mAh rechargeable Li-polymer battery Standby time:
- Up to 350 hours for UMTS
- Up to 365 hours for GSM
- Up to 264 minutes for UMTS
- Up to 420 minutes for GSM
- Up to 120 minutes for video call
Expansion Slot Supports mini SD memory standard microSD™ memory card (SD 2.0 compatible)
Interesting things I’ve noticed so far:
- While the new phone uses the “ExtUSB” port to connect the headset (meaning it should never get stuck), this does mean you can’t charge or dock the device and listen on the headset at the same time.
- The HTC device happily continues to play audio even when it loses the phone signal - my HP had this annoying “feature” that most times when I was travelling on a train through a tunnel, it would pause Media Player.
- There’s no volume control on the headset. Fortunately the headset does seem much more comfortable and clearer than the HP one.
- The HTC memory card seems a lot faster to access.
In most states and territories of Australia, we have daylight saving. While there probably aren’t as many benefits for those living in the northern areas of the continent, I quite like it.
Next year, South Australia’s daylight saving will end on Sunday 6 April at 3am. This is a change from the previous rule of the last Sunday in March, but it brings us into line with NSW, Victoria, ACT and Tasmania, which is probably a good idea.
Microsoft have been busy releasing time zone updates this year, particularly with changes in some US states and also Western Australia.
The latest revision includes updates for Australia, including Central Australian Standard Time, Australia Eastern Standard Time and Tasmania Standard Time. Updates for various operating systems are linked from the KB article.
If you have a Visual Studio add-in that references the VSLangProj assembly, that assembly implicitly refererences the EnvDTE assembly (version 7.0.3300.0). However that version of EnvDTE doesn’t ship with VS2008.
There is a binding redirect in place for Visual Studio (via a devenv.exe.config file), but this doesn’t appear to work for the Code Analysis command. I tried modifying the fxcopcmd.exe.config file to no avail.
The is the error I’m seeing:
Running Code Analysis… C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop\FxCopCmd.exe /outputCulture:1033 /out:”bin\Debug\Altinoren.ActiveWriter.Dsl.dll.CodeAnalysisLog.xml” /file:”bin\Debug\Altinoren.ActiveWriter.Dsl.dll” /dictionary:”..\CodeAnalysisDictionary.xml” /directory:”C:\Program Files\Common Files\Microsoft Shared\MSEnv\PublicAssemblies” /directory:”C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies” /directory:”C:\Windows\Microsoft.NET\Framework\v2.0.50727” /directory:”C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies” /directory:”C:\Program Files\Microsoft Visual Studio 2008 SDK\VisualStudioIntegration\Common\Assemblies” /directory:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5” /rule:”C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop\Rules” /searchgac /ignoreinvalidtargets /forceoutput /successfile /ignoregeneratedcode /saveMessagesToReport:Active /timeout:120 MSBUILD : error : CA0001 : The following error was encountered while reading module ‘Altinoren.ActiveWriter.Dsl’: Assembly reference not resolved: EnvDTE, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. MSBUILD : error : CA0058 : The referenced assembly ‘EnvDTE, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ could not be found. This assembly is required for analysis and was referenced by: ‘Altinoren.ActiveWriter.Dsl.dll’. Code Analysis Complete – 2 error(s), 0 warning(s)
Update 29th November 2007:
David Kean has responded to my query in the MSDN forums with a workaround to this problem.