system-configuration editor

[Tony Landais]

I am doing a CD32 compilation and i am looking for an editor for the system-configuration file to have a black WB in 320*256 2 colors and a black mousse pointer

I don t want to see the workbench when my apps load and i want to save the maximum memory possible

[ant512]

The system-configuration file is Workbench 1.x's equivalent of the IPrefs system. To edit it, you need to get a copy of the Workbench 1.3 disk.

Boot the WB1.3 disk, save the preferences as you'd like them using the standard WB prefs editor, then copy the system-configuration file from the WB disk to your CD-32 compilation.

[Tony Landais]

the problem is the editor is too simple
you can t go lower than 4 colors and about the resolution it only propose to interlace or not so 640 256 or 640 512

is it possible to change it more ?

[Severin]

I don t want to see the workbench when my apps load and i want to save the maximum memory possible

Then don't load workbench... If you don't have anything outputting to the cli, you won't get a cli window open either...

[thomas]

Originally posted by Tony Landais
the problem is the editor is too simple
you can t go lower than 4 colors and about the resolution it only propose to interlace or not so 640 256 or 640 512

is it possible to change it more ?


Hasn't the CD32 Kickstart 3.1 ? With Kick 3.1 the screen stays black until the first screen or window is opened. Just ensure that no command outputs anything before your application starts.

As mentioned before the system-configuration file is limited to Kickstart 1.3 (and OCS chipset) features. The include file intuition/preferences.h contains the structure of the file. As far as I can see you can change the depth, width and height but not the resolution (so your 320 pixels will fill only half of the screen).

[gary]

As said before if nothing echos text the initial CLI window won't open and I presume that will save you the most memory. I would have used that technique myself but I wanted to debug the startup/menus so what I did was:

1. Bootup an emulator with Kickstart 1.3 and use the 1.3 preferences program to change all colours to black, clear the mouse pointer and save the changes to system-configuration. It is obviously a little tricky as it is difficult to know where on screen to click but it can be done.

2. Use a program like 'add21k' or 'add44k' that reduces the current screen depth by 1 bitplane for a 2 colour workbench screen.

[thomas]

How do you debug your startup files if you don't see anything on screen ?

[Akira]

As soon as an error appears there is an output to the CLI and the window shows up, unless you have set FAILAT 21 (i think) which will not make the startup-sequence stop if there is an error in one line.

[gary]

Originally posted by thomas
How do you debug your startup files if you don't see anything on screen ?
I usually CTRL+D the startup or have a program like 'checkkey' to watch for ESC or something to break the startup-sequence. Then I have a command that uses a 'setprefs' program to use an alternative configuration than the default to change the colours/mouse to defaults so I can see what is going on.

[andreas]

I used SCT (set color table) by A. K. Levin. (PD)

Nice little tool ... but not on Aminet.