Icecast - Sep 2019 - multiple instances?

Hello, unosonic,

======= At 2019-09-09, 04:54:14 you wrote: ======
>wilderzone.radio.2:
>> >What is the use case that you are trying to address? Icecast is
well
>> >suited to running multiple streams in parallel and offers complex
>> >configuration options for many use cases.
>> 
>> Well the "case" or as others would call it "use" 
is that one stream is strictly rock format, the other stream is blues format - I
prefer to keep the 2 as separate streams.
>> 
>> So far, I've not been able to get to see a configuration with more
than one stream configuration. I'm hoping somewhere someone has an example
file that I can examine. (hopefully with some comments in the file to denote
what the heck is going on)
>no need for more than one icecast runnig
>https://icecast.org/docs/icecast-2.4.1/config-file.html#mountsettings
>just create as many mount-sections as you want. 
Again, I need an example that I can read. Not a page full of information
overload that may or may not address the issue at hand.
I do not wish to have to read an encyclopedia to discover out a simple answer.

for example do I have to create an ENTIRELY NEW SECTION in the config file 
(which will probably create a problem in configs if it's referencing the
same section name twice)

There is a LOT of stuff on that page... care to either shave it down to ONE
specific line (or function enabling) or shrug me off to someone who can answer
the question without making it even more confusing?

I should tell you that I've only been successful with this program as it
comes "out of the box" - any other port won't work for the single
working instance (at least it hasn't yet).

Let's drop the "geek speak" and geek attitudes here and try to
speak normal english as I don't speak any other form of english.

= = = = = = = = = = = = = = = = = = = 			

Best regards.				 

Foxxe
wilderzone.radio.2 at gmail.com
  thewilderzone.sytes.net
2019-09-09

wilderzone.radio.2:
> I do not wish to have to read an encyclopedia to discover out a simple
answer.
> Let's drop the "geek speak" and geek attitudes here and try
to speak normal english as I don't speak any other form of english.

you know, it's a nice warm late summer day here where I am, 
polite and friendly people are around, no greater stress to 
be expected. I'm sorry that your situation is such that you 
can't even figure out "a simple answer" yourself. So let me 
try to help you:

Copy this as often as you want into your icecast config file,
(don't forget to change mount-name and password!)

     <mount type="normal">
             <mount-name>/mountpoint1</mount-name>
             <password>password</password>
     </mount>


reload the server, then connect a source to each mountpoint,
then point your player to http://your.server:PORT/mountpoint etc.
Voila!

If you want to have more elaborated features, you may have to read
the manual, unfortunately...

Hello, unosonic,

Well it's 6am here and 15 degrees and my neighbours are uptight people in
the USA... so there is mega stress everywhere I look.
(plus I've been trying to crack this oddball XML code <that no one seems
to support at all>  for a few years without any luck or help up to now).

In the past I've had extremely rude replies mostly from kids "google
it" which of course only leads to 200 plus pages of links to pages that
tell me nothing at all.
So asking for help on the net has become extremely problematic.

I couldn't help but to notice that NO ONE mentions the OTHER XML file, towit
"icecast_run.xml".
NO changes there???


======= At 2019-09-09, 06:23:42 you wrote: ======
>wilderzone.radio.2:
>
>> I do not wish to have to read an encyclopedia to discover out a simple
answer.
>> Let's drop the "geek speak" and geek attitudes here and
try to speak normal english as I don't speak any other form of english.
>
>
>you know, it's a nice warm late summer day here where I am, 
>polite and friendly people are around, no greater stress to 
>be expected. I'm sorry that your situation is such that you 
>can't even figure out "a simple answer" yourself. So let me 
>try to help you:
>
>Copy this as often as you want into your icecast config file,
>(don't forget to change mount-name and password!)
>
>     <mount type="normal">
>             <mount-name>/mountpoint1</mount-name>
>             <password>password</password>
>     </mount>
>
>
>reload the server, then connect a source to each mountpoint,
>then point your player to http://your.server:PORT/mountpoint etc.
>Voila!
>
>If you want to have more elaborated features, you may have to read
>the manual, unfortunately...
>
>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast
= = = = = = = = = = = = = = = = = = = 			

Best regards.				 

Foxxe
wilderzone.radio.2 at gmail.com
  thewilderzone.sytes.net
wilderzone.radio.2 at gmail.com
(226) 961-5150
2019-09-09

Hello, unosonic,

nope.... I got nothing. All I get is error code 200 or 10061 in Sam's
encoder window.

(I'm using it because it gives me some sort of error code feedback unlike
winamp's DNAS)

btw, what's up with the oddball ascii arrows in the XML files?  (IE  
<!-- and --> )

======= At 2019-09-09, 06:23:42 you wrote: ======
>wilderzone.radio.2:
>
>> I do not wish to have to read an encyclopedia to discover out a simple
answer.
>> Let's drop the "geek speak" and geek attitudes here and
try to speak normal english as I don't speak any other form of english.
>
>
>you know, it's a nice warm late summer day here where I am, 
>polite and friendly people are around, no greater stress to 
>be expected. I'm sorry that your situation is such that you 
>can't even figure out "a simple answer" yourself. So let me 
>try to help you:
>
>Copy this as often as you want into your icecast config file,
>(don't forget to change mount-name and password!)
>
>     <mount type="normal">
>             <mount-name>/mountpoint1</mount-name>
>             <password>password</password>
>     </mount>
>
>
>reload the server, then connect a source to each mountpoint,
>then point your player to http://your.server:PORT/mountpoint etc.
>Voila!
>
>If you want to have more elaborated features, you may have to read
>the manual, unfortunately...
>
>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast
= = = = = = = = = = = = = = = = = = = 			

Best regards.				 

Foxxe
wilderzone.radio.2 at gmail.com
  thewilderzone.sytes.net
wilderzone.radio.2 at gmail.com
(226) 961-5150
2019-09-09

Hello, unosonic,

Okay, we'll do it this way as it appears to be the only sane way...

THIS is the xml config file that I've been using for ONE STREAM ONLY.
No more than one stream nor any other port on that single stream, for that
matter, has ever worked to date.

There also seems to be alot of clutter but as I've NEVER had to use these
oddball format files before (in any of my 30 plus years in computers),
I can't tell what is a working line and what is just geek-babble.


<icecast>
  <!-- This is the hostname other people will use to connect to your server.
         It affects mainly the urls generated by Icecast for playlists and yp
         listings. You MUST configure it properly for YP listings to work!
    -->
    <hostname>thewilderzone.sytes.net</hostname>
  
    <!-- location and admin are two arbitrary strings that are e.g. visible
         on the server info page of the icecast web interface
         (server_version.xsl). -->
    <location>Sol III</location>
    <admin>icemaster at localhost</admin>
  
    <!-- You may have multiple <listener> elements -->
    <listen-socket>
        <port>8000</port>
        <!-- <bind-address>127.0.0.1</bind-address> -->
        <!-- <shoutcast-mount>/rock</shoutcast-mount> -->
    </listen-socket>
    

    <!-- IMPORTANT!
         Especially for inexperienced users:
         Start out by ONLY changing all passwords and restarting Icecast.
         For detailed setup instructions please refer to the documentation.
         It's also available here: http://icecast.org/docs/
    -->

    <limits>
        <clients>100</clients>
        <sources>2</sources>
        <queue-size>524288</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>10</source-timeout>
        <!-- If enabled, this will provide a burst of data when a client 
             first connects, thereby significantly reducing the startup 
             time for listeners that do substantial buffering. However,
             it also significantly increases latency between the source
             client and listening client.  For low-latency setups, you
             might want to disable this. -->
        <burst-on-connect>1</burst-on-connect>
        <!-- same as burst-on-connect, but this allows for being more
             specific on how much to burst. Most people won't need to
             change from the default 64k. Applies to all mountpoints  -->
        <burst-size>65535</burst-size>
    </limits>

    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>bitchy1</source-password>
        <!-- Relays log in with username 'relay' -->
        <relay-password>bitchy1</relay-password>

        <!-- Admin logs in with the username given below -->
        <admin-user>admin</admin-user>
        <admin-password>bitchy1</admin-password>
    </authentication>

    <!-- set the mountpoint for a shoutcast source to use, the default if not
         specified is /stream but you can change it here if an alternative is
         wanted or an extension is required
    <shoutcast-mount>/live.nsv</shoutcast-mount>
    -->

    <!-- Uncomment this if you want directory listings -->
    <!--
    <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
    </directory>
    -->

    
    <!--
    <listen-socket>
        <port>8080</port>
    </listen-socket>
    -->
    <!--
    <listen-socket>
        <port>8443</port>
        <ssl>1</ssl>
    </listen-socket>
    -->


    <!-- Global header settings 
         Headers defined here will be returned for every HTTP request to
Icecast.

         The ACAO header makes Icecast public content/API by default
         This will make streams easier embeddable (some HTML5 functionality
needs it).
         Also it allows direct access to e.g. /status-json.xsl from other sites.
         If you don't want this, comment out the following line or read up
on CORS.
    -->
    <http-headers>
        <header name="Access-Control-Allow-Origin"
value="*" />
    </http-headers>


    <!-- Relaying
         You don't need this if you only have one server.
         Please refer to the config for a detailed explanation.
    -->
    <!--<master-server>127.0.0.1</master-server>-->
    <!--<master-server-port>8001</master-server-port>-->
   
<!--<master-update-interval>120</master-update-interval>-->
    <!--<master-password>hackme</master-password>-->

    <!-- setting this makes all relays on-demand unless overridden, this is
         useful for master relays which do not have <relay> definitions
here.
         The default is 0 -->
    <!--<relays-on-demand>1</relays-on-demand>-->

    <!--
    <relay>
        <server>127.0.0.1</server>
        <port>8080</port>
        <mount>/example.ogg</mount>
        <local-mount>/different.ogg</local-mount>
        <on-demand>0</on-demand>

        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>
    -->


    <!-- Mountpoints
         Only define <mount> sections if you want to use advanced options,
         like alternative usernames or passwords
    -->

    <!-- Default settings for all mounts that don't have a specific
<mount type="normal">.
    -->
    <!-- 
    <mount type="default">
        <public>0</public>
        <intro>/server-wide-intro.ogg</intro>
        <max-listener-duration>3600</max-listener-duration>
        <authentication type="url">
                <option name="mount_add"
value="http://auth.example.org/stream_start.php"/>
        </authentication>
        <http-headers>
                <header name="foo" value="bar" />
        </http-headers>
    </mount>
    -->

    <!-- Normal mounts -->
    <!--

    <mount type="normal">
        <mount-name>/example-complex.ogg</mount-name>

        <username>othersource</username>
        <password>hackmemore</password>

        <max-listeners>1</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/example2.ogg</fallback-mount>
        <fallback-override>1</fallback-override>
        <fallback-when-full>1</fallback-when-full>
        <intro>/example_intro.ogg</intro>
        <hidden>1</hidden>
        <public>1</public>
        <authentication type="htpasswd">
                <option name="filename"
value="myauth"/>
                <option name="allow_duplicate_users"
value="0"/>
        </authentication>
        <http-headers>
                <header name="Access-Control-Allow-Origin"
value="http://webplayer.example.org" />
                <header name="baz" value="quux" />
        </http-headers>
    </mount>
    -->

    <!--
    <mount type="normal">
        <mount-name>/auth_example.ogg</mount-name>
        <authentication type="url">
            <option name="mount_add"      
value="http://myauthserver.net/notify_mount.php"/>
            <option name="mount_remove"   
value="http://myauthserver.net/notify_mount.php"/>
            <option name="listener_add"   
value="http://myauthserver.net/notify_listener.php"/>
            <option name="listener_remove"
value="http://myauthserver.net/notify_listener.php"/>
            <option name="headers"        
value="x-pragma,x-token"/>
            <option name="header_prefix"  
value="ClientHeader."/>
        </authentication>
    </mount>
    -->

    <fileserve>1</fileserve>

    <paths>
        <logdir>./log</logdir>
        <webroot>./web</webroot>
        <adminroot>./admin</adminroot>

        <!-- Aliases: treat requests for 'source' path as being for
'dest' path
             May be made specific to a port or bound address using the
"port"
             and "bind-address" attributes.
          -->
        <!--
        <alias source="/foo" destination="/bar"/>
        -->
        <!-- Aliases: can also be used for simple redirections as well,
             this example will redirect all requests for http://server:port/ to
             the status page
        -->
        <alias source="/" destination="/status.xsl"/>
        <!-- The certificate file needs to contain both public and private
part.
             Both should be PEM encoded.
        <ssl-certificate>./icecast.pem</ssl-certificate>
        -->
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
        <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1
Error -->
        <logsize>10000</logsize> <!-- Max size of a logfile
-->
        <!-- If logarchive is enabled (1), then when logsize is reached
             the logfile will be moved to [error|access|playlist].log.DATESTAMP,
             otherwise it will be moved to [error|access|playlist].log.old.
             Default is non-archive mode (i.e. overwrite)
        -->
        <!-- <logarchive>1</logarchive> -->
    </logging>
</icecast>



= = = = = = = = = = = = = = = = = = = 			

Best regards.				 

Foxxe
wilderzone.radio.2 at gmail.com
  thewilderzone.sytes.net
2019-09-09

wilderzone.radio.2:
> Hello, unosonic,
> 
> Okay, we'll do it this way as it appears to be the only sane way...
> THIS is the xml config file that I've been using for ONE STREAM ONLY.

but it's not the config file you're using actually at your site.
can't find any mountpoint called /rock ...
there must be another one...

Hi,

On 9/9/19 11:35 AM, wilderzone.radio.2 wrote:
> Hello, unosonic,
>
> Okay, we'll do it this way as it appears to be the only sane way...
>
> THIS is the xml config file that I've been using for ONE STREAM ONLY.
> No more than one stream nor any other port on that single stream, for that
matter, has ever worked to date.
>
> There also seems to be alot of clutter but as I've NEVER had to use
these oddball format files before (in any of my 30 plus years in computers),

XML is not really a very human friendly format, despite being
"readable". Unfortunately this is what was chosen for the Icecast
configuration. Also I have yet to see a configuration file format that
satisfies "human readable", "easy", "allows defining
complex use cases".

> I can't tell what is a working line and what is just geek-babble.

I'd strongly recommend installing notepad++ for editing the file. It's a
simple but very helpful editor. It will give you color hilighting for
the sections. That makes it easy to see which parts will be ignored
(instead of looking for <!-- --> bracketing manually)


> <icecast>
>   <!-- This is the hostname other people will use to connect to your
server.
>          It affects mainly the urls generated by Icecast for playlists and
yp
>          listings. You MUST configure it properly for YP listings to work!
>     -->
>     <hostname>thewilderzone.sytes.net</hostname>
>   
>     <!-- location and admin are two arbitrary strings that are e.g.
visible
>          on the server info page of the icecast web interface
>          (server_version.xsl). -->
>     <location>Sol III</location>
>     <admin>icemaster at localhost</admin>
>   
>     <!-- You may have multiple <listener> elements -->
>     <listen-socket>
>         <port>8000</port>
>         <!-- <bind-address>127.0.0.1</bind-address> -->
>         <!-- <shoutcast-mount>/rock</shoutcast-mount> -->
>     </listen-socket>
>     
>
>     <!-- IMPORTANT!
>          Especially for inexperienced users:
>          Start out by ONLY changing all passwords and restarting Icecast.
>          For detailed setup instructions please refer to the documentation.
>          It's also available here: http://icecast.org/docs/
>     -->
>
>     <limits>
>         <clients>100</clients>
>         <sources>2</sources>

Beware, you are limiting the Icecast server to TWO active mountpoints.
If you try a third connection it will fail.

>         <queue-size>524288</queue-size>
>         <client-timeout>30</client-timeout>
>         <header-timeout>15</header-timeout>
>         <source-timeout>10</source-timeout>
>         <!-- If enabled, this will provide a burst of data when a client
>              first connects, thereby significantly reducing the startup 
>              time for listeners that do substantial buffering. However,
>              it also significantly increases latency between the source
>              client and listening client.  For low-latency setups, you
>              might want to disable this. -->
>         <burst-on-connect>1</burst-on-connect>
>         <!-- same as burst-on-connect, but this allows for being more
>              specific on how much to burst. Most people won't need to
>              change from the default 64k. Applies to all mountpoints 
-->
>         <burst-size>65535</burst-size>
>     </limits>
>
>     <authentication>
>         <!-- Sources log in with username 'source' -->
>         <source-password>bitchy1</source-password>
>         <!-- Relays log in with username 'relay' -->
>         <relay-password>bitchy1</relay-password>
>
>         <!-- Admin logs in with the username given below -->
>         <admin-user>admin</admin-user>
>         <admin-password>bitchy1</admin-password>
>     </authentication>

I hope that's not your real password. In case it is, please change it.

>     <!-- set the mountpoint for a shoutcast source to use, the default
if not
>          specified is /stream but you can change it here if an alternative
is
>          wanted or an extension is required
>     <shoutcast-mount>/live.nsv</shoutcast-mount>
>     -->
>
>     <!-- Uncomment this if you want directory listings -->
>     <!--
>     <directory>
>         <yp-url-timeout>15</yp-url-timeout>
>         <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
>     </directory>
>     -->
>
>     
>     <!--
>     <listen-socket>
>         <port>8080</port>
>     </listen-socket>
>     -->
>     <!--
>     <listen-socket>
>         <port>8443</port>
>         <ssl>1</ssl>
>     </listen-socket>
>     -->
>
>
>     <!-- Global header settings 
>          Headers defined here will be returned for every HTTP request to
Icecast.
>
>          The ACAO header makes Icecast public content/API by default
>          This will make streams easier embeddable (some HTML5 functionality
needs it).
>          Also it allows direct access to e.g. /status-json.xsl from other
sites.
>          If you don't want this, comment out the following line or read
up on CORS.
>     -->
>     <http-headers>
>         <header name="Access-Control-Allow-Origin"
value="*" />
>     </http-headers>
>
>
>     <!-- Relaying
>          You don't need this if you only have one server.
>          Please refer to the config for a detailed explanation.
>     -->
>     <!--<master-server>127.0.0.1</master-server>-->
>     <!--<master-server-port>8001</master-server-port>-->
>    
<!--<master-update-interval>120</master-update-interval>-->
>     <!--<master-password>hackme</master-password>-->
>
>     <!-- setting this makes all relays on-demand unless overridden, this
is
>          useful for master relays which do not have <relay>
definitions here.
>          The default is 0 -->
>     <!--<relays-on-demand>1</relays-on-demand>-->
>
>     <!--
>     <relay>
>         <server>127.0.0.1</server>
>         <port>8080</port>
>         <mount>/example.ogg</mount>
>         <local-mount>/different.ogg</local-mount>
>         <on-demand>0</on-demand>
>
>         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     </relay>
>     -->
>
>
>     <!-- Mountpoints
>          Only define <mount> sections if you want to use advanced
options,
>          like alternative usernames or passwords
>     -->
>
>     <!-- Default settings for all mounts that don't have a specific
<mount type="normal">.
>     -->
>     <!-- 
>     <mount type="default">
>         <public>0</public>
>         <intro>/server-wide-intro.ogg</intro>
>         <max-listener-duration>3600</max-listener-duration>
>         <authentication type="url">
>                 <option name="mount_add"
value="http://auth.example.org/stream_start.php"/>
>         </authentication>
>         <http-headers>
>                 <header name="foo" value="bar" />
>         </http-headers>
>     </mount>
>     -->
>
>     <!-- Normal mounts -->
>     <!--
>
>     <mount type="normal">
>         <mount-name>/example-complex.ogg</mount-name>
>
>         <username>othersource</username>
>         <password>hackmemore</password>
>
>         <max-listeners>1</max-listeners>
>         <dump-file>/tmp/dump-example1.ogg</dump-file>
>         <burst-size>65536</burst-size>
>         <fallback-mount>/example2.ogg</fallback-mount>
>         <fallback-override>1</fallback-override>
>         <fallback-when-full>1</fallback-when-full>
>         <intro>/example_intro.ogg</intro>
>         <hidden>1</hidden>
>         <public>1</public>
>         <authentication type="htpasswd">
>                 <option name="filename"
value="myauth"/>
>                 <option name="allow_duplicate_users"
value="0"/>
>         </authentication>
>         <http-headers>
>                 <header name="Access-Control-Allow-Origin"
value="http://webplayer.example.org" />
>                 <header name="baz" value="quux"
/>
>         </http-headers>
>     </mount>
>     -->
>
>     <!--
>     <mount type="normal">
>         <mount-name>/auth_example.ogg</mount-name>
>         <authentication type="url">
>             <option name="mount_add"      
value="http://myauthserver.net/notify_mount.php"/>
>             <option name="mount_remove"   
value="http://myauthserver.net/notify_mount.php"/>
>             <option name="listener_add"   
value="http://myauthserver.net/notify_listener.php"/>
>             <option name="listener_remove"
value="http://myauthserver.net/notify_listener.php"/>
>             <option name="headers"        
value="x-pragma,x-token"/>
>             <option name="header_prefix"  
value="ClientHeader."/>
>         </authentication>
>     </mount>
>     -->
>
>     <fileserve>1</fileserve>
>
>     <paths>
>         <logdir>./log</logdir>
>         <webroot>./web</webroot>
>         <adminroot>./admin</adminroot>
>
>         <!-- Aliases: treat requests for 'source' path as being
for 'dest' path
>              May be made specific to a port or bound address using the
"port"
>              and "bind-address" attributes.
>           -->
>         <!--
>         <alias source="/foo" destination="/bar"/>
>         -->
>         <!-- Aliases: can also be used for simple redirections as well,
>              this example will redirect all requests for
http://server:port/ to
>              the status page
>         -->
>         <alias source="/"
destination="/status.xsl"/>
>         <!-- The certificate file needs to contain both public and
private part.
>              Both should be PEM encoded.
>         <ssl-certificate>./icecast.pem</ssl-certificate>
>         -->
>     </paths>
>
>     <logging>
>         <accesslog>access.log</accesslog>
>         <errorlog>error.log</errorlog>
>         <!-- <playlistlog>playlist.log</playlistlog> -->
>         <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn,
1 Error -->
>         <logsize>10000</logsize> <!-- Max size of a logfile
-->
>         <!-- If logarchive is enabled (1), then when logsize is reached
>              the logfile will be moved to
[error|access|playlist].log.DATESTAMP,
>              otherwise it will be moved to [error|access|playlist].log.old.
>              Default is non-archive mode (i.e. overwrite)
>         -->
>         <!-- <logarchive>1</logarchive> -->
>     </logging>
> </icecast>
>
As already pointed out by Unosonic, there is currently no defined
<mount>. Connecting using the source-password will make it appear on the
fly, but there are no special settings applied.

You can create mountpoints by adding the earlier mentioned sections. The
only important thing is that this must be outside of sections enclosed
by <!-- -->.


Cheers,


TBR

Hello, Thomas_B._Rücker,



======= At 2019-09-09, 08:34:05 you wrote: ======
>>
>>     <limits>
>>         <clients>100</clients>
>>         <sources>2</sources>
>
>
>Beware, you are limiting the Icecast server to TWO active mountpoints.
>If you try a third connection it will fail.
At this point, I'd be happy with the 2nd one working, then I can worry about
any limitations.
>
>I hope that's not your real password. In case it is, please change it.
>
of course not, but over this entire ordeal it's been a nickname people have
given me after I tell them that their "google it" answers are f**king
useless)
>
>
>As already pointed out by Unosonic, there is currently no defined
><mount>. Connecting using the source-password will make it appear on
the
>fly, but there are no special settings applied.
Yeah he was EXTREMELY VAGUE about that comment. I have yet to suss out just what
the heck he meant by it.
>You can create mountpoints by adding the earlier mentioned sections. The
>only important thing is that this must be outside of sections enclosed
>by <!-- -->.
Also, in regards to Notepad++, I've got it but it's extremely useless to
me.
I got it for a function that it was alleged to have but I never found that
function and "words in pretty colours" don't mean anything at all
unless you have an idea of what those colours are supposed to denote.


= = = = = = = = = = = = = = = = = = = 			

Best regards.				 

Foxxe
wilderzone.radio.2 at gmail.com
  thewilderzone.sytes.net
wilderzone.radio.2 at gmail.com
(226) 961-5150
2019-09-09