There are several good reasons to keep a user-startup and startup-sequence seperate. When I still had my A4KT I was switching back and forth between WarpOS and PowerUP not to mention changing the graphics install between CGX and P96. I had it set up so that I could boot with PowerUP and CGX or PowerUP and P96 or go with WarpOS and P96 etc. Also there were some programs that didn't like to work with each other so some environments were disabled on booting. Custom scripts were written to replace the user-startup script for when I wanted to reboot the computer to play a hard drive installed game that required a few changes to the hardware via degrader. I also had some custom user-startup scripts that I used to handle multiple environments for different users and such. In all, I think I had a total of 340 someodd lines of hand written user-startup scripts. Probably more, who knows. Then there were the custom scripts that were written in arexx to handle the all the changes made to each of these scripts depending on the boot. When I ran a hard drive installed game that required a reboot to run, it would copy back the startup-sequence and boot right back into workbench without a problem. With all the components that I had and the custom amigados scripts and arexx scripts I had controlling how my Amiga booted, I couldn't use just 1 startup-sequence.
Oh yeah... plug for my friend Roj... I also had been testing something called IMACS which on a warm reset had me booted to workbench and connected to the internet in less than 4 seconds using a regular modem. IMACS is the ultimate system controller for anything internet... from email to newsgroups to irc to web... you name it, it could do it. The damn cool thing about IMACS, I think he's still developing it but it was never released for the public last I checked.
:pint:
