Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mouse stops working moments after connecting #1

Open
mogorman opened this issue Mar 3, 2014 · 8 comments
Open

mouse stops working moments after connecting #1

mogorman opened this issue Mar 3, 2014 · 8 comments

Comments

@mogorman
Copy link

mogorman commented Mar 3, 2014

on first connect the mouse moves in all directions correctly. after tens of seconds the mouse no longer moves up , all up commands are interpretted as down and left and right remain fine, down also remains fine.

@mogorman
Copy link
Author

mogorman commented Mar 3, 2014

oh i forgot to say, its an apple iic with apple mouse, and running on latest git and happened with both 1.4 po disks

@mogorman
Copy link
Author

mogorman commented Mar 3, 2014

er sorry again iic+

@dschmenk
Copy link
Owner

dschmenk commented Mar 3, 2014

Ok, thanks for the info. I will try replicating on my IIc+. I have been running on my ROM 1 IIc for months without error.

On Mar 2, 2014, at 8:00 PM, mogorman [email protected] wrote:

oh i forgot to say, its an apple iic with apple mouse, and running on latest git and happened with both 1.4 po disks


Reply to this email directly or view it on GitHub.

@dschmenk
Copy link
Owner

dschmenk commented Mar 3, 2014

I tried out my IIc+. You actually get further than I do. It appears that the code I wrote to see if the IIc has a joystick or mouse connected to the port is breaking on the IIc+. Here are a few things to try:

Start your IIc+ in normal mode (press ESC+CTRL+CMD at power up).

Try starting with the mouse unplugged, then plug it in later.

Use a joystick on the IIc+. You can use it as a mouse with 'sudo a2joymou' or as a joystick in gsport with 'sudo a2joy'. You can plug a USB mouse into the Pi for X Windows and mouse control in gsport.

I'll look into what the failure is for the mouse on the IIc+, but I can't promise when.

Thanks for your help,

Dave...

On Mar 2, 2014, at 7:59 PM, mogorman [email protected] wrote:

on first connect the mouse moves in all directions correctly. after tens of seconds the mouse no longer moves up , all up commands are interpretted as down and left and right remain fine, down also remains fine.


Reply to this email directly or view it on GitHub.

@mogorman
Copy link
Author

mogorman commented Mar 4, 2014

my joystick doesnt seem to do much of anything on my apple iic+ but i havent used it before so it might just be a garbage device. Booting in normal mode didn't seem to matter with the mouse

@mogorman
Copy link
Author

mogorman commented Mar 4, 2014

is the source for the client code on the apple ii available? or anyway i can turn on more debugging easily?

@dschmenk
Copy link
Owner

dschmenk commented Mar 4, 2014

The source code is on the boot floppy: https:/dschmenk/apple2pi/blob/master/share/A2PI-1.4.PO (A2PI.S). The Merlin assembler is also included. There could be a couple reasons why the IIc+ behaves differently than all the other Apple IIs. The mouse firmware is put in differential mode, which returns delta values instead of absolute values. That would probably be the place to start.

Dave...

On Mar 4, 2014, at 7:21 AM, mogorman [email protected] wrote:

is the source for the client code on the apple ii available? or anyway i can turn on more debugging easily?


Reply to this email directly or view it on GitHub.

@BrianHoldsworth
Copy link

I have the same problem with my IIc+ (ROM 5?). One very reliable trick is to simply CTRL+RESET to restart the connection. This restores the mouse to normal operation for a brief period. The confusion of the pointer seems sort of related to your input actions. For example, use of the menus, where the button is held down while moving the pointer, seems to exacerbate the problem. The first time this happened to me, I quickly lost sight of the mouse cursor off the bottom of my screen and wound up rebooting! After a few times, I figured out the CTRL+RESET trick.

Maybe we can add a keystroke that manually toggles the client from joystick mode to mouse mode, instead of it automagically determining which input device is connected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants