I have tested a new motherboard, graphics card combination that works better than my present setup.
How will Knoppmyth react if I replace the motherboard and graphics card but keep the current harddrive with recordings etc? I know it handles new DVB cards really well.
The graphics card is an nVidia 7100 and the present setup is nforce2. The new CPU is a E6400.

TIA

_________________
R8.1 combined backend/frontend
ASUS P7H55-M Pro
Intel i3-550, 4Gb Ram
Seagate 500GB (Sata)
2x Dvico DVB-T Lite & Sony PlayTV (usb twin tuner)
TP-Link TL-WN881ND PCIe wifi card (not working)
Logitech Harmony One remote, CoolerMaster ATC-S case

If you have onboard lan on both mobo's you'll probably need to run netcardconfig again.

Also, depending on which nvidia driver you have installed, you might have to install a newer one.

Other than that i'm not sure...

After trying to add some extra ram recently I got a Kernal Panic, so that upgrade didn't take.
I think you can get around this sort of issue by doing an auto upgrade, but after the backup switch to the new hardware BEFORE inserting your knoppmyth disc and continuing with the upgrade. That way all your hardware would be auto detected and the database for your recordings will be restored.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

^^ Yeah doing a backup then auto upgrade is probably the safest thing to do!

Another vote for this!. I have done this in the past when migrating to a new machine. Works very slick! Even if you are staying with the same version of KnoppMyth.

Heck I even use auto-upgrade to recover from botched driver tests. See the hints posting for the vitals - making a good backup, keeping the same hostname, ...

Thanks to all, I did a backup as suggested and then an auto-upgrade from 5e50 to 5f1 although with the motherboard/graphics card.
All went very smoothly except that I may have lost my recordings, I did a backup using backup.list set to include /myth/tv but forgot to write a restore.list so I am currently doing a manual restore.
No big deal if I lose the recordings after all thats all they are and it was my doing.

_________________
R8.1 combined backend/frontend
ASUS P7H55-M Pro
Intel i3-550, 4Gb Ram
Seagate 500GB (Sata)
2x Dvico DVB-T Lite & Sony PlayTV (usb twin tuner)
TP-Link TL-WN881ND PCIe wifi card (not working)
Logitech Harmony One remote, CoolerMaster ATC-S case

Not a good idea (it will bloat the the backup file) and not necessary (the whole /myth partition is left alone by the upgrade process).

Guess the exisiting warnings aren't enough and I need to add a check that pukes violently if you try to include /myth or anything underneath it...

BTW - Did you check to see if the problem was just that the backend hadn't started yet?

tjc, The backend was running as I could watch live TV and we could watch videos.
I was just trying to ensure that the Tv recordings were backed up for this particular upgrade as I had a few programmes I wished to watch. I fully realised that the backup file was going to be large (128Gb!) but it was supposed to be a quicker option than archiving all those recordings to dvd.
The restore worked but the database is messed up and can't find them, I restored the database using the and all is fine now.
I don't know if I fully agree with restricting what backup can and can not backup, maybe a warning reminding people what they are doing may be disasterous would be better.

_________________
R8.1 combined backend/frontend
ASUS P7H55-M Pro
Intel i3-550, 4Gb Ram
Seagate 500GB (Sata)
2x Dvico DVB-T Lite & Sony PlayTV (usb twin tuner)
TP-Link TL-WN881ND PCIe wifi card (not working)
Logitech Harmony One remote, CoolerMaster ATC-S case

I'm generally of the same school of thought, trying to keep naive people from doing dumb things usually ends up preventing knowledgable people from doing clever things, however, in this case the dumb thing can be pretty spectactular if someone tries to include all of /myth in their backup and it really doesn't make sense anyway. The whole of /myth is preserved across an upgrade, and If /myth is lost for some reason your backup goes with it. Finally I'm guessing that anyone clever enough to have a good reason to do this is also clever enough to disable the safety checks anyway.