Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Posts posted by hasi001

  1. @bmn

    Your changes to winnt.sif are wrong. I would suggest the following:



    Install.cmd should contain

    start /wait %systemdrive%\install\wpi\wpi.hta

    ... so you do not need to call WPI from wpi.cmd if you call it from install.cmd. There's no need for wpi.cmd anymore.

    Btw. I didn't say, that installing directly from CD wouldn't work. Of course you could search for the install-cd drive letter in the install.cmd script and run wpi from cd.

    example install.cmd (calls wpi and cleanup):


    IF EXIST D:\WIN51 set CDROM=D:
    IF EXIST E:\WIN51 set CDROM=E:
    IF EXIST F:\WIN51 set CDROM=F:
    IF EXIST G:\WIN51 set CDROM=G:
    IF EXIST H:\WIN51 set CDROM=H:
    IF EXIST I:\WIN51 set CDROM=I:
    IF EXIST J:\WIN51 set CDROM=J:

    start /wait %CDROM%\install\WPI\WPI.HTA



  2. Hi bmn

    You've got a mistake in WINNT.SIF


    You can't use %cdrom% there.

    put the .cmd Files in $OEM$\$1\Install and call them as


    Note: %cdrom% is not a windows environment variable.

    you better move your wpi folder over to $OEM$\$1\Install\wpi

    and call wpi.hta from wpi.cmd as

    start /wait %systemdrive%\install\wpi\wpi.hta

    See also the documentation on the WPI homepage,

  3. A few quick answers:

    1st thing to know is that: everything inside the $OEM$ folder gets copied to the systemdrive during textmode-setup. So if you make an unattended install DVD and place your Install-Folder into $OEM$\Install and install to c:, the result after textmode-setup would be a huge c:\Install-Folder. In this case you could use %systemdrive%\\Install\\...

    If you put your installs on cd-root\Install the files won't be copied to the systemdrive during textmode-setup. so with wpi you'd have to use %cdrom%\\Install\\...

    You could also mix up both variants. I do have a $OEM$\\Install folder, where I put all the software which won't be installed by WPI, but I want the option to install it any time. After install it just waits on c:\Install for getting installed.

    Soft that is installed and mentioned in WPI sits on cd-root\Install (so it's only available after installing XP when the DVD is inside its tray).

    In my configuration WPI can be found in $OEM\\Install\\WPI, cause after setup, the environment-variable %systemroot% is always set. so I can call wpi.hta from my install.cmd as %systemroot%\Install\WPI\wpi.hta

    If wpi only sits on cd-root\Install\WPI\wpi.hta you'd have to search for the dvd's drive letter inside the calling script, cause there's no environment-variable for it.

    so in my GuiRunOnce-section I just simply call install.cmd and from there i call everything else with the known start /wait ... calls.

    easy as that.

    PS. I'm working on a comprehensive guide for WPI right now, which should replace the out-of-date docs. I'll post when it's finished. C ya.

  4. but it still refers to D:\ in my wirtual environmnt.

    is this also fixed in 2.9.3, or only the double error?

    Hi Rodent.

    Seems you found another bug ...

    What I would like you to do ist the following:

    Download the attachment - replace the config.js and try to run WPI on your virtual environment.

    Debugs are on in this version - so you'll see some debug messages in the upper part of the screen.

    If the problem's fixed, then I'll release a fixed version - so please answer. In the negative case post the debug messages.

    All others - please do not download this version. I have to post it, 'cause Attachments are not supported with PMs. I'll post a fixed version soon.

    Check out the WPI homepage for new version

  5. dhernande: so we're going to speak of the 'modern' operating systems XP Pro, XP Home, 2003 Server, 2K Pro, 2k Server - am I wrong ?

    If you look at the registry keys in HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion what's the differences that decide if its a server-version or not. I only have XP Pro, where ProductName="Microsoft Windows XP" and CurrentVersion="5.1"

    I know 5.1 stands for XP, 5.0 for 2k and 4.0 for NT, but what differs 2k from 2k Server and what's the values for 2k3 ?

  6. Somewhere in your winnt.fis file there's a section


    so that thisbatchfilesname.cmd gets executed at the end of XPs install procedure. It's that file they mean.

    There's several ways to call programs upon end of install and this is one of them. Search the fores to find more (there's WPI for example)

    Hope I could help you.

  7. @nivek7:

    Since the machine can't read your brainwaves yet, you have to do some typing to inform it of the apps you want it to install. Your question indicates you have that information, but in another format. Give an example, be more specific what your needs are. What's the "config format from RunOnceEx" ??


    I saw such a thing once. People told me it wouldn't work on 95, 98, 98se or ME. Since I don't have any of there OSs installed I cannot check that, but perhaps you know it. In the end I'm not sure if the whole WPI thing would work on any of these old OSs.

  • Create New...