[Lancelot_Real]

Thanks Tripredacus

JFX, on 17 February 2011 - 08:32 AM, said:

As foreseen with activated firewall, fire sharing no longer works.

Thanks.

JFX, on 17 February 2011 - 08:32 AM, said:

shortcuts.exe - Created by Joshua, updated by rpaz hmm really

no really.
As far as I know, shortcuts.exe created by JFX, and Rui Paz fix/improved icon indexing
whereever such text written (inform me to fix, you know I am the enemy of liers and hypocrites... shortly idiots ), should be fixed,
and you can be sure it will be fixed since unlike some other idiots,
ChrisR has very good reputation on me with his team spirit leading.

JFX, on 17 February 2011 - 08:32 AM, said:

Since i do not decompile others scripts, what was changed in this new version?

IE added with a set of options (not default)
Add,Url api ....
Sidebar-Gadgets.... (not default)
Very Good contributions of 2aCD
Organisation for msfn distribution
and as usual, never ending story of more settings and improvments....
....
You know better JFX


edit:
I found where it is written, sharpe eyes JFX, I do not know who wrote this....... I will try to fix tomorrow.

edit2:
fixed wrong, PinTool by Rui Paz used to add pins...

This post has been edited by Lancelot_Real: 18 February 2011 - 01:07 AM

[JFX]

Thanks, Lancelot.

actually the last question was only related to shortcuts.exe


2 small things:

Audio script will need avrt.dll if not explorer script is choose.

defragproxy.dll will be needed for diskpart/MMC shrink/expand function.

further

sfc.dll
lz32.dll

crtdll.dll (no x64 version and already in wow64 script for x64 builds)

could be added to base files

BTW: Just a small tip, as I see same script now copying files to WinSxS folder. That usually is unnecessary and will only make the build time slower.

For Registry adding, it's preferable to use *.reg files

[Kullenen_Ask]

JFX, on 21 February 2011 - 02:11 AM, said:

For Registry adding, it's preferable to use *.reg files

exactly. or hive files. i like hives

[Lancelot_Real]

Thanks a looooot JFX,

avrt.dll added to Audio
defragproxy.dll added to Mmc
sfc.dll, lz32.dll, crtdll.dll added to 1-files.Script [FileCopyStandard]

JFX, on 21 February 2011 - 02:11 AM, said:

BTW: Just a small tip, as I see same script now copying files to WinSxS folder. That usually is unnecessary and will only make the build time slower.

Well, Since I do not know much about this case, I leave decision to ChrisR for now. (ps: ChrisR seems to be away for a while so it can take time he respond)

JFX, on 21 February 2011 - 02:11 AM, said:

For Registry adding, it's preferable to use *.reg files

Yep I agree, We already know winbuilder is a crap, worst written script engine to write registry (which in fact it is "primary" job as a pe builder, what a shame, well you know its developers are very hypocritical and liefull (+sabotagefull :>.... shameless....) instead of making true coding to fix & improve......)
To me it is only gut for visuals and more-or-less working macro handling, not a true builder at all but these 2 advantages helping end user start easier.
I am pretty sure we would replace it one day, not soon, but one day...

For reg handling, I convert .reg files manually with eye check, but.....

Well, I hope you accept my further request
You know, many people not aware, and they "tend" to change .reg files to some crap lines that cause slow down (ex: wallpaper) and errors (hehe, you know better, since I already workarounded many I do not know an active example).

A small, helpfull tool, would "increase" the usage of .reg files, IF you can help as an au3 master .
here is a "basic" tool which is not suitable for all cases, but would give you the idea in my mind
http://www.mediafire...5dihv790hj04mxh
its weak points
1) it uses StringReplace but for secure conversion better we have something like "SectionReplace"
2) I am not sure if it contains all possibilities ....
3) StringReplace CurrentControlSet-->ControlSet001 does not look to me very gut due to "stringreplace".......

it would be useful to have such tool to both
1) manual convert .reg files easly :> so it would give more motivation to use such tool with plugins.
2) convert .reg files dynamically , ppapps has an option for that with another crap, I am willing to replace such usage with a better tool, from someone like you who has very good reputation. (+I am pretty sure author=Amalux will like too)
3) along with 1 & 2), last contaminations would be cleaned from project hence it will be all clean with only 1 exception for now.

I hope you like the idea and take the task, See you.

This post has been edited by Lancelot_Real: 22 February 2011 - 12:43 AM

[JFX]

Hi Lancelot,

sorry for late respond, well no interest in making such a tool


Another thing, i now could confirm with 4 msdn Win7 SP1 ISO's is that the mounting with Vista imagex no longer is reliable

You guy's will have to switch to to new imagex (wimmount driver), what will surely heavily increase build time and mounting issues.

Another way would be applying wim files to hdd, that would require quite a bit space, but that should not be the a problem by today's hard disks.


At least the avoiding of old imagex will have two positive thing:

- nobody will need to have download the Vista Waik anymore

- user of Win7PE SE will no longer need to reboot when using MakePE3

[Lancelot_Real]

Hi JFX,

hehe, not important at all, only an idea to "kill" another "id*ot" tool, you know

can you guide to detect w7sp1 source

hence when w7sp1 source detected, I can arrange checking wimfltr + wimmount + imagex version ... blabla.....

hehe, I also thought about extracting all files too :> , some more, since ntfs is very popular now, having source files extracted on a different folder, and junctioninig folders (by junc.exe from Olof) during build would do the trick for the ones who have space.(~4GB for w7x86 I guess, not too much and after once extracted....) ...

Well ideas requires time, currently I am pretty much busy with Gena, and ChrisR seems away for a long while now.......
Since you betrayed (your own words) to pe1x for a while now (we miss you), I hope you can give hand on these things when you have time.

btw, I get w7-ultimate-x86 with md5 24F3A45D43D7C532AA3126CC094C61BD
http://www.pcguides....-1850-leak.html
you know, I have not betrayed pe1x ( & nt5x) yet, I am quite unsure about these stuff and always stayed at "support" side of the "JFX MultiPE Force" ,
can you confirm, is it a reliable source to make tests ?

edit-fix:
testing with extracting boot.wim (2) install.wim (5) of w7sp0 (Ultimate_x86_7600_16385_090713_1255)
boot.wim (2) 840 MB
install.wim (5) 7,88 GB
using our ntfs-compress friend
boot.wim (2) 510 MB
install.wim (5) 5,45 GB
Extracting takes quite time, but I feel 6GB is good enough to make frequent tests.....

This post has been edited by Lancelot_Real: 02 March 2011 - 04:12 AM

[JFX]

Lancelot_Real, on 01 March 2011 - 02:59 PM, said:

can you guide to detect w7sp1 source

Wiminfo.zip will convert wim xml info into a ini file, so one can easily read build number (7601) or Servicepack. (SPLEVEL)

Lancelot_Real, on 01 March 2011 - 02:59 PM, said:

btw, I get w7-ultimate-x86 with md5 24F3A45D43D7C532AA3126CC094C61BD
can you confirm, is it a reliable source to make tests ?

Sure the MD5 matches an official win7 ISO

This post has been edited by JFX: 03 March 2011 - 04:48 AM

[rpaz]

JFX, on 17 February 2011 - 08:32 AM, said:

shortcuts.exe - Created by Joshua, updated by rpaz hmm really

Since i do not decompile others scripts, what was changed in this new version?

Hi JFX,

No one is trying to get credits from your work.
In fact the shortcuts.exe doesn't include any copyright/owner information. I did a post on Bootland (now Reboot.pro) asking for the script source, no one replayed.

Searching bootland i found several shortcuts.exe probably from different authors because the files have completely different version information, and some work on Win7PE_SE others don't.

During my search's also found some winbuilder script posted by Joshua with new versions of win7peldr.exe and shortcuts.exe this and some other posts on the board led me to wrongly give the credits to Joshua.

Sorry for this misunderstanding. By the way that for the spectacular work you did on the win7PE "core" thanks.

___
Rui Paz

This post has been edited by rpaz: 03 March 2011 - 01:06 PM

[JFX]

Hi rpaz,

well no problem, only reason for compiled autoit script in the project was to avoid people making critical changes.

Shortcut.exe was tough as a temporary solution, to cover most used CAPI's and it's based on VistaPE Loader.

However it did not ended up as planed, people started to complain about missing CAPI function (which I wanted to remove for common sense reasons).


I appreciate if anyone want to improve that tool, but important to keep track on changes.

[rpaz]

JFX, on 01 March 2011 - 02:39 PM, said:

Another thing, i now could confirm with 4 msdn Win7 SP1 ISO's is that the mounting with Vista imagex no longer is reliable

You guy's will have to switch to to new imagex (wimmount driver), what will surely heavily increase build time and mounting issues.

Hi,

I don't know exactly what imagex version you are referring to but i can build Win7PE SE fine using imagex from Windows 7 WAIK (v6.1.7600.16385) on Windows XP, i didn't install WAIK only extracted the needed dlls to my system32 folder.

___
Rui Paz

[JFX]

I had chosen the vista version of imagex (v6.0.6001) for win7pe se, because it had some advantages over the one that comes with windows 7 WAIK

Sadly with the SP1 WIM files, if you mount with vista imagex the file content of some files is no longer correct.

[Kullenen_Ask]

i always use vista imagex too. can you give example about corruption? what anormallities you had?

[JFX]

if you mount an install.wim image of en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso

inside \Windows\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_neutral_423894ded0ba8fdf

wdmaudio.inf will have the content of msxml6r.dll.mui.


So it seems that there is an problem with hard links of the new SP1 WIM files. Thinking about that there are thousands of links this could be a serious problem

[Kullenen_Ask]

yes. i think sp1 is problematic. not imagex. worst sp i have ever seen. if you investigate driver inf files you can see more problems.

http://forums.mydigi...d-how-to-fix-it)

[joakim]

Could be related issue with sp1; http://forums.mydigi...-for-serial.sys

[ChrisR]

After a week of vacation without internet and then 8 days in hospital (all is well now, at last, I hope).

I look a little Win7Pe_Se but I'm busy on other things too.

Thank you JFX, 2aCD, Lancelot for modifications and corrections made .

I just tested the SP1, it is true for me too, that imagex vista 6.0.6001 seems to not work properly. Damage (5-10 times longer to mount unmount image) .



And other files also.
We'll have to go unfortunately through the version for Win7 (6.1.7600).

As JFX says

JFX, on 01 March 2011 - 02:39 PM, said:

At least the avoiding of old imagex will have two positive thing:

- nobody will need to have download the Vista Waik anymore

- user of Win7PE SE will no longer need to reboot when using MakePE3

and keep, perhaps, vista imagex for the original windows 7, that works very well


Some few questions :
With Wiminfo, we can can easily read build number or service pack of install.wim source.

How can we verify the correct version of imagex in tools related to Win7 source?
Also for the installation of WimFltr.sys and(or) wimmount.sys ?
Is that 4 files wimmount.inf, wimmount.sys, WimMountInstall.exe, wimserv.exe are necessary in tools ?
I saw that Wimb test, in MakePE3, if wimfltr is Running (sc query wimfltr | find "RUNNING") and request for reboots if it is active. Is it really necessary ? (I tested without rebooting and it seems to work for me).

This post has been edited by ChrisR: 08 March 2011 - 06:52 AM

[Lancelot_Real]

Hi ChrisR,

welcome back .
I am glad you are out of hospital, My girlf is nurse but still after years I can not get confortable there. I hope nothing serious.

I had some troubles like wimb when using new imagex (wimmount) with having wimfltr running (I can not remember cases, I remember we chat about that with JFX, maybe he remembers.....) so yes reboot is required.
On VistaPE-Capi (before JonF kicked), I had to put a checkroutine like wimb, I added to VistaPE-Capi's PreConfig script
http://www.mediafire...w374zv6fgg795ey

Run,%ScriptFile%,Checkwimfltr

[Checkwimfltr]
.....wimfltrstatus.au3.....

ps: In addition there is WaikTroubles_Button , [WaikTroubles_ReadMe] ........

For Win7PE SE, my plan was, adding things I made on VistaPE-Capi + in addition using Wiminfo.zip (Thanks JFX ) first to get If source is greater than w7sp0, and than check imagex version.......

something like

If,%w7sourcesp%,bigger,blabla,Begin
If,Not,ExistRegKey,HKLM,SYSTEM\CurrentControlSet\Services\wimmount,Halt,"you must install latest aik - wimmount"
Retrieve,FILEVERSION,%IMAGEX%,%IMAGEXVer%
If,%IMAGEXVer%,Smaller,6.1.7600.16385,Begin,
Message,"update your imagex blabla"
Halt,"update your imagex blabla"
End
Run,%scriptfile%,Checkwimfltr
End

So practically, changing imagex.exe at tools folder would be a simple way to switch between imagex versions, and initial build process only checking if things are made correctly.
(ps: AFTER** checking there is no imagex at tools folders, one can check if aik installed & location too to find imagex... or a box to give location, but first check if exists at tools please)

In the end, switching between imagex (in fact between wimfltr wimmount) would be easy, and people using w7sp0 source can mount-unmount fast when others w7sp1 can mount slow but correct with latest imagex. Who knows, maybe with w7sp2 we can switch back to speedy wimfltr (or maybe another 3rd party in future) :>.

Sorry, these days I can not have time on W7PE SE or any pe2/3 related things, lots of delays on that area, pretty busy, coming soon............. See you.

This post has been edited by Lancelot_Real: 08 March 2011 - 08:01 AM

[Lancelot_Real]

Hi all,

can we have a fix for StartUp and SendTo ?
I feel this is about shortcuts.exe.......

currently,
using SendTo adds shortcut at startmenu (StartMenu\Programs\SendTo\blabla.lnk) --> this one is a bit comical
StartUp to me half okey, it creates shortcuts at startup folder, but these shortcuts are not executed after explorer starts
(maybe startup a timing issue if shortcuts created after explorer starts......)

I hope you can fix easly,
See you.

[ChrisR]

For hospital this was my first visit (pneumothorax), I still find it difficult, fortunately there are the nurses who do a beautiful work.
It is history now, I hope.

Lancelot_Real, on 08 March 2011 - 09:52 PM, said:

can we have a fix for StartUp and SendTo ?
I feel this is about shortcuts.exe.......

currently,
using SendTo adds shortcut at startmenu (StartMenu\Programs\SendTo\blabla.lnk) --> this one is a bit comical

I modified a bit the program shortcuts.exe to manage the function Sendto, it seems to work correctly
I also replaced AU3300.exe by AU3361.exe

here the new script 2-Config.7z

Lancelot_Real, on 08 March 2011 - 09:52 PM, said:

StartUp to me half okey, it creates shortcuts at startup folder, but these shortcuts are not executed after explorer starts
(maybe startup a timing issue if shortcuts created after explorer starts......)

I do not know about the execution of programs from the Startup folder after explorer start. I hope someone can help to fix it.


I tried again windows7 sp1 with win7 imagex it is long, very long. Is anyone compared the time with dism ? there are also 7-zip.

[Lancelot_Real]

Thanks ChrisR,

yep there are 3 type of nurses, The Good , The Bad and The Ugly.
The ones who can not use needle carelfully mostly Bad, sometimes Ugly.
The ones who can use beedle carelfully and have a positive motivation, The Good.
and rarely, If its your luckly day, you can see The Good and Beatiful.....
anyway, I hope history now too.


I will test very soon :>

for startup, forget it for now I figure out how to handle startups and why people used workarounds before...... ......

for imagex,
there is one more alternate way I wrote above post 26,

Lancelot_Real, on 01 March 2011 - 02:59 PM, said:

testing with extracting boot.wim (2) install.wim (5) of w7sp0 (Ultimate_x86_7600_16385_090713_1255)
boot.wim (2) 840 MB
install.wim (5) 7,88 GB
using our ntfs-compress friend
boot.wim (2) 510 MB
install.wim (5) 5,45 GB
Extracting takes quite time, but I feel 6GB is good enough to make frequent tests.....

hence no mount-unmount required, still for build final compressing, wimgapi.dll required, and I guess can be obtained from source .......
tip: wimgapi.dll 32bit work fine for compressing on hostosx64 and I guess exists on syswow64 of x64 source......................
another tip: ntfs-compress an empty folder before extracting with 7z into it.

But I am still very busy and can not work on pe2/3... only sharing ideas... Thanks for the fix again..... See you.

This post has been edited by Lancelot_Real: 09 March 2011 - 01:06 PM