Re: WinCE 6.0 PNG Encoder by Paul
Paul
Fri Mar 28 14:49:42 PDT 2008
The Shared Source (capital letters), can be installed from the Windows CE
DVD. You had that option during installation. However, that does *not*
mean, of course, the you get every line of source for Windows CE. There's
no easy access to the source beyond what's in the Shared Source.
Paul T.
"j.l" <jl@discussions.microsoft.com> wrote in message
news:73ED7263-9664-4426-804D-EEECFF0EE596@microsoft.com...
> Thanks Paul for the response.
> I agree that the file it's trying to find is in my pc. Does CE need the
> extra shared source? where can i get those?
>
> well, reading datatype misalignment, I kind of figured it out. but Why
> would
> the same cf implementation works on CE5 but not on CE6? Am i missing
> something while making my image? what would that be?
>
> "Paul G. Tobey [eMVP]" wrote:
>
>> Well, not that it really means much, but ymzki is short for Yamazaki, the
>> code name for that version of Windows CE. As you know, if you think
>> about
>> it, the path to things that's stored in an EXE is the build source
>> location
>> *on the build system*. It has no idea where your files are going to be;
>> it's simply reporting the path, at compile time, of the file that
>> generated
>> the exception. So, for your case, c:\ymzki = c:\wince600. If you can't
>> find the source file based on that remapping, then it's not one of the
>> source files included in Windows CE (you did install the extra shared
>> source?)
>>
>> It sounds like one or more parameters you're passing to some API function
>> from your C# application (or maybe a structure that you're passing), is
>> wrong...
>>
>> Paul T.
>>
>> "j.l" <jl@discussions.microsoft.com> wrote in message
>> news:F97F5723-108C-417D-A6B7-0A36960F5692@microsoft.com...
>> >
>> >
>> > "Valter Minute" wrote:
>> >
>> >> =?Utf-8?B?ai5s?= <j.l@discussions.microsoft.com> wrote in
>> >> news:5F3D7E7B-EA09-472E-8896-D7F892030161@microsoft.com:
>> >>
>> >> > We are currently porting ce 5.0 application onto 6.0.
>> >> > working with png (32bit depth) file that reads without a problem
>> >> > but when we try to save as a file (bitmap.save()) the application
>> >> > crashes without further message.
>> >> >
>> >> > our build does include sysgen_imaging_pngencoder = 1 in the
>> >> > catagory item but somehow it does fail. all the other format;
>> >> > e.g. bmp, jpg, tiff, gif works.
>> >> > we think that while building the run-time image, it fails to
>> >> > include the pngencoder and it's missing from the image's registry.
>> >> >
>> >> > any help will be appreciated.
>> >>
>> >> Did you try to run you application on a debug build of Windows CE?
>> >> If the encoder is not present inside the OS you should get an error
>> >> return code, not an application crash.
>> >>
>> >> --
>> >> Valter Minute
>> >> www.fortechembeddedlabs.it
>> >> Training, support and development for Windows CE
>> >> (the reply address of this message is invalid)
>> >>
>> >
>> > Thanks for the response.
>> >
>> > When I run under debug mode, it looks for a symbol in
>> > c:\ymzki\private\gdiex\engine\imaging\png\libpng (exception in
>> > imaging.dll
>> > :
>> > 0x80000002: datatype misalignment)
>> > - more question arises, why c:\ymzki ?? shouldn't it be c:\wince600 ??
>> > even i directed to c:\wince600... it still doesn't find it and throws
>> > the
>> > same dialog box that states it will shut the application.
>> >
>> > application wrote in c# w/ cf2.0 sp2
>> > and i'm simply calling image.save("somestring",
>> > System.Drawing.Imaging.ImageFormat.Png)
>> >
>> > ---- debug output
>> > 544732 PID:400002 TID:3990136 Grow Gdi handle table from 512 to 576
>> > 553994 PID:3cc0146 TID:3990136 OSAXST1: >>> Loading Module
>> > 'imaging.dll'
>> > (0x956CBAA4) at address 0x406F0000-0x4079F000 in Process 'sample.exe'
>> > (0x955CF7EC)
>> > 554031 PID:3cc0146 TID:3990136 OSAXST1: >>> Loading Module 'zlib.dll'
>> > (0x956CBBDC) at address 0x401C0000-0x401D6000 in Process 'sample.exe'
>> > (0x955CF7EC)
>> > 575949 PID:400002 TID:3d70146 ERROR:
>> > C:\ymzki\private\winceos\COREOS\gwe\winmgr\wmbase\.\wbase.cpp line
>> > 1325:
>> > 575954 PID:400002 TID:3d70146 !bFound, etc.
>> > 584915 PID:3cc0146 TID:3d70146 Exception 'Data Abort' (4):
>> > Thread-Id=03d70146(pth=9541e540), Proc-Id=03cc0146(pprc=955cf7ec)
>> > 'sample.exe', VM-active=03cc0146(pprc=955cf7ec) 'SN9610.exe'
>> > 584918 PID:3cc0146 TID:3d70146 PC=407457e4(imaging.dll+0x000557e4)
>> > RA=407457d4(imaging.dll+0x000557d4) SP=1a01f454, BVA=00000000
>> > 584965 PID:3cc0146 TID:3d70146 RtlDispatchException: returning failure.
>> > Flags=0
>> > 585033 PID:3cc0146 TID:3d70146
>> > Unhandled exception 80000002:
>> > 585034 PID:3cc0146 TID:3d70146 Terminating thread 9541e540
>> > 585060 PID:3cc0146 TID:3d70146 Main thread in proc 03cc0146 faulted,
>> > Exception code = 80000002, Exception Address = 407457e4!
>> > 585231 PID:400002 TID:3d70146 DlgMgr: FindDlgItem id 1 returning NULL.
>> > 586278 PID:400002 TID:3df000a ERROR:
>> > C:\ymzki\private\winceos\COREOS\gwe\winmgr\wmbase\.\wbase.cpp line
>> > 1325:
>> > 586280 PID:400002 TID:3df000a !bFound, etc.
>> >
>>
>>
>>