Now I used Recuva, WinHex, GDBNT on installed Win10, but these apps didn't find the textexpression I have in my mind...
NTFS CheckDisk still running - Ok, now let's create "new"one.
Here a little monster plugin (MozillaLight64.script
bases on following files in my folder [BaseDir]\Projects\Win10PESE\Apps\Network :
FirefoxLight43_x64.7z (22 MB)
FirefoxLight43Profile_en-US_x64.7z (1.5 MB)
FirefoxLight43Profile_de_x64.7z (1.5 MB)
FirefoxLight43Profile_zh-TW_x64.7z (1.5 MB)
FirefoxLight43Profile_ru_x64.7z (1.5 MB)
FirefoxLight43Profile_pl_x64.7z (1.5 MB)
FirefoxLight43Profile_ja_x64.7z (1.5 MB)
FirefoxLight43Profile_it_x64.7z (1.5 MB)
FirefoxLight43Profile_fr_x64.7z (1.5 MB)
FirefoxLight43Profile_es-ES_x64.7z (1.5 MB)
FirefoxLight43Profile_cs_x64.7z (1.5 MB)
FirefoxLight43Profile_zh-CN_x64.7z (1.5 MB)
FlashAdd.script (10 kB)
FlashPackage.script (8.8 MB)
FlashPackage64.script (10.3 MB)
A folder with several firefox-addon's XPI's (about 1-2 meg's)The questions:
Which of the 7z-archives to attach to script - and which to upload on which server (or where are which already stored) ?In principle - If a script does not contain a important part - the user should find notices where to download the missing part(s)
For the example MozillaLight64.script
--> TextBox (or TextLabel or message popup) with URL(s).
--> Conceivable: Attach the small FlashAdd.script to MozillaLight64.script- and consequently where one can download FlashPackage64.script ?, url ?
Otherwise, if all archives are attached to 1 script - one gets a 45-60 MB scriptfile.
My goal is: Flexibility - no compulsion to rewrite script every half year.
Maybe the several profiles function for both variants, Light and Light64 (not tested) - and maybe the several profiles function for future versions of Light (can't foresee).
Message,NTFS CheckDisk still running...,INFORMATION,600