CGXMode
CGraphX Mode |
|
µs = ( 1 / (Vertical Resolution in seconds + blanking period)) * Line(s) * 1000000
µs = ( 1 / (Vertical Resolution in seconds + blanking period)) * Line(s) * 1000000
ms = ( 1 / (Vertical Resolution in seconds + blanking period)) * Line(s) * 1000
ms = ( 1 / (Vertical Resolution in seconds + blanking period)) * Line(s) * 1000
|
A: Front Porch B: Sync Period C: Back Porch D: Blanking Period E: Display Period F: Total Cycle S: Sync Singal Level V: Video Signal Level |
|
|
|
| When you click on the Test button from the Edit Mode window it opens a screen with a test pattern screen with the settings that are in the Edit Mode window and then puts the Edit Mode window on top of the test pattern screen. Doing this allows you to see the direct relationship between the numbers that you input and change to how it will effect editing the screen. The only difference from the normal Edit Mode window and Test-Edit Mode window is that the Hidden, Type, ScanMode, PixelClock and Resolution can not be changed and are ghosted out. |
|
As with the normalEdit Mode window you can enter the number in directly
or by using the up and down gads. With the Test-Edit Mode you can also use the keyboard to quickly edit the
screen mode values. Here is a overview table as to what the keys do:
| Key(s) | Result |
| ESC | Will exit the Test-Edit Mode and restore the values if you had changed any while editing on the test pattern screen |
| RETURN | Will accept the values you have edited and take you back to the Edit Mode window and update the new number there |
| I | Will inverse all the colors on the test pattern screen, ie black to white etc... |
| [UP-ARROW] | This is used for centering the screen by moving the screen up. This key edits the Vertical Pulse Offset (It adds milliseconds (ms) to the current value). |
| [DOWN-ARROW] | This is used for centering the screen by moving the screen down. This key edits the Vertical Pulse Offset (It subtracts milliseconds (ms) from the current value). |
| [LEFT-ARROW] | This is used for centering the screen by moving the screen left. This key edits the Horizontal Pulse Offset (It adds microseconds (µs) to the current value). |
| [RIGHT-ARROW] | This is used for centering the screen by moving the screen right. This key edits the Horizontal Pulse Offset (It subtracts microseconds (µs) from the current value). |
| [SHIFT]+[UP-ARROW] | This is used for making the vertical height (tallness) of the screen bigger. This key edits the Vertical Sync Lenght (It subtracts milliseconds (ms) from the current value). |
| [SHIFT]+[DOWN-ARROW] | This is used for making the vertical height (tallness) of the screen smaller. This key edits the Vertical Sync Lenght (It adds milliseconds (ms) to the current value). |
| [SHIFT]+[LEFT-ARROW] | This is used for making the horizontal width (wideness) of the screen bigger. This key edits the Horizontal Sync Lenght (It subtracts milliseconds (ms) from the current value). |
| [SHIFT]+[RIGHT-ARROW] | This is used for making the horizontal width (wideness) of the screen smaller. This key edits the Horizontal Sync Lenght (It adds milliseconds (ms) to the current value). |
| Tooltype OFF | Tooltype ON |
| (ADVANCED): If the ADVANCED tooltype is 'off' (ie not there or setup like '(ADVANCED)') then CGXMode will not be in the in ADVANCED mode. This means that CGXMode will do the math so that when you edit a screen it will not allow you to overdrive or push your monitor specs out side of the monitors range. This is more or less a safety check. You should check to see if ADVANCED tooltype is there before you start editing screenmodes if you wish CGXMode to check for overdriving your monitor! | ADVANCED: If the ADVANCED tooltype is there then CGXMode will NOT do 'the math', thus it will not do safety check on the numbers you input and if you overdriver your monitor (enter a number that is to high or to low) you could damage your monitor. Overdriving or underdriving your monitor could damage it. Older and 'cheaper' monitors do not have any protection against this. Some newer and 'better' monitors have protection against overdriving or underdriving.. but you should never count on that. If you do not understand what all the numbers you are editing for a screen in CGXMode do and how they related to the MAX and MIN for your monitor you should NOT USE the ADVANCED Mode. |
| Error Message | What it means |
| Can't update testmode definition: | You might have the wrong cgx library and monitor driver combination. Your libs/monitordirver/cgxmode are not current and you should try to update to the latest of everything. |
| Can't open test screen: | Can't open test screen happened with old cgxmode's when you wanted to modify a card displaymode although the driver was not installed. Also if you are low on fast memory with the old CGXMode you also might get this error. The new cgxmode versions use a new interface to update the test mode config. From r69a readme: "added 2 new LVOs to cgxsystem.library that handle communication with CGXMode" You should try to update to the latest CGX and latest CGXMode. |