86 replies to this topic

[TheHive]

You forgot to add the warning about not running the Create Iso Script with this one.



Im getting this while booting up.

[smiley]

In the path that you enter in the textbox do you have ramdisk.sys or ramdisk.sy_?The script copies the file ramdisk.sy_ ,not the ramdisk.sy_ because it can stay compressed

[TheHive]

I have the ramdisk.sys which was working previously. Ill get the ramdisk.sy_ from Win2003 and test.

[TheHive]

Thank you. That did the trick.
Now its working.

I see why I couldnt see the Disable message. I had not scrolled down all the way down.
The last thing I could see was the Download Windows 2003 Trial.

[TheHive]

Suggestion.

[_icehole_]

Very nice. Works great.

I assume this will replace the existing "Run Windows from RAM" eventually.

Suggestion for keeping WinBuilder 'out of the box' functional:

Have this script be the default "Create ISO" also. If it doesn't find valid ramdisk.sy_ and setupldr.bin files at the default location it should just create a CD iso and continue on (with an ignored entry in the log for those curious enough to find it ) instead of the 'corrupt txtsetup.sif' it gets now when trying to load.

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

Yeppers, I like that also. Makes it obvious it's a RAM build. A note to the right of the 'ISO volume name:' edit box stating that _RAM will be appended to the iso name would be helpful along with possibly a 'tip' to set that in the path before running in qEmu.

One last thought: a browse button next to the path edit box?

Great script as is.
I like to manipulate some things manually so this is all I need.
I am thinking about new users whose first impression will be what happens after they download and hit run. Then notice "Hey, What's this RAM thing? "

[TheHive]

Very nice. Works great.

I assume this will replace the existing "Run Windows from RAM" eventually.

Suggestion for keeping WinBuilder 'out of the box' functional:

Have this script be the default "Create ISO" also. If it doesn't find valid ramdisk.sy_ and setupldr.bin files at the default location it should just create a CD iso and continue on (with an ignored entry in the log for those curious enough to find it ) instead of the 'corrupt txtsetup.sif' it gets now when trying to load.
Yeppers, I like that also. Makes it obvious it's a RAM build. A note to the right of the 'ISO volume name:' edit box stating that _RAM will be appended to the iso name would be helpful along with possibly a 'tip' to set that in the path before running in qEmu.

I agree with that. That would make it more streamlined.

One last thought: a browse button next to the path edit box?

Great script as is.
I like to manipulate some things manually so this is all I need.
I am thinking about new users whose first impression will be what happens after they download and hit run. Then notice "Hey, What's this RAM thing? "

I Agree with this also but as was explained earlier its not easy to implement into scripts at the moment thats why smiley added the text box only. It would make it simpler to have the Browse button also.

[TheHive]

Build 050

Beta 3

- FileBox can safely be added inside script interface without making the labels disapear..

-------------------------------------------

Hi, smiley
Can you update your box in the RAM script with the new Browse box and see if it works.

Thanks!

[smiley]

Next release is ready!

I have added file box and an image made by TheHive . Thanks a lot!
Boot from RAM v008: download
Important:This requires Winbuilder Build 050 beta 3

[TheHive]

I tried it out on the new Winbuilder 50 beta3. Im getting this error again.
INF file txtsetup.sif is corrupt or missing, status 14.
Setup cannot contiue. Press any key to exit.

ive also noticed that the script was reduced by 9KB.

[smiley]

Sorry i forgot to raplace all the string that pointed to the old text box .It is ok now.

The reduction of the seize is because your image was smaller

[TheHive]

Cool! Thanks for the fix. Will test. So the image does make a difference. Happy you liked it.

[TheHive]

It working again.

[Brito]

I'm using version 8 from your script and it gave a few errors when building:

It couldn't find or rename the RAM boot file because I've used windows XP and haven't provided a path for the RAM files.

This will be a good replacement for the standard make ISO script and RAMboot.. don't forget to add this script to your update repository!

[smiley]

I have updated it to v009. Now it stops when it doesn't find the files

[TheHive]

Thanks for the update.

[Brito]

This script is not working for me as needed..

I'm using windows XP as source, and I'm not using the RAM boot option from Windows 2003 - meaning that the script should be able to build a plain CD bootable ISO, however it simply exits because the setupldr.bin isn't found..

I know about the changes from version 8 to 9, but this should still be available to allow replacing the create ISO script..

Can you please correct this?

This is the only script missing to fix before 050 is released..

Thanks!

Attached Files

•  log.html   2.72KB   397 downloads

[smiley]

If want to create a simple iso you have to enable the create iso script , because it isn't a replacement for the create iso script.It's a different choice

[TheHive]

I think what Nuno is asking for is that if you can have a marriage between the two Scrips "Create ISO" and and "Run Windows From RAM". So the Final baby will be able to either Create a regular ISO or Create a RAM ISO. So the Baby that is Born could be named Create ISO or a Boot from RAM ISO.

A tick option to disable the Regular ISO creation. And the ability to disable the RAM ISO creation part just in case a user has the Win2003 CD or files but does not want to build the RAM iso.

The merge would be so that the we dont have to many Scripts in the release of the Standard Project.

[smiley]

I'll give it a try

[smiley]

@ Nuno Britto: You can release Winbuilder 050 because the new script will need debuging

[Brito]

Yes, I've tried to tweak it now but I see that it will take some testing time and it's preferable to have it placed on the archive folder until we have a solution that can completely replace the create ISO script..

[Mikorist]

I think what Nuno is asking for is that if you can have a marriage between the two Scrips "Create ISO" and and "Run Windows From RAM". So the Final baby will be able to either Create a regular ISO or Create a RAM ISO. So the Baby that is Born could be named Create ISO or a Boot from RAM ISO.

A tick option to disable the Regular ISO creation. And the ability to disable the RAM ISO creation part just in case a user has the Win2003 CD or files but does not want to build the RAM iso.

The merge would be so that the we dont have to many Scripts in the release of the Standard Project.

Do you have plan for future that Boot Land Final baby will be able to
start in all windows ("Create ISO" and and "Run Windows From RAM")?

If you can make separable program "Create ISO and run From RAM" for all OS
you will become wealthy and have 50.000 members in your forum...
i think...
P.S. I have name for this now CIA-RFR= "Create ISO and run From RAM"

[smiley]

Well here is an updated version of Make Iso script.Now you can use a single script to create a sibple ISO or an ISO that loads it shelf in the ram.

But i have still some problems. In the script i have this line :

If,%error%,Equal,1,Exit,"File setupldr.bin not found.Switched to normal ISO"

In the log i get the explanation mark and the message "File setupldr.bin not found.Switched to normal ISO" but it doesn't exit and go on. Does it have to be in the [process] section or it works in any process?

Attached Files

•  CreateIsoScript_BETA.script   8.69KB   440 downloads

[smiley]

I have done some more testings . The exit command when is called from the [process] section works ok but when it is called by any other process , it works as discribed above.Nuno can you fix it?