SourceForge has been redesigned. Learn more.
Close

The newest special Version 5.7.1 2010-08-28

Ivan.Zhang
2010-08-28
2013-05-13
1 2 > >> (Page 1 of 2)
  • Ivan.Zhang

    Ivan.Zhang - 2010-08-28

    Login dialog:
    Use Tab to change selection from the auto-completion combobox;
    Use Enter to select the current host form the auto-completion combobox;

    download:
    http://www.box.net/shared/54g8slnjqc

     
  • qadex

    qadex - 2010-08-31

    I'm using poderosa 5.7.1 with cygwin terminals emulating xterm.  when I log into a remote Linux server, I get a scroll bar and can scroll back to see past output.   However if I issue the Linux

    screen
    

    command, the scroll bar grays out and I cannot scroll the terminal.

    I have tried toggling the  setting (whatever that is) but it didn't help.

    I also see lots of warnings like:

    An unknown escape sequence is detected.  unknown SGR commands 97
    

    ( or 92 or 94)  (unless I disable the warning)

    Version 4.1.0 does not have these issues and if there is no solution to the scroll bar issue , I will have to revert to it.  v5.7.0 also had this issue.

    Anyone know of a work-around?

    Thanks

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-01

    Ok, I write it down, I'll have a look at this issue.

    Actually, I don't know command "screen" before your posts.

    Why dont' duplicate another terminal in a new tab?

     
  • qadex

    qadex - 2010-09-02

    while screen can be used to manage multiple shell sessions, I use poderosa for that, as you suggest.  The reason I use screen is that if for any reason my terminal session is closed (network issues, poderosa is closed or crashed, I log of my windows laptop and take it home) then I can just open up a new terminal session, ssh to the server, type screen -r and be right back where I left off.  Any command I was running is still running, I can see the output that was generated before and while I was disconnected, etc.  really useful.

     
  • Jeev

    Jeev - 2010-09-05

    MAJOR 3 ISSUES in Poderosa

    1) once you login to the unix server with (SSH) after if you type "clear" command it does not work properly, it clear the above commands not only clearing the screen. example: in Putty if you type clear command it will clear the screen and it will push the screen to above and if we need we can scroll and see.

    2) the scroll option does not work from the laptop touchpad

    3)  if you choose the option connect to CYGWIN and if you dont have the Cywin installed it will give the below error and close the Poderosa completely (including the other tabs).  i think if the user does not have Cywin installed it should say "Poderosa  does not find Cywin installed on your system"

    ERROR LOG:
    An internal error occurred. Please check error file and report the error, thanks.
    When reporting the error,please attach the error file(error.log) which locates at the same directory with Poderosa.exe.
    At the same time, the steps to reproduce the error are expected from you.

    Can you please update the version with the above 3 errors fixed?

    Thanks in advance.

     
  • Anonymous

    Anonymous - 2010-09-07

    hello… please, support euc_kr..

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-07

    To:wizangzing
    Thank you for your explanation. It sounds a very usefull command.

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-07

    To:wizangzing
    Which version do you use?
    1. I can't reproduce the issue on my server.  Please try on your other servers and try to use different term type(xterm, vt100, kterm).
    2. I haven't verified this yet.
    3. I can't reproduce the issue. If you still have the issue, please past your error log file here.
    Thanks.

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-07

    To 수비니아빠 :
    Sorry, I have no plan to add other encoding support now.

     
  • qadex

    qadex - 2010-09-07

    with respect to the scroll bars in screen(1) issue,  I'm using Poderosa v 5.7.1  again, this works with v4.1.0 on the same servers.

    I tried several (abet similar) servers using cygwin terminals and selecting each terminal type in poderosa.  I also exported TERM and set term in .screenrc 

    $ cat /etc/redhat-release
    CentOS release 5.5 (Final)
    $ screen -v
    Screen version 4.00.03 (FAU) 23-Oct-06

    below is my error logs for xterm and kterm.  vt100 didn't generate errors but I still lost the scroll bar in screen. 

    TERM=xterm

    the 1st message appears about when the initial shell prompt occurs on my local.  the others appear after I issue the screen command on the remote.  they repeat with multiple errors for SGR commands 92, 94, and 97 always with the same stack trace.

    9/7/2010 1:11:33 PM
    ESC [?1034h
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 526
    9/7/2010 1:11:46 PM
    unknown SGR command 92
       at Poderosa.Terminal.VT100Terminal.ProcessSGR(String param) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 239
       at Poderosa.Terminal.VT100Terminal.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 116
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 103
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char[] seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char[] seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524
    9/7/2010 1:11:46 PM
    unknown SGR command 97
       at Poderosa.Terminal.VT100Terminal.ProcessSGR(String param) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 239
       at Poderosa.Terminal.VT100Terminal.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 116
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 103
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char[] seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char[] seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524
    

    TERM=kterm

    9/7/2010 1:46:38 PM
    bad number format  : Input string was not in a correct format.
       at Poderosa.Terminal.EscapeSequenceTerminal.ParseInt(String param, Int32 default_value) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 659
       at Poderosa.Terminal.VT100Terminal.ProcessCursorMove(String param, Char method) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 277
       at Poderosa.Terminal.VT100Terminal.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 138
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 103
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524
    9/7/2010 1:46:38 PM
    bad number format  : Input string was not in a correct format.
       at Poderosa.Terminal.EscapeSequenceTerminal.ParseInt(String param, Int32 default_value) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 659
       at Poderosa.Terminal.XTerm.ProcessScrollDown(String param) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 324
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 135
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524
    9/7/2010 1:46:38 PM
    bad number format  : Input string was not in a correct format.
       at Poderosa.Terminal.EscapeSequenceTerminal.ParseInt(String param, Int32 default_value) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 659
       at Poderosa.Terminal.VT100Terminal.ProcessCursorMove(String param, Char method) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 277
       at Poderosa.Terminal.VT100Terminal.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 138
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 103
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524
    9/7/2010 1:46:38 PM
    bad number format  : Input string was not in a correct format.
       at Poderosa.Terminal.EscapeSequenceTerminal.ParseIntPair(String param, Int32 default_first, Int32 default_second) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 673
       at Poderosa.Terminal.VT100Terminal.ProcessCursorPosition(String param) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 309
       at Poderosa.Terminal.VT100Terminal.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 142
       at Poderosa.Terminal.XTerm.ProcessAfterCSI(String param, Char code) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 103
       at Poderosa.Terminal.VT100Terminal.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\VT100.cs:line 58
       at Poderosa.Terminal.XTerm.ProcessEscapeSequence(Char code, Char seq, Int32 offset) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\XTerm.cs:line 75
       at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 524

     
  • qadex

    qadex - 2010-09-07

    hmm, I may have to repeat a couple of those tests.  I see that when you ask for a terminal type in the dialog for open cygwin terminal, you don't always get what you ask for.  I repeated the vt100 test with allow scroll in application mode on and in that config I get a scroll bar but it doesn't work as expected.  it doesn't let me see whats scrolled by in the screen session.  in fact I can't really figure out exactly what its showing.  something from before I started the screen session though.

     
  • qadex

    qadex - 2010-09-08

    I'd like to try skipping the cygwin terminal and just creating an telnet/ssh connection but I can't figure out what key format to use. the one I use when I ssh from the cygwin terminal doesn't work.  I tried converting it to several formats but always get a "wrong key format" error.  what format is it looking for?  if its not a format ssh-keygen can generate what does generate it?

    can you also update the error message to say something like "keys must be in the xxxx format."

    thanks

     
  • Jeev

    Jeev - 2010-09-08

    can you please check this?

    MAJOR 3 ISSUES in Poderosa

    1) once you login to the unix server with (SSH) after if you type "clear" command it does not work properly, it clear the above commands not only clearing the screen. example: in Putty if you type clear command it will clear the screen and it will push the screen to above and if we need we can scroll and see.

    2) the scroll option does not work from the laptop touchpad

    3) if you choose the option connect to CYGWIN and if you dont have the Cywin installed it will give the below error and close the Poderosa completely (including the other tabs). i think if the user does not have Cywin installed it should say "Poderosa does not find Cywin installed on your system" ERROR LOG: An internal error occurred. Please check error file and report the error, thanks. When reporting the error,please attach the error file(error.log) which locates at the same directory with Poderosa.exe. At the same time, the steps to reproduce the error are expected from you. Can you please update the version with the above 3 errors fixed?

    Thanks in advance.

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-09

    To:anjujeeva

    Which version do you use?
    1. I can't reproduce the issue on my server.  Please try on your other servers and try to use different term type(xterm, vt100, kterm).
    2. I haven't verified this yet.
    3. I can't reproduce the issue. If you still have the issue, please past your error log file here.
    Thanks.

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-09

    To wizangzing :
    I tried comman "screen" using 4.10, the scrollbar doesn't work too.
    Do you mean 4.10 works on your server?

     
  • qadex

    qadex - 2010-09-09

    Hi,

    I just tried 4.1.0 again and its behaving similar to vt100 in 5.7.1 - it scrolls but it scrolls to show some of what was there before you entered screen, but missing the last part.  not so useful.

    I wonder if there's some terminfo settings that need to be changed.  here's the settings for the default screen terminal and vt100:

    #       Reconstructed via infocmp from file: /usr/share/terminfo/s/screen
    screen|VT 100/ANSI X3.64 virtual terminal, 
            am, km, mir, msgr, xenl, 
            colors#8, cols#80, it#8, lines#24, ncv#3, pairs#64, 
            acsc=++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, 
            bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l, 
            clear=\E[H\E[J, cnorm=\E[34h\E[?25h, cr=^M, 
            csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H, 
            cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C, 
            cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\EM, 
            cvvis=\E[34l, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM, 
            dl1=\E[M, ed=\E[J, el=\E[K, el1=\E[1K, enacs=\E(B\E)0, 
            flash=\Eg, home=\E[H, ht=^I, hts=\EH, ich=\E[%p1%d@, 
            il=\E[%p1%dL, il1=\E[L, ind=^J, is2=\E)0, kbs=^H, kcbt=\E[Z, 
            kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA, 
            kdch1=\E[3~, kend=\E[4~, kf1=\EOP, kf10=\E[21~, 
            kf11=\E[23~, kf12=\E[24~, kf2=\EOQ, kf3=\EOR, kf4=\EOS, 
            kf5=\E[15~, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~, 
            khome=\E[1~, kich1=\E[2~, kmous=\E[M, knp=\E[6~, kpp=\E[5~, 
            nel=\EE, op=\E[39;49m, rc=\E8, rev=\E[7m, ri=\EM, rmacs=^O, 
            rmcup=\E[?1049l, rmir=\E[4l, rmkx=\E[?1l\E>, rmso=\E[23m, 
            rmul=\E[24m, rs2=\Ec\E[?1000l\E[?25h, sc=\E7, 
            setab=\E[4%p1%dm, setaf=\E[3%p1%dm, 
            sgr=\E[0%?%p6%t;1%;%?%p1%t;3%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;m%?%p9%t\016%e\017%
    ;, 
            sgr0=\E[m, smacs=^N, smcup=\E[?1049h, smir=\E[4h, 
            smkx=\E[?1h\E=, smso=\E[3m, smul=\E[4m, tbc=\E[3g,
    
    #       Reconstructed via infocmp from file: /usr/share/terminfo/v/vt100
    vt100|vt100-am|dec vt100 (w/advanced video), 
            am, mc5i, msgr, xenl, xon, 
            cols#80, it#8, lines#24, vt#3, 
            acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, 
            bel=^G, blink=\E[5m$<2>, bold=\E[1m$<2>, 
            clear=\E[H\E[J$<50>, cr=^M, csr=\E[%i%p1%d;%p2%dr, 
            cub=\E[%p1%dD, cub1=^H, cud=\E[%p1%dB, cud1=^J, 
            cuf=\E[%p1%dC, cuf1=\E[C$<2>, 
            cup=\E[%i%p1%d;%p2%dH$<5>, cuu=\E[%p1%dA, 
            cuu1=\E[A$<2>, ed=\E[J$<50>, el=\E[K$<3>, el1=\E[1K$<3>, 
            enacs=\E(B\E)0, home=\E[H, ht=^I, hts=\EH, ind=^J, ka1=\EOq, 
            ka3=\EOs, kb2=\EOr, kbs=^H, kc1=\EOp, kc3=\EOn, kcub1=\EOD, 
            kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA, kent=\EOM, kf0=\EOy, 
            kf1=\EOP, kf10=\EOx, kf2=\EOQ, kf3=\EOR, kf4=\EOS, kf5=\EOt, 
            kf6=\EOu, kf7=\EOv, kf8=\EOl, kf9=\EOw, lf1=pf1, lf2=pf2, 
            lf3=pf3, lf4=pf4, mc0=\E[0i, mc4=\E[4i, mc5=\E[5i, rc=\E8, 
            rev=\E[7m$<2>, ri=\EM$<5>, rmacs=^O, rmam=\E[?7l, 
            rmkx=\E[?1l\E>, rmso=\E[m$<2>, rmul=\E[m$<2>, 
            rs2=\E>\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h, sc=\E7, 
            sgr=\E[0%?%p1%p6%|%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;m%?%p9%t\016%e\017%;$<2>, 
            sgr0=\E[m\017$<2>, smacs=^N, smam=\E[?7h, smkx=\E[?1h\E=, 
            smso=\E[7m$<2>, smul=\E[4m$<2>, tbc=\E[3g,
    
     
  • Jeev

    Jeev - 2010-09-12

    TO: xjzhang1979

    Thanks for looking on the issue.
    I am using the version 5.6.0 and 5.7.1

    1)
    Seems to be the issue with the CYGWIN might be with my laptop or windows Vista. i have tried with XP and Windows 7 it is working fine.
    still i have paste the error log below

    -----------------LOG-----------------------
    9/12/2010 11:10:20 AM
    Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: startIndex
       at System.String.CtorCharArrayStartLength(Char value, Int32 startIndex, Int32 length)
       at Poderosa.Protocols.LocalShellUtil.PrepareEnv(ICygwinParameter p) in F:\Code\Poderosa\poderosa_SRC_20091218\Protocols\LocalShell.cs:line 189
       at Poderosa.Protocols.LocalShellUtil.Connector.Connect() in F:\Code\Poderosa\poderosa_SRC_20091218\Protocols\LocalShell.cs:line 107
       at Poderosa.Protocols.LocalShellUtil.Connector.AsyncConnect() in F:\Code\Poderosa\poderosa_SRC_20091218\Protocols\LocalShell.cs:line 76
    -----------------------------------------

    2)
    The scroll option does not work from the laptop touchpad. I have tried with all the different term type(xterm, vt100, kterm)
    Could you please check this?

    3)
    Clear Screen from the EDIT menu does not work properly. (OR)  "clear" command from the unix screen does not work properly. I have tried with all the different term type(xterm, vt100, kterm).

    Could you please check this?

    Setps to Reproduce the Issue:

    a) Login to the Unix or Linux system with SSH.
    b) type the command "clear"  (this will earse all the login details and the login banner)
    c) type some more command to have the more than 1 page of the screen to scroll (ex: ls -ltr in the /tmp)
    d) then type "clear" command this will clear the screen.
    e) scroll the screen using the scroll bar in the right.
    f) this should have all the details but  Poderosa will erase some details (due to this we can not check the previous details in case if we need)
    g)example: in Putty if you type clear command it will clear the screen and it will push the screen to above and if we need we can scroll it and see.


    if you can fix the 3rd issues i would be greatly appreciate. i think this is very important for all the UNIX admins since we always look for the log, etc details in the previous screen if we need.
    Hope you will be able to help in this soon

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-13

    To anjujeeva:
    for the 3rd issue, I tried as your steps.
    I can't reproduce it.
    Have tried it on different servers?

     
  • Jeev

    Jeev - 2010-09-13

    TO:xjzhang1979

    I have tried the same in multiple servers. i have upload the details with the screenshot in the below link

    http://www.mediafire.com/?ccloo3hkyyf5fij

    Please check it and let me know if you need any details. if you can resolve this issue it would be greatly appreciated.
    Thanks in advance.

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-14

    To anjujeeva :
    Ok, I understand the issue.
    I'll have a look at it.

     
  • Helmet

    Helmet - 2010-09-15

    I am attempting to use this version of Poderosa (5.7.1 2010-08-28) with Cygwin 1.7.7 and continue to get the following error.

    cygterm.exe - Entry Point Not Found

    The procedure entry point _fcntl64 could not be located in dynamic link library cygwin1.dll.

    Any thoughts?

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-15

    To wizangzing and anjujeeva  :
    About the scroll bar mode in command "clear" and "screen", Poderosa uses a standard way to process the term command.

    In SecureCRT, there is an option for user to choolse the scroll mode.

    here is a temperary build, which I didn't make enough test, please have a try.
    If no other bad impact, I'll release it.
    http://www.box.net/shared/yv9s05yaj0

    Thanks.

    In putty, for command "screen" , it also use a standard process, so it's scroll mode has the same behaviour like poderosa.

    However, I made some change so that user can select the scroll mode.

    The default mode now:
    1. "clear" command: like putty, it will scroll up the current screen, not clear it.
        you can change it to the standard way: Tools=> Detailed preference editor…=>set "scrollupSimulateEraseScree" to false;

    2. "screen" command: if you want it behave like SecureCRT, the following two options need to be enabled:
       1) options=> ternimal => enalbe "allow scroll in application mode"(default is disabled);
      2) Tools=> Detailed preference editor…=>set "ignoreScrollRegionSetCommand" to false(the default value is "false" already);

     
  • Ivan.Zhang

    Ivan.Zhang - 2010-09-15

    correct a typo:
    2. "screen" command: if you want it behave like SecureCRT, the following two options need to be enabled:
       1) options=> ternimal => enalbe "allow scroll in application mode"(default is disabled);
      2) Tools=> Detailed preference editor…=>set "ignoreScrollRegionSetCommand" to true(the default value is "true" already);

     
  • qadex

    qadex - 2010-09-15

    Thanks for working on these issues!!

    I'm seeing some problems in the temporary build. I don't think they're all new but it all seems worse today.I'll try to pin them down better as I use it more and when I'm a bit less busy, but I've seen:

    -1- terminal loose track of where the bottom of the screen is and there's a line of old text below where your shell input prompt is drawn.  I've seen this before.

    -2- in vi I've seen
    -2a- adding a line after the last line in the file (G then o commands) left the cursor on the last line instead of scrolling it up and giving me a blank line to type on.

    -2b-  a garbled display with chunks of the file missing so I couldn't tell what I was editing

    -3- problems with the screen status line display, sometimes missing, sometimes repeated in middle of the screen, sometimes poping up after several seconds delay.

    -4- my PS1 is
            PS1="${CYAN}${USER}@${HOST} \ \`date +%l:%M\`
    $ ${YELLOW}"
            export PS1
    which looks like

    wizangzing@server1 /usr/local 10:15
    $

    after tput clear (or <ctrl>L) I see the 1st line of my 2 line $PS1 prompt on the top line of a blank screen.  when I then type something, the screen scrolls one line and I see my $ prompt (the second line of $PS1) above the  wizangzing@server1 line and my input goes there above the wizangzing@server1 line.

    this is with poderosa thinking its an xterm and screen using its default TERM=screen.
    tomorrow I'll try to convince poderosa to use vt100.

     
  • Jeev

    Jeev - 2010-09-16

    TO: xjzhang1979

    Thanks a lot for looking the issue and fixing quick.

    1) Clear is working fine for the “XTERM”. Can you please make the same for VT100 also because VT100 not working for Linux servers

    2) Once we do the “clear” command it does the work fine but if we scroll up and  see the above details and then again started typing the next command it supposed to scroll the screen above and keep in the starting of the screen but poderosa  stays in the same place (this is not major)

    3) When I use the “XTERM” some time I am getting the below error (I don’t get the same error when I use VT100)

    9/15/2010 7:23:19 PM
    ESC [?1034h
      at Poderosa.Terminal.EscapeSequenceTerminal.ProcessChar(Char ch) in F:\Code\Poderosa\poderosa_SRC_20091218\TerminalEmulator\TerminalBase.cs:line 526
    9/15/2010 7:26:36 PM

    4) If possible can you please add PUTTY also with poderosa.

    Thank you

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.