Apollo 1260 - Amiga recognize CPU and memory but don't boot

[huschel5]

Hello,

I want to use the Apollo 1260 card. So at first I copied the libs 68040, 68o40o and 86060 from the floppy to my libs folder, than I copied the CPU60 file into my c folder. Shutdown the AMiga, installed the 1260 and boot.

But nothing happend, only a black screen. So ich checked into the boot menu the expansion board diagnostic:

bord number: 1
manufacturer: 8738
product: 35
status: working

Ok, all looks fine. Than I boot the Amiga without startup-sequence and check with the command CPU the prozessor. The Amiga found the 060 CPU

I tried again to boot from HDD, but the Amiga shows only a black screen. In the next step I boot from the WB3.0 floppy. The Amiga recognized the memory (RAM). So I typed CPU into the shell and the Amiga recognized the 040 CPU.

I used the OS3.1, OS3.5 and OS3.9. With all OS occured the same issue.

Today I changed the board Rev from 1D4 to 1D1 but the issue are the same.

So, what can I do now?

[fc.studio]

In my opinion hard drive seems the problem. I would try an hard drive faster to boot.

[Toni Wilen]

Non-68060 compatible patch in HD's startup-sequence?

[Zetr0]

sounds like a "setpatch" problem, I cannot be sure.

OR! it could be IDEFIX if you have that running in your startup.

[ant512]

Can you post the contents of your startup-sequence and user-startup files?

[Charlie]

Hi, I've got a blizzard 1260, the following may be relevant to you:

The previous comments are well worth investigating but given you have a 1260 & your miggy thinks it's an '040 the explanation my well be to do with your libs.

It's a known 'gotcha' with 060 card's that installing them properly isn't always that obvious. (especially with later driver releases)
Partly down to (dare I say it) a poor choice of names & less than fantastic documentation. Also AOS isn't wholly '060 aware so the drivers are a bit of a kludge.

This page may well help you out. Look for the bit titled: 'The mess with v 43+ 68040/68060.library: installation instructions'

I know this is a Blizzard not Apollo site, but the principle is the same.
I hope that helps.

Regards

[huschel5]

Many thanks

At first, I tried three different HDD (40GB Samsung 3,5", 850MB manufacturer unknown 3,5" and 250MB IBM 2,5")

I used the 40GB with OS3.9, fast ATA and 1D4 board. The 850MB with OS3.5, IDEfix'97 and 1D4 board. The 250MB with OS3.0, Amiga-IDE port and 1D1 board.

So I will copy here my startup-sequence and user-startup file.

I never changed something in my startup-sequence relating to use the 1260.

[ant512]

The Apollo is slightly different to the Blizzard. The Blizzard has a 68040 library (that acts as a dummy) and a 68060 library (that contains the real library). The Apollo has three libraries - 68040 (dummy), 68060 (real) and 68o4o (contains some of the standard 040 library). If you've copied all of these over and are running SetPatch in the startup-sequence, you've got the software installed correctly.

Most Amiga programs will report a 68060 CPU as a 68040. The 68060 was released after ROM3.1, so none of the built-in programs or programs of that era are aware of the 060 CPU. They treat anything with a revision number higher than an 040 as an 040.

It sounds to me like you've got an extra program in your startup-sequence that isn't compatible with the 060 and is crashing the system before it boots. There are plenty of programs out there that will do this. On a 1D.1 motherboard you shouldn't have any hardware problems (assuming you've got an adequate PSU - you're not running the lightweight powerpack, are you?), especially if you've already tried different hard disks.

I've got two Blizzard 1260s and had an Apollo 1260/75MHz and an Apollo 1260/66MHz. I got rid of the Apollos ages ago, so can't remember exactly which programs gave me problems during bootup, but I had no end of problems with the Apollo cards and can probably still recognise some of the issues if I can see the boot scripts.

Hmm, that's a good point, actually - do you know if you've got a 50MHz board or the 66MHz board? The 66MHz version uses a (very poorly) overclocked 50MHz chip, and isn't particularly reliable. If you can get sysspeed or something similar running you should be able to find out.

[Charlie]

@ant512:
I stand corrected - just sounded so similar to the kind of trouble caused by the blizzard mis-installed lib's thing, I wondered if it was a similar issue.

[huschel5]

Enclosed please find my startup-sequence and user-startup of my OS3.5 system.

I have the 50MHz 1260.

I'm a beginner in Amiga stuff and some months ago I boot my old A1200 without any problemes (after more than 10 years). Therefore I started to use my A1200 for fun and so on.

So I don't know what your are mean with lightweight powerpack.

[Toni Wilen]

Startup-sequence looks normal, perhaps it is SetPatch that freezes.

Boot without startup-sequence. Run SetPatch manually, keep both mouse buttons pressed and select boot without ss again.

Run SetPatch again, does it say anything about 68060 support? Output of CPU-command?

[ant512]

It could also be something unusual in the Commodities folder - what have you got in there?

[huschel5]

If I input the CPU command the Amiga recognize the 68060 CPU but with setpatch command the Amiga freeze.

My commodities folder include the following:

exchange, click to front, fkey, blanker, cross dos, mouse blanker, auto point and no caps lock.

On my Apollo is the CPU MC68LC060RC50 installed (not the best one, I know).

[ant512]

SetPatch is the program that loads the 68060 libraries. If that's crashing the libraries might be corrupt. I've got a DMS of the Apollo driver disk; if I zip it and upload it to the zone, do you have any way of getting it back onto a real floppy?

[huschel5]

I downloaded from two sites a apollo.dms file. Both are the same.

There are two interested folders for me. One are the libs folder with the 68040, 68o40o and 68060 librarys and the second one are the 68060 folder with the three libs and the CPU60 file.

I tried both folder from both floppys without any success. I copied the CPU60 file to c.

Somewhere in the web I read about an script on the floppy which installed/copied all necessary files. But I can't start any scripts or something else.

[Paradroid90]

Ah!!! Fun with Apollo 1260 been there done that........Zetro can confirm that lol......Anyway could be a libs problem....Question does the Amiga sound like its trying to reboot constantly or Guru message? Libs must be installed first before you place the card on the expansion socket on your A1200 if you dont the system will crash. Im not the real expert on Apollo's .........but i know a man who is Zetro over to you lol. But if you do get it working its a great card have mine working under OS 3.5 on a 1D4 Mobo with 64mb on board

Hope this helps!!!

[Zetr0]

@Para

thanks for the kudos my friend, but the truth is YOU are the one that stuck with it to get it working!!!!

now, it does indeed sound a lot like the libs / setpatch, what i would recommend is that you first unplug the 060 card.

Load to workbench and when done, delete the existing files from the hard drive. Now copy-move the files from the Apollo Disk to the correct place.

check your version of setpatch while we can "newcli 5:>setpatch #?" what version are you using ?

now turn your amiga off. plug in the 060 and turn on.

if you are getting a failure at this point, its most likely set patch. try commenting out this line in your startup-sequence with ";" see how that does...

[Paradroid90]

Zetro what do you think set up a English Apollo 1260 Board to run along side this board.!!!

There would be plenty of threads

[Paradroid90]

Sorry just a thought!!! Install 3.5 fully first then move the libs and CPU 60 command from your Apollo Install disk into libs and c. The set patch installed from 3.5 deffo works on my version!

[Josh]

Originally Posted by Zetr0

check your version of setpatch while we can "newcli 5:>setpatch #?" what version are you using ?

Are you sure it's "setpatch #?"
I'm sure you was mean open a newcli and type in "version c:setpatch"
Of course without ""


Cheers Josh