Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PDW Setup.lst

11 views
Skip to first unread message

Jim

unread,
Aug 25, 2002, 11:47:04 AM8/25/02
to
Hi,

Can anyone point me to a definition of the syntax for the [RunCommands]
entry created by PDW in the Setup.lst file? I have read MANY posts in MANY
NGs and haven't found anything concerning this entry.

TIA

Jim


Graham R Seach

unread,
Aug 25, 2002, 7:08:59 PM8/25/02
to
Jim,

Try here:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q189743&

Graham R Seach
Microsoft Access MVP
Sydney, Australia

"Jim" <jimcr...@cox.net> wrote in message
news:YZ6a9.7876$Ic7.7...@news2.west.cox.net...

Jim

unread,
Aug 26, 2002, 1:29:18 PM8/26/02
to
Graham,

Thanks for the pointer... unfortunately it doesn't address the syntax for
the [RunCommand] Command1 entry.

I have 'worked around' the problem by having the batch file check to see if
'c:\windows\system\regsvr32.exe' exists... if it does I use that path to
register DMO, and if the path doesn't exist I use
'c:\winnt\system32\regsvr32.exe' to do the registration.

It would still be nice to know how to manipulate the Command1 statement.

Again, thanks for your help.

Jim


"Graham R Seach" <gse...@REPLY2NEWSGROUPpacificdb.com.au> wrote in message
news:er#p5yITCHA.2216@tkmsftngp13...

Earl Lewis

unread,
Aug 27, 2002, 6:28:34 PM8/27/02
to
Jim,

I'm sure that this section of the setup.lst is what gets filled in when you
run the P&D Wizard and it asks you for a command to run after the
installation completes, although I've not tested it myself.

Have you tried to put in the path to a batch file or executable just to try
it out?

The only thing I would suggest in the way of syntax is to make sure you put
the string in quotes if there are spaces in your path to the
batch/executable.

Oh, and to think of it as a command line, so if you need to specify a path
to the executable and a separate path to a filename that you want it to load
make sure they're both in quotes.

Give it a try - *on a copy of your good file*. What have you got to lose?

HTH

Earl Lewis

"Jim" <jimcr...@cox.net> wrote in message
news:YZ6a9.7876$Ic7.7...@news2.west.cox.net...

Earl Lewis

unread,
Aug 27, 2002, 7:02:09 PM8/27/02
to
Jim,

My original assumption was correct, it does get filled by the PDW at the
point I suggested. However my syntax assumptions were badly off. Here's what
gets placed there when I tell it to run C:\foo.bat

[RunCommands]
Command1=0,1,$(AppPath),c:\foo.bat

Now that I see this I suppose you might have been asking about what each
element between the commas meant. True?

HTH

Earl Lewis

"Earl Lewis" <elewis...@nospam.virtual.com> wrote in message
news:OV6h0jhTCHA.3252@tkmsftngp12...

Jim

unread,
Aug 29, 2002, 6:04:05 PM8/29/02
to
Earl,

Sorry about being tardy in sending a reply... I've been somewhat spaced out.

True, the composition and manipulation of the command line itself would be
interesting. In what I have seen in several News Groups the syntax for this
line is a closely guarded secret... that or not many people actually know
what the syntax is.

Thanks for your replies and help.

Jim

"Earl Lewis" <elewis...@nospam.virtual.com> wrote in message

news:Otkwl2hTCHA.1636@tkmsftngp12...

Earl Lewis

unread,
Aug 29, 2002, 6:45:10 PM8/29/02
to
Jim,

I'm sure there's not a whole lot of mystery in this. The first couple
elements probably control execution order, visibility, modality,etc.. Stuff
like that. Just mess around with a few variations on the example I sent and
see what happens.

The thing I'd be interested in is to see if/how you would setup multiple
lines. Maybe the second element determines if it has to wait until prior
command completes?!?

Earl Lewis

"Jim" <jimcr...@cox.net> wrote in message

news:pTwb9.22830$Ic7.1...@news2.west.cox.net...

0 new messages