Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by favorini

  1. I figured it out! For a BAT file, use this: Command: C:\WINDOWS\system32\cmd.exe Command arguments: /c C:\admin\notify.bat "Argument with space" [Quota Path] LastArg Working directory: C:\admin For a VBS script, use this: Command: C:\WINDOWS\system32\cscript.exe Command arguments: //nologo C:\admin\notify.vbs "Argument with space" [Quota Path] LastArg Working directory: C:\admin In both of the above cases, I was able to get "quoted arguments" and [FSRM Variables] to work as arguments to the scripts. To see a list of FSRM variables, run the following command: dirquota notification /? Note regarding permissions: If you are running the command as LOCAL SERVICE or NETWORK SERVICE, you will need to make sure that account has read access to the command you are trying to run. Also, it will need write access to any files you want to write to. Note: If you give non-privileged accounts write access to the command file or directory, you will get an error saying "The specified path is insecure" and Event ID 12300 in Application Event Log. These accounts shouldn't need write access to the command or its directory. You can configure the command to run as SYSTEM, but don't use SYSTEM unless you really need to. I.e., don't just use it as an easy substitute for setting the correct file permissions.
  2. I noticed the same problem. The specified command also seems not to run if you pass a "quoted string" as an argument. Anyone out there have any luck getting this to work? I'd really like to run a command with such variables as arguments.
  3. Passing the /l argument to install.exe will create a verbose MSI log file in %TEMP%. If you want to put the log file somewhere else, you can use this: dotnetfx.exe /q:a /c:"install.exe /q /l X:\logdir\dotnet.log" If the path to your log file has a space, use this: dotnetfx.exe /q:a /c:"install.exe /q /l ""X:\dir with space\dotnet.log"""
  4. Is there a version of the MSI that is bundled with Shockwave, like there was with 7.0.19?
  5. Can you set "Computer Description" from unattend.txt? I am talking about the description shown on the Computer Name tab of System Properties. AKA the server service comment. I am using XP SP2. I was unable to find any entry in unattend.txt that seemed right. Any ideas? Note: I did find netcomment.exe here, but I'd rather do it in the unattend.txt, if possible. Thanks, Francis
  6. OK, to answer my own post: yes. WindowsXP-KB834707-x86-enu.exe supports the /integrate switch (although it isn't mentioned in the security bulletin). WindowsXP-KB834707-x86-enu.exe /integrate:W:\WinXPsp2 where W:\WinXPsp2 is your AIP (i.e. contains the I386 directory, etc.) seemed to work for me. -Fran
  7. So is there a way to slipstream the IE hotfixes, like MS04-038, into an XP SP2 admin install point? -Fran
  8. Within the past month, they changed the email you get when you register for the Flash and Shockwave Players Distribution Program (http://www.macromedia.com/support/shockwave/info/licensing/). It now includes links for Combined EXE Installer for Windows: Flash and Shockwave (not the latest version; does not include Yahoo toolbar) and Combined MSI Installer for Windows: Flash and Shockwave 8.5.1 as well as some links for Mac versions. Here is a thread on the Macromedia forums where a user states that MM said they plan to update the MSI version in the next release. -FF

  • Create New...