PlanetZ forums - scopeusers.com

Hello all,

after a while i wan't to reanimate my pulsar/luna cards on my old PPC G4 Giga Mac with Mac OS 9.2.1.

Scope 4.0 is used. Loaded succesfully when scope is lunched. sonicWorx is seen my Asio Creamware (copied Asio Driver into the folder!)

so it seems that the driver is loaded successfully.

now - i wan't to setup OMS. but OMS can't load the Creamware OMS Driver.
it says allways "The OMS driver "Creamware OMS Driver" could not be loaded. -1"
the driver is in systemfolder/oms folder/
manually copied

OMS Version is 2.3.8

hope some here can help me

best
Andy

That was the last version of OMS wasn't it? Not sure how much difference it makes but i had OS9.2.2 in the day. Also i seem to remember something about using OMS2.3.6 rather than the last one, perhaps try that (this is all a bit hazy for me now).

Make sure AppleTalk is disabled too.

Mr Arkadin wrote:That was the last version of OMS wasn't it? Not sure how much difference it makes but i had OS9.2.2 in the day. Also i seem to remember something about using OMS2.3.6 rather than the last one, perhaps try that (this is all a bit hazy for me now).

Make sure AppleTalk is disabled too.

it seems it will be very hard to get my old good pulsar running on mac os 9.2.1

i've gone an update to 9.2.2

installed for testing my m-audio ozone. OMS is seening it, it's running very well.
i don't have an older version of OMS. my current version is 2.3.8. no other version here. the Creamware OMS Driver isn't installed. very very bad i'm very sad if i can't use my lovely old good pulsar ... please help ... i love it. it's a good soundcard.

many many thanks to all who help me.

thanks again

Andy

i seem to remember that you have to manually copy the drivers into the correct folder - it doesn't always install them. i can't remember which folder you have to copy it to though (maybe Extensions, OMS folder? Not sure), but you'll find the driver in the Apps folder i think.

antman313 wrote:

Mr Arkadin wrote:That was the last version of OMS wasn't it? Not sure how much difference it makes but i had OS9.2.2 in the day. Also i seem to remember something about using OMS2.3.6 rather than the last one, perhaps try that (this is all a bit hazy for me now).

Make sure AppleTalk is disabled too.

it seems it will be very hard to get my old good pulsar running on mac os 9.2.1
...
Andy

so - if i look at the oms folder:

the m-audio usb oms support driver has an icon. the creamware oms driver don't.
i don't know if this is important ...



i'm very sad about that ...

Andy

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.

see also:
http://www.planetz.com/forums/viewtopic.php?t=24307
OMS 2.3.8 was my latest working version, and it did the job for a long time, mr Arkadin was right

OMS sucks, but if it works it mostly stays intact.
I remember there was an issue in the order of installing Cubase, Creamware and OMS.
Try OMS after Creamware.
I never got the problem or the solution with OMS 'clear', but after some trial and error I always got it to work.
You can also try different (older) versions of Quicktime.
The last version I used to use says:
N1-6.0.2
QuickTime
N-6.0.3.

I find myself talking in passed time, yet I run my cards on my OS9 mac, with mentioned specs.
My OSX mac runs Cubase SX3, and obviously I experience my OS9 mac (already) as an 'external audio box', I'm 'on OSX' for my feeling.
And I still can open Cubase (VST5) on the OS9 mac to check old 'Creamware' songs or something.
hardly needed anymore, the transition is really closed now, the OS9 mac is really my 'audio studio box' now, the CPU must get lazy already

You'll get it to work, it simply should

Hello Andy.
You should be starting scope platform before starting oms setup.
I encountered this trouble, too.