How to run LiveXP in RAM

I am trying to make an LiveXP CD to run from RAM, been trying to do it for three days, just could not do it. The aim is to run .net 2.0 apps.(using script:.NET Framework 2.0 SP2 32-bit by Henshaw) I've done Google search(unfortunetly couls not find a search on this forum), read a lot of forums(this one and 911CD, etc) still could not figure out.

In Live XP I've enabled:
1. Components -> Core -> 1 System -> All IE06 related script
2. Drivers-5 RAMdisk->FiraDisk. Downloaded latest .zip from website, user "Custom" and "Manual ->x86" option
3. Finish -> Create Image -> Boot SDI

When I run the project, it give me Winbuilder error: unable to insert an item. I reboot PC, it fix that this problem, but it does not creat an ISO, it just create empty RAM\i386 folder under the default ISO folder.

I've used VistaPE/MultiPE/Win7PE frequently,very easy to set run PE in RAM, if anyone could point me to right direction would be very much appreciated.

I would like to attach some screen shot, but do not know how to, unless I have a website to host the image first.

Edited by oopsboy, 16 May 2011 - 07:06 AM.

Hi.
There is a help button in the BootSdi script.
From that help:
“Simple Instruction for Rookie User:
Enable "Basic\Build\9 - DefineBootsector.script" (DefineBootsector) ==> Select Grub4dos
Enable "Drivers\5 Ramdisk\vFiraDisk.Script" (FiraDisk)
Enable "Finish\2 Create Image\BootSDI.script"
Make your build (Big Blue Play Button)”

Perhaps the above will help?
Good luck!

Thanks, it worked and created an ISO.
But I do not like GRUB4DOS, so I am trying \Drivers\5 RAMDISK\W2k3_RAMDISK script, it has a lot of errors, I modified the script, and hope it works, will report back.

Thanks, it worked and created an ISO.
But I do not like GRUB4DOS, so I am trying \Drivers\5 RAMDISK\W2k3_RAMDISK script, it has a lot of errors, I modified the script, and hope it works, will report back.

Well, until Firadisk was developed the Server 2003 SETUPLDR.BIN and MS Ramdisk did work allright, with the limit of 512 Mb of size......I would presume that the changes you are making are unneeded .

And it's not like you have to like or not like grub4dos, you can make it "invisible" allright.



Wonko

Could not get rid of GRUB4DOS, not working, and bootsdi script screwed up the project. If I run the porject without it, the finished ISO would have problems when booting, it will report missing dlls.

I am trying W2K3 SP2 as source, see if I have any luck to get rid of GRUB4DOS, just because I only need to boot into Windows PE. Don't get me wrong, GRUB4DOS is great if you need some advanced boot options.

Edited by oopsboy, 16 May 2011 - 03:33 PM.

Guess what, the .net 2.0 script does not work with W2k3 as source. Error message:
(.NET Framework 2.0 SP2) CopyOrExpand - Failed to copy [D:\WindowsPEs\WindowsSource\w2k3sp2\I386\winhttp.dl_] to: [%BaseDir%\Target\LiveXP\I386\System32\winhttp.dll]: The system cannot find the file specified.

and indeed winhttp.dl_ doesnot exist on the W2K3 DVD.

BTW, the Server 2003 SP2 version of the ramdisk booting related files have been reported to be flawed.
Please read this seemingly unrelated thread:
http://reboot.pro/4952/
particularly this:
http://reboot.pro/4952/page__st__2


Wonko

Could not get LiveXP boot into RAM without GRUB4DOS, the bootbdi needs GRUB4DOS!
Anyone knows?

Here is the log

Run - Processing section: [SetupBootScripts] From file: [%BaseDir%\Projects\LiveXP\Finish\2 Create Image\BootSDI.script]
SetVar - Sucessfuly changed the value of [%allok%] to: [false]
IF - [] is not equal to: [true] evaluated string: [if,%RamDiskSysBoot%,equal,true,If,%SystemFolderName_ScrollBox%,Equal,i386,If,%Non2k3Loader_Compress_gz_checkBox%,Equal,false,Begin]
[Run,%ScriptFile%,Winnt-sif-create]
[Set,%allok%,true]
[End]
IF - [true] is equal to: [true] evaluated string: [if,%ImageBoot%,equal,true,Begin]
IF - [bootsect.bin] is not equal to: [grldr] evaluated string: [if,%BootLoader%,equal,grldr,Begin]
[If,%pCheckBox10%,Equal,false,Begin]
[If,%Non2k3Loader_Compress_gz_checkBox%,Equal,True,Run,%ScriptFile%,add-firadisk-menu.lst,NTLDR,RemoveDefault]
[Else,Begin]
[If,%RamDiskSysBoot%,equal,true,Begin]
[If,%SystemFolderName_ScrollBox%,Equal,i386,Run,%ScriptFile%,add-firadisk-menu.lst,NTLDR,Prepend]
[Else,Run,%ScriptFile%,add-firadisk-menu.lst,NTLDR,RemoveDefault]
[End]
[Else,Run,%ScriptFile%,add-firadisk-menu.lst,NTLDR,RemoveDefault]
[End]
[End]
[Else,Set,%allok%,false]
[End]
[End]
IF - [false] is equal to: [false] evaluated string: [if,%allok%,equal,false,Halt,"The combination of options chosen will not work. Please click on 'BootSDI Options Help' button to know more about feasible options"]
The combination of options chosen will not work. Please click on 'BootSDI Options Help' button to know more about feasible options
Run - Processed section [SetupBootScripts] in file: [%BaseDir%\Projects\LiveXP\Finish\2 Create Image\BootSDI.script]

BTW, the Server 2003 SP2 version of the ramdisk booting related files have been reported to be flawed.
Please read this seemingly unrelated thread:
http://reboot.pro/4952/
particularly this:
http://reboot.pro/4952/page__st__2


Wonko

This thread is very simple to understand, it is talking about BartPE, I suppose LiveXP just same as that.

Here is link to Download W2K3 SP1. To extract the files from W2K3 SP1, run the downloaded .exe file with "-x" switch in command line.

This thread is very simple to understand, it is talking about BartPE, I suppose LiveXP just same as that.

Yep , no matter which builder you use, the "final result" is anyway a PE 1.x.

The TWO threads by aec have all the info about WHAT is needed/HOW it works (as opposed to the "select this, press this other, let Winbuilder do it" approach, which is very nice and useful when it works - most times unless the users fiddles with it - but that provides very little or no information ont WHAT/HOW )


Wonko

Oh well, new discovery on the LiveXP project(LiveXP_20100908_Official_3_Complete_v888.rar). To load into the RAM actually included in the CreateISO.script.

The interface include all the settings to configure it, just because lack of documentation, I had wasted around 60-80 hours and others. I really believe WINBUILDER/PROJECT seriously SUUUUUUUUUUCKS when comes to documentation. A WIKI is needed for all project scripts.

The problem is simply, we have very, very few developers and nobody pays for use of WinBuilder projects, so we all have to have a daytime job, next to doing development and support here.

But if you like to show your appreciation and say thank you, by given something back to the community, your valuable sparetime, we're more than happy to accept it.

May be some addon features for Winbuilder. I usually having problem to understand scripts include in various project. Would like each project has a wiki site, and each script would include a link to wiki topic. Suggested implementation:
1. Include a variable in project.ini as WIKI root.
2. Include a variable in script's ] section as relative/absolute url to the wiki.
3. Maybe a GUID for any script, so a script can reference a dependency script or a control or variable in it

That way everyone could help to write the document.

Other suggestion is to find a COMMERCIAL manager to manage this website and give him a cut for any money make from this website. The tool can go commercial one day and everyone of you can make some money and retire.

Sure we're making tons of money off this site, but instead of putting it in our own pockets and doing, what we love, development full time, we rather give it to someone else and keep working some other job, while doing development in our spare time.

Can you still see reality from your place or is it already behind the horizon?

Not getting into any argument, any successful product takes money to develop, with money you can have better product(like better infrastructure, develop wide community,etc). And money is worse than MedEvil if it is not proper managed. You may get someone developing for fun, but it is pretty hard to find some to manage other people's money for fun, :-).

Sorry about my previous post.
You didn't rightfully deserve that. Your post was just the the straw that breaks the camel's back.

Oopsboy’s concerns are entirely valid. I am fully aware that the Reeboot site has a wealth of information hidden within it, all due to the hard (non profitable) work that it’s leading members do in their spare time on a “hobby” basis.

Winbuilder is a great kit, but is very unforgiving when announcing strange error messages without any hint, or going through the majority of the build before failing (see Microsoft!). From a new member (or visitor’s) point of view, one of the main problems with the Reeboot site is that in trying to find the answer to an already answered question, the number of hoops you have to jump through using the site navigation or on-page links is often frustrating.

Many of these links often only have very basic instructions, placed between member’s rants, raves & opinions of often only semi-relevant (or side-tracked) information. Tutorials on common subjects, with a main reference page, do not seem to exist in a structured & accessible fashion. This posting is not intended as a downer to all those who clearly strive so hard to consolidate information that would not otherwise be available, but as a suggestion that with a bit of management, organization & professionalism (get rid of the childish “mood gif’s”) Reeboot could be as shiny as JacLas Wonko’s shoes!

Best Regards
Jet Junk Jiver

Reeboot could be as shiny as JacLas Wonko’s shoes!

Hmm.

I have seen better comparisons...




Wonko

Tutorials on common subjects, with a main reference page, do not seem to exist in a structured & accessible fashion.

Ok, would you be willing to help us solve this situation?

As MedEvil mentioned, our resources are scarce and depend on volunteer effort.

We already have a tutorials section: http://reboot.pro/forum/31/

Would you be available to write the articles that may help solving these doubts from users?

... been trying to do it for three days, just could not do it. The aim is to run .net 2.0 apps.(using script:.NET Framework 2.0 SP2 32-bit by Henshaw)...

I don't understand if your problem is succeding in creating a LiveXP CD that boots entirely from RAM or
making a RamBoot CD that includes some dotNet framework version.


The last script version (v6.2) was intended for creating a .Net LiveXP CD without the need for a dedicated
RamDisk Drive by using FBWF to allocate some cache (max 1GB) onto the CD to make it virtually writable.
In reality, the cache is a RamDrive mapped to the physical CD. Making a RamBoot System using v6.2
means creating a RamDisk on a RamDisk. However, that should not be the real issue.

Try a step-wise debug:

• try to make a RamBoot CD without dotNet. If you succeed in that, then
• simply put in the net framework 2 script as an add-on. If that does not work, then
• delete "fbwf.sys" and "fbwflib.dll" from your "Target" folder before creating your disk.

If none of the above works, then I will rob some time and go back to that script.