Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: motorollin on March 28, 2008, 04:52:38 PM
-
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 (http://aminet.net/package/biz/p5/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
-
That's normal for 3.1. I think it's a SetPatch issue that's only resolved in 3.5+. Doesn't adversely affect anything, though.
EDIT: These (http://phase5.a1k.org/) are the best 060 libs to use with any installation.
-
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
-
Why don't you use OS > 3.1?
-
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 (http://aminet.net/package/util/boot/SetPatch_43.6b) help with the CPU issue?
--
moto
-
motorolin, beware of the HD size limitations on 3.1 ... they just suck :madashell:
-
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
-
Yes, you should install the most recent Setpatch. It actually resolves some minor issues unpatched by earlier versions...
-
@ motorollin
That's a semi-official SetPatch, so you're in good shape. The Envoy network package even installs it automatically. Personally, I wouldn't mix a 3.9 CPU command with a 3.1 system (just a little OCD behavior on my part), but it's probably fine to do.
3.5 didn't come out until late 1999 and there was loads of 060 software on the market before then so I don't think you need to worry about the faulty autodetection with 3.1 (ShowConfig is also affected). As to CGX, I don't believe there are 060 libs. Just generic 040 and up.
-
Cheers Matt!
--
moto
-
@ moto
You're welcome!
I also just remembered, the phase5 060 software included a special CPU command called CPU060 to supplement the one from Commodore. It's been ages since I had it installed and I'm not sure I ever had to use it when it was, but it should be in an archive on that same page if it interests you.
-
keropi wrote:
motorolin, beware of the HD size limitations on 3.1 ... they just suck :madashell:
I probably deserve a boot for asking this one, but what are the limitations for each of the OSs. I went postal and bought a few amigas. My credit card is screaming for mercy.
-
The 68040 flag is set on a 68060 as well as the 68060 flag. A program that was written before the 68060 came out will see the 68040 flag but doesn't know to check for the 68060 flag so it reports a 68040. It's not a bug but treating a 68060 as a 68040 can cause problems in some cases.