We reported this to the author of the control some time ago, and have
not gotten a response. We will try again.

If that fails, we'll have to find someone else to fix this.

>Hi all.
>
>My application, runs correctly under a device with a Samsung ARM 
>920T processor and Windows CE 5.0 (The device does not response any 
>OS subversion number).
>
>Recently, I have purchased a new device with the same OS (Windows CE 
>5.0 Build 1400, a bit newer version of the OS) and the same 
>processor. I like it because it have a larger screen (five inches) 
>than the first one.
>
>The two devices have the "Core" version of the OS.
>
>I installed my application under the first device mentioned, using 
>the Basic.HPC_2577 installer.
>
>Now, under the same (aparently) OS and the same processor, I can't 
>be capable of have my application running.
>
>I was testing all the installers for ARM, making a hardreset before 
>of each test, with the same results:
>
>My application shows many errors because it can´t use any of the 
>controls included in NSBControls.dll, because the self-registering 
>does not run correctly.
>
>I was trying to registrate the DLL "manually" with regsvrce and 
>obtaining the same result, a error message that tells 
>that "DLLRegisterServer in nsbcontrols.dll failed".
>
>The same method under the first device runs fine.
>
>The same method applied to nscepicturebox.ocx runs fine on the new 
>device.
>
>The same method applied to MSCEFile.dll (from Microsoft runtimes for 
>evb 4) runs fine.
>
>I was trying to registrate the DLL avoiding the use of regsvrce. 
>I obtained a more detailed description using a different application 
>to registrate the DLL: "CoInitialize was not be called before of 
>DLLRegisterServer"
>
>I was trying to extract the keys created by the self-registrate 
>process on the first device, making a .reg file to import with 
>Tascal RegEdit in the new device, but my application says that could 
>not create non-visual control because IClassFactory could not be 
>obtained (err: 80040154).
>
>I suppose that the DLL can´t run correctly in this device, perhaps 
>because of some differences in coredll.dll or gwes.exe...   or...   
>bad luck...
>
>Someone can help me?
>Any ideas?????
>
>Thanks in advance.
>
>-David-
>
>
>
>
>
>
>
>------------------------------------
>
>Yahoo! Groups Links
>
>
>



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nsb-ce" group.
To post to this group, send email to nsb-ce@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/nsb-ce?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to