Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: success!
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
using the terminal services hack for windows xp, i finally got my thin clients configured and connecting into the master server. this is great. a $200 touchscreen and $25 thin client makes for a perfect remote machine. :-D

only thing that i need to do is figure out how to make the interface viewer open automatically to the appropriate template and in full screen. i am sure there is a way to do this using the command line, but i gotta learn and then figure out how to do it automatically.

if you only need a couple of locations, or if youre willing to use a few xp machines, this is a fully functioning, cheap, and 'low-profile' way to setup remote touchscreens. the ts hack allows 3 remote sessions + 1 console session. all you need is ethernet to the touchscreen/thin client location.

in case anyone is interested in this, the thin client needs to run at least Windows CE 4.2. you need to run rdp 5.1 for 16 bit color. the thin clients that i am using are Wyse WT3360SE running WindowsCE 4.2. you can find them easily on ebay in lots of 3 or 5. i picked up a lot of 5 for $55 + shipping.
See the web site FAQ. THere is a section on setting up a kiosk mode, which has the info you want.
heh ... i figured there was a way, i just hadnt gotten that far yet. Smile i followed the instructions on the website and get nothing but a blank screen. i am wondering if this is because i am using the group policy settings for the ts users. i have added the following under the startup option:

C:\Program Files\CQC\Bin\CQCIntfView.exe /DataDir=C:\Program Files\CQC\CQCData /NSAddr=media:13502 /Kiosk /Fullscreen

that is what my shortcut looks like with the kiosk and fullscreen switches added. perhaps it needs to be user installed? im not sure since i have never actually logged into console with the terminal users. ill try that and see what happens.
When you load the IV on more than one machine at the same time are you getting the error - "couldnt create window" - not binding to 0.0.0.0:13512?

Using 2 x Remote connections and the XP hack i get this error message.

I also tried a commercial mutliuser TS http://www.xpunlimited.com/ - I still got the same error which was dissapointing as its $125 for unlimited users on 1 x XP machine which would have been a really nice system...

I assume people running 2003Server and TS dont get the error.



Dean.
you know ... i got the error a couple of times. i should have paid closer attention, but after i changed a few settings in gpedit, they went away. i dont like having to deal with local user profiles, so i tend to use policies for everything. perhaps that could be the difference?

edit: when i got the error, clicking OK would just move me past it into the IV. does it let you do that?
cool ... it works. now i can get to physically setting everything up, cleaning up the house, and just using the system for a while. phew! this was a hell of a process. :-D
jkmonroe Wrote:you know ... i got the error a couple of times. i should have paid closer attention, but after i changed a few settings in gpedit, they went away. i dont like having to deal with local user profiles, so i tend to use policies for everything. perhaps that could be the difference?

edit: when i got the error, clicking OK would just move me past it into the IV. does it let you do that?

Yep - i clicked OK and moved on ok and all work properly - problem i saw/see is that it precludes me from an auto startup scenario.

I would be interested in what settings you changed in gpedit to clear it as it would be good to get it to start up properly.


Dean.
jkmonroe what sorta power is used for those thin clients? Is it a huge wallwart sort of thing or can it be run off 12/24 volt?

**I'm also curious if others are doing this sort of thing and if you have any slow downs displaying cd/dvd covers or does it almost work as good as a normal pc?

Also is their any downside to using WindowsCE 4.2 on a client versus Windows XP? I thought Dean had mentioned a graphics limitation dealing with alpha transparency or something in the past...
Ripper Wrote:Also is their any downside to using WindowsCE 4.2 on a client versus Windows XP? I thought Dean had mentioned a graphics limitation dealing with alpha transparency or something in the past...

You dont have to worry about the CE bit as its running Terminal Server so its just displaying your other XP machine just as it would on the physical XP display.



Dean.
rolecgroup: the only time that i can create the display error is when i start a local console interface viewer *after* remote viewers have been running. i played around with this for a few minutes and it happened everytime. i cant make this error pop up on my remote machines. i will post my gpedit config in a sec.

ripper: it uses a 'wallwart'. the one that it came with is a DVE switching power supply with an output of 12V 1.5A. i have done the best that i can to use the 2 monitors simultaneously and it seems snappy on both. i will monitor my network traffic over the next few days to see what kind of suck this system pulls, but its as fast as local if you ask me. also, rolecgroup hit it right on about CE. i will say this; Windows XP Remote Desktop is built on the RDP 5.1 protocol, so you absolutely *require* WindowsCE 4.2 or above to get 16-bit color, theres no workaround.

edit: the power supply is not large at all. maybe 2" wide, 1" thick, and 4" long.
Pages: 1 2 3 4