Jump to content











Photo
- - - - -

Improve RAM boot script


  • Please log in to reply
1 reply to this topic

#1 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10545 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 15 July 2006 - 11:12 AM

psc mentioned a few good ideas on how to change the ram boot script in order to the ISO creation process is made in a safer way.

psc, can you please re-post your idea?

thanks!
:P

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 17 July 2006 - 03:31 PM

Here it is:

A suggestion:

Because there are now different main scripts the ISO files and Target directory may be ambigous.

Additionally it can happen that WindowsRamBoot.script generates a RAM ISO from a RAM ISO ... from the normal ISO.

To avoid these issues, I suggest:

Target directory should be %ProjectDir%\Target instead of %BaseDir%\Target

ISO file name should be %BaseDir%\ISO\%ProjectName%.iso, in case of RAM ISO %ProjectName%_RAM.iso or similar.

Of course the %ProjectName% variable has to be created inside OpenBuilder.

I tried it successfully.
Following some fragments of WindowsRamBoot.script


[variables]

...

...

%ProjectName%=Standard (hardcoded just for test!)



[process-win2003]

...

...

echo,"Copying ISO to new location.."

FileCopy,"%isofile%","%RAMFolder%"

FileRename,"%RAMFolder%\%ProjectName%.iso","%RAMFolder%\%ProjectName%_RAM.iso"

echo,"Making Windows 2003 RAM Bootable ISO.. [%ProjectName%_RAM.iso]"

ShellExecute,open,#$q%Tools%\mkisofs.exe#$q,"-iso-level 4 -volid #$q%RAMISO%#$q -A PEBUILDER/MKISOFS -sysid #$qWin32#$q -no-emul-boot -b BOOTSECT.BIN -hide BOOTSECT.BIN -o #$q%ISODir%\%ProjectName%_RAM.iso#$q #$q%RAMFolder%#$q"

...

...

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users