I'm not expert on Linux, but why is System.dll a bad choice? I assume there's some conflict within WINE due to another System.dll somewhere..?.. Simple solution: Rename system.dll to syssim.dll, whip out your hex editor, and hack the simulator to use the different filename. If that was the only problem, you now have a working Sim under WINE.
Alan "Matthew Bevan" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Gary Desrosiers wrote: > > Then the answer is you can't run it on Linux or Mac for that matter. > > Intel x86 Windows only. Use POSE instead. > > I recently grabbed some time on a co-worker's compy to do some checks of my > recent software (gads, PilRC can be annoying with those BITMAPFAMILYEX's - I > couldn't use my 1bpp .pbitm files!) but this isn't a long-term solution. > > I wrote: > > Are there any plans to get it running under Linux? It seems there shouldn't > > be much stopping it. > > I made the above comment hoping a PalmOS techie would be on this list - I > remember comments to the effect that the PalmOS Simulator is technically a > simpler solution than a full emulator due to the way it handles ARM-lets. > > The simulator may even be easily run under Linux using the Wine libraries and > some minor code changes (read: less-crufty code). ...And possibly better > names for .DLL files - system.dll being an unwise choice. > > -- > Matthew (Darkstorm) Bevan [EMAIL PROTECTED] > Margin Software, NECTI. http://www.marginsoftware.com > Re-inventing the wheel, every time. > > - If a 6600 used paper tape instead of core memory, it would use up tape > at about 30 miles/second. > -- Grishman, Assembly Language Programming > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
