CompuServe Messages

Bob – > There already is a User-Startup but it doesn't seem to be reading > it. How do you know? 🙂 Seriously — have you visible evidence that 's:User-Startup' is being accessed — and, if so, how far does it get? (i.e. are any of the startup statements being executed — successfully or not) Back in the old old olden days of computing (and believe me I know) this would be the time to try and establish the 'standard' or original distribution configuration (if possible) since that might boot to a more useable (if not comfortable) configuration for pursuing the next tedious and (often) frustrating steps, i.e: (1) Find out what's in your 's:User-Startup' (2) Try and figure out what it was/is trying to do (<– this step is optional, of course 🙂 (3) Insert 'debugging' statements (like 'Echo "Now at line 3") to try to determine if the statements are being read (4) Check to see if there is evidence that the statements were executed e.g Was the 'Assign'ment actually made? (5) etc. Really though — there is no way (IMNSHO) of arriving at an answer to your original question > whats the purpose of two of these startup's? without knowing more about your HW/SW configuration — what version of AmigaDOS (1.3, 2.04, 2.1, 3.0 or what) are you running? — is it a 500, 1200, 2000, 3000T, 4000(<– ship it to me and I'll see what I can do :), what memory, a hardrive, …? — etc. or what was/is in your 's:User-Startup' and 's:USERSTARTUP'. As others have already noted, User-startup is where the 'boot' could be customized to suit your HW/SW configuration and your personal preferences. So, without some insight into those areas, one can only GUESS what your 's:USERSTARTUP' did. Good luck and please don't let my comments discourage you. It is a solvable problem with more info — and IMHO a lot more rational process than the bizarre 'PC Clone/MSDOS' config.sys+autoexec.bat boot nonsense! ——