A Startup sequence problem

[melott]

I have a minor startup sequence problem ..

On my A2000 /GVP TekMagic 060 with Kickstart remap
and FlickerFixer ScanDoubler.
It can't get the WB screen redrawn. Every time I reboot
I get a requester saying it can't resize the WB screen,
cancel or retry.
By hitting retry it always resets the screen.
Something in the startup sequence needs to be changed
or added but I don't know what. I think it has to do
with the KickStart remap.

Anyone know what needs to be done??

[patrik]

@melott:

Make sure everything you have added before the C:IPrefs line in your S:Startup-Sequence that outputs something has its output supressed. Either by redirecting it to NIL: (>NIL:), or by activating an option to make it quiet. The kickstart remapper sounds like a possible source of output before the C:IPrefs line.


/Patrik

[melott]

@Patrik

I just looked at the startup sequence and it looks
like everything is directed to >NIL:

I also think its something to do with the Kickstart
remap.
How much difference will it make if I disable the
KS remap?
If I understand correctly, remapping KS adds a little
speed. But for what I use that machine for, I don't
really need the extra speed, so I'm thinking I should
disable it.

Any thoughts on that??

[patrik]

@melott:

What kickstart remapper are you using?

Do you see any output before the resize requester appears?

The kickstart remapper adds quite some snappiness to Workbench and other applications using the routines in the kickstart rom a lot, it atleast severely hinders the 060 to be without it. Anyhow, have used quite a lot of kickstart remappers and have yet to stumble upon one that cant be made not to interfer with the startup in the way you are describing. Still, give it a go without it and see if it helps, it wont hurt .


/Patrik

[melott]

@Patrik

I'm using the install software for the GVP card.
(a GVP TekMagic 060 @50 mhz 128megs ram)

I just commented out KS remap in the startup sequence
and it booted fine, so it is the KS remap thats causing
the problem.

[patrik]

@melott:

In your S:Startup-Sequence, do go you call ksremap with the argument QUIET (ksremap QUIET)? If that doesn't make any difference, have you tried executing it from a shell when running Workbench to see if it reports an error of any kind, thus outputting something that produces the issue?

Btw, if you don't need the speed, I am willing to trade my GVP G-Force030 accelerator for your Tekmagic 060 ;=).


/Patrik

[melott]

@Patrik

After bootup, I called it from the shell, no problems.
It ran with no errors, said KS is remapped.

In the startup sequence its the first line.
the command is 'Utilities/KSremap'.

[patrik]

@melott:

Then just change it to "Utilities/KSremap QUIET".

Btw, not interested in my offer? :-? :-o :lol:


/Patrik

[melott]

patrik wrote:
@melott:
--------
Then just change it to "Utilities/KSremap QUIET".
--------
ummm.. That didn't work......
So I moved KSremap to the WBStartup drawer and that
works, I assume it does the same thing??

--------
Btw, not interested in my offer? :-? :-o :lol:
--------
 :-) umm sorry  :-) I like this card.

[Karlos]

@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.

[patrik]

@melott:

In what way did that not work? If you via the early-boot-menu boot without Startup-Sequence and execute the same line you have written in your S:Startup-Sequence, what does it say?

Atleast the KSremap on the latest Tekmagic disk from GVP-M supports the 'QUIET' argument. For earlier versions I don't know. You can always check what arguments it supports by typing in 'KSremap ?' in a shell. If yours doesn't support the 'QUIET' argument, putting a >NIL: at the end of the KSremap line should make it silent. Atleast the latest version on that disk is becomes completely silent with a >NIL: at the end of the line. With the 'QUIET' argument it isn't silent for me, but it should be for you as it is complaining that can't find suitable memory which isn't strange as I don't have a Tekmagic card.

I would recommend that you place KSremap in your C: drawer and insert the line "C:KSremap QUIET" as the first line in your S:Startup-Sequence to so the computer also will benefit from the added speed while booting.


/Patrik

[melott]

@Patrik..
@Karlos..

Ah.. (clumdsy fingers) ..

Yes that works now  :-D

Thanks ..

BTW .. just what does 'QUIET' do inthe the startup??

[Karlos]

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.

[patrik]

@melott:

The programmer who wrote KSremap added the option of it to be quiet and dont show any output if it gets the 'QUIET' argument when being executed, not more advanced than that. There are also other commands that supports the 'QUIET' argument, such as SetPatch. The programmer could as well have called the argument 'SVEN-GÖSTA' instead, but that would have been a bit too cryptic I suppose ;=).


/Patrik

[melott]

Well  :-D  thanks much for the help....
The Beast purrs like a kitten now .....