Jump to content











Photo
- - - - -

[script] CreateISO


  • Please log in to reply
13 replies to this topic

#1 pscEx

pscEx

    Platinum Member

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

Posted 15 October 2007 - 10:06 AM

In addition to what the title is telling:

The option contains some code lines of Higway Star's original FBWF script. Thanks to him :cheers:
The changes / differences:
  • My script code is 'legal'
    The user needs two M$ files located on his / her PC, rather than finding attached them to the script.
  • FBWF only makes the PE system drive writable.
    There is no logical connection to 'RAMDrive' or 'Where documents and settings are stored'.
    This still has to be defined in !Fundamentals.
Try the 'supercalifragilistic...' constellation sample.
(Just a sample, may not be very senceful)
This will provide
  • Writable system drive X:
  • ImDisk drive R:
  • Documents and settings on R:
  • Temp on R:
Remark to the original FBWF script:

Two M$ files are included in the script.
The GUI shows the EULA that these files are not distributable
The user has to accept the EULA in order to run the script (with the distributed files)
Logical ?
I think Ly-gical !

Peter

#2 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10549 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 October 2007 - 11:07 AM

nice one.. :cheers: :cheers:

#3 DaemonForce

DaemonForce

    Frequent Member

  • Advanced user
  • 119 posts
  • Location:SEA
  • Interests:[=D=] is online when I am.<br /><br />DaemonPE is 18% complete!<br />Latest ISO manufactured 25/09/2007
  •  
    United States

Posted 15 October 2007 - 05:06 PM

This will provide

  • Writable system drive X:
  • Users on X:
  • Temp on X:\Users\Default User\Temp

Fixed to reflect my PE and defeat the purpose of any mention of RAMdisk in this thread. :cheers:

Can you tell me the weighted worth of ImDisk and the reason the Users directory has to follow the casual 'Documents and Settings' title? I started renaming it to Users when I glanced at Longhorn 4051. Now that I think about it, that release has been a huge impression upon me. It's the reason I started to pursue WinPE. A large reason I reduced the dir name to Users was for backwards compatibility with applications that didn't like spaces in the pathname. :cheers:

#4 pscEx

pscEx

    Platinum Member

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

Posted 15 October 2007 - 06:04 PM

Fixed to reflect my PE and defeat the purpose of any mention of RAMdisk in this thread. :cheers:

Can you tell me the weighted worth of ImDisk and the reason the Users directory has to follow the casual 'Documents and Settings' title? I started renaming it to Users when I glanced at Longhorn 4051. Now that I think about it, that release has been a huge impression upon me. It's the reason I started to pursue WinPE. A large reason I reduced the dir name to Users was for backwards compatibility with applications that didn't like spaces in the pathname. :cheers:


This topic is in the forum nativeEx & LiveXP, and as the name says, the PE structure is following the different languages the user has, and different users are familar with different names.

Your idea just to say 'User' may be ok, but in this forum are propably more people with 'any name for Documents and settings' than English speaking people with 'Documents and settings'.

Sample for me as German: If I have a PE with German messages, German date and time format, German ...,
an English 'User' is disturbing, if it it different from what M$ made me familar with. For me 'User' is just 'Benutzer'.

Please try to understand that the world is not limited to North America!

Peter

#5 DaemonForce

DaemonForce

    Frequent Member

  • Advanced user
  • 119 posts
  • Location:SEA
  • Interests:[=D=] is online when I am.<br /><br />DaemonPE is 18% complete!<br />Latest ISO manufactured 25/09/2007
  •  
    United States

Posted 15 October 2007 - 07:31 PM

Sample for me as German: If I have a PE with German messages, German date and time format, German ...,
an English 'User' is disturbing, if it it different from what M$ made me familar with. For me 'User' is just 'Benutzer'.

Please try to understand that the world is not limited to North America!

I would rather have a doc directory at my root called Benutzer than the Universal live-linux directory lusers. The later just reads more disturbing than the German names. :cheers:

#6 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 15 October 2007 - 07:47 PM

I prefer "home" like in all Linux and BSD

#7 pscEx

pscEx

    Platinum Member

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

Posted 15 October 2007 - 07:59 PM

I prefer "home" like in all Linux and BSD

@Sanbarrow,
@DaemonForce:

When I developed the nativeEx idea, I put as root into the concept, that all names are equal to comparable names inside (localized) Windows XP.

I do not want to redesign everything.
(maybe somebody wants to develop esperantoEx?)

Therefore no reason to discuss.
Let's stop the discussion about (translated) folder names here.

Peter

#8 DaemonForce

DaemonForce

    Frequent Member

  • Advanced user
  • 119 posts
  • Location:SEA
  • Interests:[=D=] is online when I am.<br /><br />DaemonPE is 18% complete!<br />Latest ISO manufactured 25/09/2007
  •  
    United States

Posted 15 October 2007 - 08:42 PM

I do not want to redesign everything.
(maybe somebody wants to develop esperantoEx?)

Therefore no reason to discuss.
Let's stop the discussion about (translated) folder names here.

Si señor. :cheers:

Just wondering psc, which version of the FBWF do you recommend for maximum cross-compatibility from XP to Server 08? :cheers:

#9 pscEx

pscEx

    Platinum Member

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

Posted 15 October 2007 - 08:49 PM

Just wondering psc, which version of the FBWF do you recommend for maximum cross-compatibility from XP to Server 08? :cheers:

I do not recommend anything. My script just gives the user the ability to define the files of his / her choice.

(Currenty for my XP source I use EmbeddedXP)

Peter

#10 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4171 posts

Posted 16 October 2007 - 06:39 PM

%ProjectTemplates%\FBWF

what dir are the files suppose to be in

#11 pscEx

pscEx

    Platinum Member

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

Posted 16 October 2007 - 06:53 PM

%ProjectTemplates%\FBWF

what dir are the files suppose to be in


%ProjectTemplates% is a variable in script.project.

As 'full' path:
%BaseDir%\Workbench\%ProjectName%\UserData\FBWF

Peter

#12 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4171 posts

Posted 17 October 2007 - 07:25 AM

I kinda understand from where to start and where to point to the folder directory.

I used this and it didnt work the first time I created and ISO. I looked at the prompt which asked for the
right files and in that process its to late to put them in and make the ISO work with the files.
%BaseDir%\Projects\nativeEx_barebone\Finish\2 Create Image\FBWF

I looked at the files I had in that FBW directory and they where the wrong ones.

Found out that i had RAMDISK.SY_ , and ramdisk.sys instead of fbwf.sys, and fbwflib.dll

I think that the name of the files should be mentioned in the gui of CreateISO

After putting the right files
Found out that
%BaseDir%\Projects\nativeEx_barebone\Finish\2 Create Image\FBWF
works and it seemed to find the files.

Now that I have the right files it created the ISO fine and it has FBWF ability.

#13 pscEx

pscEx

    Platinum Member

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

Posted 17 October 2007 - 07:57 AM

I think that the name of the files should be mentioned in the gui of CreateISO

:cheers:

Done!


Peter

#14 pscEx

pscEx

    Platinum Member

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

Posted 17 October 2007 - 12:00 PM

I used this and it didnt work the first time I created and ISO. I looked at the prompt which asked for the
right files and in that process its to late to put them in and make the ISO work with the files.
%BaseDir%\Projects\nativeEx_barebone\Finish\2 Create Image\FBWF

Thanks for the hint!

Now Verify complains missing files in the very begin of the build.

For those who are interested:
CreateISO.Script contains:
&#91;Verify&#93;

...

...

If {%$$$&#58;Interface.pCheckBox2%} 

& !{%&#91;$$$&#58;Interface.pFileBox1&#93;\fbwf.sys%} Then

$File$;

If {%$$$&#58;Interface.pCheckBox2%} 

& !{%&#91;$$$&#58;Interface.pFileBox1&#93;\fbwflib.dll%} Then

$File$;

If {$File$} then

&#34;FBWF needed Files missing&#58; fbwf.sys, fbwflib.dll&#34;;

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users