Welcome, Guest. Please login or register.

Author Topic: A Startup sequence problem  (Read 2712 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: A Startup sequence problem
« on: January 29, 2005, 05:56:51 PM »
@melott

Where exactly is the KSRemap file on your system? Remember, when you first start up the machine (no startup-sequence), the only places the system looks for stuff is

Current Directory
C:

Further into the boot sequence, a load of additional search paths are added by the PATH command to cover utilites, tools, system etc.

Assuming your KSRemap file is in the Utilities drawer, you should just do

Utilities/KSRemap QUIET

as Patrik suggests.

To be totally certian, you can even prefix with SYS:, eg

SYS:Utilities/KSRemap QUIET

Of course, if your KSRemap file is in some other drawer, you must make sure the full path to the file is specified.

-edit-

Incidentally, it isn't a good idea to put these kinds of low level commands into WBStartup. This drawer is meant to be used for tools that should be started when workbench is opened, not when the system starts booting.
int p; // A
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16882
  • Country: gb
  • Thanked: 6 times
    • Show all replies
Re: A Startup sequence problem
« Reply #1 on: January 29, 2005, 06:12:27 PM »
QUIET just suppresses any textual output from the command that might otherwise force a console shell to open. If such a shell opens *before* the system preferences have run (IPrefs) it will get into a flap when it tries to change screenmode.
int p; // A