Problems with print events - WeOnlyDo Discussion board

Problems with print events (wodSSH / wodSSH.NET)

by Ivo Valente, Thursday, July 01, 2010, 22:03 (5019 days ago)

I am using wodtelnetdlx OCX and I have implemented the print events in a vb6 aplication, I connect via SSH2 to a HPUX machine.

Some printing events occur and are handled correctly, some other events trigger the object_Received(ByteCount, Handled) trigger and when the object_PrintData(Text) is finnaly triggered the recieved text is one character long.

The object_PrintEnd() does not fire until I close the aplication, so the aplication just stops any kind of SSH comunication.

Can someone help me understand what is happening and how to correct it?

Thank You,
Ivo Valente

Re: Problems with print events

by woddrazen, Friday, July 02, 2010, 01:05 (5019 days ago) @ Ivo Valente

Hi Ivo,


Can you maybe show us some code snippet so we can try to duplicate this problem on our side?

You are receiving this problem with some specific server or you receive it with all servers you are using?


Regards,
Drazen

Re: Problems with print events

by Ivo Valente, Monday, July 05, 2010, 19:54 (5015 days ago) @ woddrazen

Thankyou for your response, I am gathring more concrete evidences to post them here.

Meanwhile it seams that the things that get printed correctly are all ascii based and those that raise the object_Received(ByteCount, Handled) right after the object_PrintStart() and before the object_PrintData(Text) contain some binary or special caracters in the buffer.

I am trying to find a pattern, I will post my findings.

Also, I am using version 2.3.8 and you are now shipping version 2.4.2, this might be an issue addressed by you in later versions. Our support has expired and while I wait for approval of its renewal I will also carry out tests with your Trial Version.

I will also report on how this goes.

Thankyou,
Ivo Valente

Re: Problems with print events

by Ivo Valente, Monday, July 12, 2010, 17:52 (5008 days ago) @ Ivo Valente

Good afternoon,

I have acrried out testes with your latestes version of the OCx component and the problem persists.

An example of the what is suposed to be recieved is as follows:

00000000h: 20 20 20 20 20 2E 28 73 33 32 53 2E 28 73 33 42 ; .(s32S.(s3B
00000010h: 2E 28 73 31 50 2E 28 73 32 34 56 43 58 58 58 58 ; .(s1P.(s24VCXXXX
00000020h: 58 58 58 58 20 53 2E 41 2E 2E 28 73 30 42 2E 28 ; XXXX S.A..(s0B.(
00000030h: 73 30 53 2E 28 73 30 50 0D 0A 0A 0A 20 20 20 20 ; s0S.(s0P....
00000040h: 20 44 78 78 78 78 78 78 20 64 78 20 6C 78 78 78 ; Dxxxxxx dx lxxx
00000050h: 20 20 31 30 2F 30 37 2F 30 31 20 20 38 37 20 20 ; 10/07/01 87
00000060h: 20 20 20 20 20 20 20 20 20 43 58 58 2D 34 30 30 ; CXX-400
00000070h: 30 30 20 20 20 6F 20 20 31 30 2F 30 37 2F 31 32 ; 00 o 10/07/12
00000080h: 20 20 20 70 61 67 2E 20 31 0D 0A 20 20 20 20 20 ; pag. 1..
00000090h: 50 78 78 78 20 6F 20 6A 78 78 78 78 78 20 64 78 ; Pxxx o jxxxxx dx
000000a0h: 78 20 72 78 78 78 78 78 78 78 20 64 78 20 31 30 ; x rxxxxxxx dx 10
000000b0h: 2F 30 37 2F 30 31 20 20 4E 6F 20 38 37 20 20 20 ; /07/01 No 87
000000c0h: 20 20 20 20 61 20 31 35 3A 30 34 3A 32 31 0D 0A ; a 15:04:21..
000000d0h: 0A 20 20 20 20 20 2E 26 64 30 44 41 78 78 78 78 ; . .&d0DAxxxx
000000e0h: 78 78 78 78 20 20 20 20 4E 78 78 78 20 20 20 20 ; xxxx Nxxx
000000f0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 43 ; C
00000100h: 78 78 78 78 78 20 64 78 20 72 78 78 78 78 78 78 ; xxxxx dx rxxxxxx
00000110h: 20 20 20 20 20 20 20 20 20 20 20 20 78 78 78 78 ; xxxx
00000120h: 78 78 78 0D 0A 20 20 20 20 20 2E 26 64 40 2E 28 ; xxx.. .&d@.(
00000130h: 73 30 53 0D 0A 20 20 20 20 20 31 32 30 30 30 39 ; s0S.. 120009
00000140h: 32 39 20 20 44 58 58 58 58 58 58 2C 20 4A 58 58 ; 29 DXXXXXX, JXX
00000150h: 58 58 20 20 20 20 20 20 20 20 20 20 20 20 44 4E ; XX DN
00000160h: 20 20 50 58 58 58 58 58 58 58 58 20 52 58 58 58 ; PXXXXXXXX RXXX
00000170h: 58 58 58 58 20 20 20 20 20 20 20 20 2D 31 30 2C ; XXXX -10,
00000180h: 30 30 0D 0A 20 20 20 20 20 20 20 20 20 20 20 20 ; 00..
00000190h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000001a0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000001b0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000001c0h: 20 20 20 20 20 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D ; -----------
000001d0h: 2D 0D 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 ; -..
000001e0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000001f0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
00000200h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
00000210h: 20 20 20 20 20 20 20 20 20 20 2D 31 30 2C 30 30 ; -10,00
00000220h: 0D 0A 0A 0A 20 20 20 20 20 31 30 31 31 33 20 20 ; .... 10113
00000230h: 31 30 30 30 30 30 30 30 20 42 58 58 20 20 20 20 ; 10000000 BXX
00000240h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
00000250h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 31 30 ; 10
00000260h: 2C 30 30 20 20 20 20 20 20 20 20 20 20 30 2C 30 ; ,00 0,0
00000270h: 30 0D 0A 20 20 20 20 20 31 30 33 30 35 20 20 32 ; 0.. 10305 2
00000280h: 30 30 30 30 30 30 30 20 43 58 58 58 58 58 58 58 ; 0000000 CXXXXXXX
00000290h: 20 2D 20 53 58 58 20 20 20 20 20 20 20 20 20 20 ; - SXX
000002a0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 30 2C ; 0,
000002b0h: 30 30 20 20 20 20 20 20 20 20 20 31 30 2C 30 30 ; 00 10,00
000002c0h: 0D 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ; ..
000002d0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000002e0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000002f0h: 20 20 20 20 20 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D ; -----------
00000300h: 2D 20 20 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 0D ; - ------------.
00000310h: 0A 20 20 20 20 20 20 20 2

Re: Problems with print events

by Ivo Valente, Monday, July 12, 2010, 17:54 (5008 days ago) @ Ivo Valente

....Continuation

00000310h: 0A 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ; .
00000320h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
00000330h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
00000340h: 20 20 20 20 20 20 20 20 20 20 20 31 30 2C 30 30 ; 10,00
00000350h: 20 20 20 20 20 20 20 20 20 31 30 2C 30 30 0C ; 10,00.

The diference between the information that prints correctly and the one that doesn't is a set of printing escape sequences that format the outputed text (i.e. make it bigger, bold, etc ).

In SecureCRT, a Telnet/SSH client, for these printing escape sequences to work we have to enable printing in raw mode , other wise each squence comes out in text.

Is there a print raw mode in this OCX component? Is there a way to recieve a binary buffer instead of a sitring the object_PrintData(Text) event?

Any help will be appreciated, we are running out options.

Thank You,
Ivo Valente

Re: Problems with print events

by wodDamir, Monday, July 12, 2010, 18:57 (5008 days ago) @ Ivo Valente

Hi Ivo,

Is there any chance you could send me a sample of what you are printing? I'd like to duplicate the same behaviour on my side.

If I succeed in that, then we can debug this and see what exactly happens. Is that possible?

You can send that to techsupport@weonlydo.com

Regards,
Damba

Re: Problems with print events

by Ivo Valente, Monday, July 12, 2010, 20:14 (5008 days ago) @ wodDamir

I have sent the requested file by email as instructed.

Thank you,

Ivo Valente