Anyone had experience integrating against a VT220 emulation?

[blue_meanie]

We have been trying to integrate with what we were told was a mainframe, using the BlueZone emulator.  When we have tried spying in Mainframe mode, using BlueZone's ehlapi32.dll, the grid either doesn't appear, or on the rare occasions it does, it doesn't match the Row/Columns which BlueZoneVT is configured to use (24x80).   We have tried numerous different configurations in the BlueZone VT emulator, but with no repeatable results.   We have learned today that the 'mainframe' we are trying to connect to, is in fact NOT a mainframe at all, but an application running on Linux, and using BlueZoneVT as a VT220 emulator.  Explains why we might have been having trouble!  I'm not ready to give up yet though, as on one occasion (yes, literally one, out of many attempts!), I was able to get the grid to spy as expected, and I was able to build and test a whole object in one session.  However since then, with no config changes being made, I am no longer able to get Blue Prism to set the grid as it did that first time, and the object obviously won't work. So now i'm wondering if we need to use a different API (have also tried whllappi.dll without success) for this to be reliable. Has anyone successfully integrated with a VT220 emulator as a 'mainframe' using the Mainframe Application modeller?    

[blue_meanie]

For anyone seeing this issue in the future - We resolved this by installing V7 of the BlueZone VT software.  They have improved the HLLAPI, and it seems to work as expected now.   A bit more background on the odd behaviour seen with V6 of BlueZone VT - On the rare occasions we were able to see a Grid in the Application modeller, it would not have the matching Column/Row values.  Some times it would think there were only 32x32 rows/columns in the grid.  Other times, it would translate pixels to grid coordinates, so Blue Prism thought there were over 1980x1024, etc.