GetWizPnP Release

From OpenWiz

This page allows you to download getWizPnP in a convenient form for installation. You can also access the getWizPnP source code from the getWizPnP Redmine repository.

Thanks to alwayslooking on the Beyonwiz Forum for providing Web hosting for the distribution files themselves.

getWizPnP Current Release

Thanks to Luke on the Beyonwiz forum for help in working out how best to compile getWizPnP for OS X and Windows.

Version 0.5.2

Download Perl source package getWizPnP 0.5.2
Download pre-compiled executables:
     getWizPnP 0.5.2 Windows
     getWizPnP 0.5.2 Cygwin
     getWizPnP 0.5.2 OS X
     getWizPnP 0.5.2 Linux

The pre-compiled versions also contain getWizPnP documentation in HTML and plain text format.

Norton Anti-Virus's SONAR reports the Windows compiled version of getWizPnP as "behaving suspiciously on your computer" and and that its "file risk is high". I applied to Symantec to white-list getWizPnP on 14 Jun 2011, but the process can take up to three weeks, even if all goes smoothly.

Release notes

New in 0.5.2

No new features - bug fixes only.

Fixed in 0.5.2

Some error messages printed while a recording is being transferred will cause a Perl internal error instead of printing the error message. Workaround: use verbosity level at least 1 when copying or moving recordings.
Loading the bookmarks for a recording goes into an infinite recursion, so verbosity level 3, which lists bookmarks will cause getWizPnP to go into an infinite recursion and crash.
If the main header file is modified by --reconstruct, the length of the bookmark table is set to the wrong value, usually much larger than it should be.
Reconstruction of the stat header file fails because a reference to the wrong object is used.

Bugs in 0.5.2

On Windows 7, sometimes getWizPnP fails to discover Beyonwiz servers on the network. The reason is not clear, but it can sometimes be worked around by specifying a larger timeout. Try --wizpnpTimeout=2.
getWizPnp sometimes fail part-way through a recording copy with a HTTP 400 - Bad Request error. WizFX also seems to have similar problems on Windows 7. The cause of the problem is not clear, but it may be something common to both getWizPnP and WizFX.
The changes to the file indexing from 1.05.283 mean that if you delete a recording on the Beyonwiz (--delete/--move), it will remain in the internal index (i.e. visible in the file player, and visible in WizFX) until you start a recording index rebuild using FILEPLAYER, SOUNDTRACK on the remote, or a HDD check is done. This can only be fixed in the Beyonwiz firmware.
In free-to-air EPGs, the information used by getWizPnP for the episode name is sometimes actually the program synopsis.