Guest NRoodyn Posted December 3, 2003 Report Posted December 3, 2003 SendSMS Beta 1.5 available. Finally I have managed to get the time to work on some more features for SendSMS. You can now download the beta of SendSMS 1.5. If you download it then please be aware that it is a beta, I am interested in hearing all your feedback so I can get any issues sorted as soon as possible and release version 1.5. The 2 main new features in this version are the ones I had the most requests for: 1. Delivery receipt request 2. Sent messages added to an Outlook Folder Please note you will have to uninstall the previous version before you can install this new version. http://www.sendsms.roodyn.com/SendSMSNews.htm regards Dr. Neil SendSMS News
Guest yoos Posted December 3, 2003 Report Posted December 3, 2003 Sounds great! Your site says you need .NET Framework Library 1.1 installed on your computer... Any ideas where I can get this? Thanks!
Guest NRoodyn Posted December 3, 2003 Report Posted December 3, 2003 Try this URL http://msdn.microsoft.com/netframework/tec...et/default.aspx Get the .NET Framework regards Dr. Neil
Guest blewer Posted December 3, 2003 Report Posted December 3, 2003 Hope you have a fast internet connection (23 mbs) :lol:
Guest FrankyG Posted December 3, 2003 Report Posted December 3, 2003 Still not working for me :cry: When I click the 'To' button I get the following error. When Choose to continue, I get the same error (although I didn't read through it all to make sure it was identical!) a further two times. Then the address list box appears, but the phone numbers are mapped to the wrong names. If I manually type in a phone number, it sends the sms perfectly. I just did a test on my own number. Any Ideas?? ___________________________________________________ See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam) at System.Windows.Forms.NativeWindow.DefWndProc(Message& m) at System.Windows.Forms.Control.DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ListBox.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll ---------------------------------------- SendSMS Assembly Version: 1.1.1308.31085 Win32 Version: 1.1.1308.31085 CodeBase: file:///C:/Program%20Files/SendSMS/SendSMS.exe ---------------------------------------- System.Windows.Forms Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll ---------------------------------------- System Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- System.Drawing Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll ---------------------------------------- Interop.SMARTSMSLib Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/SendSMS/Interop.SMARTSMSLib.DLL ---------------------------------------- Microsoft.VisualBasic Assembly Version: 7.0.5000.0 Win32 Version: 7.10.3052.4 CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll ---------------------------------------- Microsoft.Office.Interop.Outlook Assembly Version: 10.0.4504.0 Win32 Version: 10.0.4504 CodeBase: file:///C:/Program%20Files/SendSMS/Microsoft.Office.Interop.Outlook.DLL ---------------------------------------- CustomMarshalers Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/windows/assembly/gac/custommarshalers/1.0.5000.0__b03f5f7f11d50a3a/custommarshalers.dll ---------------------------------------- ************** JIT Debugging ************** To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog. -------------------------------------------------------------------------
Guest gawain Posted December 4, 2003 Report Posted December 4, 2003 A great App which I am using on my E200. I don't get anything in Outlook though??
Guest JingJing Posted December 5, 2003 Report Posted December 5, 2003 Same error here... See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Interop.Outlook._MailItem.set_BodyFormat(OlBodyFormat BodyFormat) at SendSMS.SendSMS.ItemSent(String message, String number) at SendSMS.SendSMS.Send_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.onclick(EventArgs e) at System.Windows.Forms.Button.onclick(EventArgs e) at System.Windows.Forms.Button.onmouseup(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll ---------------------------------------- SendSMS Assembly Version: 1.5.1432.17232 Win32 Version: 1.5.1432.17232 CodeBase: file:///C:/Program%20Files/SendSMS/SendSMS.exe ---------------------------------------- System.Windows.Forms Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll ---------------------------------------- System Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- System.Drawing Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 7.0.5000.0 Win32 Version: 7.10.3052.4 CodeBase: file:///c:/winnt/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll ---------------------------------------- Microsoft.Office.Interop.Outlook Assembly Version: 11.0.0.0 Win32 Version: 11.0.5530 CodeBase: file:///C:/Program%20Files/SendSMS/Microsoft.Office.Interop.Outlook.DLL ---------------------------------------- CustomMarshalers Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/assembly/gac/custommarshalers/1.0.5000.0__b03f5f7f11d50a3a/custommarshalers.dll ---------------------------------------- Interop.SMARTSMSLib Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/SendSMS/Interop.SMARTSMSLib.DLL ---------------------------------------- System.Xml Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.573 CodeBase: file:///c:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog. this update would be great indeed. Thanks.
Guest NRoodyn Posted December 5, 2003 Report Posted December 5, 2003 Firstly a huge thanks to you guys for testing this and giving me feedback, its really useful. A few of you are experiencing issues. I was kind of expecting this. You can always uninstall and roll back to the previous version which is still on my site: www.SendSMS.Roodyn.com The long initialisation and failure detect if the phone is connected has been noted. This seems to be an intermittent bug (the worst kind) and I am investigating. I have not seen or been able to replicate the exception being thrown. I fear it maybe only on certain operating systems so if you post this issue to me can you please include the OS you are using. BTW: I am testing this on WinXP Pro. The issue with the TO: button not functioning correctly has been reported in the previous version also and seems to be related to strange characters in a contacts mobile phone number entry in Outlook. Again I am try to replicate this one without much success. regards Dr. Neil [email protected]
Guest NRoodyn Posted December 8, 2003 Report Posted December 8, 2003 Thanks for all the feedback guys. I have fixed some issues and released SendSMS 1.6. I have also released ReadSMS to let you read your SMS messages on your PC screens. Point your browser at: www.Smartphone.Roodyn.com to find out more Of course feedback welcomed regards Dr. Neil
Guest The Futures Bright Posted December 8, 2003 Report Posted December 8, 2003 Still no go here with my E200 and ActiveSync 3.7.1. All i get is an error saying, FAILED TO INITIALIZE SMARTPHONE DEVICE. Please ensure you have your phone connected to the computer and ActiveSync is installed and running. I have! :cry: PS I have an unlocked phone and 1.1 .Net installed. I got exactly the same error with version 1.5 of SendSMS :cry:
Guest zeta101 Posted December 8, 2003 Report Posted December 8, 2003 i get the same error as the futures bright, im using an e100, and the phone is definatly connected cos ive done a syc right before and it syncs without errors or anthing...i got the latest version from your site a few mins ago...
Guest FrankyG Posted December 8, 2003 Report Posted December 8, 2003 Same error for me - FAILED TO INITIALIZE SMARTPHONE DEVICE. Please ensure you have your phone connected to the computer and ActiveSync is installed and running. I also have an unlocked phone Mpx200 and 1.1 .Net installed. Activesync 3.7.1 WinXP pro
Guest thornton Posted December 8, 2003 Report Posted December 8, 2003 Same error for me as The Futures Bright, zeta101 and FrankyG. I am using an app unlocked original SPV. I have .NET Framework 1.1, and ActiveSync 3.7.1 (Build 3244) installed, and I am running Windows 2000 Professional with every possible update and patch on it. I was previously running SendSMS version 1.1 which worked fine for me. If I uninstall version 1.6 and roll back to that 1.1, (fortunately!) 1.1 still works. Hope this can be resolved, as SendSMS is very useful, and the new features in version 1.6 would be great if I could get them to work. Would also love to try out ReadSMS, as it sounds good too (but can't do that until I can get new version of SendSMS to work as version 1.1 of SendSMS is, as I understand it, incompatible with ReadSMS).
Guest thornton Posted December 8, 2003 Report Posted December 8, 2003 Sorry to reply to my own post, but I've just tried installing version 1.6 onto a different PC. The software set-up is in every respect identical to the first PC mentioned in my previous post. The only difference is that the hardware is higher specified - faster processor, more RAM etc. The result? Precisely the same error as with the first machine. Once again, rolling back to version 1.1 of SendSMS gets it working again.
Guest NRoodyn Posted December 8, 2003 Report Posted December 8, 2003 Thanks guys, obviously still some issues to iron out here. It works fine for me, which is why I released it. Is everyone having the same issue, or have some of you managed to get it working fine? I will keep on trying to find out what is causing these problems over the next few days. regards Dr. Neil
Guest NRoodyn Posted December 9, 2003 Report Posted December 9, 2003 Not as far as I am aware! www.Smartphone.Roodyn.com regards Dr. Neil
Guest NRoodyn Posted December 12, 2003 Report Posted December 12, 2003 Some more time and effort later and I have produced version 1.8 of SendSMS and version 1.2 of ReadSMS, they are now released. These releases address several of the more commonly reported issues and provide additional error logging to help more quickly resolve other outstanding issues. To download them go to www.Smartphone.Roodyn.com regards Dr. Neil
Guest edmund Posted December 12, 2003 Report Posted December 12, 2003 Hi, I've downloaded and installed the latest version of both apps and I'm afraid to say that I'm getting the same problems as before. Spec is: Windows 2000 with .Net 1.1, ActiveSync 3.7.1 and a MPx200 phone. ActiveSync is working fine but SendSMS reports: FAILED TO INITIALISE SMARTPHONE DEVICE ReadSMS fails with: System.NullReferenceException: Object reference not set to an instance of an object. at ReadSMS.ReadSMS.UpdateMsgList() at ReadSMS.ReadSMS.readTimer_Elapsed(Object sender, ElapsedEventArgs e) I hope this helps... Edmund
Guest thornton Posted December 12, 2003 Report Posted December 12, 2003 First of all, many thanks for your great efforts in developing this very useful program. I have now tried the new versions of both programs. Sadly, like edmund, I cannot get either of them to work. The software set-up of my machines is set out in my earlier posts. Hoping that it might be of assistance if I tell you what errors I am getting: I normally log on to my Win2k machine as a Power User. If I do that, then with SendSMS 1.8, it appears to get the contacts list initialised alright, and then when it tries to initialise to the Smartphone after that, I simply get the "FAILED TO INITIALIZE SMARTPHONE DEVICE" dialog as before. Starting ReadSMS 1.1 whilst I am a Power User originally produced an error, before it had drawn its program window, informing me that it had raised a .NET security exception due to the fact that it was making an unauthorised attempt to access the Registry. It said that I would have to amend my .NET security policies in order for it to be allowed to achieve that access. Sadly, I did not copy the full Detail error message (and I now cannot reproduce it - see below), so I am only able to give you the gist of it. It then occurred to me that the applications might behave differently if I was logged on with full local administrator rights. So I logged out, gave my normal (Power User) logon additonal rights as member of the local Administrators group, and then logged back on again as that 'upgraded' user. The results of this experiment were: On starting SendSMS, it behaved exactly as it had when I was Power User - no change at all. ReadSMS, on the other hand, did behave diferently: This time, it started up with no apparent complaint, and presented me with its regular program window. Then after about 5 to 10 seconds, without me doing anything further, it generated this dialog: "An unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will shut down immediately. Object reference not set to an instance of an object." On pressing the Detail button, it gave me the error in the attached text file. I then removed administrator rights from my usual logon, and tried all over again: SendSMS: No change there. ReadSMS: No .NET security exception message on startup any more; rather, it now behaves in the same way as it did when I used it whilst logged on with admin rights (described above - i.e. starts up apparently OK, then produces 'Object reference not set' error dialog as already detailed). I hope this has been of some debugging assistance. If I can provide any more detailed assistance with information that might help you root out the problem, then please feel free to ask me. Meanwhile. I'll revert back to using SendSMS 1.1 for a while, as that works fine on my machine (and is very useful).error.txt
Guest NRoodyn Posted December 12, 2003 Report Posted December 12, 2003 Wow, thanks for that. It is great to get such full feedback. It really gives me something to work with. Do you think you could tell me if there are any messages reported in your Application Event Log? The new version does provide event logging in order to help track down some of the issues you guys are having. I begin to wonder if it could be an issue with software versions for the phone. I havent upgraded the software on my phone for a while. There are certainly a few of you with these hard to track down issues and I'm trying to look at them over this weekend. regards Dr. Neil
Guest NRoodyn Posted December 13, 2003 Report Posted December 13, 2003 I have been asked to make SendSMS 1.1 available for those of you that are having issues with the new version. There is now a link on the SendSMS download page to both version 1.8 and the older version 1.1. Please be aware that version 1.1 is not compatible with any version of ReadSMS. regards Dr. Neil www.Smartphone.Roodyn.com
Guest The Futures Bright Posted December 13, 2003 Report Posted December 13, 2003 Version 1.1 installed ok here but on sending an sms i get "Failed to run process SMSSender" There appears to be an error sending the message, the error is "Unspecified Error" :cry: This is on my E200 :roll:
Guest grib Posted December 13, 2003 Report Posted December 13, 2003 Version 1.1 are working super, but 1.8 & read sms does not work at all for me and yes I deleted the old versions first, but i am looking forward to it does work so keep up the good work Neil
Guest briguy Posted December 16, 2003 Report Posted December 16, 2003 Neither SendSMS or ReadSMS can connect to my MPx200. I'm running on XP Pro with AS 3.7.1. Here are the errors reported by ReadSMS (from the Event Viewer): Failed to initialise Device Failed to Create connection and read SMS messages Failed to Load SMS messages locally This is followed by an exception dialog: System.NullReferenceException: Object reference not set to an instance of an object. at ReadSMS.ReadSMS.UpdateMsgList() at ReadSMS.ReadSMS.readTimer_Elapsed(Object sender, ElapsedEventArgs e) Have you considered adding SendSMS and ReadSMS to a workspace at www.gotdotnet.com? Then those of us that get these errors and have VS.NET (like me :lol: ) could help with the debugging.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now