86 replies to this topic

[smiley]

I have modified the original windowsramboot.script which didn't let you to boot from ram using xp.
The new version is merged with the create ISO script for better functionality

This version needs to specify the path of the Windows 2003 setup or a folder that contains the files setupldr.bin and ramdisk.sy_ from the Windows 2003 setup

Get it here

[TheHive]

So in order for this to work. Are you saying we need Our XP SP2 CD. Then if we have the ramdisk.sys & setupldr.bin from Windows 2003 Server we could just Create a Source Folder that we extract the contents of our Windows XP SP2 to a folder and then create a folder named rambootin within that XP sp2 source and put ramdisk.sys & setupldr.bin in the rambootin folder , then we can use that to Create a Bootable RAM.

Why not make it easier. Create the Script where we can Browse and choose what folder contains those two ramdisk.sys & setupldr.bin Windows 2003 Server files but Still use our WindowsXP Sp2 CD as the main source.

[smiley]

I have tried to make what you suggest but everytime i created a filebox, everything else disapeared. I'll try to make it only with a textbox

[TheHive]

Let me try this out see how it goes.


Replaced the
Archive\Tweaks\WindowsRamBoot.script

with yours.

Extracted all Windows XP SP2 CD contents to its own folder then created rambootin and place those two files. Used this folder as the source.

Source LAyout
------------------
DOTNETFX
I386
rambootin
SUPPORT
VALUEADD
AUTORUN.INF
README.HTM
SETUP.EXE
SETUPXP.HTM
WIN51
WIN51IP
WIN51IP.SP2
DOCS


Im getting this error.

[smiley]

I have just fixed it. Now it has a simple textbox to enter the path to 2000 source

[TheHive]

Can you make the default folder a Relative Path to

..\Source\

Of WinBuilder Directory. That would make it easier.

You can probably use the Explorer script as example as to how to make the Browse thing work. Its used on the Wallpaper choice. Or Ove can help in how he made it work.

[TheHive]

I Used the Whole Drive path to the folder that contains the 2 files
L:\OPEN BUILDER\WinBuilder049 Final\Source\
ramdisk.sys
setupldr.bin



It seems to find them When creating the RAM ISO but How do I know its running on pure RAM. As I see it know the CD still loads and the B drive still has the User Profiles.

[smiley]

Ove hasn't solved the problem. In the explore script while not editing you can see the checkboxes but while editing you can also see tow text labels!!

[TheHive]

The Browse Boxes implementation must be a WinBuilder Problem then.


I get two errors in log.

[smiley]

The errors appear because the Boot from ram script must be run after the Create iso script

[TheHive]

You mean I have to build the ISO first. Then Run the RAM script by itself. If not. I dont know how to re order the Scripts.

If I do as I stated then I get the error message I reported earlier. The one that has the 14.

will be back later.

[TheHive]

So how do I move the Boot From RAM script below the Create ISO script and before the Run ISO in Qemu.

[Holger]

What about merging the CreateIso and BootFromRam-scripts together?

[paraglider]

Change the level parameter in the script file. Within the same level alphabetic ordering appears to apply.

[smiley]

I still get some errors using the script .I'm going to do some tests and post a reply soon

[smiley]

Problems fixed.I have added the uppercase option in mkisofs.exe in the script but now i have another problem.As the script has to run after the make iso script, the ramdisk.sys isn't copied in the first iso and this leads to a bsod. I think that holger is right. I'm going to merge the two scripts and boot from ram script will not require the create iso script.

Edit:Script is ready!!!!!!!!!!!!!!
Now it doesn't need the create iso script and works ok

You can get it from my page

[Brito]

Good work!

It seems a very clean and effective solution..

Just reminded that you can add a button on the interface and use the retrieve command to get a user selected folder where the ram files are located..

Retrieve,Dir,StartDir,%var%

This should workaround the bug that makes text labels disapear..

I'm going to buy some bug-spray on monday to see if it gets squashed for good..

[smiley]

Sounds a good idea but the text box doesn't update. Can you post a sample code? I have written this but it didn't worked:

Retrieve,Dir,%pTextBox1%,%pTextBox1%

Can you fix this in next release to update the textbox when its variable changes?

[paraglider]

Maybe it should also have the option to persist the selected directory across runs of winbuilder.

The same goes for all interface elements there should be an option to save the current value to the script.

[paraglider]

You can nearly achieve what I wanted with IniWrite. However it insists on expanding variables in section names. So:

IniWrite,"%ScriptFile%","variables","%CustomDir%","%CustomDir%"

does not work.

Is there any way to force expansion of variables in the interface section. So:

pTextBox1=,1,0,81,157,201,30,%CustomDir%

would show the value of %CustomDir% instead of %CustomDir%?

[smiley]

I think that it won't work because the variable must be set before the script interface is created. This can be done if the variable is set within the project file or if nuno provides us a process just before interface is created

[Ove]

I have tried to do this a while back, but I wasn't able to make it work.
I can't wait to get home and test this script. It's a real bombshell.

Good work smiley!

[TheHive]

smiley adding version numbers and updating the first post would be easier to keep up with updates. I see you made an update.

There is a spelling error:

From
If you want to enable booting form ram using xp you have to enter below the path of the Windows 2003 source or the service pack 1.

To
If you want to enable booting from RAM using XP. Just enter the path below, of the Windows 2003 source or the Service Pack 1. Press the ENTER key for the entered path to be Implemented. You can also point to the folder that contains ramdisk.sys and setupldr.bin from Win2003


Since this part is very important we have to emphacise it more.

From
You do not need to use the create iso script because booting from ram requires some additional files in the iso image

To
DISABLE the "Create ISO Script". Booting from RAM requires some additional files in the iso image.


So does this mean we cant point to the folder that contains those two files anymore?

[TheHive]

Hey now!
Its working by pointing to the folder that contains both files [ramdisk.sys and setupldr.bin] from Windows 2003 Server SP1.
Great update.

I like that it adds _RAM after the name of the one you give it. That keeps it from overwriting the Standard build ISO.

[smiley]

Thanks to all for your suggestions. Next release is ready!

Changes:
-Changed the script interface
-Made possible to copy files by entering the windows 2003 path or another folder that contains the files(in windows 2003 the files were in the folder I386)
-Fixed the problem with file version

Download WindowsRamBoot.script v007