45 replies to this topic

[TheHive]

Proposed solution: I 'fix' qemu's parameters to also use the rt8139 adapter as NIC. It will then be up to the user to put the drivers in - if he/she wants them. Any thoughts?

//martin

I didnt find the drivers you said for the realtek drivers in the BartPE, thats why I went to search for them.

If you can implement a tick to enable and add these temp Network drivers for testing under Quemu then that will allow the user to test the Network thing with Qemu. Untick that option when a person wants to include the other Real Hardware Drivers in his final Burned CD.

How would it work with VMware. Do we use our Real Hardware Drivers. If so then we can just use the Configure Network to point to the real Harware drivers. If I can find them. lol!

[Draugen]

I didnt find the drivers you said for the realtek drivers in the BartPE, thats why I went to search for them.

If you can implement a tick to enable and add these temp Network drivers for testing under Quemu then that will allow the user to test the Network thing with Qemu. Untick that option when a person wants to include the other Real Hardware Drivers in his final Burned CD.

How would it work with VMware. Do we use our Real Hardware Drivers. If so then we can just use the Configure Network to point to the real Harware drivers. If I can find them. lol!

for the rtl8139 NIC, use netrtsnt.inf and rtl8139.sys (sorry, typo). I do not want to complicate things by adding an 'unneccesary' option. Less is more!

For VMWare, you have to use the VMWare drivers. They should be available from the VMWare page (sorry, i have NO idea )

@all: i'm working on a bugfix release. stay tuned

[TheHive]

Well! we are going to be doing our main testing on our Virtual Machines so that option is not really a waist. Its more of a time saver. And the more options the more the user will be feeling like he can make changes to the final build.

Ok! I was able to find the netrtsnt.inf and rtl8139.sys this time in BartPE. Thanks!

Ill test with these drivers when you realease the update.

[Draugen]

alpha2 released!
get it here

changes:
- only error messages which are inevitable should be left
- fixed a lot of typos
- network autostart works. But not hidden.
- rambooting is SERIOUSLY farked up at the moment. sorry guys! And help is appreciated.
- added regedit
- modpe.ini now saved to %targetdir% instead of %projectdir%. This gives a nice log for troubleshootig (in theory anyway)
- plenty of other things i can't quite remember cuz i'm tired and its late.

regarding network autostart: i use hidec to hide the network start scripts. hidec by itself (i.e. not as shell) works fine. but when i use hidec to call netstart.cmd, i get an lsass.exe error and a reboot loop (which means the shaell failed to start). Any thoughts as to why this happens?

networking and qemu/other VMs: i have not had success with qemu and enabling the rtl8139 nic yet. will try and figure it out for 0.0.3. The NE2000 card IS implemented by default in qemu, i just cant find the inf file.

and TheHive, you are wrong regarding more options. too many options is confusing and overwhelming (yes, i am stating this as fact, not opinion). Of course, options are neccesary (boring world otherwise), but in computing/programming/ui design, they also need to be relevant. And supporting every VM known to geekdom with network drivers IS irrelevant.

Sorry if I come across a little bit hard, TheHive. This is not intentional (i'm actually not ranting ). Just stating a fact and explaining my decision based on that fact. I know you are a designer, not a programmer, so no hard feelings

//martin

[TheHive]

changes:
- network autostart works. But not hidden.

For beta testing that is ok.

- rambooting is SERIOUSLY farked up at the moment. sorry guys! And help is appreciated.

Im not testing that yet. Not until a more stable ModPE is released.

- added regedit

Cant see, but ill take your word.

networking and qemu/other VMs: i have not had success with qemu and enabling the rtl8139 nic yet. will try and figure it out for 0.0.3. The NE2000 card IS implemented by default in qemu, i just cant find the inf file.

So i shoulnt expect Internet access Qemu right now.

and TheHive, you are wrong regarding more options. too many options is confusing and overwhelming (yes, i am stating this as fact, not opinion). Of course, options are neccesary (boring world otherwise), but in computing/programming/ui design, they also need to be relevant. And supporting every VM known to geekdom with network drivers IS irrelevant.

Have to disagree with that comment. Its not a fact. I agree with the gui needs to be relevant and usefull. I wasnt asking to support every VM Network driver. Just to implement the option to have the Network Driver option to wether to use the Nic Drivers for Qemu or not. Since Qemu is the VM we are mainly using to test all our projects. I was just asking what drivers I could use for VMware. My real hardware ones or some others. I had the impression that your network stuff was working on your side.

Actually more options are good. The thing is that the default options that the author makes to his program or Gui options should work out of the box. This is not possible sometimes with this type of Project because the user just needs 3 things to really configure to get these thing going. The Correct XP CD location, the BartPE folder, and the Network Drivers. The rest is on auto and should work.

But authors should include more options for those that like to tweak things even more. So far you have added alot of options to tweak things. So thats why im not asking for too many options to be added. Just 1 or 2 so far I think.

Sorry if I come across a little bit hard, TheHive. This is not intentional (i'm actually not ranting ). Just stating a fact and explaining my decision based on that fact. I know you are a designer, not a programmer, so no hard feelings
//martin

Well you can come acrross hard . Its not a big deal. I will still test the Scripts . As long as you explain things and the direction your taking this project, it should be ok if we have a differece of points . Your facts are not always true .



Now for some testing of the new release.

[TheHive]

Im finding that you have to restart WinBuilder at times when you run the Scripts. It seems to freeze the Run buttom and so you can olny shut WinBuilder down and restart. You can still move within Winbuilder, you just cant use the RUN, Refresh buttons.

ON first test. It seems to recognize the Drivers you mentioned. My Firewall asks if I want to give something net access. It takes a while for me to do so. When I do let it Net access. The Processing of the Script Stops and freezes. Then I get the TXTSETUP.SIF

Log


Will test further.

[TheHive]

I tried using the same Network driver from yesterday and see if that helps but Im getting the same TXTSETUP.SIF
error result.

I ran the Scripts from yesterday that worked and Im getting the same TXTSETUP.SIF
error results

Be back. Let me restart PC.

[TheHive]

Even if I dsable the firewall I still get the same error. Is there some internet downloads happening or something?

[TheHive]

Put my firewall backup. Tried again after a while and Weired all of sudden its running and downloading the rest and its bootting up qemu.


Log



Qemu Error.



Testing Stoped.

[Draugen]

are you sure you are using the correct modpe pack?

you need to get the 7z.file and unpack it. Using the update function in winbuilder won't work - beacause of how i've done things.

You see, you have messages in your log which should be gone by now...

[TheHive]

Hehe! I was testing ModPE_0.0.1alpha
lol

Can you put this at the top of you first post.

2006-09-01: alpha 2 out. get it here.
Changes here.

Will test it right now.

I remember now i got the download from the top link
get it here! (unpack into \Winbuilderdir\Projects).

It told me to get it here so i did.

[TheHive]

Default display settings should be 800 by 600.
I see the Regedit now. lol!

Had to activate most scripts.
Also had to change the Create RAM boot ISO to Create ISO

Location of your WIndows Install Files is more undertandable.

We still need to tell people to use the
BartPE source in the Windows Paths Tab - Source Directory

This time i dindnt see anything freeze. After selecting the options I wanted. It seemed to build ok.

Problem when it started to boot up. Now you get a black background.
File \i386\system32\ntoskrnl.exe could not be loaded
The error code is 14


Mod PE Log

[pscEx]

I tried version 002.

Still some errors:

Hardcoded path of your develop environment:

#352 [Failed] FileCopy - Failed to copy [F:\Unattended\qemu_nic\*.inf] to: [V:\BCD\cds\XPP_DE_SP2\i386\inf]
#353 [Failed] FileCopy - Failed to copy [F:\Unattended\qemu_nic\*.sys] to: [V:\BCD\cds\XPP_DE_SP2\i386\system32\drivers] #354 [Info] Setting hostname to 'ModPE'

And some others

#364 [Failed] FileDelete - Failed to find and delete [%BaseDir%\Projects\modpe_0.0.2alpha\Target\i386\system32\Readme.txt]
#387 [Failed] FileDelete - Failed to find and delete [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\menu.rc]
#388 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\backgrounds]
#389 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\docs]
#390 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\fonts]
#391 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\plugins]
#392 [Failed] FileCopy - Failed to copy [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\styles\0505 all blue\070_blue] to: [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\styles]
#393 [Failed] DirDelete - Failed to delete directory [%BaseDir%\Projects\modpe_0.0.2alpha\Target\Programs\bbLean\styles\0505 all blue]
#403 [Failed] INIRead - Failed to read value from: [%BaseDir%\Projects\modpe_0.0.2alpha\Target\modpe.ini] Section: [network] Key: [autostart] to variable: [%net_autostart%]

Iso boots into the initial blue window, then a message about a lsass error appears, reboot ....

Peter

[Yorn]

Attached is the 7zip SFX files I was talking about.

Attached Files

•  7zipsfx.zip   100.86KB   464 downloads

[Draugen]

@all: modpe_0.0.2alpha2 released. Most annoying mistakes squashed. see top post.

Default display settings should be 800 by 600.
I see the Regedit now. lol!

Had to activate most scripts.
Also had to change the Create RAM boot ISO to Create ISO

Location of your WIndows Install Files is more undertandable.

We still need to tell people to use the
BartPE source in the Windows Paths Tab - Source Directory

This time i dindnt see anything freeze. After selecting the options I wanted. It seemed to build ok.

Problem when it started to boot up. Now you get a black background.
File \i386\system32\ntoskrnl.exe could not be loaded

All scripts are now active. And RAM boot iso is disabled.

Glad 'windows install files' was easier to comprehend and i DO tell ppl to set bartpe as their source.

strange error though...

I tried version 002.

Still some errors:

Hardcoded path of your develop environment:

And some others
Iso boots into the initial blue window, then a message about a lsass error appears, reboot ....

Peter

Fixed the hardcoded paths.

those bblean filedelete errors are odd. I don't get them. and the commands all seem fine.
same for the filedelete errors after cab compression. i seriously had no errors at my dev environment when releasing this. Really weird...

Attached is the 7zip SFX files I was talking about.

thanks!

[TheHive]

Its Easier to get the newest scripts now. :ok:

I like that you are calling it by the ModPE and the Version number within Project Name. Helps to maintain it better and not loose which version your Testing.


An auto delete target contents is really needed. Specially when there are contents from other Projects.

Suggestion:

Source Directory
%BaseDir%\BartPE

Target Directory
%BaseDir%\Target

ISO file
that seems to be set properly.


After setting all the folders it does its thing and processes and downloads what it needs.

Launches Qemu then I get the same
File \i386\system32\ntoskrnl.exe could not be loaded
The error code is 14

Log



Before I forget:
Rough sketch of idea. Sleepy

[Draugen]

ModPE already clears the target folder automatically. always has. just like micrope did.

Re your suggestion - you like critiquing the size of my spoons don't you

OK, i'll use a bigger one. but not quite so big i don't think.

//martin

[TheHive]

ModPE already clears the target folder automatically. always has. just like micrope did.

Ok! Thanks!

Re your suggestion - you like critiquing the size of my spoons don't you

Untill we get a reasonal and easy way to run your project and get a good build.

OK, i'll use a bigger one. but not quite so big i don't think.

//martin

The size doesnt have to be as big as my suggestion. Its just so you can see what I changed. Just to give and idea. The format implemented is is up to the author. Maybe instead of Note. Lets try Requirements.

[Brito]

Have you made any further progress on modPE?

[wideglide]

Initial test run of ModPE worked fine for me.
used a Win2K3 build, selected file sharing client and deselected start at bootup.

when I ran the netstart batch file, it processed without error, but posted two error messages because each batch file ends by displaying the error message. netstart and msclient probably need an exit so that they don't display an error message by default.

net drivers worked fine in qEmu and I was able to use a shared drive... only had to initiate msclient via bartpe manually as that was not included in the batch file...
I will test alternative runs soon. Good job!

[Draugen]

Sadly, no. I've had visitors over for a lanparty this weekend, wich led to me wrestling with windows 200 and trying to get a working install. Still no luck actually

I'll also be away for the weekend, but i'll se what i'll do. I have a lot of travelling to do as well... may have time to hack something out on the laptop.

//martin