Besides the usual welcome comments and suggestions, there are two areas in this version that have had significant changes and may have broken things on some modems, so I'd appreciate feedback on these, preferably by email.
The first is USSD commands, I added a decoder to handle the encoding scheme used by an MTN E1750 modem, similar to that used by an E220 with Netcom Norway firmware 11.313.02.00.01, but not identical. My concern is that it may have broken USSD decoding for other modems. If you now see garbled USSD responses that previously worked, please mail me your modem make, model and firmware revision, your network operator (MTN, Vodacom, Cell-C, etc), whether you are on pre-paid or contract and what the command you sent was that resulted in the garbled response.
The second is "Negotiated QoS", previously known as "Assigned Profile". Previously MDMA used to check for, and remove offsets (a constant added value) from these values. I first found offsets with the E272 firmware 11.304.08.00.00. This was subsequently "fixed" in E272 firmware 11.415.05.00.00. The offset detection and removal has now been removed in order to accommodate new modems, like the E1820, which are able to negotiate speeds up to 21Mbps. If you now see nonsensical Qos values, please email me the details as requested above along with the values you see in the last release of MDMA.
MDMA's GUI is now in a new "landscape" orientation optimized for netbook displays, thanks to Terencek's polite reminders. I have taken a page out of Vodacom's book and forced the new version upon you, if you want the old "portrait" orientation back, there is a command line switch you can use. Would the mod oblige with a poll so those that feel strongly enough can vote on which orientation remains in the next release please?
Lastly, I have replaced the unused Cell Description field with an SNR (signal to noise ratio) display for the Huawei modems that support this feature. You don't have to do anything, if you modem supports it, you see numbers here, if not, you won't. At this stage I'm not entirely sure of what these values represent, but if you're interested have a read
here.
In order to work around the problem of the E1820 ignoring the AT to command to deactivate all PDP contexts (i.e. disconnect from the internet) from the 3gpp specification, MDMA now uses Windows RAS to hang up the connection.
The down side of this is
you must have a RAS entry named 'MDMA'. The easiest way to do this is to create a copy of the one created by your other dashboard.
Failure to do this will result in the following error when using the 'Connect' button in MDMA:
CODE
Cannot load dialog.
Error 623: The system could not find the phone book entry for this connection.
On the up side though, if you edit the properties of your 'MDMA' RAS entry and
uncheck 'Prompt for name and password, certificate, etc,', 'Include Windows logon domain' and 'Prompt for phone number' in the Options tab,
MDMA will now connect with only 1 click.