Thanks thomson for the help. But I should have mentioned this isn't the first imaging of the tivo I've done. I used an earlier 1.3 version and had similar error messages in particular the time warping and DBnotfound messages which I tried to correct by a combination of touching the timestamp and then the forcingindexing script but this didn't seem to stop the error messages.
For that reason I decided to get this latest version and try it. There seems to be a lot of solutions put forward regarding time warping given the fact I'm using v1.4 of the ozTivo I'd love to know which is the appropriate one.
As thomson had said this is not normal. The correct ntpdate file has been included with all r1.4 releases since april 1st and no workarounds should be needed.
You will have warp message within the 1st 24 hours after GS, but you should not have any after this.
Are you still receiving the warp messages?
What is the timestamp of the timestamp file?
Try this and see what you get
Code:
ntpdate 207.126.98.204 207.126.98.204 131.107.1.10
Peter.
Bookmarks