Anyway to fix the browsing issue type:
cupsctl BrowseProtocols='"cups dnssd"'
in your much neglected OSX terminal.

Job done.

I created a test page to check the Javascript method required: document.formname.submit() or document.forms['formID'].submit() (my Javascript is a little rusty because, I’m glad to say, I rarely use it). This worked fine, so I added the little bit of code to the real page. It promptly refused to work. No matter what I tried, it wouldn’t auto-submit, and the debug console said "document.formname.submit is not a function". How bizzare! No end of googling could find an answer. The code was right, according to all sources. I changed names of the form and added IDs galore, but no joy.

Then it hit me – the submit button in the form (I included one for those who might have no Javascript, or Javascript turned off) had the name attribute of "submit"! This meant that the submit button was the object: document.formname.submit , but I was trying to execute the method: document.formname.submit() . Javascript can’t cope with one object and a method of another object, having the same name. As soon as I changed the name of the submit button, all was well. It worked!

What a load of hassle for such a tiny error. So remember, when you give your form elements names or IDs, make sure they are different from the element tag. A good practice is to give the form a generic name, such as "mysite_signup" and then name its child elements with the formname as the prefix. So, an input field might be "mysite_signup_email_address", and the submit button might be "mysite_signup_submit". Unique naming baby – it’s the way forward.

defaults write com.apple.AppleShareClient afp_cleartext_allow -bool true
defaults write com.apple.AppleShareClient afp_ssh_allow -bool true
defaults write com.apple.AppleShareClient afp_ssh_warn -bool false

To verify the options type:

defaults read com.apple.AppleShareClient

1) Create a 640×480 jpg image for the splash screen

2) install squashfs-utils either from your Linux distribution’s packaging system or from http://squashfs.sourceforge.net

3) copy /var/opt/2X/thinclientserver/apache2/htdocs/tftproot/ThinClientOS-v4.1_release-r2857/rootdisk26.img from your 2XThinClient server to a suitable location to modify it. (The last directory may be different depending on your ThinClientOS release. This is for the 2.6 kernel version, just use rootdisk24.img for the 2.4 kernel. Sorry I don’t know where the windows version would put it)

4) cd to that suitable location

5) unsquashfs rootdisk26.img

(must be done as root or with sudo)

files will be extracted to squashfs-root

6) cp [the image you created earlier].jpg squashfs-root/etc/bootsplash/themes/2x/images/silent-640×480.jpg

(must be done as root or with sudo)

7) mksquashfs squashfs-root/* newrootdisk26.img

(must be done as root or with sudo)

rename /var/opt/2X/thinclientserver/apache2/htdocs/tftproot/ThinClientOS-v4.1_release-r2857/rootdisk26.img to rootdisk26.img.orig on your 2XThinClient server just in case something goes wrong

(must be done as root or with sudo)

9) copy newrootdisk26.img from wherever you created it to /var/opt/2X/thinclientserver/apache2/htdocs/tftproot/ThinClientOS-v4.1_release-r2857/rootdisk26.img  on your 2XThinClient server

10) reboot a thin client and voila!

A more advanced user may wish to further modify the bootsplash theme which they should be able to figure out fairly easily from this. I’m not sure if this is standard bootsplash that hailed from Suse or gensplash from Gentoo or something completely different. Perhaps the devs can tell us?

Obviously this isn’t an easy process to be done too often. It will also have to be re-done with each upgrade of the ThinClientOS and for both kernels if you need both.

Hope this works for you.