startup-sequence without opening CLI window

[Mathesar]

Hi,

I have been tinkering with Mika's A500ide IDE controller. For those that don't know, it is a simple non-autobooting A500 ide controller.

To boot the system I made a booting floppy that contains the following startup-sequence:

mount fre: from ide.ml
cd fre:              ;With KS1.3: fre:c/cd fre:
c/assign c: c        ;sys: etc. assigned to harddisk
assign sys: ""
assign devs: devs
assign libs: libs
assign l: l
assign fonts: fonts
assign rexx: s
assign envarc: prefs/env-archive
assign s: s
path reset

failat 22
execute s/startup-sequence ;this is executed from the hard disk!
endcli

This script mounts the harddisk partition and then transfers the rest of the boot sequence the harddisk.

On the harddisk I have ClassicWB installed.

The problem is that the floppy startup-sequence opens a CLI window thus causing an annoying requester when workbenchh tries to reset the screen. This happens even though none of the commands generate any CLI output. Add >NIL: to all the lines didn't help.

What could be the problem here? I also figured out I need a proper system-configuration file in devs: otherwise my topaz font has the wrong size. Could it be caused by a setting in this file?

Any ideas appreciated.

[Amiga1992]

It is weird, if you don't have output the window shouldn't show up.

But I think you turn output on with failat 22. Why do you have that at all? Try commenting that line out and see what happens.

system-configuration is for 1.3 as well, isn't ClassicWB 3.x? You don't want to mix stuff up so be careful about that.

[mark_k]

What program did you use to make the disk bootable? If the bootblock code is the WB 1.x version, the CLI will always open. If you Install DF0: when running Workbench 2.0 or later, it installs different bootblock code and the initial CLI will only open if some program outputs text.

[DamienD]

Is there something in the s/startup-sequence that you are executing which launches a CLI window?

[Amiga1992]

Originally Posted by mark_k

What program did you use to make the disk bootable? If the bootblock code is the WB 1.x version, the CLI will always open. If you Install DF0: when running Workbench 2.0 or later, it installs different bootblock code and the initial CLI will only open if some program outputs text.

This has to be it, I had forgotten about that.

[Mathesar]

Originally Posted by mark_k

What program did you use to make the disk bootable? If the bootblock code is the WB 1.x version, the CLI will always open. If you Install DF0: when running Workbench 2.0 or later, it installs different bootblock code and the initial CLI will only open if some program outputs text.

I thought I installed this disk on my A3000 which run OS3.9.
Shall give it a second try though.

[Mathesar]

Originally Posted by Akira

It is weird, if you don't have output the window shouldn't show up.

But I think you turn output on with failat 22. Why do you have that at all? Try commenting that line out and see what happens.

system-configuration is for 1.3 as well, isn't ClassicWB 3.x? You don't want to mix stuff up so be careful about that.

I commented out the stuff for KS1.3. The system runs fine BTW. The A500ide is actually a very nice HW project. I shall try removing the failat 22.

[Amiga1992]

That won't do it, I was barking up the wrong tree.
Check about the floppy disk installed bootblock like mark_k said, your necessity to use system-configuration hints to something being a bit weird there.
What kickstart are you running? Which Workbench version?

[Predseda]

Originally Posted by Akira

system-configuration is for 1.3 as well, isn't ClassicWB 3.x? You don't want to mix stuff up so be careful about that.

system-configuration stores colors, mouse pointer etc. and it shouldn't interfere with startup-sequence, no matter the OS version, IMO.

[Mathesar]

Originally Posted by Akira

That won't do it, I was barking up the wrong tree.
Check about the floppy disk installed bootblock like mark_k said, your necessity to use system-configuration hints to something being a bit weird there.
What kickstart are you running? Which Workbench version?

I am running KS3.1 with ClassicWB lite 3.1.

I copied the system-configuration from classicwb to the boot floppy.
Without it, the system would boot with the wrong font size.

But I will check the boot block tomorrow!

[Amiga1992]

The font you see before IPrefs kicks in is defined by system-configuration, yes.
Maybe that is what's opening a window? If you are running 3.x, a window should not open if there's no output. Unless, as said by mark_k, the floppy bootblock is 1.3

[idrougge]

Originally Posted by mark_k

What program did you use to make the disk bootable? If the bootblock code is the WB 1.x version, the CLI will always open.

You learn something every week.

[Mathesar]

Originally Posted by mark_k

What program did you use to make the disk bootable? If the bootblock code is the WB 1.x version, the CLI will always open. If you Install DF0: when running Workbench 2.0 or later, it installs different bootblock code and the initial CLI will only open if some program outputs text.

This was it! Problem solved .
I had been trying all kind of things to solve the fontsize problem (which turned out to be caused by a wrong or missing system-configuration file) and one of the things I tried was using a modified WB1.3 disk. I re-installed the bootblock and now things work like a charm.

I will post my version of A500ide next week or so. I made a nice board that fits internally to the computer that includes some ide timing improvements as well.

Thanks!