https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5437
--- Comment #3 from Harald N <harald.norvik@xxxxxxxxxxxx> 2010-11-26 14:19:57 PST ---
I will verify again, and I don't exclude the possibility of some local profile
issues could cause this. The experienced situation can be clearified like this:
1) Running 1.4.2 from the main install directory didn't want to calculate the
scaled window size - with or without the tcp protocol options set. Turning on
and off didn't affect the trace interpretation. Neighter did setting the option
in preferences, closing the trace file and/or Wireshark and reopen it.
2) Running 1.4.0 and 1.4.1 from different install directories did respond
correctly to the preference settings - either set at preference or while
looking at the trace file.
3) Reinstalling 1.4.1 on top of the 1.4.2 installation did show some odd
behaviour as it would not show the scaled window size when opening the trace
file. Toggling the relative sequence number + Window scaling while look at the
trace would then recalculate the correct window size.
It looks that the window scale calculation is not called at opening the file,
but it when the relative sequence number is toggled off and on.
For the record, i haven't seen anything wrong with the relative seq number
calc.
I will try to reinstall 1.4.2 into the main program directory and recheck. I
can then provide screenshots and trace files.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
