Hello there,

Not that I'm an expert at the OTC topic but I can try to help out;

When you locate the MacID of your wyse under OTC->PXE clients (right click
to PXE clients and refresh if in doubt), you'll see the list on the
right-pane, double-clicking the MacID entry in the right pane should open
the Convert to client dialog. Give it a name and it will be moved under
ThinClients.

If that doesn't work the only thing i can relate is the OTC Manager
misbehave based on Operating System (assuming you got the right Java
version) i.e whether its Windows/linux or MacOS X?

If its a Mac, running on Leopard Mac OSX:  (Don't bother reading beyond this
if its not Mac OS X)

 even after the latest Java updates (version 6) running the openthinclient
with ./start-server.sh from terminal seems to be problematic. Most of the
core services (tftp, nfs etc.) fail to run and you won't notice it unless
you pay attention to the debug log in the terminal. 

This results in some seriously weird stuff to surface under OTC manager
interface.

I didnt locate any solution for that, first I thought it could be permission
related because the services failed to run with 'socket or I/O permission '
error.

Then i tried to do "sudo -s" under Mac OSX Terminal, that get me into root
context.
However, running "./start-server.sh" with root context (sudo -s) returned
"wrong Java version, you need Java 6".

Strange issue, as light googling around didnt reveal any solution for this.
The normal user context locates the right version of Java but gives
"permission error" for I/O and Socket when it attempts to run "services".
The root context (sudo -s) can't locate the new version (6) and attempts to
run with version 5 or 4.1..

To sum it up, OTC Server doesn't run (specifically the core services like
NFS, TFTP, jboss etc. fails to load) well and for a use who don't pay
attention to the execution log, OTC Manager will misbehave.


Hope that sheds some light instead of confusing. Good luck...

All the best!


Jh60082 wrote:
> 
> Hi there, im very new to OpenThinClient and i am getting the hang of it.
> So i am trying to convert an old wyse i have (not too old thought) and
> when i find it in the PXE client lists i click edit but when i do that it
> says "add to thinclient list" instead of "convert to client" so at this
> point OTC knows that it exisits but it hasnt converted it to the
> Openthinclient OS. any help here?? Im using the newest version of OTC
> 

-- 
View this message in context: 
http://www.nabble.com/Converting-a-wyse-tp19642392p19742767.html
Sent from the openthinclient.org users' mailing list mailing list archive at 
Nabble.com.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
[email protected]
https://lists.sourceforge.net/lists/listinfo/openthinclient-user

Reply via email to