Arev32 form sizing (AREV32)
At 07 OCT 2020 04:52:07AM Kendal Hulbert wrote:
We are running arev32 on a windows 2016 server platform from a windows 10 client PC.
What we are seeing is that on first startup of Arev32 from the client, the screen looks correct, but when running it as part of a batch process where Arev32 is started as part of a cmd, we get the correct parent form size but that actual arev blue area is almost postage stamp size within the parent form with masses of black space around it.
This issue has only been seen in this scenario, running it on a windows 10 machine directly or from another client VDI connected to the win10 PC is fine. Just when running arev32 from a client machine from the windows 2016 server.
I have screen prints and we have looked at oinsight.ini, CFG_CTO settings and any other .ini file we can find with no success. Anyone got any ideas please?
At 07 OCT 2020 06:17AM Andrew McAuley wrote:
Not a help but we had this issue with AREV32 when remote desktopping into a specific client from a specific machine. Changing machine was the only solution we could come up with with their IT department as it seemed to be video driver related.
World leaders in all things RevSoft
At 08 OCT 2020 04:39AM Kendal Hulbert wrote:
Thanks, but we have apparently resolved this. yay!
run OCXReg.cmd and screen sizing is back to normal.
At 08 OCT 2020 04:45AM Andrew McAuley wrote:
TBH if you hadn't got a working client install I'm surprised you saw anything :). Still all's well that ends well :)
World leaders in all things RevSoft
At 08 OCT 2020 08:19AM D Harmacek wrote:
Please what is in this "run OCXReg.cmd a"?
I remind you that the configuration file for AREV32/64 is probably using the same as the DOS version.
This is named something like AREVC.INI and is found in the folder of oinsight.exe.
It appears there are coordinates on line 1.
To see this you login as SYSPROG into AREV32. Start the menu STARTUP. Then choose Options / Workstation / Hardware
You will see the form for Workstation Hardware INI. To see the name of that file press SF1.
Dave Harmacek - Harmacek Database Systems - near Boston, MA USA
At 09 OCT 2020 06:27AM Kendal Hulbert wrote:
Spoke too soon, problem still occurs.
At 09 OCT 2020 06:31AM Kendal Hulbert wrote:
What we are seeing is that at times the screen is fine, then the next time we start arev32 it's not, and so on. Need to try to find what triggers the difference. is there something in the batch startup that is affecting the display.
At 09 OCT 2020 03:02PM D Harmacek wrote:
I did a search for AREV32 startup process
Dave Harmacek - Harmacek Database Systems - near Boston, MA USA
At 14 OCT 2020 05:36AM Kendal Hulbert wrote:
Windows 10 comes with a new Windows Font Cache service and this appears to be the problem.
We have disabled this service and so far, 3 days down the line and the problem has not recurred.