Win7 64-bit PE Builds.

Hi Chris 
With X64s builds there are a few little things…   

Since using extracted Wim files is faster
I now build X64 builds with a Full File copy.
I use full file copy just for testing…. network sharing and other scripts

Extracted Wim and Full file copy 30min build time.. Not Bad 

I have found that using full file copy is different
Networking icon on taskbar,
Desktop back round ??
Optimizations - Firewall I have set default to disable
Add firewall enable and disable shortcuts does not work with a X64 build,
This maybe why I have problems with network sharing??   
Did anyone else notice differences?

@ Arvy thank you for scripts, I will try them when I get a chance.
@ ChrisR do not tell anyone but Brad = PePauser..   
@ JFX you just saved the day again...... Thanks   

Happy to see you, Brad
And for you, as the good old days with JFX and Multi7PE SE 

a little busy now, I'll watch it later, thanks for feedback on x64s build.

ChrisR and JFX

Network sharing in a X64 build now works,,,,,,,,,,, THANKS 

Desktop back round ??
Optimizations - Firewall I have set default to disable
Add firewall enable and disable shortcuts does not work with a X64 build,
This maybe why I have problems with network sharing??   

Thanks for feedback, I did not understand what you meant by "Desktop back round ??", but for others :

I changed "FireWall Disable" by "FireWall Disable (default)"  .

The shortcuts "firewall enable" and "firewall disable" works now  , by adding a space.

sc.exe config MpsSvc start=auto       --> sc.exe config MpsSvc start= auto
sc.exe config MpsSvc start=disabled   --> sc.exe config MpsSvc start= disabled

with WB, we must be added #$s for a space after = , otherwise it deletes the space when saving the script

I also added a textbox to Specified the Computer Name. thanks RoyM   

 1-50_Optimizations.7z (10.8 kB - downloaded 215 times.)

Hi 
I compared 4 builds x86 and x64 with Full and Standard file copy

With x86 builds
With Standard and Full File copy, both show same wallpaper or desktop
BUT
The Standard File copy build will not show the networking icon.
A Full file copy will display the networking icon

With a x64 build
Standard file copy, will show same wallpaper or desktop as a x86 build and no network icon

Full file copy will have default or standard win7 wall paper
And
Full file copy will display networking icon.. 

Next time I do all 4 builds I will compare log files… Sometime

Note
I have not found that any apps or scripts are affected. This is just something we should keep in mind.

I think    I sent ChrisR a message detailing this post, but my sent box is empty, and since I can not edit, disclaimer goes here..

Also … CoolMon 1 - script was used in  BB7

BG info is used with all other Win7 builds,

I can not remember why..    but I did liked CoolMon 1

I will check it out when I have time,,,,,,,,,

I saw for the network icon, thanks for the screenshot
This seems normal that with a full copy we have more things or more options
for the networ center, it certainly lacks some registry keys.

My answer is partly in this Dera's script NetworkCenter, I have slightly modified it, not perfect but not bad  .

http://www.mediafire.com/?b9fcdgy5q6aeate

Coolmon or BGInfo, the two are good  , I do not want to put both.



ps: 10 post to edit, I think and you have a chechbox "save a copy in my outbox". I forget the check too, sometimes.
edit2: I just saw, there is an option in profile > personnal messaging > Save a copy

Also … CoolMon 1 - script was used in  BB7

Yep, also used in Gena too. Check under 'Apps\System Tools\HW Info'.

Regards,
Galapo.

I can't seem to get HWPnP to work in my 64-bit Win7PE SE builds and its failure appears to result in a lot of other issues, such as NIC driver loading in my own case.

In fact, if I attempt to run the HWPnP executable after booting, it says that its required DLL support is completely missing.  Actually the hwpnpdll.dll is present in the build, but is located in %windir%\system32.  Think possibly that one may need to be located in %windir%\SysWOW64 for PE x64 builds???  And the same might also apply more broadly to some of the destination %target...% handling for others as well.

As far as I know, HWPnP is only compatible with x86 builds. That is because it makes use of MS detours package -- only the 32 bit version is free, while the 64 bit version has a $10,000 license fee per product, hence Paraglider has not update for 64 bit support due to this pricing.

Regards,
Galapo.

WOW!  That's some pricing and would certainly explain a 32-bit limitation.

Guess I'll modify that script in my set-up to make it exit automatically with a message if the build source isn't x86.

In the HWPnP script supplied with Gena, we have this line at the beginning:

Code: [Select]

If,Not,%SourceArch%,Equal,x86,Exit,"%ScriptTitle% is compatible with only PEx86 builds"

If you add something like that to the start of the [Process] section of your script, it will exit under x64 builds.

Regards,
Galapo.

I can't seem to get HWPnP to work in my 64-bit Win7PE SE builds ......

If,Not,%SourceArch%,Equal,x86,Exit,"%ScriptTitle% is compatible with only PEx86 builds"

If you add something like that to the start of the [Process] section of your script, it will exit under x64 builds.

Done ("x86 only" in title too), thank you guys 
 

With a x64 build
Full file copy will have default or standard win7 wall paper

OK seen, there is indeed a small problem with the program runbgingo.au3, I have a small correction but I prefer to do it with homes32.

What are the benefits of coolMon1 vs BGInfo ? I have to test it.
However, available easily with share script 

In fact, it's possible to use the same "If,Not,%SourceArch%" method for "auto-switching" between two scripts, both of which are selected for build inclusion by default.  Ive done that for the Attribute Changer and Properties Plus scripts in my own multi-PE builder setups.  That way the Attribute Changer extension for Explorer gets installed for x64 builds and the Properties Plus extension gets installed for all others.

Incidentally, after having very kindly created that Attribute Changer script at my request, I see that it's not included in your own DL packages.  Don't like it much yourself?

Incidentally, after having very kindly created that Attribute Changer script at my request, I see that it's not included in your own DL packages.  Don't like it much yourself?

I find him very well and it works well with Win7PE  , it seems that some dependency is missing to work also with Gena.

To include it in the dowload package, mon concern is to continue to improve Win7PE and to maintain it as a base with just few apps.
But here it is an add-in system tools, then maybe Yes    By cons I do not want to put Acronis, even if I like TI and DD.

If one day we want to offer more apps in Win7PE SE, I would like to do it as Gena-sweets with an another package. but I have not enough timeeee 

Good to see Holger is still alive.

Maybe we have a chance to get a fully working x64 version of PENetwork now

I made a small change to the x64 version of PENetwork.exe (v.056a), but before bothering Holger can anyone give me some respond?

is it still possible to crash it with the sharing tab, under Win7PE_SE x64? And is there in the  username box Administrator inside?

PENetwork v.12
 

Downloaded.  I'll run a 64-bit Win7PE SE test build with it and get back to you as soon as I can.  I usually use my own "customized" PENetwork.ini for static IP settings on my multiboot test platform.  Does that matter at all?

__

FOLLOW-UP as promised:  Built and ran using my usual 64-bit Win7PE SE script selections (mostly defaults) replacing ONLY that single script.  No crash when the sharing tab is selected nor when the start sharing button is clicked.

I do occasionally, however, seem to see other quicks with PENetwork under x64 Win7PE.  There are times when its start-up process actually seems to mess up my default 64-bit NIC driver installation so that it appears (and is) disabled under the device manager.  I realise that's a whole different issue, but just though I'd mention it if you're going to be contacting the author at some point.

Thanks, Arvy 

PENetwork.ini should not have any effect on this issue.
Every time the sharing tab is pushed, PENetwork try to build a list of the users available, thats were the crash (had) happen.

Your problem seems to be with the driver installation on first PENetwork start, maybe there are some information inside:

X:\Windows\Inf\setupapi.dev.log were all driver install/update should be logged.

 

PS: uploaded new script in  my previous post.  forgot to add startnet.exe and lang files

Congrats.  Looks like you pinned down that issue successfully. 

Your problem seems to be with the driver installation on first PENetwork start, maybe there are some information inside:
X:\Windows\Inf\setupapi.dev.log were all driver install/update should be logged.

Yes, thank you.  It's not consistent (doesn't do it every time) but basically the PENetwork start-up process seems to be trying and failing to reinstall (or update?) the NIC driver that has already been correctly installed from the 64-bit DriverStore during the PE start-up.  No immediate response is expected on that issue.  I just mention it as info that you might want to pass along if you are in contact with the author at some point.

__
P.S.: Specific NIC driver details are probably irrelevant, but just for the sake of providing complete info in case anyone wants to know, the NICs involved in my case are Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controllers and their "natively installed" 64-bit drivers are included in the Windows 7 PE build's DriverStore\netmyk00.inf_amd64_neutral_9c0c35afdddc16d2 subfolder.