GFXboot, editing, animation

GFXboot message represents CPIO archive.
The file "init" is an executable kernel of this archive.
The file "init" is compiled from a set *.inc scripts by the program "mkbootmsg.exe"
I invite to dialogue of developers of inc-scripts.
I suggest to discuss in this topic problems and solutions on advanced transformations of GFXboot messages on inc-scripts editing bases.

======================================
I have developed the base module and specifications for connection to the project of additional scripts (modules). Besides I have some own scripts (modules). (It's transferred in Post #5)

It is corrected 25/04/2010

so, with the support of google translator, i tried to lookup, what u developed. either, its very tough for non-russian to work with ur files, even to get the download link for archive DED2007v2
looks very interesting, but at least the included helpfiles (*.txt on the root) should be in a english, otherwise the obstacle is to high to take it.
a great pity.

 

its very tough for non-russian to work with ur files, even to get the download link for archive DED2007v2  

Yes, I understand it. I will necessarily make attempt competently to translate all txt files into English.

However, in this topic I want to concentrate on inc-scripts.

Me possibilities and restrictions of this programming language interest.

Very good.

Proper English support is indeed important but don't worry because we are here to help.

If you're unable to write a lot of text, perhaps it is simpler to create a small video tutorial with a free tool such as this: http://www.boot-land...showtopic=11198

This way it is possible to more or less understand how you're doing the steps and then replicate them.

Keep up the good work!

==========================
My purpose consists in discussion of language of inc-scripts,
instead of "@DED-LEGO@" message.
========================== Topic for gfxboot @DED-LEGO@ discussion, will happen HERE and also Russian forum

(It is corrected 21-12-2010)

It is definitely great job, but you should know Russian and documentation is coded in Win 866 (?) - OEM Russian

I will try to translate documents and comments in the file settings but it will take much time.

It is definitely great job, but you should know Russian and documentation is coded in Win 866 (?) - OEM Russian

I will try to translate documents and comments in the file settings but it will take much time.

No hurry whatsoever : you will be doing a great service to the boot-land community take your time, but please do come back with something that explains this tool, we all can see the great potentials it has , but are not able to understand most of it's working/settings/use .


Wonko

Outdated data (21-12-2010 DED):

Is it possible to give all three resolutions in one gfxboot.cfg?

If you have the source code of your gfxboot, then have a look at the script common.inc. You might be interested in these parts of common.inc:

false "custom_width" getgfxnum dup {
0 "custom_height" getgfxnum 16 "custom_depth" getgfxnum findmode setmode
} if

not {
800 600 16 findmode setmode not {
800 600 32 findmode setmode not {
640 480 16 findmode setmode not {
640 480 32 findmode setmode not {
false .end
} if
} if
} if
} if
} if

Here we see two parts.

The first checks the settings given in gfxboot.cfg.

false "custom_width" getgfxnum dup {
0 "custom_height" getgfxnum 16 "custom_depth" getgfxnum findmode setmode
} if

The second - is trying to brute force the graphics mode options.

not {
800 600 16 findmode setmode not {
800 600 32 findmode setmode not {
640 480 16 findmode setmode not {
640 480 32 findmode setmode not {
false .end } if } if } if } if } if

Solution: Try to include your graphics modes in the second part

not {
1280 1024 32 findmode setmode not {
1024 768 32 findmode setmode not {
800 600 16 findmode setmode not {
800 600 32 findmode setmode not {
640 480 16 findmode setmode not {
640 480 32 findmode setmode not {
false .end } if } if } if } if } if } if } if

Notes:
1. We are talking about gfxboot from "Configurable gfxmenu" topic and similar gfxboots (version 3.3)
2. You should comment out the lines in gfxboot.cfg

custom_width=1024
custom_height=768
custom_depth=32

# custom_width=1024
# custom_height=768
# custom_depth=32

3. By the way. The latest version of @DED-LEGO@ sets the graphics mode by the size of the background picture back.jpg

Edited by ded, 21 December 2010 - 05:02 PM.

Another remark:

4. Gfxboot has no built-in video drivers. It works in VESA mode. This can cause some problems. Especially in the case, if the motherboard has integrated video. 

Edited by ded, 10 December 2010 - 11:58 AM.

Does anyone know how can I bring ... blank lines in the menu.lst?

How to make skipped the menu bar in gfxboot

1. Make a backup copy of your main.inc.
2. Open main.inc with any text editor.
3. Searching for the sample "/main.input" (without quotes of course) in tne text of main.inc
- This sample is the beginning of the script that processes the keystrokes
- The opening brace "{", which goes after the specified text, shows beginning of the script
- A closing brace "}", which corresponding to a given "{", is accompanied word "} def". "} def" - this is the end of this script. And it is located after the block
dup 0 ne {
"opt" help.setcontext
} if
- Inside this script examines pressing various keys. For this reason, the script consists of a set of blocks "if", which are enclosed between commands
dup Verifiable_Code eq {
....
....
pop 0
} if
We are interested in blocks of keyUp and keyDown.
4. If all the above is clear and you have identified all of the blocks, then we can proceed to modify the script.
=========================
- Beginning of the script. Block ...
=========================
- BLOCK keyUp ...
=========================
- BLOCK keyDown ...
=========================
- END SCRIPT. Block ...



5. "---" - This is a sample menu bars to be skipped when moving up / down. Can define his own version, such as 7 spaces. Note that the first space after the "title" is a service and is not part of the menu bar.
Coincidence should be accurate, ie, "---" And "--- " is not the same thing.
6. Save the changes to main.inc, recompile gfxboot, add to menu.lst command...

title ---
configfile /menu.lst

...and test it.
*********************************************
Notes:
1. We are talking about gfxboot from "Configurable gfxmenu" topic and similar gfxboots (version 3.3)
2. All braces "{" and "}" must be framed with spaces (" { " and " } ")
3. New and modified commands are highlighted in red
4. Commands from your main.inc may differ slightly from those listed above. Try to approach creatively to main.inc editing

I think he was asking, how to add empty (non-visible extra) lines (separating menu sections) - that's how I understand his question, may be wrong.

I think he was asking, how to add empty (non-visible extra) lines (separating menu sections) - that's how I understand his question, may be wrong.

5. "---" - This is a sample menu bars to be skipped when moving up / down. Can define his own version, such as 7 spaces. Note that the first space after the "title" is a service and is not part of the menu bar.

Topic is divided into two independent ones.


An example of features that gives us the editing of inc-scripts can be found HERE