dean@ns.network.com (Dean C. Gahlon) (01/12/90)
This is kind of a peculiar problem I ran into over the past few days, and I'm curious if anyone can shed some light on it. I'm running an A500, 1 meg memory, 2 floppy drives, and have GOMF3.0, Qmouse, AREXX, and FaccII running in the background. I'm also using the PATH: device for access to all the system directories (S:, L:, C:, DEVS:, LIBS:) telling it to look on df0 then df1 for each type of directory (i.e., the C: path tells it to look in df0:c then df1:c). I had the latest version of DME in the c directory on one of my disks. Whenever I typed dme in such a way that the PATH: device would cause that copy to be loaded, the system would instantly GURU. If I specified the path to that copy explicitly, everything worked fine. If I loaded a different copy of that same version of DME, everything worked fine. I finally "solved" the problem by renaming that copy to "dme.bad" and copying dme to that disk again, but I still wonder what's going on here. It seems obvious that something strange is going on with the PATH: device, but it seems odd that it only happened with that one particular disk. If anyone has any suggestions, I'd be glad to hear them. Dean C. Gahlon dean@ns.network.com