OS/2, eCS & ArcaOS - Technical > Setup & Installation

Startup.Cmd not executing

<< < (3/3)

Lars:
Just to add,
startup.cmd has to be a plain batch file. You cannot run a REXX script or a batch file that invokes a REXX script.

Eric Erickson:

--- Quote from: Lars on August 11, 2020, 02:56:34 pm ---Just to add,
startup.cmd has to be a plain batch file. You cannot run a REXX script or a batch file that invokes a REXX script.

--- End quote ---

Lars,

No it does not. I've been running my Startup.Cmd as a Rexx script since at least OS/2 V2.0, maybe even 1.3 but its been so long I can't remember.

As for the other suggestions, thats the path I'm going to try and go down. Use XWorkplace Startup or the General Startup Folder.

Cheers,

Doug Bissett:

--- Quote ---startup.cmd has to be a plain batch file. You cannot run a REXX script or a batch file that invokes a REXX script.
--- End quote ---

Well, yes you can, but you do need to be very careful when some stupid installer modifies STARTUP.CMD for you. Often they will put their stuff at the top, which breaks the "/*  */" indicator that it is a REXX file (the first "/*" must be on the first line, in position 1, for those who may not know). A call to a REXX script will also work, and helps to avoid the "helpful installer" problem. Generally, I find it best to keep STARTUP.CMD as simple as possible, with no more than the absolute essentials.

Navigation

[0] Message Index

[*] Previous page

Go to full version