(FYI, version 3.0.1.44 does not appear in the Milestone pulldown menu.)
Running 3.0.1.44 on Win7 with SP1. The following command
"C:\Program Files (x86)\Apps\Realterm3\realterm.exe" display=1
fails with a dialog saying:
"Access violation at address 00609E8D in module 'realterm.exe'. Read of address 00000060."
I get the same failure if I put the command into a shortcut or if I point to a .ini file containing the single line "DISPLAY=1".
"C:\Program Files (x86)\Apps\Realterm3\realterm.exe" inifile=%APPDATA%\Realterm\setDisplay.ini
If I click OK on the error dialog then RT sortof works. It also redisplays the same dialog when I try to exit with the close X or with Alt-F4.
While you are testing this please also check that DISPLAY=-3 works , since HEX+[x] is what I really want.
Would you also add or give me the parameter for setting the checkbox for "\n Before/After" on the Send tab?
Would you add a checkbox on the Display tab (maybe next to Scrollback) that will disable the auto-setting of Cols when I change the Display As radio selection?
Thanks!
I get this same bug in 3.0.1.44 running on Windows 10 Home version 1709.
a) pls make a feature request explaining in more detail when and why and what display modes the auto-cols setting isn't working for you.
The whole area of term size/cols/resizing/modes is a big rentrant knot worthy of his googlyness the FSM. Generally disabling it will cause issues.
b) Not sure when work will resume. Sparks were followed by a long dark teatime for my windows laptop. RIP.
Make a feature request for new commandline params..
Where do I get a copy of 'Realterm_3.0.1.45_setup.exe' to test?
Sorry, I just don't see where to click on https://sourceforge.net/p/realterm/
Or on https://realterm.i2cchip.com/
windows update has fritzed the new laptop, so not released yet. Try this test version:
https://realterm.i2cchip.com/Realterm_BUG_TESTERS_ONLY_BETA_3.0.1.45_setup.exe
Downloaded and tested on Win7 SP1 and WinXP SP3.
The requested bug fix of running with the argument display=3 is good on both.
Works directly on the CL, and from a xyz.ini file and inifile=xyz.ini
However, on XP I sometimes get an initial dialog that says "Floating point division by zero.".
It depends on what the CL argument is.
These give the popup dialog:
realterm.exe (alone)
realterm.exe tab=port
realterm.exe display=0
These do not give the dialog and work as expected:
realterm.exe inifile=xyx.ini (with any combination of the above arguments)
realterm.exe display=3 (or 1 or 2)
After I dismiss the dialog, the requested argument succeeds and everything seems to work.
No failures on Win7.
Not filing a bug on this 'cause I use a inifile, and 'cause I figure you'll fix it in beta.
Thanks for your work!
This is a bug I introduces at V43or44 I think, but I have no idea whereit is. Anymore information or clues you can give me would be appreciated. (it never throws the error for me.) If you could test the earlier versions 43,44 and report if you can get the same error at all, that might help narrow down when I introduced the bug.
I also hope you can add, a CL param for setting the checkbox on the Send tab that says "\n Before/After". Thanks again.
make a feature request. Give me a couple of suggestions for the parameter name. (no long, not confusing )
Done
https://sourceforge.net/p/realterm/feature-requests/54/