Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


Everything posted by hasi001

  1. @bmn Your changes to winnt.sif are wrong. I would suggest the following: Winnt.sif: [GuiRunOnce] %systemdrive%\install\install.cmd %systemdrive%\cleanup.cmd 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): @ECHO OFF 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 %CDROM%\install\cleanup.cmd exit
  2. Hi bmn You've got a mistake in WINNT.SIF [GuiRunOnce] %cdrom%\install\wpi.cmd %cdrom%\install\install.cmd %cdrom%\cleanup.cmd You can't use %cdrom% there. put the .cmd Files in $OEM$\$1\Install and call them as [GuiRunOnce] %systemdrive%\install\wpi.cmd %systemdrive%\install\install.cmd %systemdrive%\cleanup.cmd 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. %cdrom% isn't a system varable set by microsoft. the others are. So you can use all vars you mentioned but %cdrom%. If you'd like a graphical interface for runonceex, try WPI
  4. By now this can't be done, but I see that it's important 'cause some apps may be dependent on each other. I'll put it on my list. [EDIT] There's a workaround, if not a good one. check out the WPI hompage help section. [/EDIT]
  5. Hi all ... Check out the WPI homepage for new version 2.9.4 Work on that pages is still in progress..
  6. 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.
  7. Hi. Read the thread Windows Post-install Wizard 1.2 Beta first. Then read this thread. Takes a time - but you'll get familiar with the program. If there's still any questions - ask again (... a detailled question will lead to a detailled answer)
  8. 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
  9. Version 2.9.3 changelog: last entry displayed twice in some circumstances - fixed os-depentent selection of progs - work in progress That's it.
  10. Ok. found the error's cause and fixed it. New Version 2.9.3 is out Check out the WPI homepage for new version.
  11. rodent. 1st question: if you put the file WIN51 in your VM's root on C: then it would function as %cdrom%. So if you call %cdrom%\\Install\\program.exe, it has to reside on c:\Install\program.exe I'll check your config on my system. Check back for an answer in a day or two.
  12. 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 ?
  13. send me your whole config.js as pm so I can search for an error. Is sorting set to true ?
  14. Sorry guys. Tried the search function (would't it be good to rename it to "read all threads by yourself" function) - no satisfying answer. Where can I find thr royale theme. Do I need any additional software and - if yes - is it free ? Thanks in advance.
  15. Remove that product key ! OemPnPDriversPath begins with " - so it should end with a " too. OemFilesPath=$OEM$ is not needed- Remove that. Don't know if its just that simple - but try.
  16. Somewhere in your winnt.fis file there's a section [GuiRunOnce] %systemdrive%\somepath\batchfilesname.cmd 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.
  17. @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" ?? @dhernande: 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.
  18. @all: Does anyone know, how to get Windows Version through WSH like "ver" in command prompt ? Registry Key ? Mod would be easy if I had this information.

  • Create New...