I believe the garbage collector is broken for this right now.  It crashes during collection.  I'll be debugging that.

> 
> First, download this PocketConsole and install it on your PDA.  It
> allows you to see command line output.  Run it, then run Hello_arm.exe
> from the command line.  If it's screaming any errors at you, you'll see
> them.  Give me the output of your program, if any.
> Here's the link:
> http://www.symbolictools.de/public/pocketconsole/download.htm
> 
> Copying the .exe somewhere with Active Sync should be fine.  You don't need to build a .cab file.  Also, if you are creating a replica of my program, try running it in the root directory, as that's where I ran mine.  I'm still not sure how pathing works on WinCE.

Everything work fine.
I have made a screenshot:
http://www.steinmole.de/d/wince.bmp

I copy the arm-wince-pe-gdc.tar.gz under http://www.steinmole.de/d/arm-wince-pe-gdc.tar.bz2


You have made a great job.
Thank you.

Manfred

Manfred Hansen wrote:
> 
> Everything work fine.
> I have made a screenshot:
> http://www.steinmole.de/d/wince.bmp
> 
> I copy the arm-wince-pe-gdc.tar.gz under http://www.steinmole.de/d/arm-wince-pe-gdc.tar.bz2
> 
> 
> You have made a great job.
> Thank you.
> 
> Manfred
> 

You're welcome.
I'm glad you like it.

On Sat, 12 Aug 2006 12:16:03 -0700, Chad J <gamerChad@_spamIsBad_gmail.com> wrote:

> Manfred Hansen wrote:
>>  Thank you, i have successfully compiled the first programm.
>>  I have compiled your example wich write the file doutput.txt .
>> This programm have i copied to the sd Card and rename the programm to
>> Hello_arm.exe .
>>  But it do nothing on my PDA.
>> My PDA is a YAKUMO with Windows mobile 4.2 .
>> The CPU is S3C2410 it should be compatible with ARM920T .
>>  I have read i must copy the programm with Active Sync or i must build a "cab" file?
>>  Manfred
>>
>
> First, download this PocketConsole and install it on your PDA.  It allows you to see command line output.  Run it, then run Hello_arm.exe from the command line.  If it's screaming any errors at you, you'll see them.  Give me the output of your program, if any.
> Here's the link:
> http://www.symbolictools.de/public/pocketconsole/download.htm
>
> Copying the .exe somewhere with Active Sync should be fine.  You don't need to build a .cab file.  Also, if you are creating a replica of my program, try running it in the root directory, as that's where I ran mine.  I'm still not sure how pathing works on WinCE.


Well... that's unfortunate.  Pocketconsole is a very old piece of software and doesn't support Windows Mobile 5.0.  So I guess the rest of us are stuck?  I know of know working command line for windows mobile 5. :(

-JJR

John Reimer wrote:
> 
> Well... that's unfortunate.  Pocketconsole is a very old piece of software  and doesn't support Windows Mobile 5.0.  So I guess the rest of us are  stuck?  I know of know working command line for windows mobile 5. :(
> 
> -JJR

Dang, I didn't know that.

WM5.suckyness++;

I already read that SynCE doesn't work with WM5 yet.  This all makes me not like WM5.  I'm going to be looking at a new PDA soon, perhaps an Axim x50v (like you have it seems), and I'll be avoiding WM5.  Hoping for WM3 SE or something.

As for "what if I don't have a command line", well, I was hoping to hijack stderr in phobos and make it open a window to display the error message or some such.  This would allow people to see the error messages without special software like pocketconsole.  This is kind of low priority for me right now though, what with the gc crashing.  Damn windows thread API is making it hard for me to get a non-pseudo thread handle...

On Wed, 16 Aug 2006 19:01:23 -0700, Chad J <gamerChad@_spamIsBad_gmail.com> wrote:

> John Reimer wrote:
>>  Well... that's unfortunate.  Pocketconsole is a very old piece of software  and doesn't support Windows Mobile 5.0.  So I guess the rest of us are  stuck?  I know of know working command line for windows mobile 5. :(
>>  -JJR
>
> Dang, I didn't know that.
>
> WM5.suckyness++;
>
> I already read that SynCE doesn't work with WM5 yet.  This all makes me not like WM5.  I'm going to be looking at a new PDA soon, perhaps an Axim x50v (like you have it seems), and I'll be avoiding WM5.  Hoping for WM3 SE or something.

WM5 is a pain. Not bad. But not good either. Not really an improvement at all over the PPC2003 SE from the UI perspective, other than proper support for VGA displays. X50V is a good price now, especially since Dell is no longer making PDAs, so expect no more support. In the end, many users have been sorely dissappointed with them mostly because of lack of support from Dell concerning WM5. Probably more so since people were given the upgrade option to WM5 and found it buggy (on that device; my experience and disappointment with WM5 may be mostly due to the problems I've had with using it on the X50v).

Dell pretty much ignored everybody's complaints because the device was all but discontinued by then.  The stock OS provided with the X50v is the PocketPC 2003 SE.  It runs fine, but then its display stretches to the 640x480 resolution and runs absolutely horribly slow (the GUI) despite having the uber-fast processor inside.  That's why I was so excited to try WM5 because not only was it supposed to run at the native resolution, but the screen performance was supposed to be fast (and it is indeed a huge improvement over the PPC 2003 SE screen which was designed for 320x200). WM5 also had persistant storage after backup battery loss.  A very important improvement over PPC2003 and earlier.  I enjoyed the improvements for awhile, but repeatedly got annoyed over some software glitches in the both the OS and software that didn't know how to play nicely with the new OS; this usually meant the battery ran dry far faster than expected because the software litterly sucked the juice out of the unit when it was supposedly "off" or in sleep mode.  Not a nice thing.

So it's your call.  My father actually has the X30 and PPC2003 SE.  He seems to have no troubles with it, and it's actually a bonus having the 240x320 resolution in that case because you don't get any problems with poor support and slow performance as you would with the high resolution displays.  You might consider that or the X50 (QVGA version).  It's your call. :)

What still bothers me, though, is that the old Palm OS 5 devices (like the Tungsten C) had incrediblely fast UI's and seemed to perform simply and responsively at all times.  I miss that greatly, and it's always made me sore at MS for their inability to accomplish the same thing despite all the time and opportunity they've poured into the Windows Mobile systems.

-JJR

John Reimer wrote:
> On Wed, 16 Aug 2006 19:01:23 -0700, Chad J  <gamerChad@_spamIsBad_gmail.com> wrote:
> 
>> John Reimer wrote:
>>
>>>  Well... that's unfortunate.  Pocketconsole is a very old piece of  software  and doesn't support Windows Mobile 5.0.  So I guess the rest  of us are  stuck?  I know of know working command line for windows  mobile 5. :(
>>>  -JJR
>>
>>
>> Dang, I didn't know that.
>>
>> WM5.suckyness++;
>>
>> I already read that SynCE doesn't work with WM5 yet.  This all makes me  not like WM5.  I'm going to be looking at a new PDA soon, perhaps an  Axim x50v (like you have it seems), and I'll be avoiding WM5.  Hoping  for WM3 SE or something.
> 
> 
> WM5 is a pain. Not bad. But not good either. Not really an improvement at  all over the PPC2003 SE from the UI perspective, other than proper support  for VGA displays. X50V is a good price now, especially since Dell is no  longer making PDAs, so expect no more support. In the end, many users have  been sorely dissappointed with them mostly because of lack of support from  Dell concerning WM5. Probably more so since people were given the upgrade  option to WM5 and found it buggy (on that device; my experience and  disappointment with WM5 may be mostly due to the problems I've had with  using it on the X50v).
> 
> Dell pretty much ignored everybody's complaints because the device was all  but discontinued by then.  The stock OS provided with the X50v is the  PocketPC 2003 SE.  It runs fine, but then its display stretches to the  640x480 resolution and runs absolutely horribly slow (the GUI) despite  having the uber-fast processor inside.  That's why I was so excited to try  WM5 because not only was it supposed to run at the native resolution, but  the screen performance was supposed to be fast (and it is indeed a huge  improvement over the PPC 2003 SE screen which was designed for 320x200).  WM5 also had persistant storage after backup battery loss.  A very  important improvement over PPC2003 and earlier.  I enjoyed the  improvements for awhile, but repeatedly got annoyed over some software  glitches in the both the OS and software that didn't know how to play  nicely with the new OS; this usually meant the battery ran dry far faster  than expected because the software litterly sucked the juice out of the  unit when it was supposedly "off" or in sleep mode.  Not a nice thing.
> 
> So it's your call.  My father actually has the X30 and PPC2003 SE.  He  seems to have no troubles with it, and it's actually a bonus having the  240x320 resolution in that case because you don't get any problems with  poor support and slow performance as you would with the high resolution  displays.  You might consider that or the X50 (QVGA version).  It's your  call. :)
> 
> What still bothers me, though, is that the old Palm OS 5 devices (like the  Tungsten C) had incrediblely fast UI's and seemed to perform simply and  responsively at all times.  I miss that greatly, and it's always made me  sore at MS for their inability to accomplish the same thing despite all  the time and opportunity they've poured into the Windows Mobile systems.
> 
> -JJR

Thanks for the info.

I was eyeballing the x50v on Ebay for its good price.  I was kind of counting on that slowness, but not from the OS :(.  I want to take advantage of 480x640 with the game I am coding, and I'd have a platform to test on and see first hand.  So I did the math - CPU is clocked %50 faster, but 4x more pixels to push.  Not good.  It means my 240x320 at 400 MHz probably won't be representative.  Maybe the intel graphics accelerator will help, though I'd have to do extra OpenGL work (oh well).  Wonder how much juice that gfx accelerator sucks.

But for personal use it might not be my first choice from what I'm reading (battery life GOOD, slowness BAD).  hmmmm...

John Reimer wrote:
> 
> Well... that's unfortunate.  Pocketconsole is a very old piece of software and doesn't support Windows Mobile 5.0.  So I guess the rest of us are stuck?  I know of know working command line for windows mobile 5. :(
> 
> -JJR

For Pocketconsole to work in WM5, you may need to set HKEY_LOCAL_MACHINE\Drivers\Console\OutputTo to 0.
It has been reported to work, although I never tested it.

Cheers,
Pedro Alves

On Thu, 17 Aug 2006 02:31:19 -0700, Chad J <gamerChad@_spamIsBad_gmail.com> wrote:


> Thanks for the info.
>
> I was eyeballing the x50v on Ebay for its good price.  I was kind of counting on that slowness, but not from the OS :(.  I want to take advantage of 480x640 with the game I am coding, and I'd have a platform to test on and see first hand.  So I did the math - CPU is clocked %50 faster, but 4x more pixels to push.  Not good.  It means my 240x320 at 400 MHz probably won't be representative.  Maybe the intel graphics accelerator will help, though I'd have to do extra OpenGL work (oh well).  Wonder how much juice that gfx accelerator sucks.
>
> But for personal use it might not be my first choice from what I'm reading (battery life GOOD, slowness BAD).  hmmmm...

Well, I may be overreacting to some extent.  Some games seemed to take advantage of the appropriate accelerated drivers and performed quite well.  At least the sample games included were just fine.  So really the slowness of the screen seemed limited to GUI operation only, while using the Dell for everyday tasks. Even that feel could be slightly improved by moving the CPU to its highest speed mode.

-JJR

On Thu, 17 Aug 2006 06:18:05 -0700, pedro alves <pedro.alves@domatica.pt> wrote:

> John Reimer wrote:
>>  Well... that's unfortunate.  Pocketconsole is a very old piece of software and doesn't support Windows Mobile 5.0.  So I guess the rest of us are stuck?  I know of know working command line for windows mobile 5. :(
>>  -JJR
>
> For Pocketconsole to work in WM5, you may need to set HKEY_LOCAL_MACHINE\Drivers\Console\OutputTo to 0.
> It has been reported to work, although I never tested it.
>
> Cheers,
> Pedro Alves


That did indeed work.  Thank you very much!  Pocket Console now works fine on the Dell X50v with windows mobile 5.0!

-JJR