CompuServe Messages

Leslie, while, theoretically, the startup-sequence is supposed to be inviolate, according to (defunct) C= dogma, I have several modifications made to mine. There are times where you absolutely have to place a particular piece of software in the startup-sequence or, otherwise, the software will not function correctly. In almost every case, the software involves some level of patching of system vectors and functions (the internal routines of AmigaDOS) and there is no way around this. I do not know if this is the case with respect to MWB2, but it may be so. I do know that MWB1 did require at least the addition of one line to the startup-sequence (the NickPrefs line) in order to function properly. As with many things, it is a trade-off. I have an even half-dozen lines added to my startup-sequence, each of them a patch to the system, and they seem to be more well behaved than the patches obtained from other software. You get what you pay for. Be it in terms of actual money cost and/or in terms of modifications to your system. I just automagically copy my startup-sequence to a seperate file s:ss.copy upon every execution of editing that file. That way, I always have a previous copy to refer to when things go wrong. Which they usually do, ala Murphy's Law. The Four Seasons of Southern California: Fire, Flood, Earthquake, and Riot.