please pardon my long disappearance but i've been doing.. uh... tests.
to avoid recommending any unnecessary or even harmful voodoo.
and indeed i deducted quite a lot and what seemed to be a longish talmud is very simple now.
install scope 5.1
if the driver doesn't install - do 'testsigning on' trick and try again
make sure you're ready for blue screens - for that, disable any fragile services like databases and don't run programs which tend to corrupt themselves while you're testing.
go to exploit protection panel and disable all mitigations you can find - they brick not only scope but other software, especially if it's older and relies on elaborate copy protection schemes.
open DAW and scan your scope vsts - if it does and no blue screen - perfect!
exit DAW, run scope standalone program - see if opening VDAT x64 gives you blue screen. if not - perfect, samplers should work too.
IF you get bluescreen just let it reboot and try loading up xtc vst (i try multifx-s and then something into it)
or just straight on go for scope application and try to open VDAT.
after some crashes in a row, windows can boot into emergency screen saying perhaps you want to do troubleshooting or fixing - say no please, just continue to windows... when booted, try loading vdat or xtc stuff again - until you're lucky.
once you're lucky, keep that boot for as long as you can and work with scope vdat, xtc, samplers...as it's 1998!...
that's it!
regards,
p
