SCOPE 4.0 + Macintosh = Error 0001
I could use some help.
I have a Macintosh 1.25g/512 running Scope on my Pulsar II (Project).
I have updated to version 4.0 and when I launch I get this error:
Unable to Start Scope Platform error 0001
Does any body knows what this means?
3.1c still runs great with no problems!
Any help would be great!
btw I love using SFP and os9 sounds awesome. Looking forward to OSX!
I have a Macintosh 1.25g/512 running Scope on my Pulsar II (Project).
I have updated to version 4.0 and when I launch I get this error:
Unable to Start Scope Platform error 0001
Does any body knows what this means?
3.1c still runs great with no problems!
Any help would be great!
btw I love using SFP and os9 sounds awesome. Looking forward to OSX!
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
I've noticed one thing: all 3.1c system folder items are replaced by the SP4 ones besides the Creamware Audio Driver. Pewrhaps during the uninstallation you deleted it and the new (4.0) installer haven't put it in a proper (extensions) place?
Please, tell us, does the 3.1c work now or worked before your all actions?
Check if all 3 drivers are in extensions folder (I mean the 3 you can find also in your SP4 folder/driver )
Please, tell us, does the 3.1c work now or worked before your all actions?
Check if all 3 drivers are in extensions folder (I mean the 3 you can find also in your SP4 folder/driver )
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
I don't know how the installer works - perhaps it overinstalls exixting files with new ones and leaves files which have different names? If so then there could be SFP application together with SP4 app. But they are only guessesOn 2004-04-23 12:58, at0mic wrote:
Probably in another folder, since it still runs great...![]()
that's what I had in mind (as it's the usual approach) when recently trying to install 3.1 (which failed due to the installer btw)On 2004-04-23 14:27, samplaire wrote:
In addition you can trash a folder called creamware from the preferences folder and then try to install once more.
But there's some info in that folder about the installation process state - the program is written like a closed loop.
If you trash it you have to start all over again from beginning.
I dunno if the new installation overwrites that folder from your previous version and leaves you in a half full half empty state.
Have a look at the text files in this folder from a working installtion (and make a copy).
The content is pretty obvious - you may need to add this manually later.
Imho the installer has trouble dealing with certain hardware, but I have no idea about the source.
[edit]
I just tried to verify that on my Mac, but had forgotten

But I got error 0001 'no access to the board' - for obvious reasons, but the 3.1 installer had delivered the same result with a board present, that's why I assume it's an installer issue.
The 3.0 installer worked flawlessly, but is a completely different piece of code. Just to clear that it's not hardware related.
[end edit]
I'd clone the structure from the 3.1 installation and move all files manually to their respective places - and of course don't forget the item belonging to the extension folder.
Then it may be necessary to add the appropriate content of the Creamware folder in preferences (before starting the app), either by using the copy mentioned above or modify the text files according to changes (possibly folder names or board ids or whatever).
Usually non-existing items in the preferences folder are generated automatically by the application from default values, but in this case it may be different and the stuff must be present before the app can start.
I hope it doesn't read too complicated...
good luck, Tom
ps: those Macs can be really wiered depending on the Ram used - is there an Apple label on the Dimms ? If not, remove all non-Apple chips and try again
<font size=-1>[ This Message was edited by: astroman on 2004-04-23 18:46 ]</font>
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
Astroman is right!
I suggest you 2 ways:
- if you still need the 3.1c then remove all the things related to CWA (that means application folder, extensions and the whole preferences folder); install 3.1a -> update to 3.1c. Then install the SP4 in another folder.
- if you don't need the 3.1c then also remove all existing CWA files from your HD (App folder, extensions, prefs) and install the 4.0
Of course you need to reboot after removing the files. Just to ensure everytjhing is alright - and do it in both examples.
Why do you have to remove the prefs? Because there is an info about drivers are installed or not. If the driver files don't exist on your HD and there is still a note in the prefs the installer could be fooled and avoid installing audio drivers causing the 0001 error. Correct me if I'm wrong.
I suggest you 2 ways:
- if you still need the 3.1c then remove all the things related to CWA (that means application folder, extensions and the whole preferences folder); install 3.1a -> update to 3.1c. Then install the SP4 in another folder.
- if you don't need the 3.1c then also remove all existing CWA files from your HD (App folder, extensions, prefs) and install the 4.0
Of course you need to reboot after removing the files. Just to ensure everytjhing is alright - and do it in both examples.
Why do you have to remove the prefs? Because there is an info about drivers are installed or not. If the driver files don't exist on your HD and there is still a note in the prefs the installer could be fooled and avoid installing audio drivers causing the 0001 error. Correct me if I'm wrong.
no need to remove any files completely. Just rename the SFP folder in question, rename the Creamware folder in preferences and move the items from the extension folder (imho audio driver, alloc.dll and crossplatformdev.dll (or something like that) into the renamed SFP folder - just to know to which installation they belong.
Then reboot and the machine's brain is washed.
The CWA installer is not that smart to use advanced Mac filesystem calls to find back a moved or renamed file
those calls do exist and and allowed a programming independend of file names, but are generally ignored in cross platform stuff - Oracle does the same for example.
When I installed (for a test) SFP 3.1c, the installer did write some text into the fake 'registry' structure in the Creamware folder in Preferences, but that installation never worked because it just didn't find the board.
The working (pre-SFP) installation left those files with only binary values (a few bytes) - dunno if there was any meaning in the content.
One thing we've missed yet:
you should either reset the parameter ram or power down, remove the board, powerup without Pulsar, powerdown again and put the board back in (which has the same effect).
For low level stuff this frequently works wonders as the machines buffer so much power that they don't reset completely on a reboot.
good luck, Tom
<font size=-1>[ This Message was edited by: astroman on 2004-04-23 20:22 ]</font>
Then reboot and the machine's brain is washed.
The CWA installer is not that smart to use advanced Mac filesystem calls to find back a moved or renamed file

those calls do exist and and allowed a programming independend of file names, but are generally ignored in cross platform stuff - Oracle does the same for example.
When I installed (for a test) SFP 3.1c, the installer did write some text into the fake 'registry' structure in the Creamware folder in Preferences, but that installation never worked because it just didn't find the board.
The working (pre-SFP) installation left those files with only binary values (a few bytes) - dunno if there was any meaning in the content.
One thing we've missed yet:
you should either reset the parameter ram or power down, remove the board, powerup without Pulsar, powerdown again and put the board back in (which has the same effect).
For low level stuff this frequently works wonders as the machines buffer so much power that they don't reset completely on a reboot.
good luck, Tom
<font size=-1>[ This Message was edited by: astroman on 2004-04-23 20:22 ]</font>
- AudioIrony
- Posts: 889
- Joined: Mon Mar 26, 2001 4:00 pm
- Location: Mood Ring Umbrella Satchel
Don't know if it's worth mentioning.... but looking at the system extensions that SCOPE 4 installs - they're all old files . . . may-sept 2002
The Scope installer replaced all the extensions EXCEPT the CreamwareAudio Driver. <-- last modified 31 May 2002
alloc and CrossDev have new mod dates, but files were created in Sept 2002.
I did both methods of install, clean and over a copy of 3.1c - both ran fine. I stuck with the over install because it has all my third party stuff already installed.
The only error messsage I got was when I tried to install and forgot that SFP was running in the background. . . . all I had to do was quit and start again.
The Scope installer replaced all the extensions EXCEPT the CreamwareAudio Driver. <-- last modified 31 May 2002
alloc and CrossDev have new mod dates, but files were created in Sept 2002.
I did both methods of install, clean and over a copy of 3.1c - both ran fine. I stuck with the over install because it has all my third party stuff already installed.
The only error messsage I got was when I tried to install and forgot that SFP was running in the background. . . . all I had to do was quit and start again.
---xxxxxxxx---
And Charlie said: "I'm cool with that" and set fire to a posh hammer to make it official
---xxxxxxxx---
And Charlie said: "I'm cool with that" and set fire to a posh hammer to make it official
---xxxxxxxx---
Just wanted to thank everbody for thier input. I do have SFP 4.0 working finally.
Tried everthing suggested! I cleaned any evidence of creamware off my hardrive then removed the card from my machine rebooted and re-installed. Still had the same problem. Then I re-installed 3.1c then 4.0 over the top AFTER I downloaded the installer again. Then - It worked.
I think I had a currupt installer to begin with. Talk about cutting my head off to cure my headache!
However, All the input made my troubleshooting my easier!
Thanks,
steb.
Tried everthing suggested! I cleaned any evidence of creamware off my hardrive then removed the card from my machine rebooted and re-installed. Still had the same problem. Then I re-installed 3.1c then 4.0 over the top AFTER I downloaded the installer again. Then - It worked.
I think I had a currupt installer to begin with. Talk about cutting my head off to cure my headache!
However, All the input made my troubleshooting my easier!
Thanks,
steb.