dlleigh@mit-amt.MEDIA.MIT.EDU (Darren Leigh) (01/23/90)
I have found a problem between SetCPU and the CLI path function. I run setcpu and and set up a new path in my startup-sequence. When I use the fastrom option, the CLI path is deleted (actually set to C:) or not accepted. I have tried various combinations of putting one before the other and in other startup files without result. Path seems to work fine in a CLI when I do it manually, but I can't get it to coexist with fastrom in the startup-sequence. I use SKsh so the loss of the CLI path doesn't hurt me much. The problem is with things like the Lattice "lc" command which looks for the files "lc1" and "lc2" apparently using the CLI path. In other words, I can't get "lc" to work while I have fastrom installed. Anybody have any ideas? My system: A2500, 1.3, SetCPU 1.50, Arp 1.3 Darren Leigh dlleigh@media-lab.media.mit.edu
daveh@cbmvax.commodore.com (Dave Haynie) (01/24/90)
in article <1464@mit-amt.MEDIA.MIT.EDU>, dlleigh@mit-amt.MEDIA.MIT.EDU (Darren Leigh) says: > I have found a problem between SetCPU and the CLI path function. I > run setcpu and and set up a new path in my startup-sequence. When I > use the fastrom option, the CLI path is deleted (actually set to C:) > or not accepted. Try "SetCPU FASTROM NOPATCH". For some reason, the PATH command relies on the Workbench string somewhere staying "Workbench" and not "Fastbench". I haven't run into this problem myself, but others have definitely reported it previously. > Darren Leigh -- Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Too much of everything is just enough