Romtags list duplicities?

[DaMi]

During playing with Deneb's flash rom, I found out I have several duplicities in a list of resident romtags. Although I empty Deneb's flash rom, Scout still shows several duplicities. Can anybody please explain why? Or are they not duplicities? :-)
http://www.efektivne.cz/residents.png

I use A4k desktop, CSPPC, CVPPC, Deneb, Xsurf, Repulse on WB3.9BB2.

[meega]

I seriously doubt that there are any duplicities... but I suppose there might be duplicates ;-)

Apart from that, I cannot offer any (more) help.

[Zac67]

Hmm - since the duplicates also share the very same address, I'd guess it's just a display issue.

[DaMi]

Sorry it's not easy for me to express in English. I hope the question is understandable   ;-)

[DaMi]

@Zac67: So you think they are just old romtags updated by BB2 or something similar?

[Piru]

*EDIT*

After checking out the relevant scout source code it probably is due to duplicate entries from KickTagPtr and ResModules lists. Scout should probably filter out duplicate entries found from both lists.

[mgerics]

@DaMi1
No need to apologize. At leat you are trying to use our language - most of us don't even put htat much effort into anyone elses' language!

[DaMi]

Does it mean it's display error of Scout and I should not bother about it?

When I run my amiga without SS and then I run scout, the result is the same. when I remove deneb, the result is also the same.

Anyway, I use the lastest version of scout from Aminet - 37.290 (3.6).

[Zac67]

Possibly this duplicate display is intended by the author. One of the entries is highlighted, probably to differentiate KickTagPtr and ResModules items and those appearing twice may be in both lists. You can find out more by clicking on More.

[platon42]

DaMi1 wrote:
During playing with Deneb's flash rom, I found out I have several duplicities in a list of resident romtags. Although I empty Deneb's flash rom, Scout still shows several duplicities. Can anybody please explain why? Or are they not duplicities? :-)

It's been a long time since I touched these things in detail, so please don't beat me to death if this wrong or twisted: There are two lists: the ResModules and the KickPtr with optional KickMem list (highlighted in Scout). The first one is initially generated by exec by scanning the Rom contents, the second one contains additional RomTags that may or may not be used to insert or replace modules into the list of ResModules depending on its version number. The ResModules are those that are used during startup of the machine. If the rom module is replaced or added due to higher version (or non-existence), you will find it in the ResModules list (not highlighted in Scout) as a duplicate (with the same address, as for most RomTags in your screenshot). If it not used, it will not show up in the ResModules (as with the NoIDE tag, probably due to higher version number of the scsi.device patched in by SetPatch over the NoIDE romtag you installed).

Depending on which boot loader your using (permanent or standard), the RomTags from the Deneb will either go into the ResModules list directly every time you boot (standard) or be added to the KickTagPtr and KickMemPtr once (permanent).

The only exception are RomTags that need to be added very early during the boot, such as exec.library updates or anything that's before diag init (bootloader code from Zorro II AutoConfig), which will always be added to KickTagPtr and then reset the machine to make it become effective by the standard exec mechanism that builds up the ResModules list.

[DaMi]

@Platon42: Thank you very much for explanation, you are probably right, I would like just add, that most of the "duplicates" occur after setpatch (eg. rom update, filesystem, excec...) they are not connected directly to deneb's flashrom, because when I remove the deneb, I see the same results. So far, I haven't put romupdates into flashrom, but I plan to do so soon :-).

@Zac67: When I choose the More button, I see the same details for both romtags.

Thanks for your answers...