I have read almost the entire forum but can find no info to tell me whether ProgDVB will function on Digiwave 103g PCI card. Is anyone using this card? Does it work with ProgDVB?
Lotsa info re Digiwave receivers but not card. Any one help?
Tanks much.
fanleaf

Search the old forums for 103g, all dates.
There are several threads found, perhaps including something important for you.

forum.progdvb.com

Thanks much Juergen. I had completely forgotten about the old forum. Searched there and voila just what I needed to know.

Hi all... new to the forum here since getting a Digiwave 103g recently.

Unfortunately I *did not* find the answer I need from the old forum.

The version of ProgDVB that came with the card seems to work fine. It is version 4.45. Also, this is after letting Vista do it's own thing as far as finding/updating drivers for the card. It's possible the subsequent installation of ProgDVB is manipulating the driver in some way, but I doubt it. In Vista the device appears in the device manager as "PCI DVB-S Tuner" or something fairly generic. (Sorry, I will reload that driver to note more carefully what it is, if necessary.) Oh yes, when running this 4.45 version and I open the Device list, ProgDVB reports the card as using DVBS.device, whatever that might be referring to.

Whether I uninstall first or simply upgrade over this version with either of the current 4.x or 5.x versions available here, ProgDVB no longer works. The installation demands the selection of the type of card and, based on some searching, I have tried both BDA-compatible and also Geniatech. When I try to run ProgDVB it pops a dialog window indicating that the device could not be started. When I acknowledge that, Vista reports an error with ProgDVB and kills the application.

As expected there are also drivers on the installation CD so I decided to try those instead of whatever Vista finds by default through Windows Update. With these installed, the device manager list is considerably more detailed. I now see entries for Conexant 23880 Video Capture, AVStream Crossbar, Transport Stream Capture and BDA DVB-S Tuner/Demod. The results however are still the same. The included version 4.45 runs fine, reporting DVBS.device in the list. The newer 4.x and 5.x versions here fail upon startup with the error mentioned above.

So, after all that (thanks for sticking around) would someone with a working configuration like mine (Digiwave 103g + Vista) be kind enough to tell me what your device manager looks like (which driver and version) and what device type you are instructing ProgDVB to use.

This, by the way, is the specific info I could not find in the old forums.

Thanks!!!
-Rob

The device file connects ProgDVB to the driver.

You should try to keep the device file that came with the original software package, and don't delete the old installation but make a full backup copy into another folder.
This way you can restore the special components of the Geniatech software construction.

However, I don't have that DVB card. So, if anyone else has success with that one, please feel free to report here in full detail

Thanks for the tip... I've been messing around with this a ton now. Had no luck at all trying to copy some of the files from one installation to another. I messed with the drivers some more, trying different things and it is now in a state where I have both the Conexant-specific things I mentioned earlier as well as the PCI DVB-S Device. I also decided to try the new 4.x version instead of trying to jump straight to 5.x.

Almost unbelievably I had some success this time! When I installed I specified "none" for the device type. This allowed ProgDVB to actually start up properly so that I could get to the device list. Some of the items in the list had a red "X" beside them, but Geniatech didn't so I chose that and clicked (enable or start, whichever it is in v4) and it started up. I decided to stop that one and try another. There were some that actually identifed Conexant and BDA so I tried one of those. I got an error that it couldn't load the filter (should know by now to pay more attention to the errors, but I didn't). From that point on I was back to the miserable state I had earlier. Even uninstall/reinstall and selecting "None" for the device type would not make it work again.

I decided to try v5 once again, doing the same thing, choosing "None" initially. Once again it worked perfectly. Went into the device list and enabled Geniatech, no problem. Disabled that and tried to enable one of the other Conexant BDA ones and once again fell down the same trap. At least this time I saved the Java exception that was produced.

I don't understand why after an uninstall/reinstall ProgDVB still wants to try to reload it's last known state, which is now an error state, even if I manipulate the ProgDVB.ini file to set StartDevice=0. Does ProgDVB store run-time data into the Windows registry perhaps which isn't getting flushed when it should?

After getting the first Java exception but allowing it to continue I think it gets really messed up. It's throwing out exceptions for all kinds of things now. Anything I try to do in the device list results in a dialog with "Cannot load filter and connect". I decided to quit ProgDVB, manipulate the .ini file to set StartDevice=0, run it again - I get the above text, followed by "Device not started! (PCI Satellite TV)", which is just one of the ones I tried earlier while it was all buggered up.

I completely uninstalled and removed the folders for both v4 and v5 and reinstalled them and I am still stuck with the above errors... very strange. I will perhaps try a new installation folder or maybe try to reboot after uninstall to see if stuff gets flushed and allows it to work again.

Below is the very first exception I encountered with v5 while attempting to switch devices in the device list. I hope it is of some use. I'll continue to play with this some more now that I've had some success at least. If it wasn't for my trying to switch devices it would probably still be running now. That is what I was doing when I got the exception below. Beyond that, if you could somehow let me know how/why the current (incorrect) device is cached and not allowing ProgDVB to start up cleanly (even after uninstall/reinstall) then maybe I can try to work around that.

Thanks again!

---

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.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ProgDvbNet
Assembly Version: 5.11.0.0
Win32 Version: 5.11
CodeBase: file:///C:/Program%20Files/ProgDVB5/ProgDvbNet.exe
----------------------------------------
EngineApiWrapper
Assembly Version: 1.0.2823.29829
Win32 Version:
CodeBase: file:///C:/Program%20Files/ProgDVB5/EngineApiWrapper.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.762
Win32 Version: 8.00.50727.762
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8/msvcm80.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
IPDev.Skins
Assembly Version: 1.2.2.0
Win32 Version: 1.2.2.0
CodeBase: file:///C:/Program%20Files/ProgDVB5/IPDev.Skins.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
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.312 (rtmLHS.050727-3100)
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.

After installing, don't let ProgDVB get started at once.
Remove all unneeded device files from the modules flder. If in doubt, check the properties of each, most of them include details.

Normally, ProgDVB saves the settings to the ProgDVB.ini when closed. The registry will not be touched by ProgDVB itself after installation, but on BDA devices it depends on tuning space entries, that would come with an original application, or in your case the routines of the original software installer.

So I've got it set up now such that ProgDVB v5 is not failing to start at least.

I noticed that even though my .ini config file (in the installation folder) specified the Geniatech device, when I started it up it was using the BDA device. As a test I removed the .ini config file - I recall that with one of the v4 versions it would create one "on the fly" it it was not present. That doesn't seem to be the case for v5. I removed the .ini file yet ProgDVB started up fine as usual. I even changed some settings under "Options" and expected that when I quit ProgDVB it would create a new .ini file, but it did not.

So where exactly does ProgDVB v5 store all these settings?

Someone else has to continue now, as right now, I'm without a compatible Windows version, due to heavy hardware installing issues, after a machine change. Win2k is not supposed to be working again here before next week, perhaps...