OS3.9 not booting properly

The OS3.9 on my A4000 doesn't always boot properly. After a longer power down period the Amiga boots to the point where Workbench window is dispalyed but no drive icons or pointer. It takes either a few reboot cycles or more probably some time powered on before the OS boots properly. This occurs with OS3.9 when RTG screenmodes are used. I've got BB3 installed.

Could this be the A4000 PSU giving up on me or something else? I've got no other expansions than the RTG card. My hdd is a compact flash card and I've also got a CD-ROM drive.

hi your cf card could be playing up as mine did it or your cdrom could be conflicting with the cf

what brand of cf are you using ?

Quote:

---

Originally Posted by rs2klee

what brand of cf are you using ?

---

Sandisk.

Might be:
1) power supply
2) electrolytic capacitors on A4000 board (loosing their capacitance).

First off, you need to know the Amiga with OS3.9 boot cycle.

1) Power on
2) Load KS from ROM chips
3) scsi.device from KS on ROM chips look for IDE drive, can take a few seconds. If they are not there and it's KS 3.1 it can take up to 30 seconds
4) Run startup-sequence
5) Hit setpatch in startup sequence. Hups, requires reboot because of patching of ROM to be 3.9
6) scsi.device again, will linger and be slow...
7) Hit startup sequence.. finally, we're ready to start booting for real...

THis is just one source of slowness.

Then there are the hardware problems that you worry about that also can cause problems and instabilities.

@Arnjolt: When all goes well in boot, it'll take less than 30 seconds to boot. It'll basically show the Indivision logo, then go black for a while and then show the workench with icons. When all doesn't go well it's basically the same sequence and duration but workbench doesn't have icons and nothing happens after that.

What kind of CPU do you have?

That was the problem I faced on a clean 3.9 install on a 060, I had the wrong 040 libraries. RAM crashed when loading wb startup contents. I first thought it was the launcher which was buggy, but installing correct 040 libs (phase5 060 libs) and I was okay.

My boot success before I realised that was about 50~60%.

I've got a rev 3.0 A3640.

I would go back to first post (about cdrom) conflicts.

I never managed to get a ide cdrom going long time, and putting a cd in caused no booting machine WHEN it worked. (or if it worked)

LOL I chose the scsi route, but please eliminate possible causes and then we can take it from there..

I think the A4000 ide port is total ****