Won't open after choosing BDA satellite
Moderators:Dreamer, FredB, X05
Installed dvdd and after choosing language and BDA Satellite it just shuts down with a microsoft window experiencing a problem and has to shut down , does it every time . Installed again and exactly same thing . any ideas or anyone else experiencing this problem ?
hi
can you try v1.3b with the following patch? after installing v1.3b , put the attached file into \dvbdream\devices folder. (overwrite)
and can you please specify your device type? (What is the model and manufacturer name ??)
can you try v1.3b with the following patch? after installing v1.3b , put the attached file into \dvbdream\devices folder. (overwrite)
and can you please specify your device type? (What is the model and manufacturer name ??)
You do not have the required permissions to view the files attached to this post.
DVB Dream - because I have to dream about having time to code it
I have the same problem - it's with the BDA drivers. You can start the app itself with a null driver, but when you try start the BDA-satellite it crashes.
The replacement bda-s file above produces a different error message:
"Cannot initialise DVB Hardware! Error code:1 Hardware will work in offline mode".
The bda.txt file has this:
[12/07/06 12:33:23 : ] StartDevice() dwDeviceNo:0
[12/07/06 12:33:23 : ] CoCreateInstance(CLSID_FilterGraph..) OK pFilterGraph:01750108
[12/07/06 12:33:23 : ] pFilterGraph->QueryInterface(IID_IMediaControl..) OK pMediaControl:017504F4
[12/07/06 12:33:23 : 16] LoadTuningSpace()...
[12/07/06 12:33:23 : 16] m_pNetworkProvider->QueryInterface(IID_ITuner..) OK
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Antenna'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'ATSC'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'ATSCCable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'AuxIn1'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Cable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Digital Cable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'DVB-T'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'FM Radio'
[12/07/06 12:33:23 : 16] TuningSpace Name: '{adb10da8-5286-4318-9ccb-cbedc854f0dc}'
[12/07/06 12:33:23 : 16] Enumeration found 9 tuning spaces
[12/07/06 12:33:23 : 16] LoadTuningSpace() OK
[12/07/06 12:33:23 : 16] Couldn't put_TuneRequest
[12/07/06 12:33:23 : 16] FAILED: LoadMCENetworkProvider()
[12/07/06 12:33:27 : 1411953] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411953] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411984] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411984] DeviceGetList(): Count:1
The replacement bda-s file above produces a different error message:
"Cannot initialise DVB Hardware! Error code:1 Hardware will work in offline mode".
The bda.txt file has this:
[12/07/06 12:33:23 : ] StartDevice() dwDeviceNo:0
[12/07/06 12:33:23 : ] CoCreateInstance(CLSID_FilterGraph..) OK pFilterGraph:01750108
[12/07/06 12:33:23 : ] pFilterGraph->QueryInterface(IID_IMediaControl..) OK pMediaControl:017504F4
[12/07/06 12:33:23 : 16] LoadTuningSpace()...
[12/07/06 12:33:23 : 16] m_pNetworkProvider->QueryInterface(IID_ITuner..) OK
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Antenna'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'ATSC'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'ATSCCable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'AuxIn1'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Cable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'Digital Cable'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'DVB-T'
[12/07/06 12:33:23 : 16] TuningSpace Name: 'FM Radio'
[12/07/06 12:33:23 : 16] TuningSpace Name: '{adb10da8-5286-4318-9ccb-cbedc854f0dc}'
[12/07/06 12:33:23 : 16] Enumeration found 9 tuning spaces
[12/07/06 12:33:23 : 16] LoadTuningSpace() OK
[12/07/06 12:33:23 : 16] Couldn't put_TuneRequest
[12/07/06 12:33:23 : 16] FAILED: LoadMCENetworkProvider()
[12/07/06 12:33:27 : 1411953] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411953] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411968] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411968] DeviceGetList(): Count:1
[12/07/06 12:33:27 : 1411984] DeviceGetList(): - 0) 'TechnoTrend BDA/DVB-S Tuner'
[12/07/06 12:33:27 : 1411984] DeviceGetList(): Count:1
Pentium dual 3.5ghz + 6600GT running Vista. Skystar2 2.68 with 4.4 mibi drivers, SG2100a motor, Triax 90cm dish.
Little update: this is a Vista BDA driver problem, I've got it closer to working with the original 1.3b install (ie without using rel's extra bda_s fle above) after a few registry hacks. It's not really working properly though, since every few seconds it goes into jerk-o-vision, then back to smooth. Better than not loading at all though.
Anyway, I added the lines below to the registry, then deleted the bda dvb-t entry in the same location:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Multimedia\TV\Tuning Spaces\42]
@="{B64016F3-C9A2-4066-96F0-BD9563314726}"
"Name"="TT-DVB-S"
"Description"="DVB-S Tuning Space Entry"
"Network Type"="{FA4B375A-45B4-4D45-8440-263957B11623}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000002
"Network ID"=dword:ffffffff
"High Oscillator Frequency"=dword:00a1be40
"Low Oscillator Frequency"=dword:0094c5f0
"LNB Switch Frequency"=dword:00b28720
"Input Range"="ex:2d,00,31,0"
"Spectral Inversion"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Multimedia\TV\Tuning Spaces\42\Default Locator]
@="{1DF7D126-4050-47F0-A7CF-4C4CA9241333}"
"Frequency"=dword:00b7e238
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:00000014
"SymbolRate"=dword:00006b6c
"Polarisation"=dword:00000002
"OrbitalPosition"=dword:00000000
"Azimuth"=dword:ffffffff
"Elevation"=dword:ffffffff
"WestPosition"=dword:00000000
ProgDVB also needs this change to recognise any hardware at all, although it doesn't have the lag problem. Alt-DVB and DVBviewer work fine with or without it (and without any lag). Other programs don't work at all regardless
Anyway, I added the lines below to the registry, then deleted the bda dvb-t entry in the same location:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Multimedia\TV\Tuning Spaces\42]
@="{B64016F3-C9A2-4066-96F0-BD9563314726}"
"Name"="TT-DVB-S"
"Description"="DVB-S Tuning Space Entry"
"Network Type"="{FA4B375A-45B4-4D45-8440-263957B11623}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000002
"Network ID"=dword:ffffffff
"High Oscillator Frequency"=dword:00a1be40
"Low Oscillator Frequency"=dword:0094c5f0
"LNB Switch Frequency"=dword:00b28720
"Input Range"="ex:2d,00,31,0"
"Spectral Inversion"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Multimedia\TV\Tuning Spaces\42\Default Locator]
@="{1DF7D126-4050-47F0-A7CF-4C4CA9241333}"
"Frequency"=dword:00b7e238
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:00000014
"SymbolRate"=dword:00006b6c
"Polarisation"=dword:00000002
"OrbitalPosition"=dword:00000000
"Azimuth"=dword:ffffffff
"Elevation"=dword:ffffffff
"WestPosition"=dword:00000000
ProgDVB also needs this change to recognise any hardware at all, although it doesn't have the lag problem. Alt-DVB and DVBviewer work fine with or without it (and without any lag). Other programs don't work at all regardless
Pentium dual 3.5ghz + 6600GT running Vista. Skystar2 2.68 with 4.4 mibi drivers, SG2100a motor, Triax 90cm dish.
Hello,
excuses to the modos, but yesterday in the night, i created a post around the same subject....my english is not very good, especially when i'm tired....
I've exactly the same problem you speak about, with a nova s+ card ( bda drivers..).even when i change bda_s.dev.
got 2 nova cards on my pc, the nova s+ and nova-t. the nova terrestrial works very well, but when i select the nova-s, with satellite configuration, "cannot initialising hardware...will twork offline mode..."
is there aniway to make work this s+-card with dvbdream....?
i don't really understand the latest post speaking about editing registry (because of my english...)
can you say me if it's possible, this way i'll try to make work it....
thanks.
excuses to the modos, but yesterday in the night, i created a post around the same subject....my english is not very good, especially when i'm tired....
I've exactly the same problem you speak about, with a nova s+ card ( bda drivers..).even when i change bda_s.dev.
got 2 nova cards on my pc, the nova s+ and nova-t. the nova terrestrial works very well, but when i select the nova-s, with satellite configuration, "cannot initialising hardware...will twork offline mode..."
is there aniway to make work this s+-card with dvbdream....?
i don't really understand the latest post speaking about editing registry (because of my english...)
can you say me if it's possible, this way i'll try to make work it....
thanks.
Return to “Old bug reports & requests”
Who is online
Users browsing this forum: No registered users and 1 guest