Conference dssdev::decforms

Mick,

Can you tell us what version of DECforms your customer is running?
We fixed a host of problems related to "disconnections" in T2.2.
Your customer may want to try a field test version of that kit.

Domenic

    
    Hi Domenic,
    		thanks for the interest.As a complete newcomer to DECforms,
    please can you explain to me what a "disconnect" is,and how it applies
    to the problem as described in the base note ?
    
    I will get the info you need asap...
    
    				Cheers Mick

Well, by "disconnect" I mean something occurred to interupt
an I/O operation.  Earlier releases of DECforms had some
problems in regards to handling and cleaning up conditions
where unexpected interruptions had occurred.

Do you know the version of DECforms your customer is running?

Is this problem you're describing unique to VT520s?

Domenic

    
    	Domenic,
    		all being will,will be able to supply the info you need 
    	tomorrow.. (7/2/97)
    
    		Thanks again for the interest..
    
    					Mick
    

    
    	Domenic,
    		 looked on the system(s) concerned,and found as follows:-
    
    	SYS$HELP contains :-
    
    	FORMS014.RELEASE_NOTES;2   FORMSECO03014.RELEASE_NOTES;2
    
    	ANA/IMA SYS$COMMON:[SYSLIB]FORMS$MANAGER.EXE  FORMS V1.4-13
    	ANA/IMA SYS$COMMON:[SYSMSG]FORMS$MSGMGRSHR.EXE FORMS V1.4-5
    	
    	Seems quite low,its on 2.1 now I believe ? Is the above sufficient
    	to determine the revision,and is the version suspect at all please.
    
    			Regards  Mick 

Those image idents are indeed DECforms V1.4 ECO3.  We did not support VT500
series terminals until V2.1.  However, they could still be using them if they
had set the terminal type and characteristics to behave as a VT400 or older.

As Domenic has mentioned, there have been disconnect problems that have been
fixed.  The latest V2.2 version has the greatest number of these fixes. 
However, since they're still back on V1.4, their problems may have already been
fixed in the current release of DECforms V2.1 MUP B.  Sounds like its worth just
having them upgrade.

-Tim

    
    So it "legal/supported" to use a VT520 posing as a VT420 on 1.4-ECO3 ?
    If so,would they still be subject to these known disconnect problems 
    that you talk about ? Do the problems apply to any terminal type ?
    
    					Cheers Mick
    
    PS I have opened discussions with the customer about why they are 
       stuck on 1.4-ECO3,and will report back soon.
    
    					

>    So it "legal/supported" to use a VT520 posing as a VT420 on 1.4-ECO3 ?

Well, you're assuming 1.4-ECO3 is still supported...  That was a few releases
and just as many years ago...


I don't think the disconnect issue has anything to do with the VT500 as it
occurred with other VT types as well in 1.4.

-Tim

    
    Hi,
    	I'm trying to reproduce this on a non-live environment on 1.4,and 
    	if I can,then upgrade to 2.1to see if it goes away.Customer
        application  is very "mission-critical" 24X7 Cross channel ferry
    	freight handling application,and difficult to drive. Does anyone
    	have a simple demo program that continually refreshes a screen full
    	of letters/numbers ?
    
    						Cheers Mick

Mick,

There are demo programs placed in FORMS$EXAMPLES (at least in the V2.1B kit)
that continually update a time field on the screen.  You could try hacking at
that.

Domenic