ETerm32 Terminal Emulator
ETerm32 Terminal Emulator
I installed Wine from Synaptic and then installed a Windows terminal emulator program called ETerm32. As I understand, mainly, it provides the keyboard translations for a VT320 terminal so I can connect and function on a VMS-based server/application.
Running ETerm32 under Wine, I can connect to the server which displays a Username prompt. After typing the user name and hitting <ENTER>, the program/server prompts for a Password. Instead of waiting for a typed response and hitting <ENTER>, it accepts a blank password automatically without any input. This makes the log in attempt fail.
When the Username prompt reappears (which it normally does on a failed attempt), there is an "OP" already entered for the response. This can be backspaced off. Any other attempt to log in produces the same chain of events.
I have tried changing a setting in the ETerm32 software which defines the KeyCodes as either 7-bit (the default) or 8-bit. Changing this to 8-bit produces a "P" after a failed login, but does not help in allowing the Password to be entered. [I have changed this back to the default of 7-bit.]
I have looked thru the Wine Configuration, but I cannot see anything that would help with a communications-type program. I am not a communications expert, so I may have missed something.
Does anyone have any ideas on why the login process does not stop to allow the entry of a Password? If I can get past this, I think I will be in business.
If it matters, I am running PCLinuxOS2007 on a Dell Inspiron 1720.
Thanks.
Running ETerm32 under Wine, I can connect to the server which displays a Username prompt. After typing the user name and hitting <ENTER>, the program/server prompts for a Password. Instead of waiting for a typed response and hitting <ENTER>, it accepts a blank password automatically without any input. This makes the log in attempt fail.
When the Username prompt reappears (which it normally does on a failed attempt), there is an "OP" already entered for the response. This can be backspaced off. Any other attempt to log in produces the same chain of events.
I have tried changing a setting in the ETerm32 software which defines the KeyCodes as either 7-bit (the default) or 8-bit. Changing this to 8-bit produces a "P" after a failed login, but does not help in allowing the Password to be entered. [I have changed this back to the default of 7-bit.]
I have looked thru the Wine Configuration, but I cannot see anything that would help with a communications-type program. I am not a communications expert, so I may have missed something.
Does anyone have any ideas on why the login process does not stop to allow the entry of a Password? If I can get past this, I think I will be in business.
If it matters, I am running PCLinuxOS2007 on a Dell Inspiron 1720.
Thanks.
ETerm32 Terminal Emulator
On Fri, Jan 16, 2009 at 1:37 PM, nomen <[email protected]> wrote:
What keyboard is this, btw?
--
-Austin
Upgrade to 1.1.13 and if it still fails, file a bug.I installed Wine from Synaptic and then installed a Windows terminal emulator program called ETerm32. As I understand, mainly, it provides the keyboard translations for a VT320 terminal so I can connect and function on a VMS-based server/application.
Running ETerm32 under Wine, I can connect to the server which displays a Username prompt. After typing the user name and hitting <ENTER>, the program/server prompts for a Password. Instead of waiting for a typed response and hitting <ENTER>, it accepts a blank password automatically without any input. This makes the log in attempt fail.
When the Username prompt reappears (which it normally does on a failed attempt), there is an "OP" already entered for the response. This can be backspaced off. Any other attempt to log in produces the same chain of events.
I have tried changing a setting in the ETerm32 software which defines the KeyCodes as either 7-bit (the default) or 8-bit. Changing this to 8-bit produces a "P" after a failed login, but does not help in allowing the Password to be entered. [I have changed this back to the default of 7-bit.]
I have looked thru the Wine Configuration, but I cannot see anything that would help with a communications-type program. I am not a communications expert, so I may have missed something.
Does anyone have any ideas on why the login process does not stop to allow the entry of a Password? If I can get past this, I think I will be in business.
If it matters, I am running PCLinuxOS2007 on a Dell Inspiron 1720.
Thanks.
What keyboard is this, btw?
--
-Austin
ETerm32 Terminal Emulator
On Fri, Jan 16, 2009 at 1:53 PM, nomen <[email protected]> wrote:
different locale...?
--
-Austin
I mean, what keyboard is on your PC? A regular US keyboard? Or aI'm not sure if I am following you, but I am using a PC-style keyboard to emulate the keys on a VT320 terminal. That terminal is what is accepted by the server/application I am connecting to.
different locale...?
--
-Austin
Re: ETerm32 Terminal Emulator
Did you use wineconsole?nomen wrote:When the Username prompt reappears (which it normally does on a failed attempt), there is an "OP" already entered for the response. This can be backspaced off. Any other attempt to log in produces the same chain of events.
Is your program a console program or GUI? If it's console, then you should try to run it under wineconsole:nomen wrote:vitamin: I will look into wineconsole. However, I do have some doubts because of the emulation of the VT320 keyboard keys/functions.
Code: Select all
wine wineconsole my_app.exe
Unfortunately, the ETerm32 software itself is GUI. If am following you, I would not be able to run that under wineconsole.
Since I last posted, I tried a couple of things. One is to use telnet to connect to the server/application. I had actually forgotten about telnet until I spoke to someone else about connecting to this server.
To my surprise, the most important VT320 keys actually work. There is one functionality that does not and I am thinking that may not be a big deal. I have to digest that more. Since I am setting this up as "emergency" connectability, telnet may end up being a satisfactory solution to my problem.
Thanks.
Since I last posted, I tried a couple of things. One is to use telnet to connect to the server/application. I had actually forgotten about telnet until I spoke to someone else about connecting to this server.
To my surprise, the most important VT320 keys actually work. There is one functionality that does not and I am thinking that may not be a big deal. I have to digest that more. Since I am setting this up as "emergency" connectability, telnet may end up being a satisfactory solution to my problem.
Thanks.