Jump to content











Photo
- - - - -

Environment Vars inside PE


  • Please log in to reply
6 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 02 May 2007 - 02:23 PM

If I compare the 'SET' of my running system with the 'SET' inside a PE boot, I find two additional variables inside PE
  • RamDrv
  • ProfilesDir
I currently do not remember anhy place where (after removing of %PEDrive%) there are used.

Has anybody an idea?
Or should I remove them?

Peter

#2 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 May 2007 - 03:15 PM

If I compare the 'SET' of my running system with the 'SET' inside a PE boot, I find two additional variables inside PE

  • RamDrv
  • ProfilesDir
I currently do not remember anhy place where (after removing of %PEDrive%) there are used.

Has anybody an idea?
Or should I remove them?

Peter

RamDrv is used in Opera script, but can be changed to Temp.
ProfilesDir(ectory) together with AllUsersProfile belong in ProfileList not in Environment.

:confused1:

#3 pscEx

pscEx

    Platinum Member

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

Posted 02 May 2007 - 04:12 PM

RamDrv is used in Opera script, but can be changed to Temp.
ProfilesDir(ectory) together with AllUsersProfile belong in ProfileList not in Environment.

:confused1:


You should use Temp!
In case of Ram Drive it is B: in case of 'No ram drive' like bootSDI it is %UserProfile%\<Local settings>\Temp (<Local Settings> from buildModel)

For me, currently both variables are candidates to retire ...

Peter

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 May 2007 - 04:53 PM

You should use Temp!
In case of Ram Drive it is : in case of 'No ram drive' like bootSDI it is %UserProfile%\<Local settings>\Temp (<Local Settings> from buildModel)

For me, currently both variables are candidates to retire ...

Peter

btw. Speaking of Local Settings a few folders end up at the wrong place.
History (Verlauf), Temporary Internet Files.
Not sure if eighter can be fixed by you.

:confused1:

#5 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 May 2007 - 05:05 PM

Just a stupid idea. Is anyone still extracting an application to RamDisk before running it?
And if so, how should he script this function without %RamDrv% ?

Just remembered why i have RamDrv in the Opera script. Because i wanted to fix Temp and Tmp to always point to %UserProfile%\Local Settings\Temp, But one specific folder should end up, where it can easily be accessed, on the Root of the RamDrive.

:confused1:

#6 pscEx

pscEx

    Platinum Member

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

Posted 03 May 2007 - 11:28 AM

Just a stupid idea. Is anyone still extracting an application to RamDisk before running it?
And if so, how should he script this function without %RamDrv% ?

Always extract to %Temp%\myAppFolder and run from there.

Peter

#7 Holger

Holger

    Silver Member

  • .script developer
  • 534 posts
  • Location:Munich
  • Interests:- programming / scripting
    - scooter driving / modifying
    - writing poems
  •  
    Germany

Posted 11 May 2007 - 10:05 PM

@Peter: could you already fix the problem that "MedEvil" described?:

...Because i wanted to fix Temp and Tmp to always point to %UserProfile%\Local Settings\Temp ...

Maybe I'm not uptodate :confused1:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users