Pages

Thursday, October 15, 2009

ActiveSync problems with cooked ROM's

I ran into an ActiveSync issue with my builded ROM's. When synchronizing with Exchange, the sync failed with the error code 80070008 or 8007000e. This means that the mobile device doesn't have enough free memory. However, my ROM's had at least 47MB of free memory. All seemed to be fine.

It turned out that I was using an old version of my OEM directory however I still used the newest SYS and EXT Packages. I downloaded the latest official Rhodium ROM from HTC, extracted it and used this OEM directory. Now my ROM was connecting fine with my Exchange server.

As you can see in my previous post I've released my 1st Beta DaxyROM release. I've also created a tutorial how you can create your own ROM.

Link to DaxyROM info.
Link to my tutorial.

DaxyROM

I've decided to create my own ROM for my HTC Touch Pro2 (a.k.a. Rhodium).
You'll see some updates on this on this blog as well.

Just a few minutes ago I released my first test build. If you would like to see what it is, what it can do and if it's something for you, just follow this link: http://bit.ly/2kRf7y

DaxyROM-v0.1e is out there now. When it's stable enough I will release v1.0 and above :)

Tuesday, August 4, 2009

Down for everyone of just me?

Everybody ran into this at least once in his life. You can't access a website and you're wondering if it's just your internet connection or an outage at the website.

You can easily check this at the website http://downforeveryoneorjustme.com/

Change the default telnet client in Windows

I just keep on forgetting what to change to get this working. As I don't want to search everytime I'm just posting a shameless copy from Rene's ICT Notepad.

Enable handling of telnet://hostname:port/ URLs on the command line. With this feature, you can now set PuTTY as the default handler for Telnet URLs

If you run the Registry Editor (Start->Run->regedit.exe) and set the value in:
HKEY_CLASSES_ROOT\telnet\shell\open\command to be: "\path\to\putty.exe" %1
(with the full pathname of your PuTTY executable), you should find that clicking on telnet links in your web browser now runs PuTTY.

This is confirmed to be working for Chrome on Windows 7.

Changes to my blog - A New Start

It was about time I started posting something again. My last post was over a year ago, this can't be the idea of a Blog ;)
I decided to change the blog a bit around. I will no longer be trying to pretend I'm a writer/journalist who can create stories which interests everybody.

As of today I will start posting small stories. Things I find interesting. Things I need in my daily life, etc. First one will be how to change the Windows registry so Putty is my default telnet application.

Hope you like the new content. Otherwise we'll meet again somewhere else :D

Wednesday, May 7, 2008

Funny: Ethereal to Wireshark Migration Guide

Someone just pointed me at the Ethereal to Wireshark migration guide posted at http://www.wireshark.org/migration.html

This is a shameless copy of this excellent (and funny) guide:



Migrating

Migrating from Ethereal to Wireshark is a long and arduous process. A typical migration project requires the following resources:

* 1 (one) project manager (PMP certification preferred)
* 1 (one) assistant project manager
* 2 (two) pirate hats
* 2 (two) system administrators
* 1 (one) duck
* 2 (two) network administrators
* 4 (four) support staff
* 2 (three) bags of hammers

If you allocate full-time staff to the migration, it can take as little as six weeks for preparation and planning, and four weeks for the migration itself. Past migrations have resulted in some maiming and blood loss. A recent survey of human resources directors found that the amounts were within acceptable tolerances.

The complete migration procedure is detailed below:

1. Place the pirate hats near the project manager, assistant project manager, and system administrators. Allow time for them to start fighting over the hats (about 3.5 seconds).
2. Place the duck on top of a core switch and allow it to nest.
3. Casually mention to a support person that you heard a quacking noise near the data center. Allow time for word to get to the network administrators, and for the support staff to gather together to watch the spectacle.
4. To ensure that you're not disturbed, keep the bags of hammers nearby and maintain a stern expression.
5. Uninstall Ethereal.
6. Install Wireshark.


Note: Steps 5 and 6 should take about three minutes.

Tuesday, May 6, 2008

Funny story: OSPF

While working in a Support Organization of a networking company, I come across a lot of funny and interesting stories. Here is one of them.

One of our customers, who's name we of course will not mention, opened a Support case. He complained that his routers were suffering from a high CPU load and thus the routing table was not up-to-date. Very quickly we came to the thought that is had to be because of OSPF not updating the hardware table quickly. At some point I asked him how many OSPF routers he had in the Area. His answer was 1500!!!

One might say that 1500 routers in 1 OSPF area can occur in large networks. This sure can happen, but then it is time for a redesign of the network. Let me explain why this isn't a good idea.

OSPF calculates the shortest path for each route. This means that if 1 router goes down, it will need to re-calculate the shortest path. With 1500 routers in 1 Area it will result in a lot of OSPF changes and thus a lot of re-calculations. Add all packets sent to the OSPF All-Routers Multicast group and you will have a swamped CPU.

What would be a good number of routers in 1 Area then? There is no clear answer for that. When asking around a number between 200 and 250 seem to be common. Keep in mind that there are routers with a stronger CPU and routers with a smaller CPU (mostly elderly routers). Remember that even the smaller sized routers need to be able to update their tables, otherwise they can choke the rest of the network. If they can't keep up with the rest, place them in a Stub Area or replace them.