Posts by fs-support_MK

I suppose this has something to do with priority or load order. Please try to set the load order of the DIO driver to 255.

yes this is possible.
I have attached the corresponding DLL version to this thread.

Does this error occur on both, debug and release build?

There was an issue with register shadowing that sometimes caused invalid values when reading from a DIO port. We have fixed this issue (0001297) in the DIO driver which will be available in the next kernel release (approx. 2 weeks).

Is your smtp client DLL accessiable generally? have you already tried to import the DLL from C/C++?

BTW:
We are currently working on a SMTP client implentation for our boards, that will released within this week for PicoCOM4. This may also include a SSH server.

We are currently evaluating this issue in more detail and will inform you this midday.

For Q1 2013 we expect a huge update for Windows Embedded Compact (WEC7 v.next) that will also include a newer version of CompactFramework. Currently it is not fully cleared which development environment will be supported by this OS version.

If you are currently evaluating which VS verion you should use for your Windows CE/EC application development here is our recommendation:
As VS2005 is resticed in debug possibilites for .NET applications and also does not include support for an easy development of silverlight applications we currently recommend using VS2008 Professional version.

It looks like the AudioCapture and SmartTee filters are not included in the current PicoCOM4 Pro kernel image. It is not possible (easily) to add these filters subsequently. We will take a deeper look at this issue and schedule these features for the next release. We will inform you in this thread.

BTW: Here is a list of all filters that are available for Windows CE 6.
<!-- m --><a class="postlink" href="http://msdn.microsoft.com/en-us/library/ee495148(v=winembedded.60">http://msdn.microsoft.com/en-us/library ... mbedded.60</a><!-- m -->)

Could you please verify if a telnet session can be opened "manually" using telnet command within command shell directly.

Sorry - there was a typo in my previous post. It should be columns instead of cols. FullHD should work poroperly with following settngs:.

This will work generall, but as driving this huge resolution on primary display interface might produces unnecessary system utilization in your application it will be a advisable to reduce this system threshold. In simplest case by reducing framerate for example.
I will discuss this with my college anyway and inform you in this thread.

I am not sure but I think the primary surface size is defined by the primary display driver. Therefore you may need to adapt the display settings in registry under [HKLM\Drivers\Display\LCD].
E.g:

I have tried this currently without success. It might be possible that the resolution for the primary display driver is limited. I have forwarded your request to the responsible developer that will be available at next week.

Quote from "al12559"

Not only that SDK4 and SDK2 cannot exist in parallel - now I get numerous linker errors with EVERY project that worked fine before:
Code:
uafxcwd.lib(cmdtarg.obj) : error LNK2001: Nicht aufgelöstes externes Symbol "IID_IDispatch".
I changed neither project settings nor source code.
(No. including uafxcwd.lib does not help - was not required before anyway.)
WHAT'S THAT?
I need a fast solution

Display More

Please try to link against uuid.lib .

To configure the command processor shell on windows CE to run over a serial connection add the following to your registry:

Here is the corresonding ndcucfg script

When starting a command window the next time (cmd.exe) in- and output will be prompted on the specified serial line.

BTW: You might use the ndcucfg command "start cmd" to run the command shell if now display is available.

In this case this problem is located differently. Please refere to following thread for details:
<!-- l --><a class="postlink-local" href="http://forum.fs-net.de/viewtopic.php?f=31&t=1110">viewtopic.php?f=31&t=1110</a><!-- l -->

I think this was only a problem in one of the early PicoCOM4 SDKs. The latest SDK version of PicoCOM4 (picocom4_sdk_v101.msi) should be completly independ from PicoCOM2 SDKs.
Which version(s) is installed on your PC currently?

Does this mean it is working now?

Please try to increase the physical page size for USB host driver.
See <!-- l --><a class="postlink-local" href="http://forum.fs-net.de/viewtopic.php?f=3&t=2870">viewtopic.php?f=3&t=2870</a><!-- l --> for more details.

We will realse the kernel image today. You may subscribe the PicoCOM4 RSS feed to get informed directly when the kernel is available in download area:
<!-- l --><a class="postlink-local" href="http://forum.fs-net.de/viewtopic.php?f=12&t=2939&p=8981&hilit=RSS#p8981">viewtopic.php?f=12&t=2939&p=8981&hilit=RSS#p8981</a><!-- l -->

It looks like the CAN driver has been removed completly in latest kernel release. We will resolv this in short term.

[IMG:http://www.fs-net.de/images/forum/WindowsCE-VS.png]