Well, it seems that I have answered my question again....
My problem was I was using an incorrect variable in the shell path, which
was not allowing my shell to start up because windows couldn't find my shell.
I still did not figure out why my shell is not showing up inside the shell's
window.
"Disco Bob" wrote:
> I've got a custom shell created. I've created a component for my custom
> shell. In the component, I've set the prototype to 'Shell prototype
> component'. I've added in the cmiShellPath under the Advanced button. I've
> added 'Software : System : User Interface : Shells' to the Group Memberships
> section. I've added the file to the Files tab. I've created the repository
> and set the component to use the repository.
>
> I configure the image in TD. When it says it is missing a shell, my shell
> does not show up in the list of available shells to choose (the popup window
> if you double click on the task). If I add my shell in manually, it gets rid
> of the missing dependency. Any suggestions to why it's not doing this? Is
> it supposed to show my custom shell in the popup window?
>
> Also, when the image boots up, my custom shell is not being launched. It
> used to launch, but I've rebuilt my image (to document everything in detail)
> and now it's not launching on startup. I am using the WinLogon component for
> logging in.
> Any suggestions??
>
> Thanks in advance.
|
Similar Threads
