CompuServe Thread

#USERSTARTUP deleted @#$$

11 messages in this thread
#187695From: Bob JennichesMar 6, 1995 6:21 AM
Yesterday I accidently deleted USERSTARTUP. The reason I did this was because I was looking in the sys: dir. and found two USER STARUP's. One writen USER-STARTUP and the other USERSTARTUP. Well needless to say the system won't bootup. whats the purpose of two of these startup's? And how can I get my system to bootup? Thanks Bob
#187705From: Zeddock MillerMar 6, 1995 8:30 AM
try undeleting the files first. Use DiskSalve by Dave Haynie or Undel Zeddock Miller
#187713From: Bob JennichesMar 6, 1995 10:02 AM
Zeddock, How do you undelete if it doesn't finish booting up? Please give me step by step instructions. Thanks Bob
#187726From: Don Curtis/SYSOPMar 6, 1995 11:54 AM
Bob, It'll boot into a CLI rather than WorkBench. Or you can simply hit (and keep hitting) Control-D as soon as it starts up…that'll cancel execution of startup-sequence (which calls user-startup). Don
#187755From: Hank DuckmanMar 6, 1995 3:59 PM
Bob; You can also access your boot screen by holding down both mouse buttons on starting your machine. Choose"boot without startup sequence" option. You will then get a shell. Assuming you have DiskSalv on a hard drive, you simply go to the drawer in which DiskSalv is located and "run DiskSalv". Hank
#187764From: Betty Clay/SYSOPMar 6, 1995 4:55 PM
Bob, If you have not written to the drive since you deleted it, you can probably use DiskSalv to retrieve the file. User-Startup is one of the files called by your Startup Sequence. You don't actually HAVE to have one, but it is the place to put all the things you do to customize your Amiga. Leave the original Startup Sequence just as it came from Commodore, and put all of your other assigns and special program requirement stuff in User-Startup. I suspect your system would boot if you just made a file named User-Startup and wrote a few commands in it, like (for example) Assign AutoPilot: dh0:AutoPilot But you'll have to rebuild all the neat things you had done to make your Amiga work the way you want it to work. Every program you install puts things in that User-Startup file. —Betty
#187767From: Bob JennichesMar 6, 1995 5:24 PM
Betty, There already is a User-Startup but it doesn't seem to be reading it. Bob
#187811From: Bob ChapmanMar 6, 1995 9:10 PM
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! ——
#187821From: Bob JennichesMar 6, 1995 9:52 PM
Hi Bob, The problem has been fixed. When I deleted the file USERSTARTUP (Not " USER-STARTUP " ) it was put in there by a file called DIRECTOR. And since iit was in the STARTUP-SEQUENCE and then came across this file and then looking for the USERSTARTUP, since I deleted it thats when the problem started. So I got into STARTUP-SEQUENCE and ; the assign out for DIRECTOR. Now verything works fine. Thanks for the help. Bob
#187829From: Bob ChapmanMar 6, 1995 10:21 PM
Bob – > The problem has been fixed. Glad to hear it! ——
#187923From: Joachim SondermannMar 7, 1995 12:49 PM
Bob, I come to believe that someone has messed up your startup-sequence. You should not need to have a user-startup to boot your system. The usual lines in your startup-sequence should be like those below: IF EXISTS S:User-Startup Execute S:User-Startup EndIF There should be nothing in startup-sequence to the effect of unconditionally executing user-startup or userstartup. If your setup is done the way C= recommended it, then in user-startup or whatever you like to call it will be only commands that are not vitally necessary to boot your system up. Those are located in startup-sequence. In user-startup you should keep any additions to the "pure" system. You said your system doesn't boot at all. Try to start it from an original Workbench disk, then check your startup-sequence, using ED, the C= editor, e.g.. I could send you an original startup-sequence, if you need it. Please let me know which version of the OS you use. Hope it helps, Joachim Sondermann-Bieker on Amiga AutoPilot 1.77 from Cologne, Germany