aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 7, 2012 16:34:55 GMT -5
Dear Brian, I don't think we have deeper issues than the Registry. As I told you before the RAW version 1 of the fireBwall script fully works in my machine, but as I have already told and you have already confirmed it we need to implement generic Registry entries for the internet adapters. I can confirm that fireBwall worked in my PE build with the script I've provided you. I have even tested fireBwall inside my PE at ShieldsUP! ( www.grc.com/x/ne.dll?bh0bkyd2) and it worked like a charm! Best regards, Aeolis
|
|
|
Post by schizo on Apr 7, 2012 17:17:24 GMT -5
Oh ok, I didn't know that. What's strange is that Windows generates a lot of the entries I removed automatically on boot, but fireBwall still doesn't see the adapters. I'll have to try modifying your original script with my values to get it to install on my end. Do the registry hives exist in the PE before it runs? Or is there something that loads default values, then the scripted values are added to the hive on run? Or does the script edit saved hives in the PE's iso?
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 8, 2012 7:07:00 GMT -5
Dear Brian,
The way I have wrote the script make WinBuilder create the Registry entries during build time so those Registry entries will be available when the PE boots up. But, there are ways of adding Registry entries during boot time too.
Best regards,
Aeolis
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 8, 2012 14:09:46 GMT -5
Dear Brian, I did it! After a lot of research! I send you attached to this post the solution. I have tested it under x86 not x64 yet, but the solution is supposed to be the same. Unpack the .zip file and run after the PE boot process the Install_x86 or Install_x64 depending of the build you are using. It will register and run WinpkFilter driver and service as well as it will integrate it with the available Internet adapters. Basically we have to run a .bat file with the following commands: COPY ndisrd.sys %SYSTEMROOT%\System32\drivers snetcfg.exe -v -l ndisrd_lwf.inf -c s -i nt_ndisrd Due to the nature of the drivers installation of PE environment we should put a delay on this bat file avoiding it trying to install the filter into adapters before they get recognized by the driver installation. Best regards, Aeolis Attachments:
|
|
|
Post by schizo on Apr 8, 2012 14:50:08 GMT -5
AWESOME! About to test it out.
|
|
|
Post by schizo on Apr 8, 2012 22:21:40 GMT -5
aeolis, I'm close to an all inclusive script. It runs the batch files for the right architectures on boot(I modified the batch files a bit for it), All the files are embedded in the script, I'm just going to take out the source folder part because I see no reason not to include the binaries right in the script. We can make scripts for modules/themes/etc after we finish this part up.
|
|
|
Post by schizo on Apr 8, 2012 22:50:52 GMT -5
This is what I have right now, give it a try. Attachments:
|
|
|
Post by schizo on Apr 12, 2012 2:51:31 GMT -5
Aeolis, I'm using this with Win7PE_SE, and if fireBwall starts before the network script, it dies. Anyway we can make it wait for the auto boot?
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 12, 2012 15:41:33 GMT -5
Dear Brian,
I am working on it. We have to create a delay using sleep command, for instance, or use a more elegant solution using a if and the tasklist command to run the script only after the driver loader finishes its job. More on weekend. During week days I don't have time to work on that because of my real job.
Best regards,
Aeolis
|
|
|
Post by schizo on Apr 12, 2012 18:15:48 GMT -5
I'm currently trying to figure out how to include the basic webcam drivers in my PE, because I want to run it on my netbook, and I mostly use it for its webcam.
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 14, 2012 8:05:14 GMT -5
Dear Brian, I suggest you go here: driverpacks.net/driverpacks/latest and download the appropriated drivers in your case (webcam, windows version and architecture). After that decompress them and put them inside the appropriate folder in the Driver Integration script on WinBuilder. Best regards, Aeolis
|
|
|
Post by schizo on Apr 20, 2012 22:55:16 GMT -5
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on Apr 22, 2012 16:46:11 GMT -5
Dear Brian,
Please, wait a little longer. Don't release it right now. I am working on a AutoIt launcher for fireBwall under PE's.
Best regards,
Aeolis
|
|
|
Post by schizo on Apr 22, 2012 23:07:51 GMT -5
Ok, the file is still up on the server, but there's no link to it, so its not really advertised. Let me know when you are happy with it, you know the PE community way better than I do. -Brian
|
|
aeolis
New Member
Resident PE Expert
Posts: 18
|
Post by aeolis on May 5, 2012 14:26:01 GMT -5
Dear schizo, This is the latest version of the script. Please, test it out. Do not post it to public yet, it has bugs. The main problem now is to keep fireBwall.exe alive because after it is launched it closes after a few seconds without user intervention. It seems that fireBwall.exe in its first run loads as dummy. It is there, but does nothing. I need you help debugging why is it happening. The AutoIt source code for fireBwall launcher is inside the zip file. Check it if you want. Best regards, Aeolis Attachments:
|
|