AmigaOS 3.9 BoingBag #4

[honx]

and what does this have to do with bb3/4? there is no afa-os on bb3/4...

[AMIGASYSTEM]

honx PowerWindows works on all OS3s, on AfA-OS I had to apply a special procedure that affects all 3.9 RTG systems.

AfA-OS is just an extension like VirtualPrefs but the system is a normal OS 3.9, where this function is missing and hopefully you can find it in the next BB, maybe with a new intuiton.library

[kolla]

I certainly hope there will be an update to icontrol prefs where this feature can be turned off, I hate how I now manually have place windows at borders.

OS3 could need an official tool like MUI PSI.

[honx]

i have a question about bb4rom added along with v1.50 update for boingbags3/4.

It assumes an A1200 is being emulated, with Windows directories instead of
HDFs.

does this mean:
do not use it if amigaos running on hdf? i only use hdf, i don't like directories.
i prefer separating amiga stuff from windows file systems...

and what exactly is this setmap which was added in v1.50 update?

[AMIGASYSTEM]

honx, i with all my systems based OS 3.9 BB4 use only HDF is I had no problem.

[Minuous]

There's no scsi.device in it. Seems to work OK even with HDFs though, WinUAE must access those through a different mechanism.

SetMap is a replacement for the equivalent program from OS1.x.

[macce2]

Could I bypass the loadmodule part in startup- sequence, if I had the according files flashed to eFlash4000 card ?
I mean the .resource files... ?! ( battmem.resource etc)

[Minuous]

@macce2:

If you already have the desired version of a library/device/resource in ROM, there is no need to LoadModule it.

There's nothing really special about .resource files as compared to .library or .device files, they are all just basically handled as libraries.

[macce2]

The problem is that I don't know, which modules etc. my Custom A4000 Rom chip ( 060 specific; came with the new A3660 board by tbtorro) contains ?!
It was said to be " Os 3.9 Rom"; I didn' t get more specific information.
If someone there with similar setup would know more, I' d appreciate any help.
By the way, wouldn't it be possible to transfer the contents of my physical custom Rom, to files ?!
I just downloaded the recent version of the BB3& 4 package, and just installed it over my older Os3.9 install ( with all the BBs installed).
However, I do have several problems.
The first is: The versions of the libraries etc. didn' t change to the more recent ones ( the relevant versions are mentioned elsewhere in this thread & other threads) ?!
How can this be ?!

Second question: With my Os3.9 060 specific Rom chip, and the AOS Rom update ( Bb2 ?!) flashed to my eFlash4000 card; would I need to use the SKIPROMUPDATE option of the Setpatch command, or not ??
And If I flashed also the most recent .resource files and, for example, the following " modules": FastFileSystem; Ram- Handler; trackdisk.device; KingCON- handler; console.device;
Would I need the Loadresident and or Loadmodule lines in startup- sequence at all ?!

[Minuous]

You can use ROMSplit to view the contents of the ROM and extract files as desired.

SKIPROMUPDATES tells SetPatch not to patch the current versions with the AmigaOS ROM Update file, so you will continue to need that.

If there are no modules needing to be loaded you would not need the LoadResident or LoadModule lines.

[macce2]

It seems I can't split my custom ROM.
Maybe someone using an A4000 with A3660 board & custom OS3.9 ROM chip by tbtorro could help ?

[grelbfarlk]

Originally Posted by macce2

It seems I can't split my custom ROM.
Maybe someone using an A4000 with A3660 board & custom OS3.9 ROM chip by tbtorro could help ?

You can't split a custom ROM into the component parts with Romsplit. Unless Doobrey has already configured it to know where the offsets are, which is unlikely unless it is one of the standard ROMs like 3.1, 2.04, 1.3 etc.

You can however use ROMSniff on a custom rom to find out what file versions are in it.

So if you use ROMSniff and it says you have funtimes.library 45.54 and that's included in BB4, then you can remove funtimes.library 45.54 from your loadmodule command.

I would avoid putting anything in your EFlash4000 until you know what's already upgraded in your custom ROM. Best case it does nothing, worst case it crashes badly requiring a power off to recover, less worsterlier it just throws some recoverable exceptions.

[macce2]

But from where to get that " ROMSniff" program ?

[grelbfarlk]

Originally Posted by macce2

But from where to get that " ROMSniff" program ?

Doobrey's site:
http://www.doobreynet.co.uk/

[macce2]

? Can't find ROMsniff from Doobrey's site.. ?
Is the app included in an another app prog archive ?

[grelbfarlk]

Originally Posted by macce2

? Can't find ROMsniff from Doobrey's site.. ?
Is the app included in an another app prog archive ?

Yes, it's in Remus in the tools directory.

[macce2]

The only module that I could make resident with LoadModule is layers.library..?!

[Minuous]

LoadModule won't replace components that have the same version number (even if the revision number is higher). You will need to use LoadResident for those.

[macce2]

Btw, all the floppy disk and cdrom icons started to appear with considerably faded, pale colours..
And because I have been testing with different lines on startup- sequence etc. and not written everything down,
I have no idea of what would be causing that ?

[PeterK]

With my icon.library 46.4 all deficons are displayed ghosted (50 % transparent) by default. If you don't like that you can either use the command IconGhostingOff from my Aminet package to disable it globally or add a tooltype "NoGhost" to the deficons like ENVARC:Sys/def_DF0.info or ENVARC:Sys/def_CD0.info.