Welcome, Guest. Please login or register.

Author Topic: user-startup -- Really useful?  (Read 9512 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AmigaHeretic

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 821
    • Show all replies
Re: user-startup -- Really useful?
« on: October 25, 2003, 01:36:28 AM »
First of all I have to ask how you figure it's any faster having something run from WBStartup as opposed to the user-startup?

My user-startup is mostly filled with Assigns that programs need ie.  assign dpaint: dh1:dpaint

To me it's just a lot easier way to keep track of everything.  I actually prefer to have as few things as possible in the WB Startup drawer and move them into user-startup to keep everything in one place.   It would seem cluttered to me to have all the assigns and programs in the middle of the startup-sequence somewhere.

As doomy would say, "You don't know what you're talking about when it comes to User-Startup!"
A3000D (16mhz, 2MB Chip, 4MB Fast, SCSI (300+MB), SuperGen Genlock, Kick 3.1)
Back in my day, we didn\'t have water. We only had Oxygen and Hydrogen, and we\'d just have to shove them together.
 

Offline AmigaHeretic

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 821
    • Show all replies
Re: user-startup -- Really useful?
« Reply #1 on: October 25, 2003, 02:03:48 AM »
Quote
Before it was very hard to determine which of the commands in the startup-sequences is executed first. (o.k., this is only a problem for those who are called in the startup-sequence after user-startup is started).


They're executed in the order that they are in the script.  How is elminating User-Startup going to change that?  And how exactly do you determine which programs are executed first in the WB Startup drawer now that you moved them there?

Quote
I had some troubles with this and only could avoid occasional gurus by inserting some wait commands at different places.


I have never had to nor have I ever heard of anyone having to add a bunch of wait commands in their startup-sequence to avoid a guru.  Even if you did have to, how would moving these programs out of User-Startup and into the Startup-Sequence fix it so that you didn't have to add these wait commands in anymore?
A3000D (16mhz, 2MB Chip, 4MB Fast, SCSI (300+MB), SuperGen Genlock, Kick 3.1)
Back in my day, we didn\'t have water. We only had Oxygen and Hydrogen, and we\'d just have to shove them together.