[script]PENetwork
#126
Posted 26 March 2007 - 09:30 AM
But i have found an issue when you run from HDD the SystemRoot folder changes from \I386 to \MININT. But the class gets registered with
[Process-Registry]
Echo,"Adding registry entries..."
...
RegWrite,"HKLM",0x1,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","%PEdrive%\i386\system32\penetwork.exe"
A more compatible option would be to register with
RegWrite,"HKLM",0x2,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","#$pSystemRoot#$\system32\penetwork.exe"
The 0x1 also registers the entry as a normal string not as an expanded string (where the OS substitutes the %SystemRoot% with the current Windows folder....) thus the OS wouldn't be able to find
%PEdrive%\i386\system32\penetwork.exe
#127
Posted 03 April 2007 - 04:47 PM
The last weeks I had not much time to do something and also had a nose problem (was in hospital).
Cause I'm now at home for futher 2 weeks I will take a look again the next days/week.
I had some problems to get the WirelessZeroConfiguration-service run correctly.
I did some little change to the WiFi GUI part even it is not working fully now.
The hardest part is still to make it usable to connect with wireless networks - seeing is just possible.
I don't know/believe it is just the problem with the old WPA impossibility cause I can't even create/connect with a WEP network.
It seems there is missing something cause while connecting I get always an error like the "wzc service is not properly configured"...
So there seems to be more needed than I always added (like XML-support).
Oh I hate Microsoft for the not opening of the WZC-API's.
Will write again lately next week what the current state is.
@Garfield: I will test it again - thanks for info
@Thunn: PENetwork uses/creates some GDI resources, however, an option to automatically end it after network starting is a very good idea - will see how to fast I will finish the network profile using.
So long...
Holger
#128
Posted 03 April 2007 - 04:52 PM
Glad your ok.Nothing new here I just want to say - just want to notify I'm still alive
The last weeks I had not much time to do something and also had a nose problem (was in hospital).
Cause I'm now at home for futher 2 weeks I will take a look again the next days/week.
So long...
Holger
#129
Posted 03 April 2007 - 05:08 PM
Nothing new here I just want to say - just want to notify I'm still alive
The last weeks I had not much time to do something and also had a nose problem (was in hospital).
Cause I'm now at home for futher 2 weeks I will take a look again the next days/week.
Mach's gut
Peter
#130
Posted 03 April 2007 - 06:03 PM
It seems to be a good alternative for WirelessZeroConfiguration - Wireless Network Ignition. Unfortunatelly it's commercial.
One more program that is free: Boingo.
These two are universal (can be used with different WiFi adapters). But there are some drivers that also can enter WEP passwords in GUI for specific adapters.
#131
Posted 14 April 2007 - 05:58 PM
WinBuilder 68, PENetwork 009, real computer and WMVare same result =(
#132
Posted 14 April 2007 - 06:05 PM
It looks like PENetwork cannot yet handle this.Could anybody confirm no access from LiveXP to other normal WinXP network share? I'm only one have this problem?
WinBuilder 68, PENetwork 009, real computer and WMVare same result =(
I use a cmd window and manually define 'net use ...'.
That works fine!
Peter
#133
Posted 14 April 2007 - 07:27 PM
btw. What happend to Holger, havn't heared from him in a while?
#134
Posted 14 April 2007 - 10:01 PM
I'm still at home for healing my nose.
The last days I put WLAN on ice for now and instead I worked on network profiles which seems to work so far.
At the moment I'm working on a small profile editor which is also embedded in the whole autoit-script.
Here is a screenshot.
So it takes some time...
Sometimes I'm a little bit tired/feel blue cause of my allergies, I would have time but have no lust/joy.
So if the editor is ready to use (there are some little quirks that I want/have to solve first) I will publish a new script version here - I think it should be ready next weekend.
Greets
Holger
@sepa/psc: don't know about those problems cause I could always connect to other XP/Vista-shares without problems.
Did you use "domain\user" as username?
@psc: what did you then put into the cmd prompt "net use..."?
Thanks
#135
Posted 17 April 2007 - 11:24 AM
I'm sure that I already gave a reply, but it seems to be lost ???@psc: what did you then put into the cmd prompt "net use..."?
So again:
Open cmd window
Execute 'net use <Drive> <share>' e.g. 'net use Z: \\server\mydata'
That will ask you for username and PWD and finally it gives you a drive Z: with the contents of \\server\mydata
Now my primary reason to post here:
The 'My Network Places' is usually empty.
It is filled if in PENetwork.script, at the end of the [process-registry] section, you add the lines
// psc added entry to show network environment RegHiveLoad,"%HiveKey%","%TargetDir%\i386\system32\config\default" RegWrite,"HKLM","0x4","%HiveKey%\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","WebView","0" RegHiveUnLoad,"%HiveKey%"
Peter
#136
Posted 19 April 2007 - 07:56 AM
do you have any plans to make a 64-bit version of your very nice tool available?
Regards,
winpe64
#137
Posted 23 April 2007 - 10:24 PM
Profile Editor is finished and profile using is working so far.
At the moment I'm just doing some tests with the new profile using.
@MedEvil: will also change the %PEDrive% things
@Peter: thanks, will buildin it..
@winpe64: didn't thought about it yet - good idea - Autoit can detect a 64bit system but I don't know if it is possible with the same macro to detect a 64bit OS.
A lot of month ago I wrote a macro to detect if running under 64bit OS but "jpm (from the Autoit-developer team) changed it a little bit/rewrote it - I never could test it (mine and the new).
So, I think I will write a small test exe for you with just some registry/macros to test during the next days and then you could send me the results.
Here is just a small snaphot of the profile selector:
It is possible to define a countdown timer and a preselected profile.
If there is no default profile defined or is wrong then the default action is "Cancel" - so no profile is used.
So, I hope lately on friday I can publish the new script with all the changes.
So long
Holger
#138
Posted 24 April 2007 - 06:02 AM
I see youre feeling better.
#139
Posted 24 April 2007 - 10:29 AM
Great!
#140
Posted 24 April 2007 - 01:31 PM
can you please perform the following change in the begin of [Process-Registry]:
//psc removed PEDrive
//RegWrite,"HKLM",0x1,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","%PEdrive%\i386\system32\penetwork.exe"
RegWrite,"HKLM",0x2,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","#$pSystemDrive#$p\i386\system32\penetwork.exe"
I already did so in nativeEX_barebone and encountered no visible problems.
Peter
#141
Posted 24 April 2007 - 01:38 PM
Ehmm... please make that:@Holger,
can you please perform the following change in the begin of [Process-Registry]://psc removed PEDrive //RegWrite,"HKLM",0x1,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","%PEdrive%\i386\system32\penetwork.exe" RegWrite,"HKLM",0x2,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","#$pSystemDrive#$p\i386\system32\penetwork.exe"
I already did so in nativeEX_barebone and encountered no visible problems.
Peter
RegWrite,"HKLM",0x2,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","#$pSystemRoot#$p\system32\penetwork.exe"
#142
Posted 24 April 2007 - 04:26 PM
Thanks, Medevil! I corrected in my/Holger's script.Ehmm... please make that:
RegWrite,"HKLM",0x2,"%HiveKey%\Classes\CLSID\{7007ACC7-3202-11D1-AAD2-00805FC1270E}\shell\open\command","","#$pSystemRoot#$p\system32\penetwork.exe"
Peter
#143
Posted 27 April 2007 - 08:51 PM
Just let me know about (new) problems - I can fix it then on Sunday/Monday.
Greets
Holger
#144
Posted 28 April 2007 - 09:43 AM
Do you know if there is any chance of disabling the built-in qemu firewall?
#145
Posted 30 April 2007 - 11:36 PM
- Added: Simple language support for PENM(English/German included - inifiles with .lng-extension)
- Changed: GUI redesign: changed main listview to tabcontrol cause it's easier to use with language files
- Fixed: Some wrong IP settings changings effects
I think at the moment it will not really work with special unicode languages - but you can try it for yourself.
Just extract the "PENetwork.exe" and the .lng-files to one folder and take a look into them.
You have to define the language code.
By default the language is automatically chosen.
To translate it you have to rewrite ~ 240 lines for translation.
I hope that I didn't forgot to translate something - if yes, just let me know.
If there are any problems with changing some IP settings just let me also know cause I changed again some internal routines...
Greets
Holger
#146
Posted 01 May 2007 - 01:32 AM
When I started translating to Portuguese, I didn't remembered my keyboard code, so I looked up on edborg's script here:
http://edborg.boot-l...Keyboard.script - Inside others can find the most common keyboard codes.
TAddDNSAddr has typo needed to be corrected on english language
Had no chance to try it out (yet) - but please let me know if the text is correctly placed on the UI, or I will just check for myself when I'm testing the projects.
btw: also included the english text file to ease translations to other languages and renamed to .txt for double click edit.
Attached Files
#147
Posted 01 May 2007 - 08:07 PM
yeah - should be DNS instead of DSN
Thanks for info and the additional language file.
@ll:
I don't really know how to provide other language files in the future.
At the moment I will put them into the script.
Later I will maybe a choosing option to select the language you wish.
Also at the moment I do some tests with one of the new Autoit3-Beta-versions cause they are Unicode by default (can ccompiled in Unicode and ANSI).
And I will put in the inf-changing routines inside the Autoit-script cause of the possible unicode-inf-write-solution...
So if you have another language file then please post it here so I can include this.
Thanks and so long
Holger
#149
Posted 02 May 2007 - 10:24 AM
thanks for info.
I will so a check later.
Maybe it's just a fault loop.
I put the detection inside the Autoit-script so we can see more info about the detected devices like in "Hardware Detection Wizard" from Windows.
259 means that there are no more items were found in a list.
Maybe also the return value from the dection-subfunction is not reseted rightly, cause 259 is no problem so maybe I have to change it a little bit.
So I think its less a WinBuilder-script-error than an Autoit-script-error
Greets
Holger
#150
Posted 03 May 2007 - 08:26 PM
- New: compiled in Unicode-Beta-Autoit-version
- Fixed: Some language settings (GUI title, etc.)
- Fixed: Some missing translation
- Changed: Error reset if "no more items found"
- Changed: Some language dependent control settings
- Added: inf-patching now buildin cause of Unicode-Autoit-version
Forgot
- Added: the following language files are also in the WB-script: English/German/Portugese (Thanks to Nuno )
Hopefully there are not to much new errors cause now of the compiling in the new Unicode version.
Just let me know otherwise
So, everybody can also test his/her own language if it has to be special unicode file.
Greets
Holger
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users