creating an Install
-
I am trying to create an install program to run on the desktop that installs the cab file automaticaly into the pocket pc. If I manually put the cab file into the pocket PC then the program runs fine. But when I try to make an install using ezsetup 2.0 I get this error
My_Test does not support the connected device typ. Application Manager will make the application available for installation when the supported device type is connected.This is what I have in the .ini file[CEAppManager] Version = 1.0 Component = My Application [My Application] Description = My test application Uninstall = Rod's PCS TEST CabFiles = My_Test.cabCan anyone see what is wrong? I I am trying to install it to a toshiba pocket pc E310. As I said if I manually put in the My_test.arm.cab file into the PPC It works fine. HELP PLEASE!! Thanks alot guys, Rodney -
I am trying to create an install program to run on the desktop that installs the cab file automaticaly into the pocket pc. If I manually put the cab file into the pocket PC then the program runs fine. But when I try to make an install using ezsetup 2.0 I get this error
My_Test does not support the connected device typ. Application Manager will make the application available for installation when the supported device type is connected.This is what I have in the .ini file[CEAppManager] Version = 1.0 Component = My Application [My Application] Description = My test application Uninstall = Rod's PCS TEST CabFiles = My_Test.cabCan anyone see what is wrong? I I am trying to install it to a toshiba pocket pc E310. As I said if I manually put in the My_test.arm.cab file into the PPC It works fine. HELP PLEASE!! Thanks alot guys, RodneyRodney I'm not sure how ezsetup 2.0 works, but the .ini file that CE App Manager is the same that is generated by the steps in the MSDN article for this subject at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/netcfdeployment.asp. Having just finished creating one of these my guess for you is that you need to generate Cab files for multiple files processors and reference those in your .ini file. The steps for creating those files is referenced under the "BuildCab.bat" section and who to list them in the .ini is under the "Setup.ini File" section of the MSDN Article above. FYI, here is what the setup.ini for my setup looks like:
[CEAppManager] Version = 1.0 Component = App [App] Description = ToDoList Viewer 1.3.0. CabFiles = ToDoListViewer_PPC.X86.CAB,ToDoListViewer_PPC.ARM.CAB,ToDoListViewer_PPC.ARMV4.CAB,ToDoListViewer_PPC.MIPS.CAB,ToDoListViewer_PPC.SH3.CAB,ToDoListViewer_PPC.WCE420X86.CABHope this helps. Thanks, Kyle -
Rodney I'm not sure how ezsetup 2.0 works, but the .ini file that CE App Manager is the same that is generated by the steps in the MSDN article for this subject at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/netcfdeployment.asp. Having just finished creating one of these my guess for you is that you need to generate Cab files for multiple files processors and reference those in your .ini file. The steps for creating those files is referenced under the "BuildCab.bat" section and who to list them in the .ini is under the "Setup.ini File" section of the MSDN Article above. FYI, here is what the setup.ini for my setup looks like:
[CEAppManager] Version = 1.0 Component = App [App] Description = ToDoList Viewer 1.3.0. CabFiles = ToDoListViewer_PPC.X86.CAB,ToDoListViewer_PPC.ARM.CAB,ToDoListViewer_PPC.ARMV4.CAB,ToDoListViewer_PPC.MIPS.CAB,ToDoListViewer_PPC.SH3.CAB,ToDoListViewer_PPC.WCE420X86.CABHope this helps. Thanks, KyleWhat are you using to compile the programs for the ARMV4,MIPS,SH3,WCE420X86 formats, I am using the Embedded Visual C++ 3.0 and I can only find options for compiling for the .ARM and for the .x86 platforms. Is there something that I have to change or is that all that is available in the 3.0 version? Thanks Kyle for the feedback. Rod
-
Rodney I'm not sure how ezsetup 2.0 works, but the .ini file that CE App Manager is the same that is generated by the steps in the MSDN article for this subject at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/netcfdeployment.asp. Having just finished creating one of these my guess for you is that you need to generate Cab files for multiple files processors and reference those in your .ini file. The steps for creating those files is referenced under the "BuildCab.bat" section and who to list them in the .ini is under the "Setup.ini File" section of the MSDN Article above. FYI, here is what the setup.ini for my setup looks like:
[CEAppManager] Version = 1.0 Component = App [App] Description = ToDoList Viewer 1.3.0. CabFiles = ToDoListViewer_PPC.X86.CAB,ToDoListViewer_PPC.ARM.CAB,ToDoListViewer_PPC.ARMV4.CAB,ToDoListViewer_PPC.MIPS.CAB,ToDoListViewer_PPC.SH3.CAB,ToDoListViewer_PPC.WCE420X86.CABHope this helps. Thanks, KyleWhat are you using to compile the programs for the ARMV4,MIPS,SH3,WCE420X86 formats, I am using the Embedded Visual C++ 3.0 and I can only find options for compiling for the .ARM and for the .x86 platforms. Is there something that I have to change or is that all that is available in the 3.0 version? Thanks Kyle for the feedback. Rod
-
What are you using to compile the programs for the ARMV4,MIPS,SH3,WCE420X86 formats, I am using the Embedded Visual C++ 3.0 and I can only find options for compiling for the .ARM and for the .x86 platforms. Is there something that I have to change or is that all that is available in the 3.0 version? Thanks Kyle for the feedback. Rod
Rod Let me start of by saying that I am using C# .NET Compact Framework. I am using the Cab Wizard that is part of the Windows Mobile SDK 2003. It appears that this particular SDK is for EVC++ 4.0 and VS.NET 2003. There may be a version of the Cab Wizard that will work with your version of EVC or you may be able to update to EVC++ 4 (see the link on SDK page). I apologize if this doesn't help you at all. Thanks again, Kyle