WTOS “include” parameter

  • This topic is empty.
Viewing 6 posts - 16 through 21 (of 21 total)
1 2
  • Author
    Posts
  • December 27, 2007 at 5:18 pm #11161
    wigadore
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    After spending some time on the phone with Wyse I found a few mistakes and now it all works flawless.

    #1 include=$MAC.ini is wrong! the correct syntax is include=$MAC

    #2 the files in the ‘inc’ DO NOT need the .ini extension

    Issue resolved with these two points.

    December 27, 2007 at 8:31 pm #11162
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I cannot repeat it often enough: USE MY CONFGEN TOOL. The pop-up help tells you exactly that!

    Good that you have resolved the issue.

    December 27, 2007 at 10:24 pm #11164
    wigadore
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    If only I knew that before…lol. Your conf tool is great for updating the config and thanks for the support.

    December 28, 2007 at 12:05 am #11165
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Yep, also ConfGEN found this error in the WTOS parameters guide a while back. The guide on this site is up to date as well as the ConfGEN tool. Its also worth checking Confgens web site for the latest version, the link to his site is on the included on the ConfGEN download page,

    Cheers,
    -TT

    January 4, 2008 at 6:35 pm #11232
    dbla
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    Hmm. That’s weird. I’ve been running my devices with the include=$mac.ini for at least a year and my included files do have the .ini extension on them and I’ve not had a single issue. My wyse support guys have never corrected me on this.

    Not saying that is correct or anything, I am thinking that it’s more like the include parameter just takes whatever you give it and resolves the variable if it can. IE. if I put include=$mac.blah, my files would have to be named with the .blah extension and as long as the files are in the /inc folder, they would be properly parsed.

    January 4, 2008 at 8:55 pm #11234
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    dlba,

    you are absolutely right with this. But it looks like there are versions out there that only support non-extension files.
    So, to be 100% sure I recommend to not use any extensions for the include files.

    CG

  • Author
    Posts
Viewing 6 posts - 16 through 21 (of 21 total)
1 2
  • You must be logged in to reply to this topic.