132 replies to this topic

[pscEx]

I embedded the VMWare.Script in its own (beta) project and stored it on the nativeEx server.

To get it:

• Create an empty folder, named on your choice
• Copy WinBuilder 072 or 072a into it
• Start WinBuilder and go to the Download tab
• With WB 072 create the server nativeex.boot-land.net, with 072a it is already included
• Unselect all servers besides nativeex.boot-land.net
• Choose download type 'Beta'
• Unselect all projects besides nativeEx_moa-lite
• Do the download

First run:

• Run the project
• In the path wizzard, define your source CD. This must be W2003
• Continue
  The project now will download the 'normal' nativeEx scripts and programs and add them to the project.
• As the message box tells, exit and restart WinBuilder
• Navigate to VMWare player and extract the needed files from the Player setup

Normal run:

• Run the project

This will finally end in VirtualBox running the PE. If you do not have VirtualBox installed, select qEmu as emulator.

Peter

EDIT:
In MOA\vmstart.cmd you must adjust the localgroup 'administrators' to the language of your source CD.
Delivered is German.
Of course, that is beta, in the final version this will be 'native'

Edited by psc, 08 November 2007 - 08:42 AM.

[TheHive]

Quick test

You need to agree to the VMmanager ULA so it can process the script
The user needs to know that they need to have downloaded the "VMware-player-2.0.1-55017.exe" which around 172MB.
In the Finish Options why not have the Option to Run final ISo in VMware.

All the time I have at the moment. Have not built it yet. Will try latter tonight.

[pscEx]

The user needs to know that they need to have downloaded the "VMware-player-2.0.1-55017.exe" which around 172MB.

Thanks! I'll add

In the Finish Options why not have the Option to Run final ISo in VMware.

The emulator test in this case can only check whether the ISO boots. Running VMWAre Player in an emulator is not (yet) possible.
Real debug / use must be made with burned CD.
Therefore I only added these two popular emulators; I also did not include M$ VirtualPC.

Peter

[TheHive]

Requirements
WinBuilder 072 or 072a
VMware-player-2.0.1-55017.exe , Size around 177MB , When extracted, its around 246 MB
Windows Server 2003 SP1
Web address to nativeEx_moa-lite Project: nativeex.boot-land.net

Note:
In MOA\vmstart.cmd you must adjust the localgroup 'administrators' to your language.
Delivered is German.
Of course, that is beta, in the final version this will be 'native'

[*]You will have to Navigate to the VMWare player Script, In Winbuilders "Scripts" Tab, and extract the needed files from the Player setup VMware-player-2.0.1-55017.exe


Lets get Started:

I embedded the VMWare.Script in its own (beta) project and stored it on the nativeEx server.

To get it:
[*]Create an empty folder, named on your choice
[*]Copy WinBuilder 072 or 072a into it
[*]Start WinBuilder and go to the Download tab

Ok!

[*]With WB 072 create the server nativeex.boot-land.net, with 072a it is already included

In the "Download Tab" use the "Add New Web Server" button to add the " nativeex.boot-land.net " server, with 072a the server should already be listed in the "Available Web Server" list.

[*]Unselect all servers besides nativeex.boot-land.net

[*]Unselect all projects besides nativeEx_moa-lite, you can keep the Tools selected

[*]Choose download type 'Beta'

[*]Choose download type 'Beta' , Normally its set as "Recommended"

[*]Do the download

[*]Run the project
[*]In the path wizzard, define your source CD. This must be W2003
[*]Continue
The project now will download the 'normal' nativeEx scripts and programs and add them to the project.
[*]As the message box tells, exit and restart WinBuilder

Ok!

Important:

[*]Navigate to VMWare player and extract the needed files from the Player setup

[*]Navigate to the VMWare player Script, In Winbuilders "Scripts" Tab, and extract the needed files from the Player setup VMware-player-2.0.1-55017.exe

Suggestion: Include someway to make sure that Vmware Player is installed before building project even though you have supposvily extracted the contents of Vmware Player. Because I built the project without installing, or extracting the Vmware Player. Because earlier in the morning when I downloaded the Project and hit the extract button I had to hit the Cancel button to cancel the Extraction of the Vmware Player because I had to leave. I came back later that night and ran the project without a warning that I did not have Vmware Player Extracted.

[*]Run the project

ok!

This will finally end in VirtualBox running the PE.
If you do not have VirtualBox installed, select qEmu as emulator.

Qemu should be the default Emu, Since some will not have VB installed.





Testing

[pscEx]

Thanks, TheHive

That shows that with this new way of download at least technical the project can become runnable.

I'm going to bring your additional hints into the project.

Peter

[TheHive]

During build I received this prompt. Target Z is not found.

[pscEx]

During build I received this prompt. Target Z is not found.

There is something wrong with vdk.

Please post the log.

Peter

[TheHive]

 log.rar   26.46KB   650 downloads

When I first ran it and I did not have Vmware Extracted I did not get that error from the build.
i was able to boot from Ram.

It seemed that when I extracted the VM Player contents and then build the build I get this error in the Final stage of building the SDI.

No errors when processing the VmPlayere Script.

[MedEvil]

Just out od curiosity, how big is a nativeEX_moaLite without any vm hdd image?

[pscEx]

 log.rar   26.46KB   650 downloads

When I first ran it and I did not have Vmware Extracted I did not get that error from the build.
i was able to boot from Ram.

It seemed that when I extracted the VM Player contents and then build the build I get this error in the Final stage of building the SDI.

No errors when processing the VmPlayere Script.

The log does give a hint on any troubles with drive Z:

Shellexecute: [Hide] using: [fsutil.exe] with parameters: [file createnew "%BaseDir%\ISO\Ram\i386\BootSDI.img" 132120576]
Shellexecute: [Hide] using: [%BaseDir%\Projects\Tools\vdk\vdk.exe] with parameters: [open * "%BaseDir%\ISO\Ram\i386\bootsdi.img" /rw /p:0 /l:Z:]
Shellexecute: [Hide] using: [format.com] with parameters: [Z: /FS:NTFS /V:BootSDI /C /X /force]
Shellexecute: [Open] using: [%BaseDir%\Projects\Tools\zCopy.exe] with parameters: ["%BaseDir%\Target\moa-lite" Z: ]
Shellexecute: [Hide] using: [%BaseDir%\Projects\Tools\vdk\vdk.exe] with parameters: [Close Z:]

Are you eventually running out of hdd space?

I'll try to build like you did

• w/o VMware player
• extract player
• build again

Peter

[pscEx]

Just out od curiosity, how big is a nativeEX_moaLite without any vm hdd image?

VMWare Player has around 250 MB.
So with BootSDI and compressed image it will be around 140 MB.

If this size hurts your ideas, nobody forces you to use the project.

Peter

[MedEvil]

If this size hurts your ideas, nobody forces you to use the project.

Thanks, i wont!
When i read the size of the VMWare plaer package, i was just wondering if you just use a small portion of it or all.
Why don't you use one of the smaller VM?
What is needed that VMware has, that the other don't?

[pscEx]

Thanks, i wont!
When i read the size of the VMWare plaer package, i was just wondering if you just use a small portion of it or all.
Why don't you use one of the smaller VM?
What is needed that VMware has, that the other don't?

As the name of the project (and this forum) tells, I'm working with sanbarrow on running his MOA in a WinBuilder created PE.

And in his MOA VMWare is a fundamental part.

BTW: It is one goal of the beta, to eliminate all unnecessary files.

Peter

[MedEvil]

And in his MOA VMWare is a fundamental part.

That question was more directed into sanbarrows direction than yours. Maybe i should have made that more clear.

[sanbarrow]

@ Peter

Running VMWAre Player in an emulator is not (yet) possible.

Thats not correct - you just need a fat host with Intel VT support or AMD pacifica - then you can test moa-lite inside a VMware-VM.

For Intel Vanderpool add :

monitor_control.restrict_backdoor = "TRUE"
monitor_control.vt32 = "true"

For AMD pacifica add:

monitor_control.restrict_backdoor = "TRUE"
monitor_control.enable_extended_svm = "true"

to the vmx-file of the test-VM.

I created all my MOA-videos running a VM in a VM - performance is quite usable.


@ MedEvil

The biggest part of the VMware-package are the vmware-tools for Linux-guest and the other isos for guest-additions.
The core-part - needed to run VMs - is about 40 MB only

[pscEx]

@ Peter

Running VMWAre Player in an emulator is not (yet) possible.

Thats not correct - you just need a fat host with Intel VT support or AMD pacifica - then you can test moa-lite inside a VMware-VM.

Thanks, but I'm not a proud owner of such HW.

I changed the above post to

Running VMWAre Player in an emulator is not (yet) possible with my hardware.

Peter

[MedEvil]

@ MedEvil
The biggest part of the VMware-package are the vmware-tools for Linux-guest and the other isos for guest-additions.
The core-part - needed to run VMs - is about 40 MB only

That sounds more like a usable size for a VM.
Thanks for the answer.

[pscEx]

VMXBuilder now works in the PE!


To get the new version of nativeEx_moa-lite, go to WinBuilder's download manager and look for new nativeEx_moa-lite files.
Should be:

• !CheckTools.Script
• VMXBuilder.script
• updateCore.Script

You do not need to start with a new folder again. Just download and start.
When asked, restart WinBuilder.

VMManager.script is not needed any more.
You may remove it.

Peter

[pscEx]

I'll try to build like you did

• w/o VMware player
• extract player
• build again

@TheHive,

I tried the procedure above.
First pass of course with 24 errors (trying to copy non-existent files), but ISO booted fine (w/o having VMWAre Player)
Second pass booted fine, VMWAre Player came up (and crashed of course my VirtualBox, when it started to create the VM).

Can you watch your installation and if something strange happenes, post here?

Thanks.


Peter

[TheHive]

I am running out of space and will try the build on another partition that has a bit more.

Testing downloading from scratch. Will have to start later tonight, have to go.

[pscEx]

I am running out of space and will try the build on another partition that has a bit more.

Testing downloading from scratch.

Thanks, TheHive

That shows me that my bug-hunter features are still up to date

Are you eventually running out of hdd space?

Peter

[TheHive]

I was able to do a clean Download and replay the build after extracting the Vmware player and Specifying the Win2003 Source Path.



The MyDocuments Icon is missing
The Update thing Vmware Player comes up.


Question:
Does the Vdk Driver install itself to my computer? Or does it use the one in the Tools forlder as is.


Still testing

[pscEx]

Does the Vdk Driver install itself to my computer? Or does it use the one in the Tools forlder as is.

Vdk is used by BootSDI.Script.

If there is vdk installed on your PC, this one is used.
Otherwise the vdk from the %Tools% folder is used.

Peter

[sanbarrow]

Peter - I thought about the net user cmds ...

Original moa doesn't need a localized version of

REM net localgroup administrators /add system
net localgroup Administratoren /add system

because I use a renamed admin-account.
In moa the admin is always "moon"

That still leaves the question wether it is easier to localize that cmd or use a larger sam-patch like I do ???

Ulli

I am still ill - so don't expect more testing today

[pscEx]

Peter - I thought about the net user cmds ...

Original moa doesn't need a localized version of

REM net localgroup administrators /add system
net localgroup Administratoren /add system

because I use a renamed admin-account.
In moa the admin is always "moon"

That still leaves the question wether it is easier to localize that cmd or use a larger sam-patch like I do ???

Ulli

I am still ill - so don't expect more testing today

I would prefer the 'moon'.
In none of the source CD files the name of the adminitrators group is clearly defined.
(Or I did not find yet)

Peter