Jump to content

JasonKiller

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Serbia

Everything posted by JasonKiller

  1. Does Wpi have a Start /wait option for Nero? I want to use the Nircmd what Jasonkiller said but it only work when nircmd is extracted in Windows/System32. (btw.: It is working just GREAT when you stick to the "extract to windows/system32") OK, for Unattended disk you should have $OEM$\$$\System32\ folder on root of your CD disk. Anything you put into that folder get copied into Windows\System32 during the installation. So you can put nircmd.exe in $OEM$\$$\System32\ and it will be in the right place when you need it. Second posibility is that you make self-extracting archive wich contains nircmd.exe. This way you can call that .EXE in WPI before NERO commands, get nircmd.exe extracted in Windows\System32 and the rest is the same as before. I hope I make it more clear this time.
  2. You can try what I did: Download nircmd.zip and extract it in Windows/System32 folder (it must be in the PATH). In WPI use nircmd waitprocess SetupX.exe in next line after you call StartX for Nero. Nircmd waits until SetupX finish and exit, then continue with the rest of the commands in WPI. Here is my example: cmd1[pn]=['"%WPIPATH%\\Install\\Nero9\\Nero9.exe"']; cmd2[pn]=['"%systemdrive%\\Nero9\\SetupX.exe" /q EULAACCEPTED="1"']; cmd3[pn]=['nircmd waitprocess SetupX.exe']; cmd4[pn]=['cmdhide "%WPIPATH%\\Install\\Nero9\\Nero9_Links.cmd"']; cmd5[pn]=['cmdhide "%WPIPATH%\\Install\\Nero9\\Nero9_Clean.cmd"']; Good luck!
  3. If you only want to include MassStorage drivers for non supported mass storage controllers, you should use DriverPack MassStorage Text Mode. That slipstream drivers in your Windows installation, so your SATA HDD may be "seen" by Windows Setup. To start Finisher in your custom procedure use Custom method, and reference to DPsFnshr.exe in your .BAT or .CMD script, (like start %SystemDrive%\DPsFnshr.exe), but I didn't tested this method myself.
  4. I'm using method 2, it's faster then method 1, and AFAIK it's used more often. If you start Finisher form RunOnceEx you can use Custom start ID to set your own ID (other that default 937), and combine it with your other entries in RunOnceEx, if you have any. Folder D is created on %systemdrive% and it is where DriverPacks get unpacked during the setup. It must be created, but it is also deleted by Finisher at the end of the setup, if everything went OK.
  5. MillenX and Prober, thanks again for your help. I've solved my problem - restart in WPI before Nero silent install did the job - now everything works well. It seems that MillenX was right, it must be that Nero ask a restart, and without that, installation breaks. BTW, I think that MillenX's method of unattended install is best of all out there, because there is no modification of original setup files in any way, and I hope it could be used with next versions of Nero. Great work!
  6. Thanx for answer, i will try with restart in WPI install sequence before Nero get started, to see if that make any changes. As I said before, I don't get any dialogs or error messages. Is there any log file created during installation ?
  7. I'm having a problem when i'm trying to run silent install of Nero in WPI Wizard. I've created 7zip silent installer following the guide by MillenX, and in preinstalled Windows XP everything works OK, tested in VirtualPC and on a real machine. But, in WPI Wizard the same installer breaks in some point, without obvious reason. It looks like SetupX starts for a moment, and then ends without any messages or errors. Any idea what could be the reason for that?
×
×
  • Create New...