v0.98.13 survival guide

[sub]

I've made this sticky (closed) thread to post useful information about problems that may arrise, or to get useful tips out there. I'll add more information to this thread as we start to get feedback from this new release. If anyone has info they feel should be included here, please PM me.

Some important first comments though...

Installing v0.98.13
As always, its recommended that you backup your config.xml and gbpvr.mdb/gbpvr.db3 files if you're upgrading from a previous release. Do not copy these back on to the new release though - these are just in case you need to go back to the old version.

This release requires .NET 2.0 to be installed. You must install this before upgrading. You can get it from http://www.microsoft.com/downloads/d...displaylang=en

[sub]

Recording service crashing
NOD32, Panda Antivirus, WebRunner and Net Limiter (and some other software) are known to be incompatible with .NET 2.0 Remoting, which is used by GB-PVR. If any of these apps are installed on your machine, they will cause the Recording Service crash, so they may need to be uninstalled before installing this update. Its possible you may just be able to set an exclusion of the GBPVRRecordingService.exe process - but I'm not sure if this is possible with all these apps.

To help you identify if you have this problem, when the recording service crashes, the following message is at the end of the GBPVRRecordingService.exe.log file:

Code:

9/4/2006 3:02:39 PM.625 ERROR [7] FATAL UNHANDLED EXCEPTION:: [b]System.AccessViolationException: Attempted to read or write protected memory[/b]. This is often an indication that other memory is corrupt.
at System.Net.UnsafeNclNativeMethods.OSSOCK.WSAGetOverlappedResult(SafeCloseSocket socketHandle, IntPtr overlapped, UInt32& bytesTransferred, Boolean wait, IntPtr ignored)
at [b]System.Net.Sockets.BaseOverlappedAsyncResult[/b].Compl etionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCo mpletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

HtV has recommened that when you have NOD32 installed, you can very easy make it work with GBPVR. Go to IMON-setup-miscelaneous. Click the edit button in the Exclusion-part. Add GbpvrRecordingService.exe to the list. Done.

UPDATE: Microsoft now has a hot fix available for this common incompatibility between firewall software and the .NET 2.0 Remoting: http://support.microsoft.com/kb/923028/en-us

[sub]

SQLite...
This version of GB-PVR gives you the option to move away from using the MS Access database. Access had a few problems that were proving a real pain in the arse (infinitely growing, commited changes not being written to disk for some time mean data changes would not appear immediately (deleting recordings etc)). While its likely that several different types of database could be used, the SQLite is my preferred option, and I've included everything you'll need to use SQLite.

How do you switch databases? Run the ChangeDatabase.exe utility installed with GB-PVR.

How can I view/edit data in the database? I encourage people to not manually change the database, but if you really feel the need to have a poke around, SQLiteSpy from http://www.zeitungsjunge.de/delphi/sqlitespy/index.htm is pretty good.

Another good one is SQLite Administrator http://sqliteadmin.orbmu2k.de/

[sub]

Skip buttons not working on MCE remote
Unfortunately there is a bug in v0.98.13 which makes the skip buttons not work on MCE remotes. A fix can be found here: http://forums.gbpvr.com/showpost.php?p=1...ostcount=2

If the version number shows as "v0.98.13b" in the config app, then the version of GB-PVR you installed already has this patch applied.

[sub]

Gaps and missing listings with DVB EPG
If you use the DVB EPG option, and find you've got missing channels and/or gaps in the listings, then you need to apply the patch from: http://forums.gbpvr.com/showpost.php?p=1...stcount=87

[sub]

Problems playing in-progress recordings, and a strange messages in the log files

If you're having problems playing in-progress recordings (no OSD, inability to skip), it can be resolved by applying the patch from: http://forums.gbpvr.com/showpost.php?p=1...ostcount=2

[sub]

A bug to be aware of...
A few users have reported all sorts of odd errors that were caused by a database lock error. (breaks pretty much everything, requiring restart)

11/9/2006 2:00:53 AM.656 ERROR [10] Unexpected error removing recording from conversion queue: System.Data.SQLite.SQLiteException: The database file is locked
database is locked
at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
at GBPVR.RecordingService.x92f6085038c83bb7.x4fa2bfc067e20d05(Int32 x0f7b9658643bceb7)

This error occurs if you've got GB-PVR set to auto convert files to another format (divx/xvid etc), but manually delete a recording before this conversion can take place. This problem is corrected for the next release.

If you temporarily set the conversions to none, then ok out of the config app to restart the recording service, then it'll clear the conversion queue. After that you can reenable it if you need to, but just be careful with deleting recordings (do it the next day), or leave conversions disabled for now.

[sub]

Another issue to be aware of...
There is bug which can cause GB-PVR to continue to update the menu in the background even though the user is watching a video or live tv fullscreen.

Patch here http://forums.gbpvr.com/showpost.php?p=1...stcount=49

This can cause some disconnections nd reduced responsiveness on MVPs, and depending on CPU could cause a minor disruptions/stuttering while watching video/tv on the PC (when next recording etc panels update on the menu every few seconds).

If you're experiencing stuttering every few seconds, its also worth trying it with the web server disabled to see if it helps - there has been at least one user with CPU spikes cause by something odd in his setup that was stopping the web server from initialising correctly.