stdm board connection error

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

Moderators: valis, garyb

Post Reply
User avatar
roy thinnes
Posts: 651
Joined: Thu Jan 09, 2003 4:00 pm
Location: Graz
Contact:

stdm board connection error

Post by roy thinnes »

hi,
I think I've installed Scope without any trouble at least 10 times before, but this time I've got this nasty error message
Image
and then
Image
Scope4.0 is installed is on a new ESata drive with fresh WinXp install.
After removing one of the Scope cards, everything works.
Scope installations on other drives are working.
WinXp, Scope + Pulsar2, Asus P5B
User avatar
astroman
Posts: 8455
Joined: Fri Feb 08, 2002 4:00 pm
Location: Germany

Re: stdm board connection error

Post by astroman »

imho it's a coincidence of the install and a bad connection of the s/tdm cable (dunno if you opened the PC right before this...)
when removing the card, you had to re-plug the cable and the connection was fine again.
If you put the card back in (maybe cleaning the contacts) and the error remains, even on a different s/tdm connector... then I'd be concerned for the card.
In my case those cables fit really bad (4 to 15 DSP card) and I've seen it a couple of times.

cheers, Tom
some of my sounds on Soundcloud
User avatar
roy thinnes
Posts: 651
Joined: Thu Jan 09, 2003 4:00 pm
Location: Graz
Contact:

Re: stdm board connection error

Post by roy thinnes »

hmm, I've already un- and replugged the stdm cable with no avail.
and, thankfully, installs (4.5 and 5.1) on other partitions are working.
the only differences are
a) it's on a ESata HD (drive letter M)
b) I updated the Intel Chipset drivers.
But cleaning the contacts is always a good idea, will do this later.
User avatar
erminardi
Posts: 1575
Joined: Fri Apr 30, 2004 4:00 pm

Re: stdm board connection error

Post by erminardi »

Cleaning the contacts is the way, Scope boards are a lot sensible to this issue.
The stange fact is that it seems ever a software problem instead of hardware, but not worry, cleaning is the solution ;)
4PC + Scope 5.0 + no more Xite + 2xScope Pro + 6xPulsarII + 2xLunaII + SDK + a lot of devices (Flexor III & Solaris 4.1 etc.) + Plugiator.
User avatar
roy thinnes
Posts: 651
Joined: Thu Jan 09, 2003 4:00 pm
Location: Graz
Contact:

Re: stdm board connection error

Post by roy thinnes »

sorry but cleaning the contacts didn't help either.
maybe a cset.ini issue? seems correct:

[Runpep]
InScreen=1
Language=Deutsch

[FileBrowser]
All Files=0
STS-Samples=0
LastPath=M:/Scope40/Devices

[AudioFormats]
Wav=Wav

[Installer]
Version=3.0
App=SFP
OS=3.1
ProductID=3

[board0]
boardid=0

[board1]
boardid=1

[Host-Config]
Numboards=2
Board0=Host

[ReferenceResolver]
All files_Paths=M:/Scope40/;
Modules/Devices_Paths=M:/Scope40/Devices/;
Presets_Paths=M:/Scope40/Presets/;
All files_AutoUse=1
Modules/Devices_AutoUse=1
Presets_AutoUse=1

[StaticPath]
Modular=M:/Scope40/Modular2 Modules/
Projects=M:/Scope40/Projects/Examples/
Effects=M:/Scope40/Devices/Effects/
Presets=M:/Scope40/Presets/
HardwareIOs=M:/Scope40/App/Application/IOs/Hardware/
SoftwareIOs=M:/Scope40/App/Application/IOs/Software/
Bitmaps=M:/Scope40/MRC Skins/
Devices=M:/Scope40/Devices/
Samples=M:/Scope40/Samples/

[Path]
Bitmaps=M:/Scope40/MRC Skins/
Projects=M:/Scope40/Projects/Examples/

[APPEARANCE]
StandardCursor=1

[LOAD]
AlignSurfaces=1
LoadMixer=STM 1632.dev
LoadMixerEnabled=1
LoadDefBoard=0

[AUTOCONNECT]
InstrumentToMixer=1
EffectToMixer=1
AudioSrcToMixer=1
DeviceToMidiSrc=2

[SFP]
Favourites_Minimized=1
Favourites_Size=187
FileBrowser_Minimized=0
FileBrowser_Size=564
Top_Minimized=0
Top_Size=419
About_Show=0
About_PosX=254
About_PosY=14
ControlRanger_Show=0
ControlRanger_PosX=289
ControlRanger_PosY=89
ControlRanger_TopLevel=2000
SFPBar_PosX=33
SFPBar_PosY=9
SFPBar_SizeX=238
SFPBar_SizeY=518
SFPBar_TopLevel=100000
SFPBar_RestoredSizeY=582
Bottom_Size=88
Bottom_Minimized=0
DSPLoad_Load=0
Dsp Load_Show=0
Dsp Load_PosX=282
Dsp Load_PosY=82
Dsp Load_TopLevel=2000
Registry_Load=0
ModuleRegistry_Show=0
ModuleRegistry_PosX=300
ModuleRegistry_PosY=102
ModuleRegistry_TopLevel=2000
Options_Load=0
Options_Show=0
Options_PosX=296
Options_PosY=96
Options_TopLevel=2000
Resolver_Load=0
ReferenceResolveOptions_Show=0
ReferenceResolveOptions_PosX=302
ReferenceResolveOptions_PosY=104
ReferenceResolveOptions_SizeX=332
ReferenceResolveOptions_SizeY=250
SFPRouting_Show=0
SFPRouting_PosX=237
SFPRouting_PosY=0
SFPRouting_SizeX=791
SFPRouting_SizeY=518
SFPRouting_TopLevel=0
FileBrowser_Show=0
FileBrowser_PosX=236
FileBrowser_PosY=0
FileBrowser_SizeX=238
FileBrowser_SizeY=518
FileBrowser_TopLevel=1
Splitter_Size=0
Splitter_Minimized=1
SFPDesktop_PosX=0
SFPDesktop_PosY=0
SFPDesktop_SizeX=1055
SFPDesktop_SizeY=548
SFPDesktop_Maximize=0
PulsarConfigSurface_Show=0
PulsarConfigSurface_PosX=274
PulsarConfigSurface_PosY=75
PulsarConfigSurface_TopLevel=2000

any idea?
Post Reply