PENetwork Manager for VistaPE/Win7PE
#76
Posted 02 August 2009 - 11:11 AM
- Fixed/Changed: Internal update procedure in WB script
- Fixed: WiFi key can now includes '&' character and '<', '>' characters (thanks to KdN)
(-> ''' and '"' - characters test is sill open cause the 1st test with XPSP: these characters were stored directly in XML,
not with "'" or """)
- Fixed: Internal script bug with some disabled controls - bug was not visible in compiled mode
- Added: Window position of PENM will be saved on GUI closing and reloaded on GUI starting
- Added: Optional using profiles in WB script (like in LiveXP script)
DirectDL: http://holger.winbui...Network_vpe.zip
Greets
Holger
#77
Posted 02 August 2009 - 01:37 PM
during built of your script I get an error beep and for a very short time in the message box of winbuilder I can read following:
!!! Can not copy xactsrv.dll file!!!I use latest win7pe from yahooUK with winbuilder 077 RC2 and win7 (7100.0.090421-1700_x86 german) as source (no waik).
Any hints about this?
In your script I found the following line:
Require_File,xactsrv.dllI can't find any hints in the log file concerning this beep/fault
tia
Patsch
#78
Posted 02 August 2009 - 01:49 PM
The beta v5 was just the last single release cause I'm merging the scripts from LiveXP and this for VistaPE/Win7PE to one.
And in this new script there are some more changes, ie my own copy function to be more independend from WB project changes.
#79
Posted 02 August 2009 - 01:56 PM
#81
Posted 02 August 2009 - 02:40 PM
#82
Posted 04 August 2009 - 08:57 PM
With this version i get this error:Update: 02.08.2009 - v5 beta (PENM 0.55)
Starte "Wlansvc" Dienst...
AutoIt Error
Line -1:
Error: "If" statements must have a "Then" keyword.
under win7pe build with german RC1 under vmware.
Joshua
#83
Posted 05 August 2009 - 04:36 AM
It seems I forgot something on updating PENM...
Will fix it in the later afternoon.
Greets
Holger
#84
Posted 05 August 2009 - 04:01 PM
- Updated "PE Network Manager" to version 0.56 -> use script option "Check for newer version of PENM..."
- Fixed: Missing 'Then' in WiFi start/stop function
- Added: Some missing lang strings
#85
Posted 05 August 2009 - 07:26 PM
You should replace
[Process-SetWin7] Echo,"Detected Win7 project. Setting variables." Set,%ProjSrc%,Win7CD Set,%ProjSec%,Win7InfoBy
[Process-SetWin7] Echo,"Detected Win7 project. Setting variables." Set,%ProjSrc%,Win7CD Set,%ProjSec%,ProjectInfoYahooUk have renamed Section Win7Info by ProjectInfo
#86
Posted 05 August 2009 - 08:29 PM
and cause of this everytime changing, changing & changing I will change the OS check in my script
Maybe tomorrow...
Greets Holger
#87
Posted 05 August 2009 - 08:32 PM
An other way use ReadEnv first
Then you know all variable no need to check if it is Vista or Win7 api do it for you
Have a look in Win7PE-CAPI how I have modified PENetwork.script
I have send a PM to JonF and YahooUk to change the ReadEnv function
So it will work like this for all Vista/Win7 project
#88
Posted 11 August 2009 - 09:17 AM
Wanted to notify you that running the RTM of Windows 7 with Winbuilder 077 RC2 works 100% with your script, at least for me! All network adapters works that I have tried, and no problems so far at all. One thing that I am wondering about though, is if it's somehow possible to FULLY AUTOMATE the program at start. I don't want to click anything at all, I want it to detect the NIC, and automaticcly use DHCP adress, without showing the main program. I have tried different ways to do this, using the ini-file and so on, but never successfully gotted rid of the main program at start.
Any Ideas? Thanks again for a great work!
#89
Posted 11 August 2009 - 12:35 PM
It's changed in my VistaPE Core and, of course, in VistaPE CAPI.I have send a PM to JonF and YahooUk to change the ReadEnv function
#90
Posted 11 August 2009 - 01:33 PM
Sorry, for my delay report about changing variables.Thanks for info
and cause of this everytime changing, changing & changing I will change the OS check in my script
Maybe tomorrow...
Greets Holger
Yes, I've changed all scripts variables to Generic ones follow by Pedrole's advice.
Great works
thanks for your very useful stuff.
yahooUK
#91
Posted 12 August 2009 - 05:08 AM
Nobody has this error on Win7PE build with Winbuilder 077RC2 and Windows Seven French DVD--->
I have already build with success a Share service script but i want known before to share my script, if anybody has the same problem ...
#92
Posted 12 August 2009 - 05:43 AM
Nobody has this error on Win7PE build with Winbuilder 077RC2 and Windows Seven French DVD--->
I don't get the error window with german-rc1, but the Share service immediately stopps after started!
Please share your 'Share service script'.
Joshua
#93
Posted 12 August 2009 - 08:33 AM
Please consider Windows firewall service as well.
No time to close it up now, sorry.
Thanks,
yahooUK
#94
Posted 12 August 2009 - 09:23 AM
Most useful for me wouldbe the ability to connect to a VPN server from WinPE. Are there any plans on adding this functionality to this utility or, alternatively, does anyone know how to do this from within WinPE 2.1 by another method?
Cheers,
Warey
#95
Posted 12 August 2009 - 07:00 PM
@ Joshua : Please share your 'Share service script'.
My Share script is here : Share.script
But it's just a beta
#96
Posted 12 August 2009 - 07:26 PM
#97
Posted 19 August 2009 - 01:48 PM
Any update as to when you might add support for enterprise encryption? Or is this something you are no longer pursuing to include in your utility?
#98
Posted 08 September 2009 - 10:42 AM
I used the PENetwork script in Joshua's Win7RescuePE project. It works fine except one little problem. It need me manually run and close the PEnetwork to obtain IP. How can I let it auto run during PE st
#99
Posted 12 September 2009 - 03:11 PM
i found some error in Your script. When building on Win7 x64, but with x86 sources it includes x64 version of PENetwork instead x86. It's probably because You check SysType. Can You please correct this or give some advice, what to change in script?
Regards,
voyteckst
#100
Posted 12 September 2009 - 08:35 PM
(I thought the "SysType" came from the OS source but I was wrong.)
In a new script version I will check the boot.wim-source install.wim-source for the WOW64 dir.
So you could try just to change the lines:
First replace %SysType% with something like %SourceArch%
Try change
IniRead,%ProjIni%,%ProjSec%,"SysType",%SysType%To
[Variables] ... %SourceArch%=x86 ... [Process] ... If,ExistDir,%InstallSRC%\Windows\SysWOW64,Set,%SourceArch%,x64
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users