On Sat, 2009-07-18 at 21:42 +0200, David Eriksson wrote: > Hi, > > Thanks for the great bug report! If you have the time, please report it > in the SourceForge tracker: > > http://sourceforge.net/tracker/?limit=10&func=&group_id=30550&atid=399601&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=&category=667878&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter
Sorry, I have no idea why I should file a bug for a resolved issue. > I have applied the patch, thanks! > > I'm thinking of moving version identification and affected offsets to > various data structures to a configuration file to avoid recompiling for > things like this. .. I would do following: If the version cannot be determined, print the whole 32-bit version field and ask the user to report it. Add an option to force unshield use specific version of the format. Stop using abort(). Instead, print a unique message (so that the condition can be identified) and exit with a non-zero error code. Thank you for maintaining unshield! Being a wireless developer, I often need unshield to unpack wireless drivers. This helps me determine the chipset of the hardware without buying it. Also, some drivers can be used with ndiswrapper. -- Regards, Pavel Roskin ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
