Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About niveknonrev

  1. LaunchApps in Winpeshl.ini not running

    Tripedacus, thanks for looking at this post. No that is not what I am saying. Startnet.cmd launches perfectly all by itself. However following Microsoft's instructions for launching a "custom shell" or "custom apps" etc. It says to use the winpeshl.ini file, the LaunchApp with the AppPath = %systemdrive%\myshell.exe - etc. Then you are supposed to be able to uset the LaunchApps section to launch other applications after your shell starts. I followed the directions below using BSExplore as my shell, but it still didn't work: Winpeshl.ini FilesWinpeshl.ini controls whether a customized shell is loaded in Windows PE instead of the default Command Prompt window. To load a customized shell, create a file named Winpeshl.ini and place it in %SYSTEMROOT%\System32 of your customized Windows PE image. The .ini file must have the following section and entry. [LaunchApp] AppPath = %SYSTEMDRIVE%\myshell.exe [LaunchApps] %SYSTEMDRIVE%\mydir\application1.exe, -option1 -option2 application2.exe, -option1 -option2 Set the AppPath entry to the path to your shell application. The path can be either fully qualified, or you can use environment variables, such as %SYSTEMROOT%\System32\Myshell.exe. The AppPath entry does not support command-line options. Use the [LaunchApps] section to run applications with command-line options. The applications run in the order listed; separate the name of the application from its options with a comma. When you exit the Command Prompt window or your customized shell application, Windows PE restarts. This way I wouldn't have the "command prompt" as my shell. I know it is just a cosmetic change (the shell), but I just thought it sounded like a better way to do it. Thanks!
  2. LaunchApps in Winpeshl.ini not running

    Bummer none of those options worked. Don't know why - no errors or anything. Nothing I put in LaunchApps section gets run, with or without options, or quotes, or spaces, or anything. Well im stuck with the startnet.cmd window as my shell for now, I just put a big "echo" banner in it saying DONT CLOSE IT LOL... If anyone else has run into this and figured out a way to get it to work let me know. I am using the following: WAIK 1.1 VMWare Workstation 6.x to test in Running on a Vista (no sp1) host Thanks!
  3. LaunchApps in Winpeshl.ini not running

    Thanks for the reply! I tried the following combinations, but none worked. Just to see if anything would work [LaunchApps] cmd.exe [LaunchApps] %systemroot%\System32\Startnet.cmd if forgot the "comma" in the first post, but I did try it like this [LaunchApps] cmd.exe, /c %systemroot%\System32\Startnet.cmd That is the article I used whe I created it, but it doesn't work like the help file or article says. Any other ideas? Thanks Kevin
  4. I have searched but I can't seem to find the problem. I have a custom WinPE 2.x and it boots great, everything works just like it is supposed to except the [LaunchApps] section of my Winpeshl.ini. All I'm asking it to do is fire off the startnet.cmd file after my bsexploreshell is loaded. ------------------------- [LaunchApp] AppPath = %SYSTEMDRIVE%\bsexploreshell\explorer.exe [LaunchApps] cmd /c %systemroot%\System32\Startnet.cmd ------------------------- That way I can have the nice GUI shell, and also autorun the wpeinit.exe and any other scripts I add to startnet. I know that the winpeshl.ini is working part way because my bsexplore shell is working great! Then I can manually run startnet.cmd and it works fine, but why doesn't it run automagically? Any help is appreciated. Maybe its something I just missed. Thanks
  5. Winnt.sif config

    I am new here also, but I put the following in my winnt.sif file: AutoPartition=1 Repartition=no In testing with a VM I got the following results: When 0 or 1 partitions exist - it formats the entire drive as NTFS and installs When 2 partitions exist it formats and installs on the first partition (both partitions were blank) and keeps the 2nd partition intact When an OS was installed on partition 1 - it comes up to the partition selection screen and you must choose to overwrite the existing windows install. (if you select the first partition, it keeps the second one intact) To make it work properly you have to manually format the first partition. Is there any way to "script" that in the unattended isntall? Now it is 99% unattended when an OS is present..... Haven't tried it with an OS on each partition..... Haven't tried it with an OS on the Second partition only..... Any help/comments/suggestions would be appreciated