Is # a comment sign for clover configuration file?

[ppdouble]

I download clover 3193. I know that its configration file config.plist is a xml file. I found there is # sign in some xml-markups. e.g.

<key>#DropOEM_DSM</key>
            <dict>
                <key>ATI</key>

Is it a comment? Does DropOEM_DSM works with # sign?

I did not find any information in document. here http://clover-wiki.zetam.org/Home

If it is a comment, what about the html-markup

<!--  some html comment  -->

Is there any document to describe # sign for clover configuration file?

 

[RehabMan]

I download clover 3193. I know that its configration file config.plist is a xml file. I found there is # sign in some xml-markups. e.g.

<key>#DropOEM_DSM</key>
            <dict>
                <key>ATI</key>

Is it a comment? Does DropOEM_DSM works with # sign?

I did not find any information in document. here http://clover-wiki.zetam.org/Home

If it is a comment, what about the html-markup

<!--  some html comment  -->

Is there any document to describe # sign for clover configuration file?

Tecnically, it is not really a comment. It is an unrecognized key. But it is a way to disable a particular setting. Because Clover will not read the value for key "#DropOEM_DSM" changing "DropOEM_DSM" to "#DropOEM_DSM" is an effective way to disable/comment the setting. You could set it to anything that is not recognized... eg "disabled_DropOEM_DSM" or "Disabled,DropOEM_DSM" or "foobar-DropOEM_DSM" or "//DropOEM_DSM" or "ILikeIceCream...DropOEM_DSM".

 

[ppdouble]

Thanks for your reply , RehabMan. Do you have any documents for this?

 

[RehabMan]

Thanks for your reply , RehabMan. Do you have any documents for this?

Most of the valid config.plist keys are documented in the Clover wiki: http://clover-wiki.zetam.org/Home

 

[logic84392]

Just wanted to comment to say this fixed an “End RandomSeed” +++++++... issue for me, since I had commented out a line using standard XML commenting. Specifically, I tried to play with the boot arguments while preserving my known-good arguments:

<key>Arguments</key>
<string>dart=0 -xcpm kext-dev-mode=1</string>
<!-- <string>dart=0 -xcpm nvda_drv=1 kext-dev-mode=1</string> -->

I also violated the “make one change at a time” best practice by upgrading Clover at the same time, so of course I spent 24 hours trying every other possible fix for End RandomSeed before stumbling on my mistake. Just wanted to post this in case it helps someone else one day!

Thanks!!!