PIC Problem

PIC Problem

[Gustavo Junior Alves]

Hi All,

I trying to run an app build on Clipper and everythigs goes fine, but 
password dialog. The keyboard freeze from this moment and on the log show:

KBD: port60 still has data

The keyboard still reported on the log but application. Any ideas about 
this problem????

This is the log:

http://www.coslinux.com.br/files/tmp/debug1.txt.gz (55kB)

Thank you,

Gustavo Junior Alves
alves@coslinux.com.br

Re: PIC Problem

[Stas Sergeev]

Hello.

Gustavo Junior Alves wrote:
> The keyboard still reported on the log but application. Any ideas about 
> this problem????
> This is the log:
> http://www.coslinux.com.br/files/tmp/debug1.txt.gz (55kB)
For some reasons the interrupts are
left masked, but from the log it is
unclear why (PIC needs more debug
messages).
Please open the bug report on an SF
page and attach your program to it.

PIC Problem

[Gustavo Junior Alves]

Hi Stas,

You remember that problem with keyboard??? (bug 663042 
<http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>). 
  The problem still occurs on text-mode (on the graphics mode, 
everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have any 
ideas?

Thanks,

Gustavo Junior Alves
alves@coslinux.com.br

Re: PIC Problem

[Gustavo Junior Alves]

Done.

PS: I tried only with DOSEMU 1.1.4.


Gustavo

Stas Sergeev wrote:

> Hello.
>
> Gustavo Junior Alves wrote:
>
>> The keyboard still reported on the log but application. Any ideas 
>> about this problem????
>> This is the log:
>> http://www.coslinux.com.br/files/tmp/debug1.txt.gz (55kB)
>
> For some reasons the interrupts are
> left masked, but from the log it is
> unclear why (PIC needs more debug
> messages).
> Please open the bug report on an SF
> page and attach your program to it.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

PIC Problem

[Gustavo Junior Alves]

Hi Stas,

You remember that problem with keyboard??? (bug 663042
<http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>). 

   The problem still occurs on text-mode (on the graphics mode,
everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have any
ideas?

Thanks,

Gustavo Junior Alves
alves@coslinux.com.br


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: PIC Problem

[Bart Oldeman]

On Tue, 28 Jan 2003, Gustavo Junior Alves wrote:

> You remember that problem with keyboard??? (bug 663042
> <http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>).
>
>    The problem still occurs on text-mode (on the graphics mode,
> everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have any
> ideas?

For all I know, running DOSEMU in terminal mode gives you an inherently
limited keyboard, so you're kind of stuck for plain text ssh and telnet
sessions.

But in X you can get good keyboard emulation using xdosemu and on the
console you can use $_rawkeyboard = (on).

Bart

Re: PIC Problem

[Stas Sergeev]

Hello.

Gustavo Junior Alves wrote:
> You remember that problem with keyboard??? (bug 663042
> <http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>). 
> The problem still occurs on text-mode (on the graphics mode,
> everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have 
> any ideas?
I have deleted your program a couple
of years ago, but IIRC it was masking
the keyboard IRQ and was reading the
port60 for keypresses - extremely dumb
way of dealing with keyboard and have
nothing to do with PIC btw.
AFAIK the problem with terminal mode is
that we can't detect the release events,
so the release event is passed to the
program immediately after the press
event, and if the program uses a polling
technique, then it will miss the press
event as it lasts for the very short
period.

Re: PIC Problem

[Gustavo Junior Alves]

The cursor prompt doen't showed on the screen, too. This event occurs 
before the keyboard reading (I believe). This may be the source of the 
problem???? (Sorry about the stupid question :-) ) If not, you can 
advice me about where to start fix this problem?

Gustavo

Stas Sergeev wrote:

> Hello.
>
> Gustavo Junior Alves wrote:
>
>> You remember that problem with keyboard??? (bug 663042
>> <http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>). 
>> The problem still occurs on text-mode (on the graphics mode,
>> everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have 
>> any ideas?
>
> I have deleted your program a couple
> of years ago, but IIRC it was masking
> the keyboard IRQ and was reading the
> port60 for keypresses - extremely dumb
> way of dealing with keyboard and have
> nothing to do with PIC btw.
> AFAIK the problem with terminal mode is
> that we can't detect the release events,
> so the release event is passed to the
> program immediately after the press
> event, and if the program uses a polling
> technique, then it will miss the press
> event as it lasts for the very short
> period.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html