ICE

We talked about this quite a bit this afternoon. The way the program works is that when you startup 4.4 it runs iceconfig which looks in the local windows directory for the icetcp.ini file. If it finds the icetcp.ini file it OPENS it as a regular file in READ-ONLY mode and scans through it for hosts. Iceconfig internally builds a list of hosts from the icetcp.ini file and then closes the file. Once you select a host it "writes" it out as a private string which is then picked up by the Deja32.exe, the emulator and used as the host to open.

Now this works fine with plain users on 2k/xp and also with citrix on a single server we have here. In the past we've also tried it with multiple servers when we had them setup.

From your last post what I'm  hearing you say is that the list of hosts in the icetcp.ini file ISN'T appearing in the scroll box in iceconfig.

I can't see any reason why it shouldn't be able to read that icetcp.ini file. You said you had this setup as a desktop and not as a series of public apps which should make it even more foolproof. I was hoping you could check the icetcp.ini file to see if it was any different after sessions in which it didn't display the host list. If you see it isn't the same please email me one and I'll check it out.

I'm going to throw out some ideas and see if any of them sound possible:

How are you putting the icetcp.ini file into the personal windows directory? Is there something dynamic about that or should they always get the last one they had? Is it possible that the icetcp.ini file is getting copied to the windows system directory after or during the time iceconfig is started and not before??

How about some glitch in that procedure when dealing with multiple servers?

Is it possible that the way you have the server setup that iceconfig isn't being allowed to read that file for some reason??

I'm going to send you a seperate email because I'm out tomorrow and if you have any ideas I'd like you to talk to Jim Nordgaard about them...

We are still having problems picking up the icetcp.ini file. This file is copied as part of our network logon script to each users Windows folder.

Were you able to check out any of the ideas we suggested in the last message? Is it possible that you aren't getting the icetcp.ini file copied consistently to the users windows directory? It would be good to know if the icetcp.ini and registry entries that you sent me are from a non-functioning setup because they worked fine here.
When you said before that if you "open and close" the program repeatedly it eventually works, I assume that is WITHOUT logging out of the citrix server??? If you DO log out it would seem to point to a multiple server problem.

A further piece of information, when the icetcp.ini file is not being read if you delete it and try to recreate it using the Ice Configuration program you can’t change any of the settings.

Looking at our problem from a different angle is it possible to change the following default program settings to:
Terminal Type = Wyse60   24 Lines   instead of ANSI
Keyboard Language = United Kingdom   instead of United States
If this was possible when users ran Dejawint the main connection settings would be correct and they could select a host from the drop down list.

Just for informational purposes, when iceconfig cannot create a icetcp.ini with new settings, can you try to create a file in the windows directory and let me know if you can??

Would you try copying a correct icetcp.ini profile into the users windows directory on logon and give it READ-ONLY attributes and see what happens then? I tried that here and it works fine.

When you have trouble with it, you are saying the HOST is still there with the IP address and ONLY the terminal type settings are wrong??

BTW, you don't have mixed versions of 4.4 on your citrix servers right? (like something more than a couple of years old).

Thanks for the very detailed feedback. We'll get a technical meeting together and see if we can figure out what could be going on. The bit about it working sometimes and not others is really odd.

Thanks for the new iceconfig.exe file.
We had already changed the icetcp.ini file to a default profile.

Renamed the old iceconfig.exe file to .bak and loaded the new one. Tried to run DajaWint and had the same problems as before, but no error messages. Next I ran the Iceconfig program and it was able to see the host names, but was unable to change any of the settings. I deleted the icetcp.ini file and tried to create a new one but was unable; all it created was a blank file. There have been no error messages at any stage.
After a while the program started working and I was able to create a new icetcp.ini file, again there were no any errors messages at any stage. I reran DejaWint and it loaded up fine however on occasions it is losing some of the setting IE: keyboard, colour, disable exit and ctrl C. I have made the .ini file read only because when it was losing a setting it was changing the .ini file, it is also sometimes changing any other session you may have open making the screen go blank.
It doesn’t seem much different to us, works when it wants maybe a little more often.

This now beginning to drive us ALL mad!! We are thinking of going back to your unsupported 16 bit version 4 which is annoying having paid for your 32 bit version.