Search the Community

I'm having a problem getting access to the USB sticks on my thin clients (These are all old PC's converted to thin clients with thinstation btw). The USB drive maps correctly to U: as I want however I get an 'access denied' errror when I attempt to open the drive up. This even happens as Administrator. I have checked: Group Policy Settings Terminal Server connection settings Citrix Policy Settings Citrix Server Settings Any ideas?

I am now introducing thinstation to a bunch of our old machines around the school, to utilise them again and I have hit a roadbump. I have successfully been using thinstation with our Samsung 911NT and 920XT thin clients, but cannot get it to work fully with these old machines. I have made sure the right xorg modules are being put into the image (intel i810), but when I start the machines up, they go through the motions and fail to start X. When I look at the Xorg log file, it says no Screens exist? Any ideas?

Does anyone have any info on this monitor? I'm trying to set it up on a old Dell PC converted to be a thinclient with Thinstation. However the Xorg.0.log complains the monitor does not support DDC and cannot get it to run in anything other than 640x480. Here's the relevant snippet from the Xorg.0.log (II) TRIDENT(0): VESA VBE DDC supported (II) TRIDENT(0): VESA VBE DDC Level none (II) TRIDENT(0): VESA VBE DDC transfer in appr. 0 sec. (II) TRIDENT(0): VESA VBE DDC read failed (--) TRIDENT(0): Revision is 106 (--) TRIDENT(0): Found CyberBlade/i1 chip (--) TRIDENT(0): RAM type is SDRAM (--) TRIDENT(0): Using SW cursor (--) TRIDENT(0): VideoRAM: 8192 kByte (--) TRIDENT(0): TFT Panel 1024x768 found (--) TRIDENT(0): Memory Clock is 57.27 MHz (==) TRIDENT(0): Min pixel clock is 12 MHz (--) TRIDENT(0): Max pixel clock is 230 MHz (II) TRIDENT(0): Monitor0: Using default hsync range of 28.00-33.00 kHz (II) TRIDENT(0): Monitor0: Using vrefresh value of 60.00 Hz (II) TRIDENT(0): Clock range: 12.00 to 230.00 MHz (II) TRIDENT(0): Not using default mode "640x350" (hsync out of range) (II) TRIDENT(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x400" (hsync out of range) (II) TRIDENT(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "720x400" (hsync out of range) (II) TRIDENT(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) .... .... .... .... (II) TRIDENT(0): Not using mode "800x600" (no mode of this name) (--) TRIDENT(0): Virtual size is 640x480 (pitch 640) (**) TRIDENT(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) TRIDENT(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (==) TRIDENT(0): DPI set to (75, 75) I really need it to run at a higher resolution. I specifically need the horizontal and vertical refresh rates.

Hi, Not sure how big of a Thinstation community lives here so here goes nothing. I'm attempting to create a VMWare View workstation based on ThinStation. I'm using TS-o-Matic to create my builds. Currently my testing is only with CDs/ISOs. I haven't tried any other implementations such as a PXE boot. I have created custom builds and used the LiveCDs available from Thinstation.org, both result in the error below when I boot my HP T5135 Thin client PC. Error, no valid session type!!! Boot aborted, please check youru thinstation config files are correct My feeling is that this error is based on a missing driver. I think this because I download the current Thinstation LiveCD for VMWare View and it worked fine in my Lenovo T61. Connected to VM and everything. When I use the CD with my HP T5135 I get the no valid session type error above. I'm thinking it just doesn't know how to communicate with the internal network card(NIC). I tried using TS-O-Matic to create a build with all network drivers included but that did not work. Does anyone have any suggestions of what to try next?

Hi everyone I'm trying to set up ThinStation to point at either our VMWare ESX or any of our RDP servers as a proof of concept but I can't make head nor tail of how to do anything with it All I want is a 'LiveCD' but ThinStation and I seem to have very different idea of what a LiveCD is - I'm used to Linux LiveCDs where I download an ISO and burn it to disc. I put this in a PC and switch the machine on. It boots from the CD as if I had installed the contents on the hard disk but without making any changes to the installed O/S This is what I want to do but if this isn't possible (I have no idea how the livecd.exe you can download from their site fits in to my understanding of a LiveCD...) then I would settle for having to install it on a VM as I have VirtualBox which should be ok for it but I can't find any documentation anywhere which discusses tells me how to really do any of this! I have found some bits which say 'modify the build.conf as required for your hardware' but I've also read somewhere that the build.conf isn't really one specific file or something crazy like that! If anyone knows any resources that can help (or knows what I've misread) then I'd really appreciate it! Thanks

I hope someone can help, I know there are lots of Thinstation fans out there..!! I can't get it to boot. I am running the TSOMATIC script, and entering what I think are sensible values, but when I try to boot from CDrom I get and error message "DHCP error - wrong network module installed" The PC has a Broadcom NetXtreme Gigabit controller - and that exact product is listed and selected in the network menu... I was hoping to be able to boot the PC direct into an Rdesktop connection, using a hardcoded server IP address and DHCP enabled - am I being realistic ? (the Thinstation website gives information overload, and I can't understand from it if this is feasible or if I have to set up a TFTP server to send IP config on every boot...) Does anyone have a minimum config file for Thinstation they could provide, the template they provide is massive and gives no indication which are mandatory parameters and which are optional. I am running out of blank CDs trying to find the right settings !!! (Does anyone have an "Idiots Guide" to setting this up....?) Many Thanks in advance

Bit of an Oxymoron for me. We are successfully using old kit and a HDD setup of Thinstation to contact Terminal servers. All very nice when wired up. Mind-blowingly frustrating via wifi; especially for a linux newbie. Read a 3yr old post claiming it was possible. Anyone care to share their working build.conf / buildtime.conf to get me farther along? Ta

Hello, I have gotten the LiveCD.Basic version customized as to how I want it with the .user configuration file and the system boots successfully every time but I was wondering on how to force this connection to always reconnect. I have it going straight into an RDP session connecting to our terminal server but if I were to hit 'Cancel' on the logon screen, it goes back to TS and asks me if I want to reconnect. I have changed the Auto start Option as well as the Reconnect_Prompt and it merely asks me if I want to reconnect. I want it to force a reconnection so if the user ever presses 'Cancel' or if they Log Off, it reconnects them and displays the logon screen. Is there anyway to do this by editing the .user configuration file? I can only work from a Windows machine and I previously tried building an image from the TS-O-Matic site but it wouldn't ever initialize DHCP. Please let me know if this is possible, I read in another topic that it was but no one posted on how to do it. Thanks, Chris