Well, as an example from your CHECKDISK script..

you create a configure script - let's call it CDcfg.kix - it asks for the name of the email account to send mail to, and the name of the mail server.

Once it asks for and the user enters those values (and you potentially do some error checking, like verifying you can resolve the mail server name in DNS), you write the values to the config file (called CHECKDISK.ini):
 Code:
CLS
'Send mail to: ' Gets $MailUser ?
' Mail Server: ' Gets $MailServer ?
$ = WriteProfileString('%S_CONFIG%\checkdisk.ini', 'COMMON', 'MailUser', $MailUser)
$ = WriteProfileString('%S_CONFIG%\checkdisk.ini', 'COMMON', 'MailServer', $MailServer)

Of course, this assumes that you have properly defined the System environment var "S_CONFIG", and have created the path it refers to. This could be done by the process used to install this utility.

Your process script - CHECKDISK.KIX - would begin by loading its parameters:
 Code:
If Not Exist('%S_CONFIG%\checkdisk.ini')
  'ERROR: not configured!' ?
  Exit 2
EndIf
$MailUser = ReadProfileString('%S_CONFIG%\checkdisk.ini', 'COMMON', 'MailUser')
$MailServer = ReadProfileString('%S_CONFIG%\checkdisk.ini', 'COMMON', 'MailServer')

; rest of your script . . .

That's the basic idea - you will need to customize this to your specific needs.

Glenn

Edited by Glenn Barnas (2008-04-22 07:57 PM)
Edit Reason: missing param
_________________________
Actually I am a Rocket Scientist! \:D