Nova Bits and Contribute Bits used

has 1.0.A changed them?

Searching the forum I found the following information in a couple of disparate places:

Quote

Used bits in Nova 1.0.9:
0-90, 96, 123-149, 152-170, 175, 178-237, 250, 275-327, 330-335, 340-341, 347-377, 415,
417, 422-446, 450, 467, 500, 502-503, 509-513, 515-519, 600-613, 650-653, 666-667, 677, 681,
749-753, 800-819, 838, 850-852, 995,

1000, 1100, 1300-1309, 1500-1502, 3000-3007, 3009, 3015, 3025, 3050, 3721, 3789,
4000, 4322, 4444, 5757-5765, 5770, 5999-6034, 6100-6106, 6137, 6200-6206, 6300-6302,
6666, 6723-6724, 7777-7788, 7878-7880, 8338-8340, 8444, 8888-8911, 9011-9015, 9111,
9200-9208, 9215-9216, 9333-9334, 9500-9501, 9666, 9812, 9995, 9998-9999

The EV:Nova scenario (v1.0.2) uses the following contribute bits:

Contribute0 uses 000003FF (the low order 10 bits) leaving 22 bits free for our usage.
Contribute1 uses C0000071 leaving 26 bits free.

As an addendum, the Contribute0 flags are used by the ränk and oütf resources and the Contribute1 flags are used by the shďp resources.

Does anyone have a list of current (version 1.0.A) bits and contribute bits used?

More important to me, does anyone have a utility for OS 9 that I can use to compile such lists myself?

A utility for listing c/r bits? No, but I do have one for control bits and also a list of what each c/r bit is used for but I don't know what version it relates to (it's the same number of bits that you show though).

Here's the quick summary from Mission BitMap II on Nova 1.0.A:

 Bit Usage Analysis:
 -------------------

 Total Bits Used		  : 0
 Total Unique Bits Used   : 554
 Total Bits Tested		: 2803
 Total Unique Bits Tested : 537
 Total Bits Set		   : 2202
 Total Unique Bits Set	: 551

 Bits Tested But Not Set:
  503,3005,9999,

 Bits Set But Not Tested:
  467,4322,6001,6003,6014,6015,6018,6019,6020,6021,6022,6024,6025,6026,6027,6032,6034,

This post has been edited by Guy : 18 July 2006 - 06:46 PM

@qaanol, on Jul 18 2006, 12:11 PM, said in Nova Bits and Contribute Bits used:

More important to me, does anyone have a utility for OS 9 that I can use to compile such lists myself?

I thought I'd sent you a copy of Mission BitMap back in January. Did it not work on your system?

For Contribute bits, if you search for posts by Zacha Pedro with the word "contribute", you should be able to find one where he explains how he came up with his list of used Contribute bits- I remember that it involved ConText and AppleWorks.

As for bit changes in 1.0.A, there don't seem to be any NCBs changed. I'm not sure about Contribute bits, although I suspect that those haven't changed either.

Edwards

@edwards, on Jul 19 2006, 04:33 AM (GMT+2), said in Nova Bits and Contribute Bits used:

For Contribute bits, if you search for posts by Zacha Pedro with the word "contribute", you should be able to find one where he explains how he came up with his list of used Contribute bits- I remember that it involved ConText and AppleWorks.

(...)

Edwards

Well, I don't know if anyone would want to do that, as it wasn't pretty. Basically, you ConText all the resources that use a contribute or a require field, then you delete all other stuff to leave only four columns: two for contribute and two for require (put 0x00000000 in the empty spaces). Then on the first line manually do 64 boolean cells that will each take a different bit from the data in the first columns, and copy these 64 down for as many lines as there are Contribute/Require lines. Finally, put a cell below the first column of 64 that massively ORs the column above it, and copy this cell 63 times for the other columns. There ya go, for each cell that says true, the corresponding contribute bit is used.

When I did it (probably on 1.0.8), I came up with the following result:
The ones already in use are the 23rd to 34th, 58th to 60th and the last, 64th bit (ordered in order of significance, most significant bit first, with the first field considered most significant so coming first), forming the hexadecimal 0x000003FF (first field) and 0xC0000071 (second field).

Log in to reply