|====| NTLite Research Presets & Custom Scripts

|====|

Active Member
But that doesnt tell us anything useful like which components you have kept/not kept, it just tells us how many.
It doesnt give us the actual installation size either, nothing at all of any use.
i will share extra component packages removal script very shortly with nuhi . i do it after OS installation via setupcomplete.cmd.
thanks my dear friend for reminding me that i havent shared the work for the same images i update regularly
Plus theres a lot of scripts plus reg files plus group policy files too inside my $OEM$ pack :)
 

garlin

Moderator
Staff member
If you're removing them during post-setup, why can't you apply these changes to the original or edited images? Are you bypassing DISM and removing files directly? The question is not whether it works, is it supportable for average users?
 

|====|

Active Member
If you're removing them during post-setup, why can't you apply these changes to the original or edited images? Are you bypassing DISM and removing files directly? The question is not whether it works, is it supportable for average users?
Yes i do remove files & services directly too via trusted installer rights . no its not for average users . thanks a lot :)
 

AeonX

Active Member
Although scripts are useful people are more interested in presets, registry files, post-setup commands as they can be used with NTLite. After all this is a forum about NTLite.

But neither the scripts you want to share so I don't see the point of the existence of this topic.
 

|====|

Active Member
Thanks a lot garlin for moving this thread to correct subforums on our NTLite Community :)
i dont have any issue if its been trashed too as been requested by some friends here via there comments. thanks to them too ;)
Be happy always & stay blessed ............ yes i agree sharing images but not the procedure "how to" doesnt make any sense on a tech forum.
my own NT10 $OEM$ pack is about 1.5 gb of disk space with lots of scripts reg pol installer files etc etc . most important thing is a sql script which patch dnsapi dll the correct way which is restricted to be shared on line in any scenario ;)
 
Last edited:

garlin

Moderator
Staff member
My question still hasn't been answered. If your $OEM$ folder is 1.5 GB, and we assume that's not personal apps then why aren't the changes applied to the offline image? 1.5 GB of post-setup overhead is really big compared to the starting size of single-edition ISO's.

What the community is saying is you've posted "progress reports" for months. And you haven't shared anything.
No presets, no scripts, no walk thru's, no explanation of methods, no known issues or problems.

Either your project is incompatible with NTLite forum's standards, or this thread has run out of purpose. I'm sympathetic, but you're getting trashed because this thread is more about visibility than contributing wisdom.
 

Clanger

Well-Known Member
Either your project is incompatible with NTLite forum's standards
I work mainly with post install scripts so i cant post them here, they are not part of the tools capabilities and as nuhi rightly pointed out "this isnt a scripting forum". Most i could probably do is a preset and an ntlite generated setupcomplete file but all my tweaks are post install only.
 
Last edited:

|====|

Active Member
My question still hasn't been answered. If your $OEM$ folder is 1.5 GB, and we assume that's not personal apps then why aren't the changes applied to the offline image? 1.5 GB of post-setup overhead is really big compared to the starting size of single-edition ISO's.

What the community is saying is you've posted "progress reports" for months. And you haven't shared anything.
No presets, no scripts, no walk thru's, no explanation of methods, no known issues or problems.

Either your project is incompatible with NTLite forum's standards, or this thread has run out of purpose. I'm sympathetic, but you're getting trashed because this thread is more about visibility than contributing wisdom.
"i am getting trashed or this thread is" hmm :)
 

AeonX

Active Member
my own NT10 $OEM$ pack is about 1.5 gb of disk space with lots of scripts reg pol installer files etc etc .
I don't think that 1.5GB is essential, it's probably software you use in particular so you could share the pack without them.

Where is the preset you use then?

Predefined presets for Super Lite win10 any build ie from 14393 to 19044
Plus installing Softwares on Offline Image according to our needs.

Edit : Post Restored with Org MSG & Love to use NTLIte.
Reread the content of the first post in the topic. You are contradicting yourself.

Note that no one is forcing you to do anything, if you don't want to share anything that's fine, but make a coherent topic then.

If it's to clarify doubts and improve your project that's fine but make it clear so you don't confuse people.

But I haven't seen you ask for help or opinion on anything. So for me this topic is for no purpose other than visibility as well commented by garlin.

About sharing scripts, I think that's fine as long as it's not the focus of the topic. The focus should be on using NTLite in everything that is possible and scripting in everything that is not. You cannot disable scheduled tasks with NTLite for example, only remove them. So I see no problem in using and sharing a script for this.
 
Last edited:

Clanger

Well-Known Member
1.5GB $OEM$ folder aint that big when you consider that the nvidia GT710 display driver installer i got is 683MB, audio driver, realtek? how big is that sucker? i dont know cos im using an external usb dac/semi pro interface and the driver installer for that is only around 20MB. Other installers he might have,, Some reg files or reg scripts maybe, its easy to eat up 1.5GB really quick. Dont forget nuhi adds a command to delete the default setupcomplete files and script folders so he might be using that or similar too. A reboot and quick defrag and hes prolly got 99% at least of everything he needs installed. I have no problem in doing that myself if needed.

Scripts? i only shared my Scheduled Tasks scripts because nuhi didnt do them back then, my defender killer script i asked nuhi about and if he had said No i wouldnt have posted it. Reg files instead of scripts yeah, scripts? possibly although i would ask permission first only if they dont do anything the tool does. If in doubt about anything grey area ask first :)
 
Last edited:

AeonX

Active Member
Well, drivers are for personal use and for specific hardware and can be removed from the $OEM$ folder as well. I understand your point, but his justification for not sharing is because of the 1.5 GB size when most of the content should be for personal use and unnecessary to be shared. You can share the scripts to install the software and indicate how people should download the installers. It is completely unnecessary to include software and drivers in the pack that you can download from official websites.

As for the tools used by scripts they are usually small in size and will not occupy that huge size.
 
Top