#3
If you already have that hardware, simply try and find out.

If it's using BDA drivers, there is a chance, after installing and setting up the original software completely.
Generally, ProgDVB can handle BDA devices. But problems are possible, like scanner not working or alike. Remote control also won't work in many cases.

But don't buy hardware only for ProgDVB, if it's not known to work flawlessly with it...
My signature:

Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!



I don't give support by e-mail or PM.

And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!

NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.

Please keep it in English here, or Russian in the Russian section, or German in the German section.

I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!


1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode

19.2°,13°,28.x°E,30°W, DiSEqC 1.0


Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>

#6
Hi.

I've bought ProgDVB 5.15.2, because I was full of hope it works together with my FireDTV. But nothing. The program crashs ever and ever. Updating the firmware from July 1st 2008 didn't followed any success.

So much money for nothing, I'm frustrated.

Greetings
nofreak

#8
selected this
Name: {BDA} FireDTV BDA Tuner DVBS2
Filename: BDA.Device
Version: 1.53
API version: 1.33


If I select that and hit the Enable button, a new window pop up:

Device list
Unandled exception has occurred in your application. If you click Continue, the application will ignore this error and attept to continue. If you click Quit, the application will close immediately.

Attempted to read or write protection memory. this is often an indication that other memory is corrupt.


I'm sure my memory moduls work fine.

If I click Details I get:

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 (* , Int32 )
at ..(ArrayList dev_info_list)
at ProgDvbNet.DeviceListForm.()
at ProgDvbNet.DeviceListForm.(Object , EventArgs )
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.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ProgDvbNet
Assembly Version: 5.15.2.0
Win32 Version: 5.15.2
CodeBase: file:///D:/Programme/ProgDVB/ProgDvbNet.exe
----------------------------------------
EngineApiWrapper
Assembly Version: 1.1.3.0
Win32 Version:
CodeBase: file:///D:/Programme/ProgDVB/EngineApiWrapper.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.1433
Win32 Version: 8.00.50727.1433
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2/msvcm80.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
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.1433 (REDBITS.050727-1400)
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.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ProgDvbNet.bc
Assembly Version: 1.0.4.0
Win32 Version: 1.0.4.0
CodeBase: file:///D:/Programme/ProgDVB/ProgDvbNet.bc.DLL
----------------------------------------
IPDev.Skins
Assembly Version: 1.2.15.0
Win32 Version: 1.2.15.0
CodeBase: file:///D:/Programme/ProgDVB/IPDev.Skins.DLL
----------------------------------------
ProgDvbNet.EPG
Assembly Version: 1.0.1.3
Win32 Version: 1.0.1.3
CodeBase: file:///D:/Programme/ProgDVB/ProgDvbNet.EPG.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
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.1433 (REDBITS.050727-1400)
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.



Greetings
nofreak