Thanks Darren, I'll look at the CRT project and see if he did anything special. While iMame compiles fine for the ARM, compiling it for MIPS it gives me the same type of errors. Probably a difference between processors. I'll look into it.

Good notes...yeah, I will try to do a better job this time around versus iMame. : )

Thanks again.

Dario

> > Okay, I did what I could with iMame, added a dozen more drivers, customized
> the
> > keys, added the Mame Config menu, etc. Gandalf did a great job making the
> > source very PocketPC friendly.
>
> Yes, well AFAIK it was developed in the eMbedded toolkit environment...
>
> > Well, I figured it was time to play with Mameboy. Using the PalmPC SDK the
>
> ...which, of course, has thus far been done in MSVC++6.0, as it comes from the
> Original-MAMECE / MAMECE-10X bloodline.
>
> > Embedded Toolkit did a good job converting all of the projects to the latest
> > platform but I think I am getting the dreaded inconsistency errors between
> > compilers. Here is what I am getting:
> >
> > File.obj : error LNK2001: unresolved external symbol fopen
> > core.lib(unzip.obj) : error LNK2001: unresolved external symbol fopen
> > core.lib(cheat.obj) : error LNK2001: unresolved external symbol fopen
> > core.lib(datafile.obj) : error LNK2001: unresolved external symbol fopen
> > core.lib(cheat.obj) : error LNK2001: unresolved external symbol fgets
> > WMIPSRel/MAMEBoy.exe : fatal error LNK1120: 2 unresolved externals
> > Error executing link.exe.
> >
> > PocketProjects.com had some references to these routines not being supported
> > well in the new compiler which doesn't make sense since it is part of the C
> > Run-time library for WinCE. The most common answer to this was rebuilding it
> in
> > an empty project with cut-n-paste.
> >
> > I haven't done C programming in a long, long time so maybe it is just
> ignorance
> > on my part. I know I have a lot to learn and working with this code is the
> best
> > way to learn it the hard way. Any suggestions in dealing with projects that
> > need to be converted from the old WindowsCE Toolkit to the new version?
> > Anyone know where I can get the old Toolkit for a reasonable price? A web
> > search didn't help much but show some websites that are still selling it for
> the
> > old $200+ price tag.
> >
> > Thanks for whatever help you can offer.
> >
> > Dario.
> >
>
> Yes, "fopen" and other similar file access functions are not supported in WinCE
> (and haven't been even from CE1.0 AFAIK). Best I can tell from the Ben's
> source, this functionality is added with the "crt" project. I think I remember
> reading a while back that Gandalf had to make some tweaks to it to get it to
> work within eMbedded toolkit. Try looking at Gandalf's "crt" project, or
> substituting it in :) or if all else fails drop him a line.
>
> And please take good notes, because if you get it working in the embedded
> toolkit, I'd like to know exactly how, and I suspect others would too.
>
> Darren
>