Hello Guest it is May 15, 2021, 08:08:40 PM

Author Topic: machine.ini  (Read 1360 times)

0 Members and 1 Guest are viewing this topic.

« on: July 01, 2016, 06:14:10 PM »
Is the machine.ini connected to the screenset in anyway other than defining what screenset to load? What I attempted todo in order to save myself some effort once again
was to copy the working .ini file from a profile into a newly created profile which uses wxrouter.. When I do this, I notice there are some color changes?? where there should not be. As well
upon exit I can an error msg as shown here


This is due to wxrouter storing values in the machine.ini. I eventually found these values and copied them over. This is not very unhandy.. wxrouter should have it's own ini to store values in and not store them in the machine definitions. doing this causes it to be highly unportable and makes updating a frustrating process as you need to copy machine settings down on paper and then re-write your machine.ini.

Offline DazTheGas

  •  753 753
  • DazTheGas
    • View Profile
Re: machine.ini
« Reply #1 on: July 01, 2016, 07:10:37 PM »
The Tframe var is a part of the Touch button and screen unload script, it is implemented in all the latest profiles so perhaps the machine.ini is from a version that did not originally have this implemented.

Theres always time for a choccy biccy