View Single Post
  #157 (permalink)  
Old 12-04-2007, 09:41 PM
tiermann's Avatar
tiermann
VIP Member
Offline
Threadstarter
Location: PA, USA
 
Join Date: Apr 2007
Posts: 815
Reputation: 3165
tiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to tiermann Send a message via Yahoo to tiermann
It's sounds like it's running into that problem because your OEM has an sms_providers.dll which is already part of the system. The system version is a module though which is basicly a dll broken down into parts in a folder named sms_providers.dll.

Solution for now, since Palm Threaded can't be redistributed anyway (i'm guessing you're just making this for yourself) would be to move the sms_providers.dll from your OEM to the Patches folder in the kitchen. Files in the patches folder have the ability to overwrite moduled versions of dlls, but OEM's do not, without some trickery.

Another solution is to rename the sms_providers.dll in your OEM to sms_providers_palm.dll and use your initflashfiles.txt to copy it over the original during first boot...
Code:
Directory("\Windows"):-File("sms_providers.dll","\Windows\sms_providers_palm.dll")
This works, but it's sloppy because the final result is that you have 2 copies of the file. Not recommended to do more than once per OEM or with large files.

Last edited by tiermann; 12-04-2007 at 09:48 PM.
Reply With Quote