Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!sci.kun.nl!wn3.sci.kun.nl!ge
From: ge@wn3.sci.kun.nl (Ge' Weijers)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Mouse vectors etc.
Keywords: mouse vector
Message-ID: <2447@wn1.sci.kun.nl>
Date: 13 Nov 90 14:19:04 GMT
References: <2417@wn1.sci.kun.nl> <3250@medusa.informatik.uni-erlangen.de>
Sender: root@sci.kun.nl
Distribution: comp
Lines: 27

csbrod@medusa.informatik.uni-erlangen.de (Claus Brod ) writes:

>Must be when the AES come up. The ROM jumps over exec_os, then does
>some Dgetpath and Dsetpath calls to get its view on paths right,
>and at some time opens a physical workstation which is when the
>mouse vectors are probably being initialized. You will have to
>implement some technique for checking whether your program starts
>in the AUTO folder, make it resident and sit there and wait for the
>AES to come up. I'm not sure that there is any decent and documented
>method for doing things like this. Moving your routines to a DA
>might solve your problems.

(Thanks for answering whilst working on your thesis)

That was my thought. The thing actually works up to the point the desktop
finishes writing the folder windows, and then the mouse freezes. I have
not yet disabled the normal mouse, and that continues to work.
I guess I have to do some debugging, tracing the contents of vectors etc..
(Yes, I have killed the Rsconf() call so the control panel does not reset
the serial port.)

Ge' Weijers
--
Ge' Weijers                                    Internet/UUCP: ge@cs.kun.nl
Faculty of Mathematics and Computer Science,   (uunet.uu.net!cs.kun.nl!ge)
University of Nijmegen, Toernooiveld 1         
6525 ED Nijmegen, the Netherlands              tel. +3180652483 (UTC-2)