Friends of Gabriel Chantayan

z0pl's fluke firmware dates from 2003 and the DST patch was never applied. also he demands EXIF timestamps from others.

EuroTrash_Herr666 finally readin the firmware date correctly what's the column K thermal offset at row 45 under 2005-09-12 DST correction

ScribeOfTheGrid still citing sheet 3 when I corrected him in topic 319 row 46. Firmware blind leading the meter blind

FlameFury24 already corrected row 46 in topic 319 and I conceded. LyrikUebersetzer citing the same correction like its new is just post padding. whats the DST flag on your NIST file reference.

Agreed. per firmware date check, column K thermal offset at row 45 requires full DST correction applied to NIST reference.

scribe still citing column K row 45 after topic 319 migrated it to row 79. lyrik and scribe going back and forth about who corrected who first while both citing the wrong row. this is the evidence base the doubters corner is working with.

ScribeOfTheGrid wrote:FlameFury24 already corrected row 46 in topic 319 and I conceded. LyrikUebersetzer citing the same correction like its new is just post padding. whats the DST flag on your NIST file reference.

U WOT M8. U "conceded" in topic 319 but STILL cited row 45 in topic 314 which is BEFORE u conceded?? So either ur chronology is garbage or u admitted row 46 was right and then went BACK to row 45 in the same breath. That's not a correction, that's u playing both sides so u never have to admit u were wrong across the board. Pick a row and STICK to it or take ur outdated spreadsheet back to 2005 where it belongs

EuroTrash_Herr666 wrote:z0pl's fluke firmware dates from 2003 and the DST patch was never applied. also he demands EXIF timestamps from others.

EUROTRASH YOUR FLUKE IS A GRID TRANSMITTER DISGUISED AS A METER

EuroTrash_Herr666 wait so if the DST patch was never applied does that mean ALL the euclid readings are off by like an hour or something?? this changes everything surely???

lyrik and scribe burning 7 posts arguing about who corrected who first while both of them are still citing the wrong spreadsheet row. this is like watching two men argue over the steering wheel of a car that's been parked in a lake since 2004.

elderprophet07 noticed the exif firmware date on classof04's cuff photo but somehow missed the padding at 0x4B that reads 'REV_B' which rewrites the whole timeline if you bother to scroll past the first 3 bytes. but nobody here scrolls do they

I say unto you all: the DST patch does not alter the firmware version number, only the timezone tables So z0pl's 2003 firmware date stands regardless of the patch. Now -- which of you has the Fluke's thermistor continuity reading, because four posts in and ScribeOfTheGrid still has not answered TechAngel_00 Ask the question that matters.

EuroTrash_Herr666 still posting "REV_B" from offset 0x4B like it's news when the padding at 0x4C is all zeros scroll one more byte next time

NeonNites_UK realizing the DST bug invalidates all euclid readings is like finding out the church potluck was scheduled for last week honey we been eating cold casserole since August

has even ONE of you checked the battery compartment on your own fluke for the 2003 date code

this thread is just people arguing about who cited the wrong row first while gabriel's hum sits there unmeasured, the proof is in the trembling hands not the firmware date