no longer getting prompted to resume?

[sub]

Its not supposed to update the old empty.db3. Its supposed to overwrite it each upgrade. For whatever reason it wasnt able to do that one your upgrade. You got it working though, so not worth worrying about.

[mvallevand]

Odd. I just checked the empty.db3 file that is distributed with the application and it definitely has the new database columns, so I cant think why you wouldnt have had them if the app had to recreate the database.

...anyway, try executing those statements from above and you should be ok.

I check my original download and it had an older empty.db3. I redownloaded it and noticed that there are actually several updates to the installer including empty.db3 after the original release date.

Code:

29/05/2008   2:38p        151,552  GBPVRTSReader.ax
29/05/2008   2:45p        143,360  GBPVRPublic.dll
29/05/2008   2:45p         90,112  PVRUiPublic.dll
29/05/2008   2:47p      1,261,568  NativeUtilities.dll
29/05/2008   4:17p         65,536  GBPVRTSMon.ax
30/05/2008   5:52a         49,152  ChangeDatabase.exe
30/05/2008   5:52a        802,816  Config.exe
30/05/2008   5:52a        360,448  GBPVRBackendCommon.dll
30/05/2008   5:52a        167,936  GBPVRRecordingService.exe
30/05/2008   5:52a        110,592  GBPVRTray.exe
30/05/2008   5:52a        806,912  PVRX2.exe
30/05/2008   6:04a         31,439  configmaster.donteditme.xml
30/05/2008   6:10a        232,448  empty.db31

Martin

[sub]

Yes, true.

About a half day after the 1.2.13 release I found I'd had left two settings set to the wrong default value in the config.xml file. This was going to cause problems for new users, so I decided to quietly fix it by repacking the installer and uploading it again. At the same time I decided to include the two minor patches that had been made available during that day for other things. I wouldnt normally have done it, but because I was going to be away and not always around to help people through any issues they had, I decided it was the best course of action (and it didnt justify a new version number)

[techstacy]

Sub,

I'm having an identical issue. I successfully updated the database with your three statements and the resume function returned. However I would prefer to start my most recent fresh install with a working .db3 vs patching what I've got now. I just downloaded GBPVR10213.msi from the link at http://forums.nextpvr.com/showthread.php?t=35528 and PLAYBACK_POSITION showed only 3 columns(?) My empty.db3 shows a modified date of 2/20/2007. Is this correct? :confused: I've reinstalled several times clearing any remaining .db3 files each time just to make sure I'm not overlooking something. The SQLlite screen shot is from my most recent GBPVR10213.msi install.

[truks]

XP with sp3, everything works, but no resume. There was no previous GBPVR install, so no upgrade.

Thanks,

Kurt

[sub]

I'll fix it in the next release. In the meantime, use SQLiteSpy or similar tool to apply the follow statements to gbpvr.db3 and it'll fix it:

Code:

alter table PLAYBACK_POSITION add column duration int
alter table PLAYBACK_POSITION add column last_watched DATETIME
update PLAYBACK_POSITION set last_watched = DATETIME('NOW') where last_watched is null

[jordnära]

Had the same problem and couldn't get SQLiteSpy to execute anything but SQLiteAdmin worked as it should.

[techstacy]

I've noticed several posts in this thread regarding issues with updating their gbpvr.db3 with SQLiteSPY. The following method worked for me. Launch SQLiteSPY and load the gbpvr.db3 database. You'll notice the SQLiteSPY screen is broken into four areas. We'll worry about three of those. A tables view on the left, the contents of those tables in the middle right and the query language field in the upper right (it's blank initially). I was able to get Subs recommened statements to work by copying and pasting each line seperately (in the upper right hand corner area) and executing them individually (the execute command will not be active until you paste a statement into the upper right hand area). For those with little or no experience with databases, such as myself, this process is not especially intuitive. Hope this helps.

SQLiteSPY Screen shot from the author's site: http://snipurl.com/3spn6

[truks]

I'll fix it in the next release. In the meantime, use SQLiteSpy or similar tool to apply the follow statements to gbpvr.db3 and it'll fix it:

Code:

alter table PLAYBACK_POSITION add column duration int
alter table PLAYBACK_POSITION add column last_watched DATETIME
update PLAYBACK_POSITION set last_watched = DATETIME('NOW') where last_watched is null

Thanks much, that worked!

Kurt

[tvshowman]

I had a fresh new drive and windows xp and fresh files from the gbpvr homepage and had the no resume...

Today I finally got around to fixing it with sqlitespy available here. Been too lazy to fix it and PVRX2 is working just flawless for like forever! Bought another 500gig cause they are cheap so went with a fresh install of everything. no database carry over just brand new. I used vidimport and mpgimport to add files on the other hard drives... maybe that's where it messed my resume?

anyway, sqlitespy worked without problems


Happy Thanksgiving to our Canadian friends! (oct 13)