PlanetZ forums - scopeusers.com

I downloaded the scope 4.5 package for mac OS 9 from soniccore FTP site but I would need help about how to install the files. I suspect that the installation flow is not that obvious. Anybody ever did this ?

Thanks in advance.

I would need help to set-up a test bench machine for my home made plug deisgned on my PC. The setup is:
- 1 PowerMac G3 with Mac OS 9.2.2 to host the stuff.
- 2 Scope Board (1 Pulsar I + 1 Scope Luna).

I do not know where to check if the board are recognized by the MAC and the driver correctly installed (complete Mac newbie !!! )

I succeed to install 3.1a from an old creamware original CD but was stopped at the key request step as I only have scope 4 keys for the boards.

I downloaded the Scope 4.5 for Mac from soniccore FTP site but I do not find any setup file just as on the 3.1a CD.

Any help would be welcome ...

CheerZ

i'm guessing hubird is on holidays.

Back in the day i could have helped, but my memory is a bit hazy. Have to say it was very easy to do though.

Check the Extensions folder - these are the 'drivers' (PC term), disable stuff you don't need.

i seem to remember you have to disable AppleTalk.

Those were about the only optimisations you needed to do as i recall.

I think I find the trick: the name of the directory was just WRONG !!!
After a rename operation, everything seem to go much further (finger crossing).
I keep you informed to tell you what the solution is ...

CheerZ

Talking of renaming i seem to remember having to rename .oxe files for them to work.

Still have some trouble.

The installtion complete but I now have error -39 (!?!) when trying to launch Scope

What do you exactly mean about renaming the oxe file. Do I have to rename them to a different extension ?

that's a file system error, meaning unexpected end of file...

actually there (really) is no such thing as an 'install process' on a (pre-OSX) Macintosh, but afaik the Creamware 'Installer' is so much 'Windows-like' that a number of things is messed that you wouldn't expect on a Mac at all.

Basically you just need the Scope folder and a few items that go into the System folder, usually it's automatically detected by the file type if those items belong to the Extensions or Control Panel folder.
There may be 3 letter filename extensions required (which MacOS does not need at all), or a directory must have a specific name - at least I remember that someone wrote about his experience with the process and I found it rather wiered.

As mentioned it's overcomplicated as the Mac doesn't have a registry or something like that - one could just copy the files to their respective location.

cheers, Tom

HUROLURA wrote: What do you exactly mean about renaming the oxe file. Do I have to rename them to a different extension ?

They should be just .oxe as normal, but i seem to remember that they sometimes had something weird at the end, like .oxe_something.

just coming home, nothing broken

In exensions folder (systemfolder):
- alloc
- CrossDev.dll
- Creamware audio driver

In preferences folder:
- HKEY_LOCAL_MACHINE (never had to care about this file manually, it's just always there after installing).

In OMS folder:
- Creamware OMS driver

use the OMS search for drivers function to detect the card(s).
Make your own OMS Auto Setup, don't forget to make it 'current', see OMS menu.

Make a backup of these files in case you are in trouble.
Renewing the Creamware driver and (especially) the OMS Midi driver assures you that an eventual problem is located elswhere if it doesn't solve the problem.

Oxe files are helpfull when installing new plugs not available yet in you all-keys file (ask Ralf to make that file updated).
Put the new plug files (dev, presets, etc) in the appropriate Scope folders, create a folder named 'oxe' (sic), and put the xxx.oxe (sic) files in it, and just start SFP, import the key when asked.

never had any problem with installing, Tom has right, no registry issues, copying the whole thing and making sure the system files are placed and the keys are imported should work.

It's amazing that Creamware did a so good job, as Scope is stable as hell on mac OS9, while .
Can't remember any system crash caused by Scope.
Tom already refers to the huge list of 'strange' looking system files in your Scope program folder, you get scared if you see all those files in the Scope folders for the first time if you don't know Windows.
I also had to get used to the 'ghost' SFP main menu bar, as normally the system takes care for creating the system standard menu bar.
It was the price for 'compatibility' (shared projects) between both platforms (tho I never was able or needing to test that).

that's definitely a first time seen for an OS 9 install

I still have a bunch of tips'n'tricks bundled in text files on how to make the best of OS9 for scope use. I can get to them on Monday.

About seven years has my machine been running extremely stable. The only crashes seem Modular or sequencer app related. Scope as standalone (without using Modular) and fed audio (ADAT) and midi from a laptop through an RME Multiface has never given me problems.

This is on a BW G3 450Mhz running 9.2.2
Soon to be replaced by a stellar intel/XP machine...