[ryju]

ok I was running panther. I switched back to 10.2 using archive and install, NOT keeping the user/network settings. either way somehow my panther's apps got pushed into the root Application folder. No problems there.

Now whenever I open terminal to check my processes or uptime (using "top" and "uptime") neither work, it says Bad Command or filename. I also tried that in X11 with no luck.

Then with Pacifist I extracted another Terminal app from 10.2's essentials package, still no luck.

I was wondering if I'm missing some unix command or step to make Top work. My CPU app is showing 100% usage and i want to see what's causing it.

Thanks a ton in advance. olaha.

[CharlesS]

Perhaps you could show us the exact error message you get, copied and pasted from the Terminal? 'Bad command or file name' is a DOS error.

[ryju]

Originally posted by CharlesS:
Perhaps you could show us the exact error message you get, copied and pasted from the Terminal? 'Bad command or file name' is a DOS error.

Last login: Thu Jul 31 20:54:29 on console
[ryju:~] ryju% top
top: Command not found.

Voila ^_^

[Art Vandelay]

It sounds like your problem lies in choosing Archive & Install to downgrade to Jaguar. Since you said your Panther apps are still in the Jaguar apps folder, you may have other Panther stuff scattered in your Jag install, which is causing your problems. You probably need to format the drive when downgrading to Jaguar from Panther.

[CharlesS]

Originally posted by ryju:
Last login: Thu Jul 31 20:54:29 on console
[ryju:~] ryju% top
top: Command not found.

Voila ^_^

Sounds like the top command is either missing or /usr/bin is not in your search paths for some reason. Before I went as far as reformatting your hard disk, I'd go check out /usr/bin and see if top is in there. If it is, then it's probably just the search paths - type "echo $path" in the Terminal to find out if /usr/bin is in the search paths or not.

If top is missing from /usr/bin, you can reinstall it with Pacifist. Otherwise, you should just have to make a few changes in the config files to include /usr/bin in the search paths and you should be good to go.

[Art Vandelay]

Yeah, listen to CharlesS. I didn't notice what the error message was before I replied.

[Sarc]

Looks that you somehow didn't install the "BSD Subsystem", a vital component if you want to mess with the Terminal.

[ryju]

Thanks so much guys.
What I did was reinstall the BSD subsystem, now all is good.

Thanks again!