Hmmm, somehow I feel like doing some new versions of some of my Amiga Projects again

MagicSN

Just wondering (if any OS4 devs read this)

Is there ever going to be a driver for the A3000 SCSI? 'cause I would quite like to have access to the drives connected to it from OS4 :)

_________________
Back to action!

@BinoX

Quote:

Is there ever going to be a driver for the A3000 SCSI? 'cause I would quite like to have access to the drives connected to it from OS4 :)

When you have an A3000 and want to run OS4 you need to plug in a CSPPC board.
The CSPPC board already includes an UWSCSI controller and OS4 comes with
a driver for this, so you can attach the drives there and use them.

There exists 68k assembler source code for the A3000 version of scsi.device.
Unfortunately the developers dont know yet why it does not work with OS4 anymore.

I'm not aware of a developer who has the skills, the time, the motivation,
an A3000, a CSPPC, some SCSI drives and access to the OS4 CVS with the
68k source code. Such a person would be needed to fix the driver. Creating
a new driver without the old sources is possible too, but its IMHO more
complicated than other drivers because of the SCRIPTS code which is executed
by the WD SCSI chip.

Quote:

When you have an A3000 and want to run OS4 you need to plug in a CSPPC board. The CSPPC board already includes an UWSCSI controller and OS4 comes with a driver for this, so you can attach the drives there and use them.

Well.. I don't want to do the INT2 mod to the motherboard... I wanna keep it as it is... 'cause I'll probably mess it up big time!

Hoepfully they'll add support for it sometime...

For now I'll just use OS4 on my A1200T I guess...
And I'll investigate whether my 3000T needs the INT2 mod 'cause the later ones didn't...

Also, since I'm on the subject of asking... I see no mention of the Algor USB device on the compatibility list... Any idea if that works?

_________________
Back to action!

@TetiSoft who said Quote:

scsi.device. Unfortunately the developers dont know yet why it does not work with OS4 anymore.

On the rare chance this might be related: The author of TLFSMem reported that scsi.device has a nasty memory bug where it writes a few bytes past the end of it's memory allocations. To me it seems likely that such a bug (if not already fixed in OS4) would upset OS4's new memory system...

Last edited by ChrisH on 26-Nov-2007 at 09:34 PM.
Last edited by ChrisH on 26-Nov-2007 at 06:21 PM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@BinoX

Quote:

I see no mention of the Algor USB device on the compatibility list... Any idea if that works?

The E3B website says it uses a different USB chip than the Highway so the
OS4 Highway driver wont work with it.

The compatibility list says that its possible to use the Poseidon USB stack
instead of the OS4 Sirion USB stack to use a Subway card. Eventually its also
possible to use Poseidon with its Algor driver, but it was not tested.

@ChrisH

Quote:

Quote: scsi.device. Unfortunately the developers dont know yet why it does not work with OS4 anymore. On the rare chance this might be related: The author of TLFSMem reported that scsi.device has a nasty memory bug where it writes a few bytes past the end of it's memory allocations. To me it seems likely that such a bug (if not already fixed in OS4) would upset OS4's new memory system...

Yes, this is likely to cause problems with OS4, unfortunately the following
suggests its already fixed.
Quote:

scsi.device 50.5 (19.6.2006) (dwuerkner) - The device init code did write to the io_Offset field of a faked IORequest (not IOStdReq) structure which caused a longword to be cleared which was located behind the end of the memory which was allocated by the device. This fixes a problem on my machine where the exact number of KickLayout modules and their order was important for a successfull boot.

The different scsi.device versions share common source code parts so
I guess that this fix which I did for the A4k IDE driver also affected the
A3k SCSI driver.

@MagicSN
Welcome back to the Amiga community.
I hope you will work on your game projects for AmigaOS 4.

_________________
AmigaOne X1000 1,8 Ghz/2 GB Ram + Radeon 6670 2 GB + AmigaOS4.1
A4000T CyberstormPPC 604e-200Mhz/060/128MB+CybervisionPPC 8MB + AmigaOS4
and anymore other Amigas...

Have read several times about PCI cards working in a Mediator under OS4, if the Mediator drivers are used instead of OS4.0 drivers.

Have any of the beta testers tried this and can they provide any tips on how to go about this?

_________________
If your nose runs and your feet smell, you're upside down.