2007-02-03, 06:23 PM
UncleJohnsBand Wrote:Use the new database in the zaptools archive. Also...there is a bug tht imapcts me where I can no longer use the already downloaded zapt data from gbpvr....so if you have that option set try going back to using your user id and password and doing the zap download rather than using what gbpvr creates.
sub is looking into tht issue.
Yes, I found that GB-PVR seems to be over writting the previously saved zap2it.xml instead of replacing the file. So, if the new data is fewer bytes than the previous data, the tail end of the previous data remains in the file, and the xml parsing becomes confused due to the extra garbage at the end.
Deleting the xml file after zapimport forces GB-PVR to create a new file each day, which appear to be fine.
David
PVR PC: Win2K3, Athlon x2 64 4600+, 1280MB Ram, 40+400 GB HD's, Gigabyte Network
PVR-250, ATSC-110 digital x2, GBPVR v1.3.7 w/SQLite DB
Extras: Addepisode 41, Comskip 79.46, EWA 76, Zaptools
DSM-520 (D-Link Media Lounge) FW 1.04 using TVersity Media Server 0.9.11.4
DSM-320 (D-Link Media Lounge) FW 1.09
MediaMVP
More specs
PVR PC: Win2K3, Athlon x2 64 4600+, 1280MB Ram, 40+400 GB HD's, Gigabyte Network
PVR-250, ATSC-110 digital x2, GBPVR v1.3.7 w/SQLite DB
Extras: Addepisode 41, Comskip 79.46, EWA 76, Zaptools
DSM-520 (D-Link Media Lounge) FW 1.04 using TVersity Media Server 0.9.11.4
DSM-320 (D-Link Media Lounge) FW 1.09
MediaMVP
More specs