< class='quote'>[b:]nlastovi wrote:[/b:]
I'm sure that since you are running on freeaxp, there isn't much need for "support". so I'd suggest take the .A saveset apart and edit KITINSTAL.COM to remove the check and then repack the .A saveset. I'm moderately sure that there is not a run-time check for AMASK/IMPLVER for EV56.
I don't think it's a matter of trying to trick RDB into not checking / by-passing the check
Oracle state that from a certain version of RDB 7.2.XXXX, they are not going to be producing non-optimised version of RDB anymore
In other words, the minimum supported Alpha CPU type is now EV56 (as per their product support pages - I don't have the link)
If FreeAXP presents itself as anything less than an EV56, then newer versions of RDB will not run (assuming it checks) and even if you hack the check, how long before you encounter an EV56 instruction set and get a bugcheck?
It would seem to me that the only way to use FreeAXP with later versions of RDB is if FreeAXP presents itself as being an actual EV56, or at least allows a setting of the same to be set (since according to Bruce, it runs as an EV56 internally anyhow)
In the end it was just easier to switch to EmuVM as that presents itself as an EV56 - simplest way to solve the problem IMO
