When Binary Breaks Happens, Who Should Fix It?
Opinion April 4th. 2007, 7:27amSome of you may now know that I used to a Windows developer (not mobile version, but desktop one). The software that I have developed is still sold on the Internet although the volume has dropped significantly because I don’t maintain it any more.
Recently, I received massive amounts of emails from my customers. They are all complaining that my application does not work any more on Windows XP Service Pack 2 after latest security update 925902 (MS07-017) and security update 928843 (MS07-008). Each time, my application is launched, Windows XP complaints:
The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C:\Windows\System32\Hhctrl.ocx occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.
It affects not only my application, but others too, for instance Realtek HD Audio Control Panel. A binary breaks has happened in Windows XP Service Pack 2. Who should fix the problem? Microsoft or developer? For this specific case, Microsoft released a fix to their latest patch.
If we look at mobile world, especially Symbian OS, we have seen so many binary breaks. Even after Symbian and other manufacturers have promised for binary compatibility starting from version 9, this does not happen in reality. There are still some breaks on many different phones.
So, if something breaks on Symbian OS or UI variants, S60 or UIQ, who should fix it? Symbian (phone manufacturers) or third party developers?
Bonus Links
- Binary Compatibility - Is It Really Important? - from Antony’s Mobile Blog.
- Time to start taking good care of S60 backward compatibility - from Tommi’s Application Blog (S60).
- Application Compatibility - from SymbianExample.com.
One Response to “When Binary Breaks Happens, Who Should Fix It?”
Comments are disabled.
April 12th, 2007 at 1:08 am
“The system DLL user32.dll was relocated in memory…”
I just had this problem recently and had no idea what it is and the consequence. Now I know!!