Apollo 2030

Drake008@ · 21 August 2008, 10:43

Well where should I begin. So I installed the workbench 3.9 and the boingbags. Works like a charm. I put the cpu chache burst fastrom in the startup-sequence ... nice somewhat faster. But everytime I wanna open makecd and choosing my controller Apollo-SCSI.device or SCSI-Apollo.device (don't know yet anymore) I get the 8000004 error. The funny thing is. When I delete the setpatch line from the startup-sequence erverything works fine. My controller is being detected my hdds are there and also the two cd drives. Is there something wrong with the setpatch command?

musashi5150 · 21 August 2008, 10:47

There is a setpatch option to skip SCSI updates. Can't remember the exact format though - maybe that could help? Someone here will remember.

keropi · 21 August 2008, 10:51

AFAIK the onbard SCSI controller on the Apollo2030 is crap... I am amazed it works for you!

alexh · 21 August 2008, 11:54

Quote:

Originally Posted by musashi5150

There is a setpatch option to skip SCSI updates

Not applicable to 3rd party SCSI controllers. Just integrated ones (onboard IDE and SCSI).

SetPatch QUIET SKIPROMUPDATES "scsi.device"

Perhaps you need to add/remove SCSI-Apollo.device to/from the file DEVS:NSDPatch.cfg

keropi · 21 August 2008, 12:06

why I am still under the impression that the apollo2030 scsi "controller" is an "emulated" one inside that big mach chip?

alexh · 21 August 2008, 12:46

Because it is. There is no dedicated SCSI chip on that board.

Drake008@ · 21 August 2008, 13:08

Problem is that I got an SCSI COntroller from GVP with 8 MB RAM. But the apollo and the gvp getting themself in the way in my a2000.

alexh · 21 August 2008, 13:34

You should not need any of the RAM on the GVP. Take it all off.

Drake008@ · 21 August 2008, 17:07

Problem is that the gvpscsi.device wants to write in the fast ram of the Apollo and then I get an error. Like $6F/$00 or $17/$60.

alexh · 21 August 2008, 17:30

Remove the card alltogether and connect the drive(s) to your 2030?

Leave 1Mbyte on the GVP card?

Change the values in HDToolbox for the MASK settings?

(Someone recently mentioned a mask of 4FFFFE helped him with his CDTV and Derringer accelerator.)

Drake008@ · 21 August 2008, 17:46

Quote:

Originally Posted by alexh

Remove the card alltogether and connect the drive(s) to your 2030?

Leave 1Mbyte on the GVP card?

Change the values in HDToolbox for the MASK settings?

(Someone recently mentioned a mask of 4FFFFE helped him with his CDTV and Derringer accelerator.)

Same here. Some said when I don't use the fast mem then it should work. But how could I do that I only got 500K left when 3.9 is loaded already.

alexh · 21 August 2008, 18:01

??

A2030 can have 64Mbytes. OS3.9 cannot use all that?

I say if the SCSI works on A2030 then remove GVP card altogether! Just use 64MBytes on A2030.

Jakodemus · 21 August 2008, 22:01

Sadly the newer GVP scsi cards don't work with Apollo 2030. Only the older and slower cards work. Mine is http://amiga.resource.cx/exp/impact2000scsi2 Well it's better than nothing. My a2000 won't even boot if scsi in Apollo is enabled

alexh · 21 August 2008, 22:07

Quote:

Originally Posted by Jakodemus

My a2000 won't even boot if scsi in Apollo is enabled

Gotta be something wrong there!

Drake008@ · 24 August 2008, 11:57

So back to the Apollo.

After I tried a bit I flagged setpatch to nonsd. And it runs more stable now.
Someone wrote me that it is possible to put the SCSI-Apollo.device in the nds list in the devs folder. But how am I going to do that. I don't know the correct settings for that device.

Maybe so we can get it more stable as it is now!

Also my connection try from the SCSI HDD to my SCSI Controller in the PC to get WinUAE with the HDD to work. Doesn't start so. Ok I put back the HDD in my Amiga and swoops the data was completely away. No boot no nothing on it. Great and again I have to read out these nifty disks again for them spscrew.

21 August 2008, 10:43	#1
Drake008@ Registered User Join Date: Jun 2006 Location: Germany Age: 45 Posts: 132	Apollo 2030 Well where should I begin. So I installed the workbench 3.9 and the boingbags. Works like a charm. I put the cpu chache burst fastrom in the startup-sequence ... nice somewhat faster. But everytime I wanna open makecd and choosing my controller Apollo-SCSI.device or SCSI-Apollo.device (don't know yet anymore) I get the 8000004 error. The funny thing is. When I delete the setpatch line from the startup-sequence erverything works fine. My controller is being detected my hdds are there and also the two cd drives. Is there something wrong with the setpatch command?

21 August 2008, 18:01	#12
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,411	?? A2030 can have 64Mbytes. OS3.9 cannot use all that? I say if the SCSI works on A2030 then remove GVP card altogether! Just use 64MBytes on A2030. Last edited by alexh; 21 August 2008 at 18:10.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Wanted: Amiga 2030 Accel Card for A2000	kjmann14	MarketPlace	1	08 June 2013 08:52
Apollo 630 help	DoogUK	support.Hardware	12	15 April 2009 14:31
Apollo 2030 troubles...	keropi	support.Hardware	13	11 March 2008 22:22
Apollo 2030 SCSI Controller	Drake008@	support.Hardware	5	10 April 2007 00:19
Apollo 1240	DDNI	support.Hardware	34	20 June 2006 20:29

21 August 2008, 10:47	#2
musashi5150 move.w #$4489,$dff07e Join Date: Sep 2005 Location: Norfolk, UK Age: 42 Posts: 2,351	There is a setpatch option to skip SCSI updates. Can't remember the exact format though - maybe that could help? Someone here will remember.

21 August 2008, 10:51	#3
keropi . Join Date: Oct 2004 Location: Ioannina/Greece Posts: 5,040	AFAIK the onbard SCSI controller on the Apollo2030 is crap... I am amazed it works for you!

21 August 2008, 12:06	#5
keropi . Join Date: Oct 2004 Location: Ioannina/Greece Posts: 5,040	why I am still under the impression that the apollo2030 scsi "controller" is an "emulated" one inside that big mach chip?

21 August 2008, 12:46	#6
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,411	Because it is. There is no dedicated SCSI chip on that board.

21 August 2008, 13:08	#7
Drake008@ Registered User Join Date: Jun 2006 Location: Germany Age: 45 Posts: 132	Problem is that I got an SCSI COntroller from GVP with 8 MB RAM. But the apollo and the gvp getting themself in the way in my a2000.

21 August 2008, 13:34	#8
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,411	You should not need any of the RAM on the GVP. Take it all off.

21 August 2008, 17:07	#9
Drake008@ Registered User Join Date: Jun 2006 Location: Germany Age: 45 Posts: 132	Problem is that the gvpscsi.device wants to write in the fast ram of the Apollo and then I get an error. Like $6F/$00 or $17/$60.

21 August 2008, 17:30	#10
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,411	Remove the card alltogether and connect the drive(s) to your 2030? Leave 1Mbyte on the GVP card? Change the values in HDToolbox for the MASK settings? (Someone recently mentioned a mask of 4FFFFE helped him with his CDTV and Derringer accelerator.)

21 August 2008, 22:01	#13
Jakodemus Registered User Join Date: Aug 2006 Location: Finland Posts: 62	Sadly the newer GVP scsi cards don't work with Apollo 2030. Only the older and slower cards work. Mine is http://amiga.resource.cx/exp/impact2000scsi2 Well it's better than nothing. My a2000 won't even boot if scsi in Apollo is enabled

24 August 2008, 11:57	#15
Drake008@ Registered User Join Date: Jun 2006 Location: Germany Age: 45 Posts: 132	So back to the Apollo. After I tried a bit I flagged setpatch to nonsd. And it runs more stable now. Someone wrote me that it is possible to put the SCSI-Apollo.device in the nds list in the devs folder. But how am I going to do that. I don't know the correct settings for that device. Maybe so we can get it more stable as it is now! Also my connection try from the SCSI HDD to my SCSI Controller in the PC to get WinUAE with the HDD to work. Doesn't start so. Ok I put back the HDD in my Amiga and swoops the data was completely away. No boot no nothing on it. Great and again I have to read out these nifty disks again for them spscrew.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)