Hopefully I didn't put an overload on You.
...+ I do not know why you prefer xcopy, following you I also use Call,XCopy ...
I hope all these posts will be a nice head start to HeyJoe.
I do. I will be again away in short time.... These days only reason I keep around is HeyJoe.
Waiting for your next on the other topic, I hope you have free Saturday time.
Quote from: Lancelot on March 26, 2021, 05:48:54 PM...+ I do not know why you prefer xcopy, following you I also use Call,XCopy ...I love using xcopy (and other) since Good Old BartPE by Bart Lagerweij
Regrettably no free time.
I believe I catch you again......
I recently did a comparison of latest WinPE_SE_2021-03-19.zip with plugin files below My %ProjectDir%to find changes I made in the past.
...Also, If I miss one of your reports let me know.
Hmm, what does that mean:Quote from: Lancelot on March 26, 2021, 05:48:54 PMI believe I catch you again......1.: meant fun ?2.: Try harder !I belive 1st one, Am I right ?
-------------------------------------------------------------------------Recent update "Win10PE_SE_2021-03-28.zip" - big thx for it.What a time investment every time ! --> collecting, commenting, inserting, copying, ..., zipping, put on server(s) ... etc.Wow ! -------------------------------------------------------------------------
Reminding: My source is v.1809 x86 - I prefer to build with BuildClass=2
Dealing with public is mostly not funeven recent examples:...
It is quite fun to get good feedback
Better split replies, see you on next reply ...
As far as I know, Index 5 is the right index ?
See Reply #24: The 2nd comment in codebox starting with line: "// 2nd: I inserted between org. lines 459/460 saying:"gives Us: See (selfmade) blue arrow in pic "BuilClass2.png"
Hi HeyJoe,Yes index 5 with Win10_1809_German_x32.isoAs you already figure out BuildClass3 get ProductName info from wim file BuildClass2 get ProductName info from registry and with Win10_1809_German_x32.iso ProductName info (index 5) mismatch.I believe BuildClass2 should follow the registry following its install.wim independent nature.So I leave it as it is since the index is auto-detect correct with 5 which is the important part. Let's see that a bonus feature to catch when there is such a case. I add History Notes about that.
Btw, BuildClass=3 is OK, except gui entry saying: Service Pack : SP0Because most likely M$ won't deliver so called SP's for Win10 anymore, We can correct it this way (cosmetics ?):
More to come soon.
Further, I will come with a midway solution
Made more clarification and added some new things/thoughts
I will change BuildClass2 to write SP0 to ui when registry entry not exist.
Quote from: HeyJoe on April 01, 2021, 11:37:37 AMSee Reply #24: The 2nd comment in codebox starting with line: "// 2nd: I inserted between org. lines 459/460 saying:"gives Us: See (selfmade) blue arrow in pic "BuilClass2.png"I already replied that:Quote from: Lancelot on March 23, 2021, 08:05:36 AMI believe BuildClass2 should follow the registry following its install.wim independent nature.
I believe BuildClass2 should follow the registry following its install.wim independent nature.
// But consider: this way We have equal results for both BuildClass 2 + 3 which would (bonus) avoid cache new writing in case You want quickly change/test BuildClasses.
Sorry, No. I don't think it's worth the effort.Where there is nothing, nothing has to be written.
...Sorry, No. I don't think it's worth the effort.Where there is nothing, nothing has to be written.
"Service Pack : blablabla" ???????????
"WallPaper Login" v3 on server
...Main reason is, ...
Hi Noel,...BTW: How did You manage (in admin session) that the explorer remembers the setting changes?Ex.: After changing the icon view (or other things) and reloading the panel, the icon view was not lost unlike in my PESE!...
Still, PE not saving folder settings after boot is the main "issue" ...
This way when there is no Service pack, ServiePack ui invisible will not create emptiness feeling. What you think ?
QuoteThis way when there is no Service pack, ServiePack ui invisible will not create emptiness feeling. What you think ? Hoping "emptiness feeling" on plugin UI goes away. Let's try.See You.