![]() |
|
|||||||
| DVRupgrade Store | DVRupgrade Blog | DVRupgrade Helpdesk | Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Slicer Upgrade to 6.3e
I purchased Slicer v1.3 more than a year ago and was able to upgrade my HR10-250 from 3.1.5f to 6.3a to 6.3b to 6.3c at various times. I've run the echo mls /SwSystem | tivosh and see the 6.3e-01-2-357 software downloaded to my system. When I try to run ./slicer 6.3e-01-2-357 , I get the following messages:
bash-2.02# bash-2.02# echo mls /SwSystem | tivosh Directory of /SwSystem starting at '' Name Type FsId Date Time Size ---- ---- ---- ---- ---- ---- 6.3a-01-2-357 tyDb 572808 02/27/07 04:06 772 6.3c-01-2-357 tyDb 1147837 02/27/07 04:06 796 6.3e-01-2-357 tyDb 1946383 08/11/07 10:40 780 ACTIVE tyDb 1147837 02/27/07 04:06 796 bash-2.02# ./slicer 6.3e-01-2-357 ./slicer: ?xml: No such file or directory ./slicer: !--TransferQueueItems--: No such file or directory ./slicer: line 3: syntax error near unexpected token `'/slicer: line 3: `1 bash-2.02# bash-2.02# Any ideas? |
|
#2
|
|||
|
|||
|
Quote:
|
|
#3
|
|||
|
|||
|
Yes, I've used this version of Slicer many times in the past to go from 3.1.5f to 6.3a, 6.3a to 6.3b and 6.3b to 6.3c.
Is there another script that you can recommend running? |
|
#4
|
|||
|
|||
|
You can try mounting your filesystem read only with
Code:
mount -o remount,ro / Code:
e2fsck -p |
|
#5
|
|||
|
|||
|
The "rootwrite" and "rootread" scripts work fine. I've also tried copying Slicer to \var\hack, \var\tmp and one other location, but I get the same error wherever I run it from.
I'll try your file system repair when my HR10-250 is not recording a show. Thanks for your suggestions. |
|
#6
|
|||
|
|||
|
Quote:
|
|
#7
|
|||
|
|||
|
Looks like somehow my Slicer file was corrupted? I located a Slicer 1.9 file which was 63 kB in size and worked fine. For some reason, the Slicer 1.3 file I had was only 1 kB in size.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|