Jump to content











Photo
- - - - -

Question on WinPESHL.ini syntax

paths with spaces

  • Please log in to reply
5 replies to this topic

#1 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1337 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 15 November 2011 - 01:54 AM

OK...maybe a dumb question, but how do I put in a path to a command that has a space in it (like running a cmd script from the "Program Files" area?

or is this a loosing battle, and just stuff it in the windows/system32/drivers area?

#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13923 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 November 2011 - 08:37 AM

OK...maybe a dumb question, but how do I put in a path to a command that has a space in it (like running a cmd script from the "Program Files" area?

or is this a loosing battle, and just stuff it in the windows/system32/drivers area?


The WINPESHL.INI is tricky, see if this helps :unsure::
http://reboot.pro/13...546#entry120546
http://www.msfn.org/...ni-not-running/
http://www.msfn.org/...ng/page__st__12

:cheers:
Wonko

#3 RoyM

RoyM

    Frequent Member

  • .script developer
  • 415 posts
  • Interests:"Booting and Owning".
  •  
    United States

Posted 15 November 2011 - 02:24 PM

%ProgramFiles%

#4 Tripredacus

Tripredacus

    Frequent Member

  • Expert
  • 234 posts
  • Interests:K-Mart-ian Legend
  •  
    United States

Posted 15 November 2011 - 02:37 PM

Here is my example winpeshl.ini I use to launch BurnInTest:
 

[LaunchApps] 
%SYSTEMDRIVE%\Windows\System32\wpeinit.exe 
%SYSTEMDRIVE%\Windows\System32\wpeutil.exe, "initializenetwork" 
%SYSTEMDRIVE%\Windows\System32\setres.exe, "1024 768 32 1" 
%SYSTEMDRIVE%\Windows\System32\diskpart.exe, "/s %SYSTEMDRIVE%\Windows\System32\diskpart.txt" 
%SYSTEMDRIVE%\Windows\System32\cdrom.exe 
%SYSTEMDRIVE%\Progra~1\BurnInTest\bit.exe, "-x -r -c burn.bitcfg"

See the last line, WinPE will recognize the DOS 8.3 format as well. :P


Edited by Tripredacus, 11 March 2014 - 02:36 PM.


#5 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1337 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 15 November 2011 - 04:02 PM

All good suggestions!

I knew we would collectively have the answer!

:cheers:
Scott

#6 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1337 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 15 November 2011 - 09:31 PM

Here is my example winpeshl.ini I use to launch BurnInTest:

[LaunchApps]

%SYSTEMDRIVE%WindowsSystem32wpeinit.exe

%SYSTEMDRIVE%WindowsSystem32wpeutil.exe, "initializenetwork"

%SYSTEMDRIVE%WindowsSystem32setres.exe, "1024 768 32 1"

%SYSTEMDRIVE%WindowsSystem32diskpart.exe, "/s %SYSTEMDRIVE%WindowsSystem32diskpart.txt"

%SYSTEMDRIVE%WindowsSystem32cdrom.exe

%SYSTEMDRIVE%Progra~1BurnInTestbit.exe, "-x -r -c burn.bitcfg"

See the last line, WinPE will recognize the DOS 8.3 format as well. :P

I think that is what I have to use...BUT, just as an FYI, on an X64 based machine, it is progra~2 if you want the 64 bit default...the "Program Files (x86)" is the ~1 DOH :frusty:

%ProgramFiles%

This gets expanded and replaced before being passed to the PE for execution...
  • Tripredacus likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users