OS9 and Classic the same ???

[BondoMan]

I have this problem when loading Classic....
I have DAVE (network utill) installed under OS9 on another partition.
But when starting Classic I get DAVE loading also.....!!!!

I want to disable DAVE when using Classic (because I have it under OSX)...but NOT when using OS9.

Are they sharing the same setup ???
(I guess this applies to any other installed controlpanel or utill)

[xchanyazy]

From the classic control panel, you can open up the extension manager. I suggest making a special set just for when booting into classic - take off DAVE and any other programs you have OS X replacements for. Then, you can just switch between extension sets when booting.

[BondoMan]

.....that wouldn't be the best way, would it ??!!!
Then I had to start Classic from the SystemPref. every time.

I want it to start the right stuff when double-clicking a Classic application.

But I thought of trying to use the StartUpManager inside OS9 Classic and finetune the startup........

But that makes me think again.....is OS9 and Classic the same ??
If I change the settings in Classic are they changed in OS9 also ???

[bakaDeshi]

But that makes me think again.....is OS9 and Classic the same ??
If I change the settings in Classic are they changed in OS9 also ??? [/B]
Yes and Yes. Classic is OS9. Whatever you have set in your extensions manager to load in os9, is what loads in classic. If you make changes to this in classic, you make changes to os9. The alternatives are: 1) make an extension set named classic(from the extension manager) as suggested previously or 2) install another copy of os9 specifically for classic. Either way you can specify what you want loaded when you launch classic in osX and what you want launched when you boot into os9. There are hints and other threads that go into optimizing classic inside of osX, do a search if you're interested in the gory details.

[vonleigh]

Hello,

1. Grab your OS 9 system folder and copy it to your users folder anywhere you want.

2. Go to system prefs and tell it to launch your new OS 9 folder, from your user's folder, as Classic.

3. Customize this classic environment with as few control panels and extensions as is humanly possible. I would even go as far as suggesting turning off everything and seeing what complains, then activating that only (there is overlap with OS X).


HTH,
Vonleigh

[BondoMan]

...Thanx for all your patience and good replies ;-)

[lerkfish]

vonleigh beat me to the punch, I was going to suggest a separate OS9 and classic folder.

The only thing I might do differently than he suggests is to take an absolutely clean OS9 folder, freshly installed (like on a different partition) to use as your classic, and add things as you find you need them, otherwise you might find yourself needlessly troubleshooting extensions conflicts from extraneous legacy installed applications if you just duplicate your present OS9 folder.