2012-02-05, 08:40 PM
If you search the binary for 01 02 DC 07, and change it to something like 01 20 EF 07.
2012-02-05, 08:40 PM
If you search the binary for 01 02 DC 07, and change it to something like 01 20 EF 07.
2012-02-05, 09:37 PM
Sub, is the source "01 02" or "01 20" The three GBPVR.exe's I still have don't have the 01 02 DC 07 sequence.
Martin
2012-02-05, 10:08 PM
Sorry, it was "01 20 DC 07"
2012-02-05, 10:17 PM
Ok thanks for those that want this here is a sed command line to do the replace that sub wrote about
Code: sed.exe -b "s/\x01\x20\xDC\x07/\x01\x20\xEF\x07/g" GBPVR.exe > newfile fla, here is your file after running this confirmed with fc Comparing files GBPVR.exe.1.1.5.patched and GBPVR.EXE.1.1.5.ORIGINAL 00049977: EF DC Martin
2012-02-05, 10:43 PM
Thanks mvallevand. I had already edited 2 bytes with a hex editor but had to change the replacement bytes to get the mini-guide to work. I attached the modified version that fixes it in my installation of gbpvr 1.1.5. Others can try both versions to see what works for them.
I'm exhausted but this brings back great memories. The people on these forums follow sub's lead and are so kind and helpful.
2012-02-05, 10:50 PM
So you changed the DC to an E4 instead of EF, I don't know why that would make a difference for the mini guide (2031 vs 2020) but glad it works for you.
Martin
what kind of bug is this? I've been running gbpvr for a few years on one version and it also started showing up. It's a time bomb?
will it fix itself? I'm not ready to upgrade yet ![]()
E6400, 2 GB RAM ,500 GB + 250 GB HD, PVR150+ Adaptec 3610, RW 2 + HIP, Antec 2480 w/ mini ninja ...still using v 0.99
2012-02-06, 04:45 AM
Sometimes when you code, you base things on limits that only look bad in retrospect. Files size > 2GB and 4GB are notorious for that and there are still lots of useful and unsupported utilities that can't handle today's big files. The classic example though happened in Y2k and another is coming in Y2K38
If sub meant this maliciously do you think he would have issued a patch? You can try my sed command line (sed is here http://gnuwin32.sourceforge.net/packages/sed.htm you need the binaries and dependancies) against your GBPVR.exe or I guess you could upload your GBPVR.exe and I can do it. Martin
2012-02-06, 04:50 AM
It was just some dumb logic I had in this very early TV Guide code back in 2004, that said 'grab all the listings between now and 2012', and my intention was come back and replace it with something smarter at a later stage (which I eventually did). Unfortunately I never anticipated anyone would still be using those old versions in 2012.
Back in 2006, PVRX2.exe sported a rewritten TV Guide screen and didnt have this type of limit. Neither did NextPVR.
2012-02-06, 12:29 PM
My apologies Sub, I didn't mean any disrespect. It was a bad choice of words. Hopefully it only affects the guide and not the actual recordings as we can still use the search function. I'll try the EWA as a kludge for me while I set up my new one. I guess it was a good time for me to start my upgrade.
E6400, 2 GB RAM ,500 GB + 250 GB HD, PVR150+ Adaptec 3610, RW 2 + HIP, Antec 2480 w/ mini ninja ...still using v 0.99
|
|