[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
We have an IT department, and I take your point, but they are pretty much engaged on other tasks—supporting a handset that gets e-mail isn’t one of their primary responsibilities, nor really should it be.

Yes, we can afford spares and Yes we can afford warrant exchanges, but our guys bought the unlocked devices so they could use the best regional carrier.

I’ve read the Wiki file. I installed the cab file before (before the SD card slot on my device blew out on a restore) and it didn’t work. Reading your instructions here, it still seems unclear to me.

In the directions you state:

>>>>>>You have to move the following files from \windows directory to a temporary location before installing the cab.

CallerID.dll

DisplayCID.dll

IA_CID_StartUp.exe

IA_CID_StartUp.lnk (From /windows/startup)

IACIDSync.dll

iacontacts.dll

After re-installation, change all the dll files in the temporary location to txt file. Softreset. You can then delete these files in temporary location.<<<<<<

* sigh * Ok. Let’s take it a step at a time.

I’ve read the Wiki, but I don’t see in there where to get the file explorer software you describe. Is it free? Will it screw up the ROM to use it?

Assuming I can locate all of the files you list above, where do I move them too? Is a generic folder on the SD card ‘temporary’ enough?

Those files all look pretty essential. What constitutes a ‘temporary’ place? Will a new folder on the SD card work for that purpose? Then how do I change them to txt files from dll files when I move them? Is holding the stylus on them, and cutting and pasting them into the SD card temporary folder sufficient or does this need to be done through activesync?—will just changing the file extension work to change them from dll files to txt files?

OK, so let’s say I’ve moved the listed files to the SD card ‘temp’ folder. I’ve changed the extension from dll to txt and I now have the cab file you linked to and I have dropped it into the Windows/program files folder. I now reset the device. Won’t I get errors because I just got rid of all of these files and dlls the device needs?

What is the order of 1) moving files, 2) renaming the moved files 3) installing the cab 4) what do you mean by ‘reinstallation’? Does that mean tapping the cab file of the caller id 1.02 dll file in the program storage folder or another folder (Is there a specific place where it should be)?

I don’t mean to be dense, but these instructions don’t help because you take for granted some things I don’t know.

The point is my IT department doesn’t want to support cell phones that get e-mail—they want to outsource that or simply exchange the broken part or give the poor guy with a broken device a backup file to restore that’ll work. With the TREO (even though I hate that device) no matter what is wrong (unless the hardware is hosed) I can have them load a file form the network to the SD card, restore and re-provision the goodlink license in minutes.

I take your point, but there is just no reason why a ROM upgrade should hose the device. Especially when the company you bought it from sends you an e-mail telling you to upgrade it.

Yes, it’s frustrating, but the fact remains, we don’t want to hire consultants or extra IT people whose sole job it is to tweak our cell phones (that ought to work).

I can’t expect that many people to go through this sort of thing, and I can’t expect our Oracle and Windows help desks to be customizing extended ROM versions on Win mobile devices. It just shouldn’t be that hard. I understand what you’re saying, but the tree VPs who are using this device do so as a test. So far, HTC is losing because they happened to get two guys who are on T-mobile and one on Verizon. The Verizon guy is happy. All the t-mobile guys have stopped using the device and gone back to their original dedicated good link device and cell phone because of the problems. That’ll never pass muster. Hey, it’s only money. If HTC doesn’t want to support the device on T-mobile, that’s cool, but it’s kind of a shame. I strongly feel this is the device we need, but if it consumes days and weeks and months during which mobile executives are out of communication, well, that’s a deal breaker. So far, I haven’t seen a single step by step walk through for fixing this, and HTC being completely out of motherboards and having all of their shipment arrive and fail test is not really a good sign—inventory management is a pretty basic expectation.