RIM comes through, very responsive!
Category BlackBerry Domino RIMAwaiting me this morning, not 10 hours after my last post (modified on request for legal purposes):
Hello Mr. Novak,
I came across your recent blog post at http://www.lotusrockstar.com/blog/robblog.nsf and wanted to reach out to you to let you know how we’re planning to address the concerns you raised. I also want to thank you for raising this, though we always prefer it to be sent to us directly J I read Domino / BES blogs frequently and they can be a good source of finding ways to make our product better.
One of the tasks we’ve focused on recently is making the Installer smoother and easier. Other than the BlackBerry Smartphone, the BlackBerry experience often starts with the Installer so having a high success rate is vital for RIM.
I’ve submitted a request to our development team to implement these changes:
1. When launching the MR installer, the initial welcome screen will advise the user that the original install files are required. This will likely be on the ‘This setup program will install the Patch for …..” screen.
2. If the files cannot be located, the error returned will be more indicative of the cause. Rather than reporting “Please run setup.exe to apply this maintenance release”, it will return something similar to, “The ‘BlackBerry Enterprise Server.msi’ file cannot be located. Please browse to the folder containing the original install files and click OK’. A browse feature would be included to permit the user to navigate to the folder where the install files are stored.
If you are interested in following the progress of this request, let me know and I can keep you updated.
Regarding the availability of MR3, it is scheduled for public release around January 5th 2009.
One thing I would like to do is verify the condition that caused your BES to become unstable is actually the issue resolved in SDR237069. I hope this won’t cause too much of an inconvenience for you – I would only need a couple of hours to verify. If you can supply me with the NSD(s) from the day it crashed I can check the stack trace to see if SDR237069 was indeed a factor. You can reply back to this email with the NSD attached (it should be less than 1MB).
...
I will be out of the office for the rest of today, but I’ll be back in tomorrow.
Please let me know if you have any questions
Thanks,
....
....
Research In Motion, Limited.
+++++++++++++++++++++++
And the better news, so far so good on MR2.
Comments
Kudos to RIM for hiring people who "have their shit together".
Posted by Devin Olson At 07:32:27 AM On 12/26/2008 | - Website - |