call SMS functions from driver

Hi All,

Can I use SMS functions(smsopen, SendSmsMessage...) in my driver? I am 
developing a driver, I called sms functions from my driver, however it 
return the fail code - 120 which means

      120 This function is not valid on this platform. 
ERROR_CALL_NOT_IMPLEMENTED


The the functions I called in a normal application, it works fine. Can 
anyone tell me whether I can not use SMS function calls in driver?

-- 
Avex 

Sms messages are supposed to return HRESULTs, not Win32 error codes.  Are 
you getting E_NOTIMPL?  If you are really getting 
ERROR_CALL_NOT_IMPLEMENTED, are you getting it as a return code from 
SmsOpen/SendMessage, or by calling GetLastError?  If calling GetLastError, 
you shouldn't be calling that.

S_OK (0) indicates success.  Other HRESULTs should indicate the specific 
error (don't call GetLastError).

Is it SmsOpen or SmsSendMessage that is failing?

Are you getting SMS_E_RECEIVEHANDLEALREADYOPEN from SmsOpen?  In device.exe 
space, there may already be a driver that has it open.  I think the MS Sms 
receiver is in a different process, but I'm not certain about that.

-- 
Michael Salamone [eMVP]
Entrek Software, Inc.
www.entrek.com

I work on 'Dopod 818' pocket pc phone which has SMS functions 
supported(sms.dll). On
this device I wrote an SMS application, it runs well. However, the same SMS 
function I used cannot be run in my driver application.

The error code SmsOpen gived is  E_FAIL(80004005), I use GetLastError it 
returns ERROR_INVALID_HANDLE(6)  and ERROR_CALL_NOT_IMPLEMENTED(120).

What does it mean E_FAIL?


No,
Everytime I am going to try my driver, I tried a normal SMS application 
which I wrote to ensure that SMS is not occupied and close it before trying 
my driver.

I just want to ensure that whether if I can use SMS functions in driver?

Again, don't call GetLastError().  It is incorrect to do so, and the code it 
returns does not relate to the call to SmsOpen.

Read the doc about SMS_E_RECEVEHANDLEALREADYOPEN.  It says SmsOpen will 
succeed the first time called in each process, so you open multiple times 
from multiple processes.  But only one time in each process.  Since you are 
a driver and presumably loaded into device.exe, it is possible that another 
driver (an MS driver?) already called SmsOpen in that process.  Subsequent 
attempts to open would fail.

E_FAIL is a general error that is not at all informative.  It means an error 
occured, but it conveys no clue as to what the error is.  It should be 
banned from use (it should have never been invented).  It's unbelievable to 
me that it's still in use.

-- 
Michael Salamone [eMVP]
Entrek Software, Inc.
www.entrek.com

I have already check SMS_E_RECEVEHANDLEALREADYOPEN for SmsOpen, however it 
never happened.

 hr = SmsOpen (SMS_MSGTYPE_TEXT, SMS_MODE_RECEIVE, &smshHandle, 
&hReadEvent);
 if (hr == SMS_E_RECEIVEHANDLEALREADYOPEN)
 {
    ....  // never came into this subroutine
 }
 else if (hr != ERROR_SUCCESS)
 {
   ....
 }


I can't have enough information about E_FAIL, hence I guess there should be 
something I need when using SMS in driver. The same function works well in 
applications I wrote.