Jump to content











Photo
- - - - -

nativeEx .Scripts


  • Please log in to reply
8 replies to this topic

#1 pscEx

pscEx

    Platinum Member

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

Posted 08 January 2007 - 03:09 PM

At several posts the question appeared about rules for scripts suited for nativeEX.

The rules are very simple. Better said: There is only one simple rule:

No hardcoded folder names

This rule has to be seen directly and indirectly.
Directly is clear and easy to be detected:

CopyFile,....,%Target%\programs

Indirectly is a little bit complicated.
One candidate is shortcuts.Script.
Usually the shortcuts are written correctly because the .au3 program uses environment variables to place the shortcuts.
But when you e.g. want to have a 'SendTo' shortcut, it is created in

..\Documents and Settings\Default User\SendTo

This is bad for every Non-English system.

How to work:
  • To create shortcuts, use buildModel (see the Help button in the buildModel.Script interface)
  • For folder use the localized names which are found in ProjectInfo.ini
IniRead,"%ProjectInfo%","TargetStrings","sProgram_Files","%progs%"

   CopyFile,....,%Target%\%progs%
Similar with the use of %PEprograms%. It brings a hardcoded 'programs':
This has to be replaced by %PEDrive%\%progs% (from the above snippet)

Not a rule, but a recommandation:
For hive names you should use the nativeEX standard names:

WB-Software, WB-Setup, WB-Default

Second recommandation:
Do not use the Variables
  • %TargetWin%
  • %TargetSys32%
  • %PEwin%
  • %PEsys32%
Third recommandation:
Instead of hardcoding the target windows directory as 'I386', use the variable %nExWin%.

The latest version of nativeEX plays a little bit with logos.
At every .Script which is fundamental for nativeEX, you can find the 'exec' logo in the lower right.
A script which is adapted for nativeEX or is written fullfilling the above rules, has the start 'e' in the lower left.

Peter

#2 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4147 posts

Posted 08 January 2007 - 05:45 PM

The latest version of nativeEX plays a little bit with logos.
At every .Script which is fundamental for nativeEX, you can find the 'exec' logo in the lower right.
A script which is adapted for nativeEX or is written fullfilling the above rules, has the start 'e' in the lower left.

Peter

I was wondering what that was about.

#3 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 01 May 2007 - 06:51 AM

At several posts the question appeared about rules for scripts suited for nativeEX.


@Peter.

Would you please consider adding two more script rules?

Fourth recommendation:
Script should be coded for English XPSP2 source, build under English XPSP2 or Vista as default,
with selectable options for Win2003 source and other languages localizations.

Fifth recommendation:
By default script should be made according to 4S standards,
with selectable options for bells and ribbons.

phox.

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 May 2007 - 01:09 PM

Fourth recommendation:
Script should be coded for English XPSP2 source, build under English XPSP2 or Vista as default,
with selectable options for Win2003 source and other languages localizations.

You know, that the big thing about nativeEx is, that it is language independent, don't you?

#5 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 01 May 2007 - 02:45 PM

You know, that the big thing about nativeEx is, that it is language independent, don't you?


Yes, but with unnecessary NLS support for English/English version!

#6 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 May 2007 - 03:28 PM


You know, that the big thing about nativeEx is, that it is language independent, don't you?

Yes, but with unnecessary NLS support for English/English version!

:confused1: Do you actually read what you write, before posting?

#7 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 01 May 2007 - 03:35 PM

Yes, but with unnecessary NLS support for English/English version!

:confused1: Do you actually read what you write, before posting?


To illustrate how wrong you are, see my Cleaning.Script:
Attached File  Cleaning.zip   547bytes   189 downloads

#8 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 May 2007 - 05:18 PM

To illustrate how wrong you are, see my Cleaning.Script:
Attached File  Cleaning.zip   547bytes   189 downloads

So Peter should rewrite his script to just include the nl_ files, that you really need, not care about everyone else and all this just to save you a whole 18,1kB?

Though i might agree upon the i386\Biosinfo.inf being useless.
At least ISO-boot is not using it.

#9 pscEx

pscEx

    Platinum Member

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

Posted 01 May 2007 - 05:25 PM

To illustrate how wrong you are, see my Cleaning.Script:
Attached File  Cleaning.zip   547bytes   189 downloads

The NLS files used inside a specific language are taken from HIVE???.INF files on your source CD.
The HoJoPE program has no knowledge about that a certain user does not use them all.
It is a good idea to continue using your cleaning script do get your special ISO .

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users