Solaris v5_0 - blue screen of death

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
MimozeM
Posts: 8
Joined: Mon Aug 25, 2008 1:08 am

Solaris v5_0 - blue screen of death

Post by MimozeM »

Hello

I tried to find here a solution for BSOD when loading Solaris v5_0 plug-in but unfortunately without success for now.

1. after installation ( copying files to C:\Program Files\SCOPE PCI ) I get " Can't find DSP file JBCtrlSh VxD - Please check installation" message.
2. after I added zarg_64bit files to C:\Program Files\SCOPE PCI\App\Sys and trying to load Solarisv5_0 plug-in I get BSOD with :

Page_Fault_In_Nonpaged_Area, what failed : JBCtrlSh64.sys
Driver_irql_not_less_or_equal error, what failed : JBCtrlSh64.sys

I am using Sonic Core SCOPE v7.0.1706 software with 3x(45 DSP) PCI cards on 64bit Windows10 - 22H2 system.
Hope this can be avoided with some help.
It's a shame that 299Eur plug-in doesn't work as it should.

Please if there is some workaround for this please let me know.
Thank you
User avatar
garyb
Moderator
Posts: 23262
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Re: Solaris v5_0 - blue screen of death

Post by garyb »

the sample OSCs in Solaris do not work in 64bit windows. Solaris is a very old plugin.
remove the thing1 and thing2(and any others) from the sample folder. i suspect Solaris is trying to load one of the presets that use the sample OSCs.
MimozeM
Posts: 8
Joined: Mon Aug 25, 2008 1:08 am

Re: Solaris v5_0 - blue screen of death

Post by MimozeM »

garyb wrote: Wed Jul 10, 2024 6:15 am the sample OSCs in Solaris do not work in 64bit windows. Solaris is a very old plugin.
remove the thing1 and thing2(and any others) from the sample folder. i suspect Solaris is trying to load one of the presets that use the sample OSCs.
Unfortunately, I already have removed all samples from that folder, but this BSOD's happened when loading plug-in into a (new) routing window.

As some "ancient" posts on similar subject with this plug-in says that " Can't find DSP file JBCtrlSh VxD - Please check installation"
message can be ignored, but doesn't it affect some plug-in functions perhaps ?

Anyway after adding zarg64bit files to Sys folder and trying to load that plug-in I have BSOD.
Last edited by MimozeM on Wed Jul 10, 2024 7:26 am, edited 1 time in total.
User avatar
valis
Posts: 7358
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Re: Solaris v5_0 - blue screen of death

Post by valis »

Are you on 64bit Scope? Also pay attention to the file date(s), Scope7 has newer versions of some files.
MimozeM
Posts: 8
Joined: Mon Aug 25, 2008 1:08 am

Re: Solaris v5_0 - blue screen of death

Post by MimozeM »

valis wrote: Wed Jul 10, 2024 6:52 am Are you on 64bit Scope? Also pay attention to the file date(s), Scope7 has newer versions of some files.
I am using Sonic Core SCOPE v7.0.1706 64bit software for PCI boards downloaded this year from their web site.
That file has been modified 21 oct, 2021.

But if you meant a difference between Solaris vs Scope7 files you are right.
There is one newer in Scope7 Dsp folder : Attenuator.dsp
And one "older" ( but only 1hour difference between the one inside Solaris and other in Scope7) : LQXVWS2.dsp
Last edited by MimozeM on Thu Jul 11, 2024 12:37 am, edited 1 time in total.
Casper
Posts: 361
Joined: Mon Apr 19, 2004 4:00 pm
Location: Netherlands (Almere)

Re: Solaris v5_0 - blue screen of death

Post by Casper »

"the sample OSCs in Solaris do not work in 64bit windows."

Thus, Solaris does not work (practically) period. :D Just as the samplers, and anything (still) using 32 code in a 64 bit architecture Gary.
And that is not the fault of the Solaris Developer btw... who also can't fix this, because of drivers.
User avatar
valis
Posts: 7358
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Re: Solaris v5_0 - blue screen of death

Post by valis »

The Solaris works fine, some of his other modules from what red dwarf are included in many presets, and those do not work; same presets that use the sample OSC from creamware.

Otherwise, all versions of the Solaris are working fine here on both my PCI cards and the Xite.
User avatar
Bud Weiser
Posts: 2715
Joined: Tue Sep 14, 2010 5:29 am
Location: nowhere land

Re: Solaris v5_0 - blue screen of death

Post by Bud Weiser »

Casper wrote: Wed Jul 10, 2024 9:19 am "the sample OSCs in Solaris do not work in 64bit windows."

Thus, Solaris does not work (practically) period. :D Just as the samplers, and anything (still) using 32 code in a 64 bit architecture Gary.
And that is not the fault of the Solaris Developer btw... who also can't fix this, because of drivers.
You´ll have to live with, John Bowen and others, developing SCOPE plugins in the past, won´t fix these at all,- drivers or not.
As an example, John Bowen never owned a XITE unit for development and it´s well known the hardware Solaris synth, now available in rev2, is his "new" baby.
Solaris for SCOPE was the basis for the hardware synth and when you want a up to date Solaris, you´ll heve to buy the John Bowen Synth Design hardware keyboard/desktop device.
ZARG is legacy.

And,- the (SCOPE) "drivers" are only critical when using ASIO and WAVE devices.
Development of SCOPE devices works w/o using these and in SCOPE standalone mode using SDK instead.

So, the ZARG devices are usable as long as you avoid using their sample oscillators.
The presets are old too and created w/ 32Bit SCOPE,- so when using 64Bit Scope,- make your own presets.
These are synths, made for programming,- and not only preset-players.

Solaris and other Zarg devices run in 32 and 64Bit SCOPE PCI and XITE,- I´m using both systems..
VxD files became obsolete long time ago and carefully compare release dates of other .sys files.
Don´t overwrite younger SCOPE files w/ older ZARG files.
The main issue w/ ZARG devices was and is polyphony ´cause these devices are very DSP cycle demanding which is synth architecture- and patch- complexity related.
These devices might come up w/ long load- and unload times in combination w/ audible artefacts when changing patches and some patches might work only monophonic or w/ 3 voice polyphony,- depending on DSP chip count and host computer configuration.
It´s a SAT connection thing,- the big Zarg devices want a lot of "communication lanes" across DSP chips and to/from host computer´s RAM.
It´s the price for that kind of modularity these devices offer (and bring SCOPE DSP to it´s limits).

The smaller "Sonic Core optimized" ZARG devices work better that the others.
You recognize reading "SC" in their name.

And,- "try before you buy" ...
You can always request a demo key for every device available from S|C shop.

:)

Bud
MimozeM
Posts: 8
Joined: Mon Aug 25, 2008 1:08 am

Re: Solaris v5_0 - blue screen of death

Post by MimozeM »

valis wrote: Wed Jul 10, 2024 2:31 pm The Solaris works fine, some of his other modules from what red dwarf are included in many presets, and those do not work; same presets that use the sample OSC from creamware.

Otherwise, all versions of the Solaris are working fine here on both my PCI cards and the Xite.
Good to know.
I did a clean installation of Scope7 software and Solaris v5_0 ( not replacing Attenuator.dsp file - Scope7 has a newer one )
Not adding Zarg64bit files - Still have a message Can't find DSP file JBCtrlSh Vxd - which is present in C:\Program Files\SCOPE PCI\App\Vxd
But this can be ignored and what's good - plug-in loaded without BSOD and it's working.
MimozeM
Posts: 8
Joined: Mon Aug 25, 2008 1:08 am

Re: Solaris v5_0 - blue screen of death

Post by MimozeM »

Bud Weiser wrote: Wed Jul 10, 2024 3:40 pm
Casper wrote: Wed Jul 10, 2024 9:19 am "the sample OSCs in Solaris do not work in 64bit windows."

Thus, Solaris does not work (practically) period. :D Just as the samplers, and anything (still) using 32 code in a 64 bit architecture Gary.
And that is not the fault of the Solaris Developer btw... who also can't fix this, because of drivers.
You´ll have to live with, John Bowen and others, developing SCOPE plugins in the past, won´t fix these at all,- drivers or not.
As an example, John Bowen never owned a XITE unit for development and it´s well known the hardware Solaris synth, now available in rev2, is his "new" baby.
Solaris for SCOPE was the basis for the hardware synth and when you want a up to date Solaris, you´ll heve to buy the John Bowen Synth Design hardware keyboard/desktop device.
ZARG is legacy.

And,- the (SCOPE) "drivers" are only critical when using ASIO and WAVE devices.
Development of SCOPE devices works w/o using these and in SCOPE standalone mode using SDK instead.

So, the ZARG devices are usable as long as you avoid using their sample oscillators.
The presets are old too and created w/ 32Bit SCOPE,- so when using 64Bit Scope,- make your own presets.
These are synths, made for programming,- and not only preset-players.

Solaris and other Zarg devices run in 32 and 64Bit SCOPE PCI and XITE,- I´m using both systems..
VxD files became obsolete long time ago and carefully compare release dates of other .sys files.
Don´t overwrite younger SCOPE files w/ older ZARG files.
The main issue w/ ZARG devices was and is polyphony ´cause these devices are very DSP cycle demanding which is synth architecture- and patch- complexity related.
These devices might come up w/ long load- and unload times in combination w/ audible artefacts when changing patches and some patches might work only monophonic or w/ 3 voice polyphony,- depending on DSP chip count and host computer configuration.
It´s a SAT connection thing,- the big Zarg devices want a lot of "communication lanes" across DSP chips and to/from host computer´s RAM.
It´s the price for that kind of modularity these devices offer (and bring SCOPE DSP to it´s limits).

The smaller "Sonic Core optimized" ZARG devices work better that the others.
You recognize reading "SC" in their name.

And,- "try before you buy" ...
You can always request a demo key for every device available from S|C shop.

:)

Bud
Thank you for a complex answer !
Post Reply