Overview Features Coding Performance Forum Downloads Products OrderV4 Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Questions and Answers for AMIGA Workbench or Coffin

Workbench 3.1 On Apollo V4

Martin Ketter

Posts 70
24 Mar 2022 22:54


I installed the workbemch 3.1 on Winuae on a CF-card. When I try to run this workbench on the Apollo then the message appears "Insert DF0 in any drive"

I think it's because of the Icon "DF0:????" How can I delete this Icon or how can I prevent that apollo with CF-card with WB 3.1 installed try to read from any disk drives because there's no real disk drive and no emulated disk drive?


Amiga User
(Needs Verification)
Posts 104/ 1
25 Mar 2022 00:25


If you don't have a floppy drive, in the startup-sequence you have to deactivate all commands dedicated to DF0.

On OS 3.1 you should have the command:

C:AddBuffers >NIL: DF0: 15

The command is deactivated by adding a semicolon (;) in front of the command like this:

;C:AddBuffers >NIL: DF0: 15


Martin Ketter

Posts 70
25 Mar 2022 17:47


This command is in the startup-sequence. Despite of this there's the same message on the Apollo V4


Amiga User
(Needs Verification)
Posts 104/ 1
25 Mar 2022 18:01


Check that there are no other DF0-related commands in the startup- sequence, user-startup, WBStartup.
 
Did you install the standard Workbenc 3.1 or some distribution?
 
 


Martin Ketter

Posts 70
25 Mar 2022 21:00


I installed the standaed Workbench 3.1 from Amiga forever.

I deliberated to flash the Apollo with the Kickstart 3.1 ROM for Amiga 1200.
Does this could be useful?


Amiga User
(Needs Verification)
Posts 104/ 1
25 Mar 2022 21:30


The Workbench 3.1 Amiga forevere standard, you just have to delete or disable in the startup-sequence the command
 
C:AddBuffers >NIL: DF0: 15

Try again the workbench on WinUAE, but this time you have to disable DF0 from "Amiga Early Startup Control".

Doing so will give you the same error if you don't delete the command above.



Martin Ketter

Posts 70
26 Mar 2022 00:20


I flashed the Apollo with kickstart 3.1. Now it works.

Thank you!

posts 7