Re: INSTALL.CMD


<cut>

Thanks for the ideas and inspiration, I'll investigate it further.

Anyway, the time stamp, the extended atributes and so on ARE LOST
when you put the EXE file inside the CMD file.

There are a few identified disadvantages:

- size (<64 KB, EA-related?)
- by default no compression
- it's not that obvious that "INSTALL.CMD" can be deleted when done
- occupying about twice the size of the *.EXE when INSTALL.CMD is kept
- indeed loss of EA's, e.g. both MY.EXE and MY.ICO required
- to be honest, no "Disk full?"-checks, et cetera

WarpIN packages (WPI or EXE) are a better option, I think.

In general, yes. In this case I need customized interaction with the
user, and there's no "the" way to install the *.EXE. I recommend to
install it in a certain way, but it also works any other way. WarpIN
could fullfill my needs. If so, a part of the interaction/information
may get lost due to repetetive use of the "Next>"-button, so that's
why I tried to embed the *.EXE in a single *.CMD first.



---
.

Relevant Pages