First Embedded Image is running!

[Franco König]

Hi all!

I have made my first embedded Image, and it working fine. but some things i
want to do with this system. i want a desktop with some symbols. first i
want that i see the workplace and the network-symbol on desktop, to make the
correct network-settings ( with right-click on the symbol). the same with
the display. ( right click on desktop, when it works?) i want change the
display settings. and the important thing is, a desktop symbol for the
RDP-Connection, because the embedded system should take the programms from a
terminal. and maybe the taskmanager. what for components must i take for
these things? i want a very small embedded system. plz help me by the
configuration! and maybe a logon screen, do logon the domain! let me know
what i must take for components.

thx and greetz

Franco K.

 

[Guest]

You want to modify the User Interface Core component to enable these
features. Expand the component node and select Settings. Enable the
following:
Show Desktop Icons
Show context menus on shell folders
Show context menus on task bar

Include the following macro component to enable RDP:
Software:System:Management:Terminal Services

Include the following component to enable task manager:
Software:System:Shells:Windows Shell:Task Manager

-harrier

 

[Franco König]

hi harrier!

You want to modify the User Interface Core component to enable these
features. Expand the component node and select Settings. Enable the
following:
Show Desktop Icons
Show context menus on shell folders
Show context menus on task bar

hmm i can´t find these settings in "UserInterface"
are u sure that they are under "Software-System-UserInterface?

Include the following macro component to enable RDP:
Software:System:Management:Terminal Services

ok, that i found!

Include the following component to enable task manager:
Software:System:Shells:Windows Shell:Task Manager

ok, that also! maybe u can help me again!

greetz

franco

 

[Guest]

Let me first assume you're using the Explorer Shell. Without the Explorer
Shell you will get no desktop icons. With that assumption, the User
Interface Core is already in your configuration. The User Interface Core is
an indirect dependency of the Explorer Shell. Explorer Shell is dependent
upon Explorer Application, which is dependent upon User Interface Core.

Anyhow, User Interface Core is in
Software:System:User Interface:Shells:Windows Shell:User Interface Core

I usually create a custom component that derives from User Interface Core
that overrides the properties that I change from the default settings.

 

[Franco König]

Hi harrier!

Let me first assume you're using the Explorer Shell. Without the Explorer
Shell you will get no desktop icons. With that assumption, the User
Interface Core is already in your configuration. The User Interface Core
is
an indirect dependency of the Explorer Shell. Explorer Shell is dependent
upon Explorer Application, which is dependent upon User Interface Core.

Anyhow, User Interface Core is in
Software:System:User Interface:Shells:Windows Shell:User Interface Core

I usually create a custom component that derives from User Interface Core
that overrides the properties that I change from the default settings.

Ok, i found the settings for the UserInterfaceCore. Ok, thats good for me.
Know i have again a question. I only need the windows explorer shell, with
some icons. when i take the template for windows professional terminal
services, can i take only this component for a working terminal embedded
system? i´m testing know only these components: windows explorer shell,
UserInterfaceCore,Display-properties, Basic Networking, windows professional
terminal template, thats all. i hope it working! thx for answering!

greetz

franco

 

[Guest]

I'm not exactly sure what you're asking so I'll rephrase in two ways:

Q: Can you include additional components in addition to the Windows Based
Terminal macro component?
A: Yes, you can include what ever components you wish as long as there are
no conflicts.

Q: Can you remove components other than windows explorer shell,
UserInterfaceCore, Display-properties, Basic Networking, windows professional
terminal template?
A: To some degree. The auto-resolver will include components that are
dependencies so you might have to turn that off. I don't recommend it.
Terminal Services is dependent upon Internet Explorer and ADSI. Internet
Explorer has 64 direct dependencies and brings in many, many other
components. It will take some work but you can probably remove some of them.
Again, I don't recommend it.