Unresponsive app

[GoogleCodeExporter]

App will occasionally become unresponsive to keyboard input, seemingly random.

Original issue reported on code.google.com by pissmasterplus on 19 Jun 2012 at 11:11

[GoogleCodeExporter]

I think this issue should be fixed urgently, it makes the tracker useless.

Original comment by k.dron...@gmail.com on 16 Sep 2012 at 3:16

[GoogleCodeExporter]

Has this been fixed in a recent version?

Original comment by Kdeeze...@gmail.com on 10 Aug 2013 at 9:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This is more-or-less fixed in the official SDL Win32 version (available in 
download section at program homepage). Still occasionally, if program window 
loss focus for awhile, there might be some pending events buffered which lead 
to no response from keyboard. However, since program version 2.4.09, there is 
key combo for such situation (Ctrl+Shift+F10) which makes the program 
responding again even in this case.

Original comment by subz3ro....@gmail.com on 12 Feb 2014 at 10:31

[GoogleCodeExporter]

That's no good for me. I run AT2 in a Toshiba Libretto. 

Original comment by k.dron...@gmail.com on 12 Feb 2014 at 11:11

[GoogleCodeExporter]

Could you please fix it for DOS? It's really important that this would run in 
old machines running DOS that have the right hardware.

Original comment by k.dron...@gmail.com on 12 Feb 2014 at 11:13

[GoogleCodeExporter]

Wow, thanks for looking into it, this issue was driving me crazy! I'd really 
love to see this fixed in the DOS version though. May I ask, what caused this 
exactly?

Original comment by ikk...@gmail.com on 12 Feb 2014 at 12:24

[GoogleCodeExporter]

What exactly is the problem with responsiveness in DOS version?

Original comment by subz3ro....@gmail.com on 12 Mar 2014 at 6:16

[GoogleCodeExporter]

As the original message says, app becomes unresponsive to keyboard. Keyboard 
stops working. TEsted on my Toshiba Libretto CT50.

Original comment by k.dron...@gmail.com on 12 Mar 2014 at 6:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry, but I would need more thorough symptom description than this if you want 
me trying to do something with it :) Actually DOS version wasn't ever suffering 
from keyboard not working. I only have one report (also with Toshiba Libretto 
notebook) about keys being stuck while previewing instrument and multiple keys 
are touched.... but pressing further "note" keys resolves that situation and 
new keyboard presses are again recognized. As this has not happened to me on my 
old DOS desktop PC back then (when used to had it yet), maybe this can be some 
specific issue related to Toshiba Libretto model, so I can hardly do much about 
it without possibility to reproduce this faulty behavior. I recommend you to 
try brand new DOS version (2.3.46) that is already available for download on 
AT2 homepage, which has completely rewritten some critical IRQ stuff for more 
responsiveness on slower CPU's. Maybe this helps for your issues with keyboard 
too. If not, let me know and I can try to guess something out (just from my 
mind - without testing) also with the keyboard routine.

Original comment by subz3ro....@gmail.com on 14 Mar 2014 at 7:44

[GoogleCodeExporter]

I'm using the DOS that comes with Windows 95, not MS-DOS, so I suppose it 
should be a little bit updated.

This issue happens both by booting straight into DOS or by exiting to DOS under 
Windows. Also probably on a DOS box in Windows, but I don't remember.
Let m know what I can do to help you out!

Original comment by k.dron...@gmail.com on 14 Mar 2014 at 9:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

First thing what you can do is trying this new version... ;)
http://adlibtracker.net/files/at2g3r46.zip

Original comment by subz3ro....@gmail.com on 14 Mar 2014 at 1:16

[GoogleCodeExporter]

Sweet! I'll give that a try and report back. Thanks man!

Original comment by k.dron...@gmail.com on 14 Mar 2014 at 2:55

[GoogleCodeExporter]

Yup, after a while, keyboard s tops working completely. 
I pressed one of the note keys and made it stop.
Nothing works, not even ESC. The cursor blinks but I can;t do anything with it.

How else can I assist you to fix this problem up? It's a shame, the Libretto is 
the perfect little AT2 machine.

Original comment by k.dron...@gmail.com on 15 Mar 2014 at 12:53

[GoogleCodeExporter]

Like, now I typed a few notes in, and after 5 keypresses, again, keyboard locks 
up and I cannot operate the computer anymore.

Original comment by k.dron...@gmail.com on 15 Mar 2014 at 12:56

[GoogleCodeExporter]

Unless we're talking about different issues, the program doesn't actually "lock 
up", but one or more keyboard keys get stuck. Usually it's one of the 
"MIDIBoard" or modifier keys (ctrl/alt/shift). It never happens with other keys 
like function keys or tab/enter/backspace/arrows etc. Pressing the stuck keys 
fixes it but there's usually no way to tell which keys you have to press.

The weird thing is that it seems to happen at random for the modifier keys. 
When it happens to the MIDIBoard keys it's more predictable (usually at the 
Instrument window, any keys you previously pressed in the pattern editor will 
activate simultaneously on the first keypress). The modifier keys tend to lock 
up at random in the pattern editor. For example when holding arrow down to 
scroll down, after a while it'll start selecting stuff as if you pressed shift. 
Or you press key 3 and instead of inserting note D# it will switch to octave 3, 
as if you're holding ctrl.

I used to think this was related to the FreeDOS kernel.. however I have never 
encountered any other programs/games that do this. And since 
k.dron...@gmail.com is using Win9x DOS it can't be caused by that (unless, as I 
said, we're talking about two entirely different issues here)
Maybe MSDOS 6.2 allows some non-standard way to access the keyboard buffer, 
which Adtrack2 happens to use, that was removed in MSDOS 7 and FreeDOS? (just 
thinking out loud here)
It might be a BIOS issue too but I've had this happen on three computers with 
different chipsets. In fact I've never had a computer where this DIDN'T happen!

Original comment by ikk...@gmail.com on 17 Mar 2014 at 12:51

[GoogleCodeExporter]

No, this isn't the case, at least not in mt Toshiba Libretto.

The program gets stuck for input after pressing any of the "note" keys 4 or 5 
times, as described above. Nothing can be done after that. None of the keys 
unstuck the software.

Original comment by k.dron...@gmail.com on 17 Mar 2014 at 1:47

[GoogleCodeExporter]

Ah, sorry for the confusion then, I thought we were talking about the same 
thing. I didn't notice the new version though, will give that a spin to see if 
the stuck key issue has been fixed.

I think I got an old Toshiba Sattelite here somewhere with YMF715, maybe I can 
reproduce your issue on it.

Original comment by ikk...@gmail.com on 17 Mar 2014 at 2:59

[GoogleCodeExporter]

Ok, some experimental changes done to keyboard routine. Please try with 
attached EXE. If you encounter key stuck anyway, try with pressing CTRL key 2 
times, whether it helps. Let me know then....

Original comment by subz3ro....@gmail.com on 17 Mar 2014 at 10:11

Attachments:

• ADTRACK2.EXE

[GoogleCodeExporter]

ikk...: I think the problem only happens in Toshiba Librettos. I only heard of 
this from other fellow Libretto users!
Subz3ro: thanks, I'll give it a try and report back!

Original comment by k.dron...@gmail.com on 17 Mar 2014 at 10:19

[GoogleCodeExporter]

k.dron: So, any news? I'm waiting with new release for this late change :)

Original comment by subz3ro....@gmail.com on 19 Mar 2014 at 7:14

[GoogleCodeExporter]

I've got two gigs coming up and had no time to test this with the Libretto. I 
asked a friend to chip in the conversation and test it too.
Let me see if I can test it today.

Original comment by k.dron...@gmail.com on 19 Mar 2014 at 9:55

[GoogleCodeExporter]

OK, gave it a try, still doesn't work. 
Program does not respond to keyboard input after 5 notes are entered.
It's always after 5 notes.
CTRL does nothing.

Original comment by k.dron...@gmail.com on 19 Mar 2014 at 10:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@k.dron: Hmm, weired. So back to the issue description. You say then, that you 
do encounter key stuck after 4-5 presses of "midiboard" keys on your keyboard 
right? Here are some additional questions:
- Does this happen only when testing instrument (in Instrument Control panel, 
Instrument Editor window, File Selector, Replace Instrument dialog, etc.) or 
also when putting notes to pattern in Pattern Editor?
- Does this happen also when you are (in Midiboard mode) playing already put 
notes in pattern with Space key?

Original comment by subz3ro....@gmail.com on 20 Mar 2014 at 7:54

[GoogleCodeExporter]

This happens with "midiboard" when trying to enter notes on the pattern editor.

Pressing spacebar works fine.

Original comment by k.dron...@gmail.com on 20 Mar 2014 at 3:32

[GoogleCodeExporter]

@k.dron: Ok then, one last idea.... Try with attached version, whether it 
resolves the problem.

Original comment by subz3ro....@gmail.com on 1 Apr 2014 at 2:36

Attachments:

• ADTRACK2.EXE

[GoogleCodeExporter]

Sorry I couldn't try this before, I was away.

I don't know what you did, but you rock. IT WORKS NOW!!!!

I've been hammering at the keyboard and it doesn't lock up!

Original comment by k.dron...@gmail.com on 15 Apr 2014 at 12:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok, that's good info. I already implemented some changes to the new 'official' 
DOS version. Please try if it works too and let me know :-) Thanks.
http://adlibtracker.net/files/at2g3r47.zip

Original comment by subz3ro....@gmail.com on 16 Apr 2014 at 11:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It seems to work fine too.

Original comment by k.dron...@gmail.com on 24 Apr 2014 at 5:11

[GoogleCodeExporter]

That's fine! I'm closing this issue then. If anything occurs, you know what you 
should do :-)

Original comment by subz3ro....@gmail.com on 25 Apr 2014 at 7:38

• Changed state: Fixed