I lost the F-key buttons on TN5250.  Can you tell me how to 
restore them?

You are flying--this breaks a record for losing PF keys so 
quickly after downloading :)

Sounds like you've been editing personal.stml, and 
global.stml...

We can critique your changes for you, and hopefully set them 
straight, if you zip whichever ones you've changed and 
attach to an e-mail: send to surfer@ie.com, subject Ticket 
#589

I like to test programs very thoroughly.  I haven't changed 
any of the html templates.  Maybe I should reinstall the 
server?

Hmmm, OK, the buttons maybe you lost by selecting the 
ActiveX control or Netscape Plug-in from the pull-down?

When you do that, the control or plug-in is activated on 
your PC (as long as you go-along with the install), and from 
then on the F-keys are your PC keyboard F-keys.

If there is any way you can reproduce the program exception, 
I would really appreciate you performing the following:

1. Start Screensurfer in "diagnostic mode"
2. Reproduce the sequence of events leading to the exception
3. edit the file "\screensurfer\hostserver\surfdiag.log" and 
replace any passwords with asterisks
4. e-mail to surfer@ie.com, attaching the surfdiag.log file 
and using a subject of Ticket #589

We are very responsive to any issues with Screensurfer and 
with your help we can make it function to its best in your 
environment.

It might.  We have a W2k server that we can test your log 
file on, if it doesn't reproduce on a NT4 server.

W2K has much tighter runtime protection for memory 
allocations, so we could have a little memory nipper running 
around that only shows-up on W2K (although we have many in 
production, this environment has lots of wrinkles so there's 
always a first for every system).

We are working on the reproduction, but it might take a 
while--can you please try this:

First, upgrade your .EXE to the latest, from:

ftp://www.screensurfer.com/T2_0_10Q.zip (unzip to 
\screensurfer\bin to replace files)

Start screensurfer--

Open the console settings page, and set the "Catch Program 
Exceptions" to OFF, submit...

Then, reproduce the error--this time, Screensurfer will 
really trap and you should get a Dr. Watson.

Then, zip-up c:\winnt\drwtsn32.log and e-mail to 
surfer@ie.com.

Thank you for your patience and help.

The F-keys now appear on the screen.  No errors so far.

Is all OK with your F-keys?  If so, can we close this 
ticket?

Thanks, and hope your evaluation is going well.