2008-03-30, 07:15 PM
Thought it time to give something back. I seem to collect MVP dongles either based on suggestions from posts or rename existing ones as backups before upgrading gbpvr.
Either way, it is easy to lose track, convince yourself that dongle.good.bin is better than dongle.bin when they are in fact the same ( some different versions do have the same size ) and posting dongle related queries is complicated by not knowing _which_ dongle inspired the query.
Anywho, I wrote a simple utility, donglever, which lists the dongles in the Dongle directory together with their version.
You can download and save the utility either to the "gbpvr" or the "gbpvr\Dongle" directory and just double-click or run from the command line.
You can save it to a different location but in that case you have to pass the path to the "gbpvr" directory as the argument. Note the path will need to be in double quotes if it contains spaces.
Then just match the output from donglever with the dongle filename specified in the MVP tab of the gbpvr Config app ensuring, as documented elsewhere, that the MVP is using the specified dongle by power-cycling it.
Download donglever windows binary from here : http://turland.org/downloads/donglever.exe (153 KB)
(md5sum: fc702401f56dbd9cc9e49ad2c2c884e6)
Source here (though you will need http://boost.org and a c++ compiler should you wish to build ) : http://turland.org/downloads/donglever.cpp
Sub: Please reply if posting an external link to a binary is bad forum etiquette? I could instead zip it and upload or have it wiki'd somewhere. However, zipping an exe seems to go against the sprit of the "Valid file extensions" listed for attachments.
Martin V: Not sure if or how you want your mvpmc versions presented?
Note: credit for locating the version embedded in a dongle goes to Martin V and one of his posts in this thread http://forums.nextpvr.com/showthread.php...le+version
Regards
David
Obligatory screenshot :
Either way, it is easy to lose track, convince yourself that dongle.good.bin is better than dongle.bin when they are in fact the same ( some different versions do have the same size ) and posting dongle related queries is complicated by not knowing _which_ dongle inspired the query.
Anywho, I wrote a simple utility, donglever, which lists the dongles in the Dongle directory together with their version.
You can download and save the utility either to the "gbpvr" or the "gbpvr\Dongle" directory and just double-click or run from the command line.
You can save it to a different location but in that case you have to pass the path to the "gbpvr" directory as the argument. Note the path will need to be in double quotes if it contains spaces.
Then just match the output from donglever with the dongle filename specified in the MVP tab of the gbpvr Config app ensuring, as documented elsewhere, that the MVP is using the specified dongle by power-cycling it.
Download donglever windows binary from here : http://turland.org/downloads/donglever.exe (153 KB)
(md5sum: fc702401f56dbd9cc9e49ad2c2c884e6)
Source here (though you will need http://boost.org and a c++ compiler should you wish to build ) : http://turland.org/downloads/donglever.cpp
Sub: Please reply if posting an external link to a binary is bad forum etiquette? I could instead zip it and upload or have it wiki'd somewhere. However, zipping an exe seems to go against the sprit of the "Valid file extensions" listed for attachments.
Martin V: Not sure if or how you want your mvpmc versions presented?
Note: credit for locating the version embedded in a dongle goes to Martin V and one of his posts in this thread http://forums.nextpvr.com/showthread.php...le+version
Regards
David
Obligatory screenshot :
1.2.13, XP SP3, C2Duo E6550,2GB, 2600XT, 500GB + 750GB raid 1, 2 * MVP (wired)
Nova-T 500 ; PVR150 << Manhattan st550 << 90cm motorised dish
USB-UIRT + HIP + custom 'HipSend' to change channels and coordinate dish
Nova-T 500 ; PVR150 << Manhattan st550 << 90cm motorised dish
USB-UIRT + HIP + custom 'HipSend' to change channels and coordinate dish