HELP-Can't Add EN-IN Feature On Demand (FOD) packs in latest NTLite, getting error everytime

SM03

Member
Since version 1.8.0.6930, NTLite introduced a new feature of adding 'Feature On Demand' packs under Configuration/Feature but I am unable to add those three Englis- India FOD packs listed there i.e Speech recognition, typing & text to speech as shown in 1st Screenshot.
1780


Every time I tried to make an ISO, after setting up everything, while processing finally, it always ends up gives me the following error as shown here in this screenshot
1781

I already downloaded those three required FOD cab files & extracted all the contents of those three cab file & put all those extracted files into the NTLite Sub-directory properly as shown in this screenshot followed, still, don't know why I am getting this message.
1782

Today, after the release of the newest NTLite v1.8.0.6942, I tried to make an ISO adding those but that too ends up in this same so posting here for help.
 

nuhi

NTLite developer
Staff member
As I replied to your PM:

Language.Basic~en-in~1.0 needs:
"LanguageFeatures-WordBreaking-en-Package"
"LanguageFeatures-WordBreaking-en-legacy-Package"
"Microsoft-Windows-Hyphenation-Dictionaries-en-Package"
"Microsoft-Windows-Spelling-Dictionaries-en-in-Package"
"Microsoft-Windows-TextPrediction-Dictionaries-en-Package"
"Microsoft-Windows-LanguageFeatures-Basic-en-in-Package"

Language.Speech~en-in~1.0 needs:
"Microsoft-Windows-LanguageFeatures-Speech-en-in-avcore-Package"
"Microsoft-Windows-LanguageFeatures-Speech-en-in-onecoreuap-Package"
"Microsoft-Windows-LanguageFeatures-Speech-en-in-Package"

Language.TextToSpeech~en-in~1.0 needs:
"Microsoft-Windows-LanguageFeatures-TextToSpeech-en-in-Package"

As far as I gather from your PM reply, you extracted those packages?

Try to keep them in their original CAB format, just extract the FOD ISOs to the mentioned directory.
 

SM03

Member
Hi nuhi
yes, you replied that in my PM, but after that, I sent you another 2/3 PM stating that all those files you listed exist in that list (3rd Screenshot) but the issue still persisted, & you didn't reply further to those last messages of mine.

So, I asked in the open forum. Requesting you to check my reply there as I already replied there in a more detailed manner, & if you don't wanna check & reply there in pm, then tell me, I will copy-paste those messages there.

'As far as I gather from your PM reply, you extracted those packages?' = YES ( as you can see in the 3rd screenshot)

'Try to keep them in their original CAB format'= I don't understand this, I didn't modify anything, just extracted from CAB & paste in NTLite SUBDIR as said/wrote earlier.

'just extract the FOD ISOs to the mentioned directory'= I don't have any FOD ISO, don't know what are you talking about. Just download these three EN-IN FOD CAB packages (Screenshot referred) from Here (UUP Dump)
1783

If these are not the correct packages /files that need to be extracted there, in NTLite FOD SubDIR then kindly re-direct me from where I should download those FOD packages or the 'FOD ISO' as you mentioned.

P.S: In PM, I also shared the LOG & Preset files as well for investigation, just to remind you.
 
Last edited:

Clanger

Well-Known Member
IF a feature is supplied as .cab files then they must be added as a cab file. NTLite uses dism for update integration and dism uses cab files, it wont work if you extract the contents of those cab files. IF you open Task Manager or Process Explorer during the Apply phase then you will see dism regularly start then stop, this will be for adding updates and setting Features. Adding .net3.5 on w10 is by cab files but on w8.1 its by extracted files.

NTLites own engine does the removals. NTLite sends the appropriatee commands to dism to mount, integrate updates, set features, mount registry(i think), apply and save changes to the image and to unmount.
 
Last edited:

SM03

Member
IF a feature is supplied as .cab files then they must be added as a cab file. NTLite uses dism for update integration and dism uses cab files, it wont work if you extract the contents of those cab files. IF you open Task Manager or Process Explorer during the Apply phase then you will see dism regularly start then stop, this will be for adding updates and setting Features. Adding .net3.5 on w10 is by cab files but on w8.1 its by extracted files.

NTLites own engine does the removals. NTLite sends the appropriatee commands to dism to mount, integrate updates, set features, mount registry(i think), apply and save changes to the image and to unmount.
Hi Clanger
Firstly, thanks for replying.

Yes, FYI, I've earlier tried to add them by retaining the CAB format as well, but that gave me the same error, then as instructed by nuhi earlier in PM, I tried extracting them in that SubDIR

You can try that for yourself to see whether adding as CAB will done the job or not. For me, everything fails. That's why I posted here.
 

Clanger

Well-Known Member
In that case sit tight and wait for nuhi to get back to you :) , 1903 is new and it takes time to iron out the wrinkles.
 

nuhi

NTLite developer
Staff member
'Try to keep them in their original CAB format'= I don't understand this, I didn't modify anything, just extracted from CAB & paste in NTLite SUBDIR as said/wrote earlier.

'just extract the FOD ISOs to the mentioned directory'= I don't have any FOD ISO, don't know what are you talking about. Just download these three EN-IN FOD CAB packages (Screenshot referred) from Here (UUP Dump)
Please re-read my reply, I see no point going in circles.
Do not extract the CABs please.

If you don't have FOD ISOs, then that feature is not for you, MSDN access to the ISOs is required. Even though it sounds like you got quite a lot of CABs, so just start over and only move CABs in the FOD folder, do not extract them.
 

SM03

Member
Please re-read my reply, I see no point going in circles.
Do not extract the CABs please.

If you don't have FOD ISOs, then that feature is not for you, MSDN access to the ISOs is required. Even though it sounds like you got quite a lot of CABs, so just start over and only move CABs in the FOD folder, do not extract them.
Hello nuhi

Well, First, in my earlier PM, I already told you that at first, I tried to add those three En-In FOD without extracting those CAB files, just keeping them inside the NTLite SubDIR, that failed with the same error so, in my next try, I extracted them.

As you're saying this again to keep them in their original CAB format, I 'll try that out once again with the latest version & get back to you with the result & preset & logfile if failed.

Secondly, I don't have the official subscription or access to the MVS/MSDN so I only rely on this UUP Dump website to get those FOD CAB packages, if you can redirect me whats the particular ISO file that you're referring here, then I will try to find that out. Let me know about any clue of that SO like name, or screenshot or whatever you can refer for better understanding.

EDIT: Okay, I got that FOD ISO & added those three En-In CAB packages from that ISO without any error, so it seems those CAB files that I downloaded earlier has some problem. Thanks, nuhi & Clanger for your replies & helping me out to sort this issue.

EDIT 2: Okay so I found what causes the problem earlier & thought to share with you guys nuhi & Clanger

The problem was not in those packages that I got earlier separately from official UUP Dump website, the issue is the way NTLite designed & handle those packages so if you rename those packages anything apart from the original file name, that particular error pop-up in NTLite while adding. Tried & tested with the latest version of NTlite of those official CABs that I got today from the official FOD ISO.

Just a suggestion to the developer nuhi might consider changing the rules in future ntlite builds so that those CABs can be added even though it renamed
 
Last edited:

nuhi

NTLite developer
Staff member
Good that you figured it out, so don't extract or rename CABs.
It's Windows that pulls it automatically as is, I have no control over it.

That feature where NTLite pre-detects CAB existence and lists exact ones missing would help.
 

freMea

New Member
The problem was not in those packages that I got earlier separately from official UUP Dump website, the issue is the way NTLite designed & handle those packages so if you rename those packages anything apart from the original file name, that particular error pop-up in NTLite while adding. Tried & tested with the latest version of NTlite of those official CABs that I got today from the official FOD ISO.
What’s the naming pattern used in FOD ISO for language feature pack ? I have the same issue with the files found in UUP Dump and I didn’t find a FOD ISO to compare.
 

SM03

Member
But you said files from uupdump can NOT be used because of their name. That’s you searched for the FOD ISO that have the naming pattern shown in the screenshot, right ?
YES, RIGHT. Edited my earlier comment with ISO link
 

SM03

Member
good finding. I'll try this in my next test for 19h2 build. Meanwhile, requesting you to share your test results while making ISO via NTLite, whether those CABs from uupdump can be successfully integrated by renaming according to the cat file, or not, any error occurred while making/integrating those with Win ISO via NTLite or does that finally effectively showing after instaling that very modded/customised Win ISO or not.

& here are the links for FOD & LP ISO
FOD ISO x64 Part 1

LP ISO (x86+arm64+x64)
 
Top