Jump to content











Photo
* * * * * 1 votes

New nativeEx server


  • 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 03 May 2007 - 09:26 AM

Last days there have been some troubles with upload and somtimes with download, too, to / from nativeEx server.

Therefore I completely deleted the server anhd created a new one.
The adress in your WinBuilder download did not change by that.

When uploading the project, I made some changes.

I deleted (obsolete) environment variables
  • RamDrive
  • ProfilesDir
  • UserProfile
There was an issue with the Temp environment variable: It has been defined in the ramdrive script.
If there is no ramdrive (e.g. BootSDI) there is not Temp :confused1:

Now Temp is removed from ramdrive script and defined in buildModel. Depending on an existing ram drive it is
  • either %RamDriveLetter%
  • or %SettingsDrive%\<localized 'local settings'>
    e.g. German:=X:\Dokumente und Einstellungen\Default User\Lokale Einstellungen\Temp
@MedEvil:
Is it necessary for you to simplify the path maybe to %SettingsDrive%\Temp ?

Last but not least in winBuilder I reanimated the 'refresh shortcut' for phox's Vista.

Peter



#2 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 03 May 2007 - 01:33 PM

Now Temp is removed from ramdrive script and defined in buildModel. Depending on an existing ram drive it is

  • either %RamDriveLetter%
  • or %SettingsDrive%\<localized 'local settings'>
    e.g. German:=X:\Dokumente und Einstellungen\Default User\Lokale Einstellungen\Temp
@MedEvil:
Is it necessary for you to simplify the path maybe to %SettingsDrive%\Temp ?

As long as you don't really write X:\... to the registry but %SystemDrive%\... i have no objections. :confused1:
Where does Temp point to, when i use FBWF.script?

:confused1:

#3 pscEx

pscEx

    Platinum Member

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

Posted 03 May 2007 - 01:40 PM

As long as you don't really write X:\... to the registry but %SystemDrive%\... i have no objections. :confused1:
Where does Temp point to, when i use FBWF.script?

:confused1:


regeditwb.gif
:confused1:

FBWF should be same as BootSDI:
Temp = %RamDrive% if there is a Ramdrive
Temp = %SettingsDrive%\bla bla ... if there is no Ramdrive

Peter

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 03 May 2007 - 01:53 PM

Temp = %RamDrive% if there is a Ramdrive
Temp = %SettingsDrive%\bla bla ... if there is no Ramdrive

Good solution!

:confused1:

#5 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 03 May 2007 - 03:02 PM

If there is no ramdrive (e.g. BootSDI) there is not Temp :confused1:


I have done some testing of BootSDI and did not find way to avoid using RAMDrive!
Please, how I should set up scripts to do it correctly?

Last but not least in winBuilder I reanimated the [color=#0000ff]'refresh shortcut' for phox's


Thank you!

#6 pscEx

pscEx

    Platinum Member

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

Posted 03 May 2007 - 03:11 PM

I have done some testing of BootSDI and did not find way to avoid using RAMDrive!
Please, how I should set up scripts to do it correctly?

1st: You need the complete new nativeEx_barebone. (better to delete prebuild and temp folder)
2nd:
fundamentals.gif
3nd: (of course) Uncheck ramdrive, check BootSDI and uncheck CreateISO
Peter

#7 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 03 May 2007 - 03:20 PM

1st: You need the complete new nativeEx_barebone. (better to delete prebuild and temp folder)
2nd:fundamentals.gif
3nd: (of course) Uncheck ramdrive, check BootSDI and uncheck CreateISO
Peter


Will do! Thank you!

#8 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 03 May 2007 - 05:09 PM

Initial testing of new nativeEx_barebone on Vista Ultimate with English XPSP2:

1.Default settings and BootSDI.script selected.
As before; Application programs problem.
After clicking icons appear except Explorer QL icon:

Vista_31.JPG

2. “Do not refresh” unchecked.
New Application programs problems: After clicking icons completely disappear!

Vista_28.JPG
Vista_30.JPG

I will now make my usual customization and do detailed testing.

@Peter.

You should not spend time with Vista problems if I am the only one using it.
I have installed XPSP2 as secondary OS on my notebook and could use it for WB.
Thank you for your time and attention.

phox

#9 pscEx

pscEx

    Platinum Member

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

Posted 03 May 2007 - 05:21 PM

@Peter.

You should not loose time with Vista problems if I am the only one using it.
I have installed XPSP2 as secondary OS on my notebook and could use it for WB.
Thank you for your time and attention.

phox

I know what it is, but I do not know how to fix. :confused1:
Instead of the string '%SystemDrive%' Vista writes the value of the actual system drive into the shortcut. In your case is that D:

In older versions there have been no problems, because I wrote a hardcoded X:
But since we removed %PEDrive% ...

Nice of you to offer me not to loose time!
Thanks!

But it is my strong intention to solve this issue.
I think I need your help for that to do tests.

Peter

#10 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 03 May 2007 - 05:30 PM

I know what it is, but I do not know how to fix. :confused1:
Instead of the string '%SystemDrive%' Vista writes the value of the actual system drive into the shortcut.

Interesting.
Does that happen with all variables or just %SystemDrive% or maybe just with Type String?

#11 phox

phox

    Silver Member

  • .script developer
  • 764 posts

Posted 03 May 2007 - 05:31 PM

But it is my strong intention to solve this issue.
I think I need your help for that to do tests.

Peter


That’s the spirit! Just tell me what I should do.

#12 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4171 posts

Posted 04 May 2007 - 04:44 AM

By default there is no RAMdrive selected or SDI.
Verify says to choose one.
Just noting it.

Project built fine after selecting Ramdrive.
Booted up fine also.
:confused1:

#13 pscEx

pscEx

    Platinum Member

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

Posted 04 May 2007 - 08:00 AM

By default there is no RAMdrive selected or SDI.
Verify says to choose one.


Thank :confused1:
Fixed.

Peter

#14 pscEx

pscEx

    Platinum Member

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

Posted 20 May 2007 - 05:56 PM

Again I removed the use of a PE environment variable: %ProgramFiles%

Currently it is used exclusively in buildModel:add-shortcut.

The disadvantage is, that %ProgramFiles% is undefined in the PE when using minlogon.
So, in the current stage, when using minlogon, there are issues with shortcuts.

Therefore I removed the use of %ProgramFiles% and added a new project-wide variable %PE_Programs% instead.

Do not worry, this is not a fall back to %PEDrive% time!
This new variable is changed dynamically by buildModel and contains %SystemDrive%\<localized program files>.

To use the new functionality, you have to:
  • Download buildModel version 033
  • Change in all of your applications %ProgramFiles% or #$pProgramFiles#$p to %PE_Programs%
    (In nativeEx_barebone that are:
  • OffByOne
  • Welcome
  • Services)

For nativeEx_barebone I did the changes and upload the new versions to the server

Thanks to Thunn for his tests, investigations and development with the barebone in a 'real' environment :confused1:
NativePE is a great project and (I'm glad about that) contains always actual nativeEx core functionality.

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users