Rigo wrote:At a guess, I would suggest that RunInUae is doing something with the volume/device list which is causing the ASL requester to constantly refresh.
Perhaps asking Chris Handley personally what his program is doing might reveal more useful feedback, but it certainly doesn't seem like an OS problem, more that the OS is revealing some operation in RunInUae that it shouldn't be doing.
Simon
The ASL library sets up a filesystem notifyrequest for the current directory, also, it sets up a DosList change notification.
Either of these will cause a refresh. I have not used that program, so i'm just giving general advise on possible causality here.
It's unlikely that the program is modifying the current directory on a continual basis, nor is it likely that the program is
modifying the DOS device list constantly either.
It is likely that it could be patching some DOS or Workbench function/s incorrectly, which could easily cause an event loop
feedback effect like this, if the patch code happens to be calling another function which causes an event signal.
This is frequently a major cause of problems, when anyone patches operating system functions without knowing what is
happening inside, it immediately makes the external program unsupportable across different OS versions, because you only
have to change something minor and the external programs patch code blows up, worst of all, OS patches done by external
programs seldom do propper version checks, so it's nearly impossible to disable faulty code when used on later OS versions,
not only causing the program to break something, but crippling the OS for many other programs too.
I would suggest you run "Snoopy" and see if it's doing something continuously when just sitting there, or if it kicks it into
action when opening an ASL requester. It may show something interesting or usefull.
Or, you could simply not use UAE.
) And I don't remember this happening under update 6. Any ideas?
