inf file with nested quotes

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

what's the proper way to write this line? i'm not sure of the quotes
(wrapped for readability)

[DefaultInstall]
"StorageServer","""msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,
UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesk
top,
SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,
Services,DisksAndVols" /qn"""
 
Actually that should read [GuiRunOnce] instead of [DefaultInstall]... I was
just testing something there.
Basically I have a command line entry that executes fine from a cmd box, but
I need to put it in
unattend.ini which requires me to enclose the whole command in quotes... so
now I have quotes within
quotes and I don't recall the syntax for that.

Rob said:
what's the proper way to write this line? i'm not sure of the quotes
(wrapped for readability)

[DefaultInstall]
"StorageServer","""msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,
UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesk
top,
Click to expand...
SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,
Services,DisksAndVols" /qn"""
Click to expand...
 
Rob said:
what's the proper way to write this line? i'm not sure of the quotes
(wrapped for readability)

[DefaultInstall]
"StorageServer","""msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,
UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesk
top,
SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,
Services,DisksAndVols" /qn"""
Click to expand...

i always take the cmdlines.txt in the $oem$ folder to start installation
processes. Nice side effect is a "cmd" call. Here you get a command
shell to test your installation calls.
 
cant use the cmdlines.txt for this install unfortunately. cmdlines.txt wont
install .MSI files as there is no user logged in at the point when it is
run.

Martin Klinzmann said:
Rob said:
what's the proper way to write this line? i'm not sure of the quotes
(wrapped for readability)

[DefaultInstall]
"StorageServer","""msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,
UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesk
top,
SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,
Services,DisksAndVols" /qn"""
Click to expand...

i always take the cmdlines.txt in the $oem$ folder to start installation
processes. Nice side effect is a "cmd" call. Here you get a command
shell to test your installation calls.
Click to expand...
 
You can start a script at this position.

## File myinst.cmd ##
msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesktop,SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,Services,DisksAndVols"
/qn
## File myinst.cmd end ##

[DefaultInstall]
"StorageServer","cmd /C myinst.cmd"



If you don't like it, test the following entry. I'm not sure if it work.

[DefaultInstall]
"StorageServer","msiexec /i c:\stage\sasetup30.msi
ADDLOCAL='BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesktop,SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,Services,DisksAndVols'
/qn"


cant use the cmdlines.txt for this install unfortunately. cmdlines.txt wont
install .MSI files as there is no user logged in at the point when it is
run.

Rob wrote:

what's the proper way to write this line? i'm not sure of the quotes
(wrapped for readability)

[DefaultInstall]
"StorageServer","""msiexec /i c:\stage\sasetup30.msi
ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,
Click to expand...
UsersAndGroups,NetworkSetup,Logs,SystemBackup,AlertEmail,Shutdown,RemoteDesk

SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,FoldersAndShares,
Services,DisksAndVols" /qn"""
Click to expand...

i always take the cmdlines.txt in the $oem$ folder to start installation
processes. Nice side effect is a "cmd" call. Here you get a command
shell to test your installation calls.
Click to expand...
Click to expand...
 
Back
Top