Adding a Folder to the Desktop
- Thread starter CraigR
- Start date
C
Clanger
Guest
CraigR Easiest way is with $OEM$.
This will go to all user accounts as they are created.
Source\$OEM$\$1 is the root of the drive.
Source\$OEM$\$$ is the Windows folder.
The benefit of using $OEM$ is that you dont have to extract an iso mount etc. Its much easier to make changes, add newer versions of things and add new stuff incrementally.
Code:
Source\$OEM$\$1\Users\Public\DesktopSource\$OEM$\$1 is the root of the drive.
Source\$OEM$\$$ is the Windows folder.
The benefit of using $OEM$ is that you dont have to extract an iso mount etc. Its much easier to make changes, add newer versions of things and add new stuff incrementally.
Last edited by a moderator:
C
Clanger
Guest
Other $OEM$ folder that you might find useful.
Source\$OEM$\$$\Web\Wallpaper\Windows for wallpapers
Source\$OEM$\$$\Resources\Themes for themes
Source\$OEM$\$1\Program Files (x86) portable programs
Source\$OEM$\$1\Program Files portable programs.
I use $OEM$ on every install i do.
Source\$OEM$\$$\Web\Wallpaper\Windows for wallpapers
Source\$OEM$\$$\Resources\Themes for themes
Source\$OEM$\$1\Program Files (x86) portable programs
Source\$OEM$\$1\Program Files portable programs.
I use $OEM$ on every install i do.
crypticus
Well-Known Member
- Messages
- 1,664
- Reaction score
- 461
1) Use 7-Zip
Open Install.wim via 7zip, Place your files to here; Users\Public\Desktop\
Then create your iso with NTLite
2) Use NTLite
Mount Image, Right Click To Mounted Image, Click Explore Mounted Content. Place your files to here; Users\Public\Desktop\
Save changes and then create your iso with NTLite
3) OEM Folder
Make folder changes as explained ^
Then create your iso with NTLite Or add your oem folder to already burned USB
Open Install.wim via 7zip, Place your files to here; Users\Public\Desktop\
Then create your iso with NTLite
2) Use NTLite
Mount Image, Right Click To Mounted Image, Click Explore Mounted Content. Place your files to here; Users\Public\Desktop\
Save changes and then create your iso with NTLite
3) OEM Folder
Make folder changes as explained ^
Then create your iso with NTLite Or add your oem folder to already burned USB
Last edited:
I know that I am reviving an old thread, but I can't figure out how to use "Source\$OEM$\$1".
Where do I enter that so that I can get a file on the root of a drive? The primary goal is to get a file on the desktop of a user created when the ISO is used, but just figuring out where the line and variable would/should be a huge help.
Where do I enter that so that I can get a file on the root of a drive? The primary goal is to get a file on the desktop of a user created when the ISO is used, but just figuring out where the line and variable would/should be a huge help.
Last edited:
Is it possible to copy files to certain directories?
btw it's "\sources" not "\source".
btw it's "\sources" not "\source".
garlin good catch. However, that link speaks of adding $OEM$ to the Sources folder "...in the extracted ISO's directory". With my 8 hours experience with NTLite, I am not sure what that is. So, I loaded the Win10 Pro 'Install.wim' and hit 'Explore mount directory'. There is no Sources folder.
I then loaded the boot.wim and both the PE and Setup have a Sources directory. I added "$OEM$\$1" folder structure inside the 'Setup' Sources directory and placed my file in there, applied it, and expected to see that file at the root of C:. No good. What am I missing?
I then loaded the boot.wim and both the PE and Setup have a Sources directory. I added "$OEM$\$1" folder structure inside the 'Setup' Sources directory and placed my file in there, applied it, and expected to see that file at the root of C:. No good. What am I missing?
NTLite's original method of working with an ISO, was expecting you to first extract its file content (using 7-Zip or whatever) to a local folder.
This was referred to as the "ISO folder". When added, NTLite would recognize the folder layout and automatically create a "sources" folder whenever Post-Setup files are staged. If you loaded an image file by itself, without the context of a parent ISO folder, NTLite considers that an "isolated image". Isolated images can never have Post-Setup files, because they're not part of an ISO folder.
Later on, NTLite allowed you to load a raw ISO file and have it automatically extract the contents by itself into a private cache folder. NTLite controls this cache folder, and you're not supposed to manually pick at the files.
boot.wim's internal folder layout does include a \sources folder, but that only exists in RAM disk when WinPE is loaded. The install media has a separate \sources folder because it's the ISO written to disk.
This was referred to as the "ISO folder". When added, NTLite would recognize the folder layout and automatically create a "sources" folder whenever Post-Setup files are staged. If you loaded an image file by itself, without the context of a parent ISO folder, NTLite considers that an "isolated image". Isolated images can never have Post-Setup files, because they're not part of an ISO folder.
Later on, NTLite allowed you to load a raw ISO file and have it automatically extract the contents by itself into a private cache folder. NTLite controls this cache folder, and you're not supposed to manually pick at the files.
boot.wim's internal folder layout does include a \sources folder, but that only exists in RAM disk when WinPE is loaded. The install media has a separate \sources folder because it's the ISO written to disk.
When you ask NTLite to create a new ISO, from an extracted folder distribution, it should sweep everything underneath including the sources folder. If you don't see as part of the finished ISO, then you're probably in the wrong root folder.
Also, you're using an USB device right? Not some wacky network install...
Also, you're using an USB device right? Not some wacky network install...
No wacky install. This is all on my laptop.
1. Get OEM ISO.
2. Use NTLite to do many things, culminating in the creation of a custom, silent installing ISO.
3. Use VirtualBox to test the result.
When the other thread states "$OEM$ folder is something you can create in the extracted ISO's directory.", where do I see that? How do I get to the 'extracted ISO's directory'?
1. Get OEM ISO.
2. Use NTLite to do many things, culminating in the creation of a custom, silent installing ISO.
3. Use VirtualBox to test the result.
When the other thread states "$OEM$ folder is something you can create in the extracted ISO's directory.", where do I see that? How do I get to the 'extracted ISO's directory'?
Don't overthink this.
1. Get OEM ISO.
2. Use 7-Zip to extract ISO to \My_ISO_Folder
3. Use NTLite to load Image Folder from \My_ISO_Folder. Do many things.
4. "mkdir \My_ISO_Folder\sources\$OEM$\$1\Destination"
5. Ask NTLite to create ISO from your Image Folder project, or click the Create ISO button during the Apply.
6. Profit!
1. Get OEM ISO.
2. Use 7-Zip to extract ISO to \My_ISO_Folder
3. Use NTLite to load Image Folder from \My_ISO_Folder. Do many things.
4. "mkdir \My_ISO_Folder\sources\$OEM$\$1\Destination"
5. Ask NTLite to create ISO from your Image Folder project, or click the Create ISO button during the Apply.
6. Profit!
Extract (unzip) the ISO before loading into NTLite? An interesting additional step.
So I now have;
1. Get OEM ISO.
2. Extract ISO (7-zip).
3. 'Add' the folder containing the extracted files into NTLite (Add>Image directory>My_ISO_Folder).
4. 'Load' the desired edition of Win10 (in this case).
5. Do the many things, including run "mkdir \My_ISO_Folder\sources\$OEM$\$1\Destination". Is this run as just a command in Post-Setup>User?
6. Ask NTLite to create an ISO.
I think that it is really the where/how do I run that command that I think that I am missing at this point. Once I can get a test file to appear in the root of C: (mkdir \My_ISO_Folder\sources\$OEM$\$1\test.txt), I know that I have put that script/command in the right location and should be able to subsequently work the path to the actual location.
So I now have;
1. Get OEM ISO.
2. Extract ISO (7-zip).
3. 'Add' the folder containing the extracted files into NTLite (Add>Image directory>My_ISO_Folder).
4. 'Load' the desired edition of Win10 (in this case).
5. Do the many things, including run "mkdir \My_ISO_Folder\sources\$OEM$\$1\Destination". Is this run as just a command in Post-Setup>User?
6. Ask NTLite to create an ISO.
I think that it is really the where/how do I run that command that I think that I am missing at this point. Once I can get a test file to appear in the root of C: (mkdir \My_ISO_Folder\sources\$OEM$\$1\test.txt), I know that I have put that script/command in the right location and should be able to subsequently work the path to the actual location.
What's the part that's confusing? The extracted ISO folder is just a normal set of folders & files.
You can use Explorer to create new subfolders, or use CMD since the mkdir command creates a long folder path in one go. This step is done outside of NTLite.
You can use Explorer to create new subfolders, or use CMD since the mkdir command creates a long folder path in one go. This step is done outside of NTLite.
Except NTLite puts everything in a private cache folder, not one of your own. If you extract it, you know where everything lives.
I'm not saying you can't have NTLite manage your ISO, but if you're going to do a lot of $OEM$ work, do it the old fashioned way. Not because I haven't learned the new way, but honestly it's faster and easier to give instructions.
OK, got it working. Thank you garlin for pressing forward with this.
Here is what the issue was;
<tldr>
You have to manually extract (7-zip) the OEM ISO to a folder on your desktop/laptop before 'Adding' the OS files to NTLite (Add>Image directory, not Add>Image (ISO, WIM, ESD, SWM)) so that the correct 'sources' folder is available/exposed.
</tldr>
Although NTLite will ingest the raw (compressed) OEM ISO and do all the things, only by manually extracting the OEM ISO first, will you expose the needed 'sources' folder that the other threads reference.
To add to the confusion, the two folders under "Boot/Setup" in the NTLite interface each have a 'sources' folder (only visible in NTLite), but those will not work for this activity.
Once the correct 'sources' folder is available, you can then start creating the $OEM$\$1\<more folders here> folder structure to meet your needs.
Here is what the issue was;
<tldr>
You have to manually extract (7-zip) the OEM ISO to a folder on your desktop/laptop before 'Adding' the OS files to NTLite (Add>Image directory, not Add>Image (ISO, WIM, ESD, SWM)) so that the correct 'sources' folder is available/exposed.
</tldr>
Although NTLite will ingest the raw (compressed) OEM ISO and do all the things, only by manually extracting the OEM ISO first, will you expose the needed 'sources' folder that the other threads reference.
To add to the confusion, the two folders under "Boot/Setup" in the NTLite interface each have a 'sources' folder (only visible in NTLite), but those will not work for this activity.
Once the correct 'sources' folder is available, you can then start creating the $OEM$\$1\<more folders here> folder structure to meet your needs.