I don't know if this is possible, b

[kestrel1]

I don't know if this is possible, but I have got an old PC that I have setup with DOS, Lanman & Citrix ICA Client for DOS.
I can get the ICA Client to run, but is there a way of bypassing the DOS logon & automatically starting the ICA client so that I just have the Citrix ICA logon screen.
We run about 80 thin clients (some old ACORN clients, IGELS & ThinTunes) The Thintunes are the best Thin Clients I have come across. I would like to be able to use any old PC's as thinclients without too much hassle. I do know of another way, but this will cost extra & I don't think the old PC's are really worth it.

 

[ascotta]

You shouldn't have to logon to DOS.

If you put the

WFRUN32.exe <App Name> into the autoexec.bat that should connect automatically.

Long time since I've done that.

Cheers
Scott

 

[kestrel1]

Thanks. This gave me some pointers.
The file is actually WFCDOS32.EXE
When I type this in with the app name in brackets I get the following error
TCP/IP Protocol is not available. (Browser 23)
TCP/IP is loaded & if I go through WFCLIENT.EXE & click connect, I can connect to ICA server. Any idea what is going on or am I missing something.

 

[Ogi]

Have you loaded &quot;sockets.exe&quot; within your script, I've found that it doesn't get loaded by default and although you have an IP address, you don't get to connect!

Cheers,
carl.

 

[kestrel1]

Yes sockets is loaded. It doesn't really make any sense because I can get a connection fine if I run the WFCLIENT.exe file & click connect or just press return.
The other thing that I would like it to do, when I eventually get it to work, is to restart the ICA session when someone logs off. In Linux I think this is called respawning. I can get an old Acorn RISC PC to boot to the ICA screen & when someone logs off it will go back to the logon screen. This took some work, but it works well. I would like to do the same with these old PC's
Thanks
Glyn

 

[ascotta]

Dragging the bottom of the old brain barrell here. I think you nmeed quotes round the applciation.

I would try keeping the command out of autoexec until you know you have it working with TCP/IP.

Once you can ping after boot then the WFDOS32 (or whatever) should then work.

Ogi was right about sockets. I had forgotten that one.

Cheers
Scott

 

[kestrel1]

Thanks for your help with this. I don't know why I said brackets when I meant to say speach marks &quot;app name&quot;.
I can ping fine. I can even get a connection to the Citrix server with the ICA wfclient.exe file. I am wondering if my wfcdos32.exe is corrupt in some way. I will replace it, try it again & let you know.

 

[kestrel1]

I have tried another file, re-installed the whole Citrix client from scratch & still get the same problem.
I can't understand why it keeps saying that the TCP/IP protocol isn't available when it is. I haven't needed to work in DOS for a long time & I have never connected a DOS machine to a network before.
I might think about doing a total re-install of DOS & start at the beginning again.
If you have any more thoughts before tomorrow (Thursday) Please post them. You might save me more work.
Many thanks all.
Glyn

 

[kestrel1]

Please disregard my last post. I have managed to get this working. I deleted the connection that I had made with wfclient.exe
Instead of running wfclient.exe to make a new connection I used wfcdos32.exe without anything else. This loaded the configuration program. I made a new connection to the server, saved it & typed wfcdos.exe &quot;network&quot; & it worked. Many thanks for all of your help guys.
Glyn