Question about $1 and $$

Discussion in 'Windows 7' started by RobertX, Sep 23, 2022.

  1. RobertX

    RobertX MDL Senior Member

    Dec 6, 2014
    279
    35
    10
    I have a question about $$ and $1 and other related directories under $OEM$.

    Would I summon $1 and $$ depending on different tasks, say pre-activation and integrating updates. Is it a means to organise them?
     
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    #2 mxman2k, Sep 23, 2022
    Last edited: Sep 23, 2022
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. RobertX

    RobertX MDL Senior Member

    Dec 6, 2014
    279
    35
    10
    Thanks, I'll have a read.

    By the way, is there something else that I should read about Windows scripting before I proceed with more scripts? A course maybe?
     
  4. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    I am no professional by any means but i dived in at the deep end when i took over the MRP project here on MDL in 2016, took me a few attempts to get new bits added and fix old errors but i still can have bad days when things just not go to plan! (a good job not many see my f ups :D:D)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. RobertX

    RobertX MDL Senior Member

    Dec 6, 2014
    279
    35
    10
    From what I understand, $$ and $1 call up different directories.

    Is that right?

    EDIT: No, I read too fast. Will read it later.

    Thanks anyways!
     
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    yes , $1 refers to the root of the drive example C:\
    $$ refers to the Windows directory so anything placed there will be put in the Windows folder of the installation during the setup phase.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. RobertX

    RobertX MDL Senior Member

    Dec 6, 2014
    279
    35
    10
    Cool.

    But if $1 refers to Drive C and can refer to the Windows directory itself, why even have one that goes directly to the Windows directory, why have $$?
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,602
    107,777
    450
    Because the scripts folder put in "c:\windows\setup\" by "ISO:\Sources\$OEM$\$$\Setup\" is automatically checked by windows for scripts to run at OOBE.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. RobertX

    RobertX MDL Senior Member

    Dec 6, 2014
    279
    35
    10
    So it's mandatory to use that or they won't be recognised in OOBE.
     
  11. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    Yes, unless you use a unattended xml which can point to another folder (mentioned in the msdn website i linked to regarding $OEM$), but then it gets complicated, easier to use the mechanism via $OEM$\xx to do what you wish.

    As @Enthousiast mentioned that the windows setup looks for specific folders and files to perform certain actions etc so using stuff outside of the $oem$ method can get messy and complex to keep a eye on what is doing what more so for a beginner.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,602
    107,777
    450
    :eek:;):D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,534
    21,765
    210
    With windows 8.x and above that uses a MSDM for its 'key' activation via the bios tables, windows setup will ignore the oobe.cmd /early stages completely unless you use a ei.cfg or PID.txt in the sources folder to tell setup to ignore the MSDM key.

    Nothing is simple as the XP days now :D once you master the hurdles you can pretty much get setup to do your bidding :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...