I am writing out some more things I wanted to fix
Three new folders will be made in MODWIN to allow custom user files, apps, and packages
hates the get admin code and is weird in getting the modwin batch to just work as an executable so I had to add code to have it push the batch file in the build for QoL Options --- will explain in OP
move modwin.bat "C:\MODWIN"
move oscdimg.exe "C:\MODWIN"
So since we will be turning the executable into an installer the build code was removed from the modwin batch and just turned into its own thing to be called upon as soon as you run the exe
This answer showed
me "-packagePath:" the part I was missing to get the add code working
So now we can add apps easier -- will be explained
This link showed me
that we can reuse the code above for PACKAGES and replace -Add-ProvisionedAppxPackage with: AddPackage
Now able to enable features:
Trying to find a specimen to test the package code on led me to this video
Which led me to this link to get cabinet file updates
I am getting an error. this link suggest angle bracket
which did not fix the issue
The command shows that the code is right and if you only specify a folder name you could push all files. but DISM is not working as intended
So if the tool worked right we would be able to push the whole folder at once with just this code
Diving deeper into the mystery
DISM Driver Servicing (.inf) Command-Line Options
Well I have about given up on dism as far as adding packages.
Seeing if https://wimlib.net/
has a solution in their binaries and no they dont
Maybe I can find an old DISM or an old pkgmgr that wont be rude!
well I got it to stop erroring i am unsure if it is actually working, as I don't have a Real use case for these cab files so would need someone to test
that is the code to push any user add files or folders in the USER folder to the WIM
Add the ability for MODWIN to detect if the install file is a wim or esd so we can trigger that for the user
Make the executable pretty with a picture.