langz@athena.mit.edu (Lang Zerner) (12/08/87)
Here's how it goes: I'm using an Amiga 500 w/ Amiga RAM/clock module, Amiga external 3.5" floppy. Used setfont to set the system font. Also running are Conman 1.0, Heliosmouse 1.0, ClickUpFront 1.0, and PopCLI III. I'm running Diga! to talk to a Unix machine at MIT. I notice that one of the characters in the font I'm using is not to my liking, so I push the Diga! screen back and bring up fed, from the Amiga Extras disk. I make the change, exit fed, and go back to Diga!, only to find that she isn't talking to me. Or, that the machine at the other end is hung (I can still use menus, etc.). Leaving the modem connection, well, connected, I quit Diga!, then start it again. All appears well again. To test whether it was an interaction with fed, I run the same sequence again. After exiting fed I go back to Diga! and find everything hung again. So I quit Diga!, leaving the connection on, and bring Diga! back up again. Now, whenever I press a key, I get a bunch of at signs (@). I quit Diga! again, and quite finally, for at this time my Amiga hangs completely. No mouse movement, no nothing. I may not have given enough time for the power light to start blinking, but I didn't need to be warned that something was wrong with the machine. I rebooted, and now all is fine. It seems it was not that the remote machine was hung, nor that there is some major bug in Diga! or fed, since I've used both a number of times before with no troubles related to multitasking or what-have-you. Rather it looks like there is some kind of interaction between Diga! and fed that neither was expecting. I suspect fed of breaking the rules, since it doesn't seem to have changed much since the early anarchistic world of 1.1, but I don't have the facts. Does anyone know what the problem might be? --- Be seeing you... --Lang Zerner langz@athena.mit.edu ...ihnp4!mit-eddie!mit-athena!langz "No one is exempt from talking nonsense; the only misfortune is to do it solemnly" --Michel de Montaigne