Jump to content











Photo
- - - - -

My grub4dos Utilities

grub4dos scripting

  • Please log in to reply
47 replies to this topic

#1 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 18 October 2022 - 11:37 AM

Occasional I write scripts to have a grub4dos utility. I am planning to report in this thread.

 

BTW Last versions can be found on https://github.com/deomsh

Published so far: ATTRIB.G4B (v0.4.4), ATTRIBFT.LLL (v0.7.1.0.1), CALCD.G4B (v0.2), TEXTSTAT.G4B (v0.7), Fn11.g4b (v0.3.1)

 

This time TEXTSTAT.G4B, for me quite useful when writing big scripts.

 

Function:
detect zeros before last EOL
count lines (with EOL & Text-type)
count labels
count remark(ed)-lines
returns line-number(s) with spaces at end-of-line
count chars of longest line
optional: count phrase with switch

 

BTW remarks NOT at the beginning of a line needs a space before to be counted (and in case of ; a space behind too!). Standard remarks supported: # :: ; and REM - otherwise search with /COUNT:phrase or "/COUNT:phrase" is available.

 

Although I made TEXTSTAT.G4B for grub4dos-scripts, the utility can be used for other text files too.

Detection of text files is rather primitive: if a zero (00) is found, file is rejected. :ph34r:

 

Three print-screens, first one with help, second one with some of the examples, third one with random text file.

 

 

TEXTSTAT.G4B v0.6 with no arguments.jpg TEXTSTAT.G4B v0.6 with TEXTSTAT.G4B (space before EOL on Line 2) + three examples from Help.jpg TEXTSTAT.G4B (hd0,0)-WINDOWS-PROGRAMM.TXT.jpg

 

BTW the space showed at the end of line two (second print-screen) is not in the published version. :D

 

There are two versions available, last version is v0.6: https://github.com/deomsh/TEXTSTAT.G4B



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 18 October 2022 - 11:43 AM

I use the pragmatic approach...

 

At the beginning of the grub4dos batch file I put

set CHECKLEN= ;; call :CHECKLEN ;; if "%CHECKLEN%"=="" pause ERROR: %~f0 IS TOO LONG! ;; set CHECKLEN=

[LOTS MORE LINES HERE]

 

at the end of the file I put

# ----- THIS MUST BE AT THE END OF THIS FILE! DO NOT REMOVE IT! -----
:CHECKLEN
set CHECKLEN=1

That way I instantly know if there is a problem. Of course it does use one extra label and extra lines.

 



#3 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 18 October 2022 - 11:53 AM

Results for my large batch file attached.

 

For batch files:

# Max no. code lines = 2048 in a batch file, Max. no. labels in a batch file = 128, file must start with !BAT on first line.

 

So it is useful to count the code lines (i.e. ignore lines not starting with : space or a-z  ???)

 

Attached Thumbnails

  • textstat.JPG


#4 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 18 October 2022 - 12:06 PM

Can't seem to get /COUNT to work?? Haven't tried looking at code though...

 

Not echoing %result% at end ??

Attached Thumbnails

  • textstatdebug.JPG


#5 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 18 October 2022 - 10:23 PM

Thanks for testing.

Your CHECKLEN approach sounds interesting, especialy at the border of 2048 (not 2000?) grub4dos code-lines.

About targeting these code-lines: TEXTSTAT.G4B is ment to be general, it's not BAT!TEXT.G4B... Most of the time I watch total number of lines together with remarked lines to see how much slack I have left. But I have the habit to remark more or less working lines before I try a variation. Now and then I 'clean' my scripts.

About counting a phrase: don't forget the colon in /COUNT:phrase (and before the filename). If spaces are involved use "/COUNT:p h r a s e" (or \x20 of course). It's all in the help, together with Examples.

I just retested TEXTSTAT.G4B on my smartphone with Limbo x86, everything seems good.

Screenshot_20221018-231723.png

The result-variable is not exported by TEXTSTAT.G4B, only used internally (in fact subroutines generate a result).
Subroutine :count is not called now, but accessed with 'goto'.
If you want access to variable 'result' afterwards, just double Line 201, or rewrite line 33, for instance:

if exist COUNT && call :count &; endlocal && set result=%result% && debug msg=3 && goto :eof
(and delete line 202). Maybe you should left out first '&&' (-:

BTW can't do formatting or code-box in stupid mobile Firefox.

#6 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 18 October 2022 - 10:47 PM

maybe the version on github is not the same one that you are using?



#7 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 18 October 2022 - 11:23 PM

Sure, I just downloaded v0.6 to my smartphone from github to test from scratch. I used the zip (version 0.4 has no /COUNT:phrase, but seen your last print-screen you have version 0.6.

My grub4dos version is 20220915, started from MS-DOS command-line with 'grub', no special graphicsmode

This is my debug, searching 'if':


Screenshot_20221019-010724.png

As far I can judge from your print-screen you where searching 'set'.

No problems either with a MS-DOS text file (CALCD.G4B was Unix)

Screenshot_20221019-011322.png

Also the if-statements with '\x0D\x0A' does not seem to have problems:

Screenshot_20221019-014432.png

#8 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 19 October 2022 - 07:36 AM

does not work unless using text mode !

 

I use 800x600

Attached Thumbnails

  • t1.JPG
  • t2.JPG


#9 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 19 October 2022 - 08:16 AM

Issue seems to be that Fn.5  sometimes returns true and sometimes false!

 

call Fn.5 0 3 || echo YES

 

this works in mode 3 but not in 800x600 (it returns true and YES is not printed)



#10 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 19 October 2022 - 08:49 AM

suggest avoid cursor commands so can use in any mode.

 

or use

 

echo -P:XXYY

 

e.g.  in a batch file 

#set two digit decimal values for x and y
set /a x=x ;; if "%x:~1,1%"=="" set x=0%x% ;; set /a y=y ;; if "%y:~1,1%"=="" set y=0%y%
echo -P:%x%%%y%  HELLO

I think echo always returns true ???



#11 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 19 October 2022 - 10:07 AM

Wow!

This is a bad day for humanity!

So a Fn.5 call must be always at the end of code-line....

When I started using Fn.5 call's I had to made an extra subroutine for the 'Fn.5'-call if I wanted to continue my line (in case the line contains an if-statement before). Until I found 'Fn.5' returns 'false', so I could continue with '||' or '|;' ...

Earlier I investigated following returns:

Returns always 'true': set, echo, debug 1-3, debug msg=3, pager on, echo -n > FILE (without ' > nul ' - is not needed anyway as far I tested!) - continue line with '&&' or '&;'
Returns always 'false': Fn.5 (not anymore...), debug 0, debug msg=0, pager off - continue line with '||' or '|;'

BTW 'call Fn.11' has both, so can be used same as 'if', for instance:
'call Fn.11 "%~1" "," && echo %~1 contains a comma ! echo %~1 contains no comma'

I will retest in color-modes!

In this case 'echo -P yyxx' is good, I will change in next version (I normally use directly after the 'Fn.4'-call: 'if %y%<=9 && set y=0%y%' - I will test if your approach is faster).



#12 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 19 October 2022 - 10:24 AM

I have reported the Fn.5 issue as a potential bug, though it may just be a 'feature'.

 

P.S. with the -P:  parameter, not sure what happens if you want to set y to 110 for instance (e.g. 1024x768 we have 128 chars per line) ???



#13 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 21 October 2022 - 09:01 PM

New version of TEXSTAT.G4B: https://github.com/d...ases/tag/v0.6.1

 

Tested on various graphicsmodes, seems to work now.

 

I pimped the [/]COUNT[C]:phrase function to max 48 chars. Also the '/' in /COUNT[C]: is optional now, so whatever one like.

There are provisions to count grub4dos ASCII-codes, like \x25 (see last example on print-screen:

 

TEXTSTAT.G4B v0.6.1 in graphicsmode 0x147.jpg

 

BTW I added [/]MDBASE:startsector if default value of 0x3000 gives problems.

 

About the Fn.5 returns: seen the answer to the issue steve6375 reported: there will be different behavior in console-mode/ graphicsmode.

 

In the end I choosed not to use echo -P yyxx but to return to my old workaround, with a nice variation:

 

call :Fn.5 %h% %v% && echo .....

 

and small sub-routine:

 

:Fn.5
call Fn.5 %~1 %~2
goto :eof

 

BTW 'h' is horizontal, 'v' vertical (instead of 'x' and 'y' or was the 'official' notation 'y' and 'x' ?). Instead of variables numbers can be used too of course. Found no problems with numbers above 99 for 'h'.

 

 



#14 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 22 October 2022 - 08:18 AM

Looks very good! Haven't tested it much yet though.

If you want another project, a grub4dos-based text editor would be really handy so we can quickly edit text files under grub4dos...



#15 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 22 October 2022 - 08:40 AM

P.S. I know main task of textstat is for text file statistics, but it might be useful to have a switch for case sensitivity e.g. /i ?

 

Also, might be useful to return variables such as TSLABELS and TSCOUNT and TSLINES  if /v specified ?

/textstat.g4b /v /textstat.g4b

/textstat.g4b /v COUNT:if /textstat.g4b



#16 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 22 October 2022 - 11:16 AM

What do you mean with 'switch for case sensitivity' ?

 

In case of COUNT there are two options: ["][/]COUNT:phrase["] for no case sensitivity and ["][/]COUNTC:phrase["] for counting WITH case sensitivity ('C' for 'case' - internally 'cat --locate%i%=' and set 'i=i' for no case sensitivity or 'i' not exist for case sensitivity).

 

About exporting TSLABELS etcetera: no problem, all/ (most?) subroutines export variable 'result'. If I make a next version I will work on it.

Also: why should an extra switch needed for this?

 

But I can add switch /Q to get the output variables only. What use you would have for variables like TSLABELS?

 

------------------------------------------------------------------------------

 

I am happy to get your suggestion 'If you want another project, a grub4dos-based text editor would be really handy so we can quickly edit text files under grub4dos...' because I am already working on it for a long time.

When Jaclaz 'initiated' me to grub4dos (on msfn.org) he mentioned a grub4dos text editor too, if I remember well.

 

I started this project in winter 2021, and although I reached version 0.199x it's still unfinished but (more or less) operational.

 

Luckily I didn't publish any version, because I will have to rewrite ALL my Fn.5 call's, or force console mode. But I don't trust my find of the return value of call Fn.5 anymore. :(

 

The size of this script was one of the reasons I made TEXTSTAT.G4B. The COUNT:phrase function I made recently, seems to be quite handy for fast inspection. See print-screen:

 

TEXTSTAT  FATTEXT.G4B + with COUNTC todo Fn.5 call's.jpg



#17 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 22 October 2022 - 01:09 PM

Apologies! I missed the COUNTC switch!

 

The number of variables allowed in grub4dos is limited to about 60. If TEXTSTAT added more variables by default then it will add more variables to the user's environment - this could affect his/her batch files if the variable limit is approached or exceeded. Hence I suggest to add an optional switch so user is aware that extra TS* variables have been added to the environment.

 

Counting labels etc. would be useful for batch file checking. For instance, I could run a batch file which checked all other batch files in my project and warn me if any batch files had too many labels or were getting near to an arbitrary limit I could set - e.g. 100.

 

It would be useful if you could count the lines of code  (i.e. all lines containing text but not comment lines or label lines (I think?)) as 2048 lines of code is a limitation of grub4dos batch files.

One of my batch files has 108 labels and 2876 lines (as counted by TEXTSTAT) or 2877 as counted by NotePad++ and Windows NotePad (last line is blank)

I am not too sure however what counts as a non-code lines (seems to be lines beginning with [whitespace]# or [whitespace]:   where [whitespace] is zero or more space or tab characters???

 

P.S. Just thought of another option!! Add /P which prints each matching source file line + its line number when using COUNT:

This is useful because sometimes a line is OK and sometimes not

For instance  a line may end in a space intentionally  or it may be an excess character. By printing the matching lines we can quickly see if the file needs editing or not

/textstat.g4b /p "COUNT: \x0d" /file.txt

Line 35
set /p Enter a number :           (space at end) - valid
Line 67
echo %fred%                       (space at end) - usually not required
Line 109
map %iso% (0xff)                  (space at end) - not required

attached is a test file with just over 2048 lines of code and some labels and comment lines. Note that when you run it, the last few lines are just not executed with no error reported!

Attached Files



#18 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 22 October 2022 - 03:31 PM

Good suggestions, thanks. I will see what I can do.

 

This is what is changed already, I will add some switch to export the variables if desired. See next print-screen:

 

TEXTSTAT.G4B v0.6.2 preview I.jpg

 

BTW echoing TS-variables for print-screen only

 

 

Only identifying grub4dos code-lines is not going to happen. As I stated earlier TEXTSTAT.G4B is ment as a general tool. That's why I want to count remarks 'REM ', '; ' (beginning of line) and ' REM ' and ' ; ' too (although with restrictions to not count grub4dos operator ' ;; ').

If you are not sure about the definition of grub4dos code-line ;) counting seems useless to me anyway.

 

However: I can add counting 'space' at beginning of line and add variable TSBSPACE.

And: if you are planning a batch for batch-TEXTSTATS, it would be an easy job to do your own counting with 'TEXTSTAT.G4B "[/]COUNT:%EOL%\xASCII-code" ["]FILE["]' and using output TSCOUNT (on your behalf I will add a ready made TSEOL with \x0D\x0A, \x0A or \x0D - unless EOL-markers are 'mixed').

 

What do you mean with '[whitespace] is zero (...)'? I tested, but with one '00' before last line my batch is not running:

 

ZEROS.G4B BAT!-file containing one 00 does not run I.jpg

 

I did a first test of your batch TEST2.G4B, horizontal tab is not counted in TEXTSTAT.G4B. Maybe I should add '# ' to get last '# fred', but earlier I thought ' #' was good enough - apart from the problem of double counting in case of adding '# ':

 

TEXTSTAT.G4B test2.g4b (from steve6375) - space '09' is not counted I.jpg

 

For now I have no ideas how to identify a grub4dos code line, but it would be nice if labels are not counted - max 120 code lines for free :rolleyes:



#19 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 23 October 2022 - 12:56 AM

How does this look like?

 

First print-screen: use of /T-switch and /Q-switch on command-line:

 

TEXTSTAT.G4B v0.6.2 preview II.jpg

 

Next print screen: use of /P-switch on command-line:

 

TEXTSTAT.G4B v0.6.2 preview III.jpg

 

BTW In this new version switches will have to come after FILE because the new switches can be filenames too :unsure:

 

In next print-screen: printing-to-screen of last 8 lines with 'cat ' as found in TEXTSTAT.G4B. For first attempt of the new subroutine :printline take a look at lines 248, 279 (printed two times!), 281 and line 293.

 

TEXTSTAT.G4B v0.6.2 preview V.jpg

 

Same in graphicsmode 0x143, more lines :blink: :

 

TEXTSTAT.G4B v0.6.2 preview VI.jpg

 

EDIT:

 

BTW version not published yet :ph34r:



#20 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 23 October 2022 - 07:40 AM

by [whitespace] zero or more

I mean 0 or more occurrences of any preceding whitespace characters (tabs or spaces)

e.g.
#
#
#
#
#
#

#21 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 23 October 2022 - 08:26 AM

Thanks for explanation! Sorry for the misunderstanding..

#22 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 26 October 2022 - 12:38 PM

I have a strange problem in certain cases while using 'call Fn.11 "%variable%" "\x0A" && some command' if variable contains \x22 (grub4dos ASCII-code for double quote char)

 

I found while testing the COUNT-function of TEXTSTAT.G4B that phrase ' \x22 ' (or '\x20\x22\x20') gave 'true' in a Fn.11-call  while evaluating for \x0A

Strange enough this is not the case for \x22 without spaces or with one space only.  :blink:

 

See first print-screen:

 

TEXTSTAT.G4B v0.7 Example counting Grub4dos operators and double-quote - surrounded bij spaces crashes call Fn.11 I.jpg

 

BTW: End-Of-Line markers are separate evaluated in my script and are split of from the 'phrase' (for certain reasons End-Of-Line markers are only allowed at begin or end of 'phrase'). If \x0A or \x0D are found in the remaining 'phrase', the script will exit.

 

I run some more tests, and it appears that \x00 \x09 \x0A and \x0D give 'true' with variable ' \x22 ' (same for '\x20\x22\x20'), while 'space' (or \x20) is identified correctly. On the other hand: \x22 is NOT identified. :(

 

See next print-screen:

 

Weird Fn.11 problem with excaped x22 overview.jpg

 

Any idea's? I really need help :frusty:



#23 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 26 October 2022 - 04:59 PM

I think it is because  call Fn.11  is first translating \x22 into a double-quote

so the line 
call Fn.11 " \x22" "\x22" && echo YES
becomes
call Fn.11 " "" """ && echo YES

The only way around this that I can think of, would be to convert any string of two characters that are  \x  to maybe @x or $x  - then do the Fn.11 calls and then maybe translate it back again to \x afterwards if needed.

!BAT
set "p= \x22abc"

call :conv
echo %xx%
call Fn.11 "%xx%" "\x0a" && echo FOUND LF
call Fn.11 "%xx%" "ab" && echo FOUND ab
call :convbk
echo %p%

goto :eof

:conv
echo !BAT > (md)0x300+2
echo set xx=%p% >> (md)0x300+2
raw cat --locate=\\x --replace=@x (md)0x300+2 > nul
call (md)0x300+2
goto :eof

:convbk
echo !BAT > (md)0x300+2
echo set p=%xx% >> (md)0x300+2
raw cat --locate=@x --replace=\\x (md)0x300+2 > nul
call (md)0x300+2
goto :eof


#24 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 26 October 2022 - 10:24 PM

Thanks a lot :rolleyes:

 

I tried to avoid use of memory, but it seems I will have to use it.

 

I am going to study your ideas and suggestions.

 

BTW translating \x22 to a double-quote sounds reasonable, but if the result is that call Fn.11 is not working, I am not so sure anymore. :unsure:



#25 deomsh

deomsh

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    Netherlands

Posted 27 October 2022 - 09:36 PM

@steve6375, I have tested your script, works good.

 

Only redirect to memory has certain limitations regarding grub4dos operators inside VARIABLE, but I expect they can be overcome with ''pause --wait=0" to not expand color codes and use pause --wait=0 "%VARIABLE%" > (md).... plus some corrections in the search-length of cat --locate

Sadly there seems no real solution for unequal number of double quote chars (so not \x22 but the 'hard' " ) which would be very, very useful.  :(

 

Please correct me if I am wrong...

 

 ---------------------------------------------------------------------------------------------------------------------------------------

 

During traffic today I did some investigations on my smartphone about the behavior of call Fn.11 and also in combination with echo %@retval% and with read %@retval% too.

 

It seems that call Fn.11 has no 'limit' (like cat --locate) for the length of the 'phrase' searched in %VARIABLE% (so maybe max 511 chars?). I tested up to 72 chars:

 

call Fn.11 test varlen I.png

 

BTW in sixth line before end the initial var-text is simply doubled

 

Trying to read-out a variable containing \x22 with %@retval% on a new line: no results

 

call Fn.11 test bsx22 I.png

 

In cases if two \x22\x22 however the value of %@retval% gave some interesting results:

 

call Fn.11 test bsx22bsx22 + address from @retval & calcd II.png call Fn.11 test bsx22bsx22 + cat --hex of cmd-buffer IIi.png

 

It seems the memory address in %@retval% is some cmd-buffer, quickly overwritten by the cat --hex I used to read-out. But some remains of the Fn.11-call are still visible.

After a calculation with CALCD.G4B (can be done with calc too of course) read %@retval% is showed, giving some information about the FN.11-call. Also a corroboration of what steve6375 said about expanding of \x with ASCII-code.

 

I followed this trail a while, the 32-bits value of read %@retval% seems to include information about searched 'phrase' and the first 'found'. Also space between %VARIABLE% and phrase becomes a zero and last double-quote around "%VARIABLE%" too (if used):

 

Fn.11 x58 info in 32bit @retval not & between double-qoutes II.png

 

The weird behavior of \x22 in the variable and searching for \x00 \x09 \x0A and \x0D has something to do with expansion of \x00 \x09 \x0A and \x0D too. This became more clear to me when \x20 in variable was not found if 'phrase' \x20 was without double-quotes (lines 4-9):

 

Fn.11 x20 in 32bit @retval not & between double-qoutes I.png

 

BTW \x20 in %VARIABLE% without double-quotes does not seem to be affected (not fully fully sure, but normally I use "%VARIABLE%" and "phrase").

 

The behavior of \x20\x22\x20 versus \x20\x22 or \x22\x20 seems to me explained in the variation of the remaining number of double-quotes through expansion and not enough remaining double quotes around \x0A:

 

Fn.11 expansion of x20 x22 x20 and x0A II.png

 

BTW the last line in last print-screen showing \x0A is different if for instance \x0B is searched - not fully clear for me somehow. :blink:

 

Can not show more print-screens because I reached some upload-limit of reboot.pro :dubbio:







Also tagged with one or more of these keywords: grub4dos, scripting

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users