OS3.1 thinks my 060 is an 040

[motorollin]

This is probably a really easy one, but I haven't installed 3.1 from scratch for a long time. I have decided to do so due to niggly problems with my 3.9 installation.

I have installed 3.1 on a new disk, and initially it wouldn't boot at all after the installation. I booted with no S-S and copied 68#?.library from my 3.9 installation to my 3.1 installation and it booted ok. However, "cpu" reports that I have a 68040. I downloaded 68060-V44_3 and copied everything from the Libs drawer to Libs:, and now 3.1 won't boot any more. The original libraries from my 3.9 installation correctly report a 68060, so I'm wondering whether this could be a setpatch issue. I'm using the one which came with 3.1.

Thinking about it now, I seem to remember I have to delete one of the libs (68040.library?) and rename one to replace it (the dummy?) but I'm really fuzzy on this so would really appreciate a pointer.

--
moto

[motorollin]

Ok thanks for that. I noticed when I was installing CGX that some of the libraries were 040 versions. Is there a hack to make the system appear (correctly) to be an 060 so that software which uses the cpu command to decide which version to install will detect the 060?

[EDIT]
Also, is it safe to use newer versions of setpatch with 3.1? For example the 3.9 setpatch? Would that fix the problem?
[/EDIT]

--
moto

[motorollin]

Because 3.1 always felt faster to me, and building the system with just what I want on top of an empty 3.1 installation feels cleaner than customising 3.9.

Would this updated SePpatch help with the CPU issue?

--
moto

[motorollin]

Setpatch 43.6b (linked by me above) plus the cpu command from OS3.9 has solved this problem.

@keropi
I'm using cybppc.device with PFS partitions. Should be ok shouldn't it?

--
moto

[motorollin]

Cheers Matt!

--
moto