Forum Replies Created
-
AuthorPosts
-
Hi everyone,
Jus saw this post so logged in to post my experience with S10.
For a month now I’m trying various Linux’es with S10 and most of them boot with success within the S10.Let me explcain, my S10 had originally 128MB RAM which I changed to 256. So I don’t know if this could be the problem you’re having.
With this setup, various kind’s, brands and cappacity’s pen drive, I have succesfully run various diistro’s e.g. Puppy (latest), DSL 4.4.10, Xubuntu 10.10.Unfortunatly, from the above, only DSL could be installed in a internal attached HD.
To put any (current) linux distro on to USB go to http://www.pendrivelinux.com and try it. It’s free, easy and work’s like a charm.
Let me know if you need something else.
HTH
Luís
March 11, 2008 at 11:08 pm in reply to: Multiple Configuration wnos.ini deployment on one site #12121Hi ConfGen, and thank’s
I think you were referring to my question, when you talked about the “VDI Broker field in your WTOS” network setup.
The answer is no, I don’t have the VDI Broker field in my network setup… but seems that I should have.Can you clarify a little that parameter?
Seems to me that that parameter should point to a server that will return something to the client… (?)
Can you point me anything that I should know?Tomorrow I will be a great part of the day out of my office, but Thursday I’ll continue trying.
(I’m talking about tomorrow because I am in Portugal, so here is almost time to sleep ;), when there you’re probably waking up!)Thank’s for your help.
March 11, 2008 at 5:16 pm in reply to: Multiple Configuration wnos.ini deployment on one site #12101Sorry, I don’t want to to hijack the thread, but I have the same question.
I can’t get this to work. (different config to different machines)
I’m creating a file in /wnos/inc name is the real mac address of the client I am testing, i.e.: 0080646711c3 without any extension or wahtever. The file name is just the plain mac address of my terminal. I include it in the main wnos.ini file with:
include=$mac
After booting, I can see in the “system log” tab that the terminal do not “call” for it in the boot process.
The terminal is an Winterm S10 (System Version VDI: 5.1.028f ROM: 1.14i )
After reading the information that I could find about this (and the hints in confgen), I think that probably the system version does not support this feature. Can someone confirm this?Once I haven’t any maintenece agreement with wyse is there any other way to get different configs to different machines?
Thank’s for any information.
-
AuthorPosts