| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 既知事項/未実装 | 中 | 仮承認 | 未処理 | 2019-10-25 04:23 | 2019-10-25 23:23 |
| テスター | cube1us | 担当者 | ソース | interpro/interpro.cpp | |
| バージョン | 0.214 | 発生バージョン | 修正バージョン | ||
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | ip2000 | ||||
| セット詳細 |
 ip2000 - InterPro/InterServe 20x0 | ||||
| 概 要 | キーボードのリピートとストロークの問題について。 | ||||
| 詳 細 | The Intergraph Interpro (Clipper) driver page at https://wiki.mamedev.org/index.php/Driver:InterPro says: "One last known bug relates to the keyboard emulation; occasionally some keys can get "stuck", and endlessly repeat, and in other cases require several repeated presses before a character is generated." On my Windows 10 X64 i7-8700K 3.70Ghz system, this issue is making the Clipper emulation very difficult to use. It is far from "occasionally". It is more like 20% (or more) of the keystrokes. There are also dropped keystrokes. It also affects trying to use the delete key to back up. (As an aside, I went looking for a way to essentially turn off typematic completely in mame or the interpro driver, but in looking through the XML config files and the like, I was unable to find a way.) | ||||
| 再現手順 | When installing CLIX, during newprod when trying to use the arrows. After install. Try to log in - on the login page it is particularly bad. Or, try to do editing (e.g., of /etc/inittab) and notice "funky" operation. Or try to enter commands. It can result in double "enter" keys which can cause real headaches. Or just about anything else that uses the keyboard. ;) | ||||
| 追加情報 | Turning off auto-repeat in the settings => keyboard area of CLIX text windows helps (thanks for the suggestion). That also makes the dropped keystrokes symptom more obvious. This problem seems unaffected by win32 vs. win64 executables. This problem does not seem to be affected much by the speed of the host machine - I tried it on an old, slow laptop with similar results. This problem is noticeably worse if one is running with the emulation speed set to >100% It looks to me as though it sees the keypress event, but not the release - and then it sees a release on the next keystroke. As a hunch, it seems likely to do with the i8049 -- perhaps with a mismatch between the i8049 emulation speed and the clipper CPU speed or some other issue relating to the i8049. Until I was told about the idea of disabling auto-repeat in CLIX window, I was resorting to enabling getty on -serial2, and accessing the command-line stuff that way. JRJ | ||||
| 添付ファイル | |||||