Page 1 of 2

Can't run ProgDVB

Posted: Mon Jan 07, 2008 7:35 am
by doveman
Hi

I'm running XP Pro with a Nebula Electronics DigiTV PCI card with BDA v1.111 driver.

I tried to run ProgDVB 4 and it loaded but straight away I got an error about BDA.device and it closed.

Then I tried ProgDVB 5 (after installing NET Framework 2) and it just says "ProgDvbNet has encountered a problem and needs to close".

Can anyone help me get it working please?

Posted: Mon Jan 07, 2008 11:15 am
by Juergen
Does the original application work, that came with that hardware?

Posted: Mon Jan 07, 2008 3:09 pm
by doveman
Yeah, DigiTV works and so does DVBViewer's Transit MMC Demo.

Posted: Mon Jan 07, 2008 6:14 pm
by Juergen
Look into ProgDVB.ini with your editor and set device to not start, try again.

If this does not help, delete ProgDVB.ini

Posted: Mon Jan 07, 2008 10:19 pm
by doveman
OK, that lets ProgDVB 5 start :)

Now, if I go to Settings - Device List, I see
{BDA} Nebula DigiTV PCI BDA Tuner Filter BDA.Device v1.44 and
{BDA} Nebula DigiTV PCI BDA Tuner Filter anysee.Device v1.36

If I enable the anysee.Device one it says "Tuner space not founded" so I disabled that and tried to enable the BDA.Device and I get an "Unhandled exception has occurred in your application" error with the details as below.
--------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Device_Set(TDeviceInfo* , Int32 )
at ProgDvbEngine.CDeviceInfo.Set(ArrayList dev_info_list)
at ProgDvbNet.DeviceListForm.SendEnabledList()
at ProgDvbNet.DeviceListForm.StartButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ProgDvbNet
Assembly Version: 5.12.7.0
Win32 Version: 5.12.07
CodeBase: file:///C:/Program%20Files/ProgDVB/ProgDvbNet.exe
----------------------------------------
EngineApiWrapper
Assembly Version: 1.1.0.0
Win32 Version:
CodeBase: file:///C:/Program%20Files/ProgDVB/EngineApiWrapper.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/msvcm80.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ProgDvbNet.bc
Assembly Version: 1.0.0.2
Win32 Version: 1.0.0.2
CodeBase: file:///C:/Program%20Files/ProgDVB/ProgDvbNet.bc.DLL
----------------------------------------
IPDev.Skins
Assembly Version: 1.2.7.0
Win32 Version: 1.2.7.0
CodeBase: file:///C:/Program%20Files/ProgDVB/IPDev.Skins.DLL
----------------------------------------
ProgDvbNet.EPG
Assembly Version: 1.0.0.1
Win32 Version: 1.0.0.1
CodeBase: file:///C:/Program%20Files/ProgDVB/ProgDvbNet.EPG.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Posted: Mon Jan 07, 2008 10:27 pm
by Juergen
That 'tuning space' message gives us a hint.

You will find data for a .reg file to import, if using our search function for
tuning space
(all terms) (show as posts) (return all characters)

This might let the device work, I hope.

Posted: Tue Jan 08, 2008 4:31 am
by doveman
I thought I'd check what's in my registry first and found this entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\7]
@="{C6B14B32-76AA-4A86-A7AC-5C79AAF58DA7}"
"Name"="DVB-T"
"Description"="Local DVB-T Digital Antenna"
"Network Type"="{216C62DF-6D7F-4e9a-8571-05F14EDB766A}"
"System Type"=dword:00000001
"Network ID"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\7\Default Locator]
@="{9CD64701-BDF3-4D14-8E03-F12983D86664}"
"Frequency"=dword:ffffffff
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:ffffffff
"SymbolRate"=dword:ffffffff
"Bandwidth"=dword:ffffffff
"LPInnerFECMethod"=dword:ffffffff
"LPInnerFECRate"=dword:ffffffff
"HierarchyAlpha"=dword:ffffffff
"GuardInterval"=dword:ffffffff
"TransmissionMode"=dword:ffffffff
"OtherFrequencyInUse"=dword:ffffffff

but I searched the forum as you suggested and found and added this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\44]
@="{C6B14B32-76AA-4A86-A7AC-5C79AAF58DA7}"
"Name"="TT-DVB-T"
"Description"="DVB-T Tuning Space Entry"
"Network Type"="{216C62DF-6D7F-4E9A-8571-05F14EDB766A}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000001
"Network ID"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\44\Default Locator]
@="{9CD64701-BDF3-4D14-8E03-F12983D86664}"
"Frequency"=dword:000b0450
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:ffffffff
"SymbolRate"=dword:00000000
"Bandwidth"=dword:ffffffff
"LPInnerFECMethod"=dword:ffffffff
"LPInnerFECRate"=dword:ffffffff
"HierarchyAlpha"=dword:ffffffff
"GuardInterval"=dword:ffffffff
"TransmissionMode"=dword:ffffffff
"OtherFrequencyInUse"=dword:00000000

but unfortunately I still get the same errors :(

Posted: Tue Jan 08, 2008 1:20 pm
by Juergen
Did you try the anysee BDA again?

Else I am running low on ideas now..

Posted: Tue Jan 08, 2008 1:32 pm
by doveman
Yes, I tried enabling the anysee device first and got the same "Tuner space not founded" error and enabling the BDA device causes the same crash.

Thanks for trying to help anyway.

Posted: Thu Jan 10, 2008 4:38 pm
by descite
Hello.

Using progdvb 5.12.7...

Using kworld 320U (hybrid) or Pinnacle 2000e
I'm having similar problem with both usb dvb-t device. Both working correctly with original software and nero8 home and with other players..
After deleting ini fileprogdvb starts. exception after enabling bda device progdvb crashes. When started with bda device enabled got same error as mentioned above. When I try to enable bda device it will get some memory addresses (devices connected to usb) with notification that some memory addresses could not be read. ( first one is 0x57ec1fa referenced memory at"0x051d3c1c").
Some more details :
Exception data contains System.Collections.ListDictionaryInternal
( when exception catched inside vs )
And as i understand ( I'hope so :P ) the exteption occurs inside EngineWrapper.dll.
Maybe this information helps further to solve this prblem...

Posted: Thu Jan 10, 2008 7:57 pm
by Rille_lkp
Try using this version instead: http://download.progdvb.com/ProgDVB4.88.6Std.exe

I have the exakt same problem as you with 4.88.7 (using a WinTV Nova 500) and have had it with several versions for a long time (think it started somewhere around 4.84). Some versions have this problem and some not. Those versions after 4.84 that does work also seems to have some weird problem with the driver as the icon on the lower left that shows encryption/FTA keeps switching between encrypted and free every 2 seconds on fta-channels (i have no problem watching the channel though). 4.88.6 does however work without any of the 2 problems.

Posted: Thu Jan 10, 2008 9:02 pm
by descite
Hello. tested different versions with results:
not woring means same problem.

4.88.7std : not working
4.88.6std working ok.
5.12.6pro working ok.
5.12.7pro not working
5.12.7std not working
5.12.6pro working. ( sticked to this version right now. )

All versions installed in different directories and launched directly from folders.

Posted: Thu Jan 10, 2008 9:25 pm
by descite
I made one more test. Maybe problem lies in changes made in BDA.Device ?

Taking bda.device file from 5.21.6 and putting it into 5.12.7 modules folder resolves this problem (renaming original one). Program starts and at first look looks like working one.

Posted: Sat Jan 12, 2008 11:57 am
by Rille_lkp
After a restart of the application the icon on the lower left indicating encrypted/FTA started switching every few seconds again. Is it supposed to do that?

Posted: Sun Jan 13, 2008 9:05 am
by karlbo
I have the same problem since version 5.12.7. and 8

I installed 5.12.6. made a copy of modules/dba.device file
and installed 5.12.8, renamed the installed dba.device to dba.device144
and the copyfile dba from 5.12.6 to dba.device

Now 5.12.8 works with dba.device 1.42