I was reading on a blog that HTC released an email (if you are on there mailing list you would have also got it too) that was  an invite to a product launch on the 24th of July!! whilst the invite does not specify what product it is, but in saying that what else do they have that’s not yet been released…. NOTHING.

see below for more info on the invite

http://www.techau.tv/blog/?p=479

but back to the features list

now For the

HTC Diamond

Processor
Qualcomm® MSM7201A™ 528 MHz

Operating System
Windows Mobile® 6.1 Professional

Memory
ROM: 256 MB
RAM: 192 MB DDR SDRAM
Internal storage: 4 GB

Dimensions
102 mm (L) X 51 mm (W) X 11.35 mm (T)

Weight
110 g (with battery)

Display
2.8-inch TFT-LCD flat touch-sensitive screen with VGA resolution

Network
HSDPA/WCDMA:

• Europe/Asia: 900/2100 MHz

• Up to 384 kbps up-link and 7.2 Mbps down-link speeds

Tri-band GSM/GPRS/EDGE:

• Europe/Asia: 900/1800/1900 MHz

(Band frequency and data speed are operator dependent.)

Device Control
TouchFLO™ 3D
Touch-sensitive navigation control

GPS
GPS and A-GPS ready

Connectivity
Bluetooth® 2.0 with EDR
Wi-Fi®: IEEE 802.11 b/g
HTC ExtUSB™ (11-pin mini-USB 2.0 and audio jack in one)

Camera
Main camera: 3.2 megapixel color camera with auto focus
Second camera: VGA CMOS color camera

Audio
Built-in microphone, speaker and FM radio with RDS
Ring tone supported formats:

• MP3, AAC, AAC+, WMA, WAV, and AMR-NB

• 40 polyphonic and Standard MIDI format 0 and 1 (SMF)/SP MIDI

Battery
Rechargeable Lithium-ion or Lithium-ion polymer battery
Capacity: 900 mAh
Talk time:

• Up to 270 minutes for WCDMA

• Up to 330 minutes for GSM

Standby time:

• Up to 396 hours for WCDMA

• Up to 285 hours for GSM

Video call time: Up to 145 minutes for WCDMA
(The above are subject to network and phone usage.)

HTC Touch Pro

Which is what I AM VERY excited about, in my opinion this has it all over the I-Phone.

Processor
Qualcomm® MSM7201A™ 528 MHz

Operating System
Windows Mobile® 6.1 Professional

Memory
ROM: 512 MB
RAM: 288MB

Dimensions
102 mm (L) X 51 mm (W) X 18.05 mm (T)

Weight
165 g (with battery)

Display
2.8-inch TFT-LCD flat touch-sensitive screen with VGA resolution

Network
HSDPA/WCDMA:

• Europe/Asia: 900/2100 MHz

• Up to 384 kbps up-link and 7.2 Mbps down-link speeds

Tri-band GSM/GPRS/EDGE:

• Europe/Asia: 900/1800/1900 MHz

frequency and data speed are operator dependent.)

Device Control
TouchFLO™

(Band  3D
Touch-sensitive navigation control

Keyboard
Slide-out 5-row QWERTY keyboard

GPS
GPS and A-GPS ready

Connectivity
Bluetooth® 2.0 with EDR
Wi-Fi®: IEEE 802.11 b/g
HTC ExtUSB™ (11-pin mini-USB 2.0, audio jack, and TV Out* in one)

Camera

Main camera: 3.2 megapixel color camera with auto focus and flash light
Second camera: VGA CMOS color camera

Audio
Built-in microphone, speaker and FM radio with RDS
Ring tone supported formats:

• MP3, AAC, AAC+, WMA, WAV, and AMR-NB

• 40 polyphonic and standard MIDI format 0 and 1 (SMF)/SP MIDI

Battery
Rechargeable Lithium-ion or Lithium-ion polymer battery
Capacity: 1340 mAh
Talk time:

• Up to 397 minutes for WCDMA

• Up to 485 minutes for GSM

Standby time:

• Up to 503 hours for WCDMA

• Up to 406 hours for GSM

Video call time: Up to 201 minutes for WCDMA
(The above are subject to network and phone usage.)

Expansion Slot
microSD™ memory card (SD 2.0 compatible)

Remember to book in the 24th of July 08, I know I have.

The job was huge (and something I am very proud of) as we had the massive tasks of changing all clients DNS both internal and roughly 150-200 External DNS’s, Configuring the firewall and then implementing.

here is a rough plan of how we went about it.

1. We first started to collate a list of all domains that we hosted from our IIS servers
2. We Then created a script to go through and complete Ping and NSlookup requests against every single domain
3. Taking the log file that the script created we then were able to determine what Domains we hosted and had control of the DNS, and also had a list of what we didn’t have control of.
4. Before we could go changing DNS’s we needed to ensure that there was no down time for any of the sites, as this we see as not acceptable. So we devised a plan where we would take of our DMZ internal range and give the subnet a 255.255.254.0, which effectively gives us another 0 – 255 set of IP addresses.
5. We then set this on the firewall (again no down time was required here) with NAT and changing a few subnet’s
6. Now that we had a range that was being routed through the firewall we needed just needed to add them to the interfaces, however we wanted this to have alot more structure and organization for future growth, as the range before was fast becoming outgrown and as a consequence had lost any meaning to what what was and where it was located, so we needed to figure out a mapping plan.
7. Now that we had put down what server gets what IP(s) we were ready to start adding the additional internal range to our network interfaces.
8. Once this was done we needed once again to put pen to paper… Here we had to analysis the traffic usage for the last 12 – 6 months from clients, this told us who we can put on shared IP and of course who needs to go on a dedicated IP address.
9. After this was nutted out we then could go into IIS and then apply the new IP to each web site and host header.
10. Only after this was completed on all web servers could we start changing the DNS’s that we had control of
11. Once this was completed we ran a ping test on all the domains we had access to change to ensure nothing was missed.
12. Once we could ensure that all the DNS’s we had control of were completed, I had the task of coordinating who would contact which client, once I had created this list it was distributed to each member of helpdesk (and myself) and we went calling crazy. This persisted for about 2 solid months of constant calling to get the client to change the DNS. But in the end we got every client over to the new IP range
13. Configure the firewall, I undertook this task, because our previous firewall I had inherited when I got to Elcom, and the policy’s I did not agree with, I felt that they were far to open, so being the security conscious person I am, or like to be (most of the time) I really put alot of thought and effort into this firewall. I dislike lots of polices, as it slows down the firewall, its harder for the user to read and understand. So I wanted to condense it but yet has a very secure network, so I created groupings for everything I could think of, Production Web servers, Dev Web servers, ALL web servers, Mail servers, Services, the list goes on and on. But this really made it ALOT easier to put together the polices. With this Being that we could not test the firewall to its full potential before going live, I rechecked and rechecked, I also had Alan recheck the firewall settings. I also did put fail safe policies in place that were more open (these were not active at the time just there as a just in case)
14. Now that the firewall was done we needed to do some checking, so Alan setup a 3rrd party app that did monitoring on every single web site through our ADSL connection (external from Elcom) to ensure everything looked healthy from the outside. In addition to this Alan also setup another PC that had all of our external IP address added to the 1 interface of a server, where this would show a message explaining that maintainance was being completed
15. We then were ready to rock and roll, so after giving sufficient notice to our clients we changed the firewall over.

As you can see there is a considerable amount of preparation into the whole saga, but all in all it was a very smooth transition with minimal downtime for clients, and now we have a very clean secure firewall, which is now out showing huge network increases. This is mainly due to the fact that now the DMZ (web servers) and the Trust (Database Servers)  are on full gigabit links, as the firewall was out bottleneck previously.

We can see that we are now getting about 350MB/S speeds through transferring over the 2 networks, the response times of web sites have decreased by an average of 35milli seconds, Latency has decreased.

as a result of quicker and more secure environment I am now getting more sleep at home now

Serach functionality, now WM6 has a search function, which can crawl your PDA for what ever you are looking for similar to google desktop. To be honest i dont use this, it could be helpful with email, but i find it just takes more room up on my today screen.

WM6 is also said to have better or faster web browsing, really to be quite honest, i am still yet to see this… Although i do connect to my WIFI faster, this could be something that MS did that wasnt really noted.

Some other things they have done, as MSN is now called Messanger LIVE, this also has been intergrated into the WM6 release, and again this looks alot better.

other then what MS has released I have found that there is alot of other very, very nice applications that will make your life alot easier, the one i have found to be sensatioal, and also looks very tidy is the HTC home plugin v1.0.

Performance wise well its the same, maybe a little more stable but essentally the same thing with a few more tids and tads, Do i recommend the upgrade… yes i do, its worth it just for the new look, it really does look a whole lot better, you will only gain functionality.

If you are upgrading just remember to read the instructions very carefully, you could potenally BRICK your phone. There are ways of avioding this by using something called Hard-SPL-V7, I highly recommend using this before upgrading to any new rom. HARD SPL can be found here.

I do not recommend recommend any of this be attempted if you do not feel 100% sure about the whole proceedure of course.

Enjoy