Is NPVR alive and well?

[Antmannz]

I would've thought that 2Gb RAM should be enough, and shouldn't cause the choppy playback Grampz is experiencing.

One thing I would check though is hard drive speed. If it's an old drive perhaps its only a 5400rpm model rather than 7200rpm (although scrolling back I see that recording works flawlessly - but worth a mention anyway).

[Grampz]

Ok all, here is the latest...

- added 1gb ram, now 3
- installed .5tb sata drive
- installed 600 watt power supply, old one was 300 and only 20 pin atx power connector to board, now 24
- in process of setting up win7-64bit

I think this should speed things up and add to system stability.

After os, directx, .net, etc... setups I will install new npvr version. My thoughts are to copy npvr data and program folders, live tv and recorded tv folders from old drive to new, and then install the new version of npvr. Will this work or not?

Greg

[bgowland]

My thoughts are to copy npvr data and program folders, live tv and recorded tv folders from old drive to new, and then install the new version of npvr. Will this work or not?

sub might correct me on this but I would do a vanilla install of the same npvr version you have now onto your new drive in order to put the registry entries in place and to register the various filters etc.

I'd then stop ntray, the npvr rec service and any nextpvr.exe instances THEN drag and drop all of your folders from the old drive (but don't start any npvr components up). After that I'd do an updrade to 2.3.6.

[sub]

I'd just install the new version, then stop it, then copy across the config.xml and npvr.db3. Since its a different version, you'll need to update the database by running "nextpvr.exe -updatedb".

[bgowland]

I'd just install the new version, then stop it, then copy across the config.xml and npvr.db3. Since its a different version, you'll need to update the database by running "nextpvr.exe -updatedb".

Ah, forgot about the -updatedb command-line parameter (haven't had to use it myself). The DB was mostly what I was worried about which is why I suggested installing the previous version first. Might have known you'd have a better answer.

[sub]

No worries, this "-updatedb" parameter is new, and going to simplify the steps to fix problems when people are trying to move old databases to new versions.

[Grampz]

am now ready to proceed with installation. install new version first, stop services, copy old data folder, then convert? Recordings and programs plugin folders already moved.

[Grampz]

also, just the config.xml and db file? what about the scripts and plugin folders..... ???

[bgowland]

also, just the config.xml and db file? what about the scripts and plugin folders..... ???

It should be safe to drag and drop those in as well unless any plugins did anything 'special' as part of an installation in which case re-install them. If they are plugins that just needed unzipping into the plugins folder then copying from the old drive would work.

[steeb]

Sorry to hijack this thread

I feel a need, now particularly with sub's new -updatedb command line parameter, that this really would benifit a write up on the wiki.

Basically what to do if upgrading/changing machines etc from having had a fully running NextPVR PC.

Before I suggest that for the wiki would this thread be the one to point to as a kind of definitive "what to do"?

cheers all

steeb