Smartphone Developer Forum - "May not display properly" message during install

Author

"May not display properly" message during install

Todd Saylor

2006-04-14, 7:08 pm

Hi,

I've been testing under the new landscape emulator image, and I find that
whenever I install my app I receive this message: "The program you have
installed may not display properly because it was designed for a previous
version of Windows Mobile software". The app was compiled under eVC3 (for
WM2002 compatibility). I thought the answer would be to set
BuildMax=0xE0000000 in the .inf file, but that hasn't helped. I've had no
luck with VersionMax or PlatformMax settings either.

How can I prevent this message?

Thanks,
Todd

Bill Stelzel [MSFT]

2006-04-14, 10:08 pm

I'm able to disable this warning with the BuildMax = 0xE0000000 value. I'm
using the following inf file and if I uncomment the line "; BuildMax =
0xE0000000" I don't see this warning. If you want to try this inf file copy
it to a directory and create a file called Test1.txt then use the command
line "cabwiz Test1.inf" to create the cab file.

-------- Begin File -------------

[Version]
Signature = "$Windows NT$"
Provider = "Microsoft"
CESignature = "$Windows CE$"

[CEStrings]
AppName = "TestApp1"
InstallDir = %CE1%\%AppName%

[CEDevice]
; BuildMax = 0xE0000000

[DefaultInstall]
CopyFiles = Files.Common

[Files.Common]
"Test1.txt",,,0

[SourceDisksNames]
1 = ,"Common files",,""

[SourceDisksFiles]
"Test1.txt" = 1

[DestinationDirs]
Files.Common = 0,%InstallDir%

----- End File -------

Bill Stelzel [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

"Todd Saylor" <tsaylor@nospam.com> wrote in message
news:%23PHkMd%23XGHA.4248@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> I've been testing under the new landscape emulator image, and I find that
> whenever I install my app I receive this message: "The program you have
> installed may not display properly because it was designed for a previous
> version of Windows Mobile software". The app was compiled under eVC3 (for
> WM2002 compatibility). I thought the answer would be to set
> BuildMax=0xE0000000 in the .inf file, but that hasn't helped. I've had no
> luck with VersionMax or PlatformMax settings either.
>
> How can I prevent this message?
>
> Thanks,
> Todd
>

Todd Saylor

2006-04-15, 4:12 am

Thanks Bill for the reply! BuildMax certainly seems like the logical
solution. I should also mention that the new 320x240 emulator image is the
only one that has ever given me that warning message. I am using device
specific builds, so I had tried a CEDevice section but also added BuildMax
to the existing device specific sections, to no avail:

[CEDevice]
BuildMax = 0xE0000000

[CEDevice.x86]
BuildMax = 0xE0000000
ProcessorType=686

[CEDevice.ARM]
BuildMax = 0xE0000000
ProcessorType=2577

Could the problem be that I'm using the wce300\Smartphone2002 version of
CabwizSP.exe? I'm using that version on the assumption that it is necessary
for Smartphone2002 support.

Regards,
Todd

"Bill Stelzel [MSFT]" <bstelzel@online.microsoft.com> wrote in message
news:ePZlzXDYGHA.4988@TK2MSFTNGP05.phx.gbl...
> I'm able to disable this warning with the BuildMax = 0xE0000000 value. I'm
> using the following inf file and if I uncomment the line "; BuildMax =
> 0xE0000000" I don't see this warning. If you want to try this inf file
> copy it to a directory and create a file called Test1.txt then use the
> command line "cabwiz Test1.inf" to create the cab file.
>
> -------- Begin File -------------
>
> [Version]
> Signature = "$Windows NT$"
> Provider = "Microsoft"
> CESignature = "$Windows CE$"
>
> [CEStrings]
> AppName = "TestApp1"
> InstallDir = %CE1%\%AppName%
>
> [CEDevice]
> ; BuildMax = 0xE0000000
>
> [DefaultInstall]
> CopyFiles = Files.Common
>
> [Files.Common]
> "Test1.txt",,,0
>
> [SourceDisksNames]
> 1 = ,"Common files",,""
>
> [SourceDisksFiles]
> "Test1.txt" = 1
>
> [DestinationDirs]
> Files.Common = 0,%InstallDir%
>
> ----- End File -------
>
> Bill Stelzel [MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Todd Saylor" <tsaylor@nospam.com> wrote in message
> news:%23PHkMd%23XGHA.4248@TK2MSFTNGP05.phx.gbl...
>
>

Todd Saylor

2006-04-19, 10:03 pm

After further investigation I believe I can answer the rest of my question.
The "BuildMax = 0xE0000000" .inf file setting is indeed what is needed here,
but apparently the Smartphone 2002 version of CabwizSP.exe does not support
this. Once I switched to the version of CabwizSP in wce420\Smartphone
2003\tools, I no longer received that message.

Thanks!

"Todd Saylor" <tsaylor@nospam.com> wrote in message
news:%23QHfzKGYGHA.4424@TK2MSFTNGP05.phx.gbl...
> Thanks Bill for the reply! BuildMax certainly seems like the logical
> solution. I should also mention that the new 320x240 emulator image is
> the only one that has ever given me that warning message. I am using
> device specific builds, so I had tried a CEDevice section but also added
> BuildMax to the existing device specific sections, to no avail:
>
> [CEDevice]
> BuildMax = 0xE0000000
>
> [CEDevice.x86]
> BuildMax = 0xE0000000
> ProcessorType=686
>
> [CEDevice.ARM]
> BuildMax = 0xE0000000
> ProcessorType=2577
>
> Could the problem be that I'm using the wce300\Smartphone2002 version of
> CabwizSP.exe? I'm using that version on the assumption that it is
> necessary for Smartphone2002 support.
>
> Regards,
> Todd
>
> "Bill Stelzel [MSFT]" <bstelzel@online.microsoft.com> wrote in message
> news:ePZlzXDYGHA.4988@TK2MSFTNGP05.phx.gbl...
>
>

Sponsored Links