Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Erebos on February 19, 2008, 04:03:42 PM
-
Hi,
I've got a problem to install my FasATA MKII under OS4 and found a website where someone had the same problem but unfortunately it is written in polish, could someone please translate this text:
d). FastATA
Działa sterownik do kontrolera FastATA. Można dodać go do sekwencji startowej systemu. Niestety zwraca komunikat:
***Polecenie "ata3.driver" zakończyło działanie nie zwalniając sygnałów 8000000!
którego nie potrafiłem się pozbyć. Nie przeszkadza to jednak w starcie systemu.
Osiągi dla dysku - ok. 4 MB/s (PPC 200 MHz). Dla porównania pod AmigaOS 3.9 (040/33 MHz) - ok. 4.7 MB/s. Oczywiście sterownik pod AmigaOS 4.0 działa pod emulatorem JIT 68k - Petunia.
Innym problemem związanym z FastATA 1200 jest nie działanie systemu plików dla napędu CD (Kickstart/CDFileSystem) gdy sterownik ata3.driver jest aktywny. Rozwiązaniem jest stworzenie mounlisty CD0 (pobierz i ewentualnie zmień Unit) w katalogu Devs/DOSDrivers i wyłączenie automatycznego montowania napędu CD w pliku Kickstart/diskboot.config (ustaw - scsi.device 8 1).
Thx :-)
-
Why not tell us what your problem is and see if we can help?
-
How you figured out that the problem is the same as yours? Or the question was in english and the answer in polish? :-D :-D :crazy:
-
Hello,
My problem is that when i launch the ata3.driver, after a couple of second i've gt a message telling me that the program terminated because of an error in 8000000 adress, that's all i have, and after that, OS4 is still running but I have no more access to drives content.
@phantom
Because of the error message in its sentence (***Polecenie "ata3.driver" zakończyło działanie nie zwalniając sygnałów 8000000!) It really looks like mine :-)
-
1. you have to enable base page access, see your manual how to do it, from memory (and I could be wrong) it's "c:bootloader commandline allowbasepageaccess" in your startup-sequence (without the ""s obviously)
2. Use the latest ata3.driver, that's 7.1 I think, ask elbox to send it to you if you don't have it already. Run it at some point in your startup-sequence as "c:ata3.driver quiet" - I'm not sure about the "quiet" switch, it might not be needed any more.
3. To access your cds in the second channel you can just use allegro cdfs and your dosdrivers from 3.x (ie cd0, cd1), adjust the paths in them and put them in devs:dosdrivers of your OS4 instalation.
That's how it works for me. Except that I have to manually set the hd in nosplit mode that is....weird bug this one....!
-
@Vulture
Yeah, I added the AllowBasePageAccess in the Startup-Sequence but not the automatic load of the ata3.driver because I wanting to be sure it run fine. So I launched it manually after booting OS4, but it crashed :-(
-
I no longer need the AllowBasePageAccess with the latest drivers released recently.
That was with a MKIII.
Presumably that is not the case with the MKII.
You can do as suggested above or alternatively, Elbox will allow you to do a trade in your MKII for the MKIII.
Could be worth looking into.
http://www.elbox.com/news_08_01_11.html
-
@TiredOfLife
Yes, that will be the last solution, but i'd like to make this one function if possible. Many people still have their MKII or MKI and dont want to upgrade or have not the money, so if there is a solution...
Does MKII drivers could work with MKII ?
-
I wrote to elbox directly to see if they have a solution as nobody seems to have the same problem as mine
-
Why don't you try the automatic loading of the driver?
You can always take it out if it doesn't work.
Also, how exactly did you install OS4?
The drive should be formatted with the driver in place according to Elbox.
I did this by formatting the my OS4 partition when running the driver under my 3.9 partition.
-
I did not try the automatic loading because I wanted to see if it worked before beeing unable to boot :-)
I installed OS4 without the FASTATA, with a minimal os3.1 partition and another one containing OS4 CD files