Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: kreciu on September 08, 2016, 05:05:02 AM
-
I'm trying to install AmigaOS3.9 "for real (on my A1200 :) ). I have plain AmigaOS3.1 + Fast ATA drives with CD driver (from AmigaOS3.9). CD ROM is on second eide port (Master).
I would like to create Emergency DisK to install AmigaOS3.9, but my CD ROM is not detected.
How can I make Emergency Disk to "see" CDROM so I can boot from CD and install system?
THANK YOU!
-
You need drivers to activate the second port, so if they fits you could put them on the emergency disk, or put the cd rom on the first port as slave (and adopt the dosdriver for your cdrom to suit your new config).
-
You need drivers to activate the second port, so if they fits you could put them on the emergency disk, or put the cd rom on the first port as slave (and adopt the dosdriver for your cdrom to suit your new config).
I know, but I don't know how to do it :).
I can't connect CD ROM to first port as a slave, since I want emergency disk that will "rescue my Amiga" without switching ports.
I moved FastATA drivers and preference to floppy, edited startup-sequence, put CD2 into DEVS: but there is still no CD ROM detected when I boot from Emergency-Disc :(.
Can someone help me with more detailed instructions?
Thank you!
-
You also need ATA3.driver. Read the "manual installation" section of the FastATA readme.
http://www.elbox.com/downloads_fastata.html
-
You also need ATA3.driver. Read the "manual installation" section of the FastATA readme.
http://www.elbox.com/downloads_fastata.html
Yes, copied it there and still doesn't work :(
-
Copying the file to the disk does not change anything. You also have to run it. Please read the readme.
-
Copying the file to the disk does not change anything. You also have to run it. Please read the readme.
"Very funny"
-
"Very funny"
:laughing:
He's right though, you know. :)
I don't own a FastATA but I do own a VXL*30, that to enable it's 32-bit RAM you have to run a program at the beginning of the Startup-Sequence. I was able to get it working on my 3.9 ERD just by copying the program into the C: folder on the disk and modifying the Startup-Sequence on the disk accordingly. I imagine the process would be the same for the FastATA. Whatever process you use to activate the two additional ports normally, just include it on the ERD. :)
-
:laughing:
He's right though, you know. :)
Yea, and please tell me to insert... floppy into drive, NOT Zip drive.
I don't own a FastATA but I do own a VXL*30, that to enable it's 32-bit RAM you have to run a program at the beginning of the Startup-Sequence.
It is already there... and it is not detecting CD ROM.
I was able to get it working on my 3.9 ERD just by copying the program into the C: folder on the disk and modifying the Startup-Sequence on the disk accordingly. I imagine the process would be the same for the FastATA. Whatever process you use to activate the two additional ports normally, just include it on the ERD. :)
This is problem, I DID like you wrote and it is not working. That is why I'm asking for help...
-
Okay then, another step by step...see the "official" instructions
http://www.gregdonner.org/os39faq/installtips.html
enjoy
-
Okay then, another step by step...see the "official" instructions
http://www.gregdonner.org/os39faq/installtips.html
enjoy
I think I will not get any specific help :(.
BTW. I have this page bookmarked... and I tried to use apply few ideas from it, no joy...
-
I think I will not get any specific help :(.
You need someone who has the specific hardware as you, and who has also made a 3.9 ERD. Surely you can't be alone, but the people who have may not be visiting this forum.
FYI I don't think your problem is a "3.9 problem". You're trying to make a bootdisk that supports the second IDE header on the FastATA card. You need it to contain the necessary applications/commands to activate said header. This could be a bootdisk for anything, really, it doesn't have to be specifically 3.9. You might try googling the process to make a bootdisk for FastATA, rather than anything 3.9 specific. Even just a regular old 3.1 floppy with FastATA support, etc. Make sense?
-
I think I will not get any specific help :(.
BTW. I have this page bookmarked... and I tried to use apply few ideas from it, no joy...
Maybe this is related to your problem: http://www.gregdonner.org/os39faq/installtips.html#11
-
Mike is right! I remember when we started installing 3.5, we were told the ERD was to be left in the drive so that at the end of the process, it could copy over the needed files for cd and other items.
I had Asimware and it never copies over. I just re-installed Asimware and and it worked until I needed the ERD. So when I needed to fix the ERD, I discovered it didn't have enough room. I had to delete files in order to fit the BASIC Asimware stuff. Then it worked!
I never had a four way ide thing (sorry)
BTW, another thread...http://www.amiga.org/forums/showthread.php?t=39742
-
support@elbox.com
-
http://www.gregdonner.org/os39faq/installtips.html#12 (http://www.gregdonner.org/os39faq/installtips.html#12)
(#12 in above link)
Idea being that when you boot your emergency disk and hold in the left mouse button it will run ATA3Prefs. You then save the correct settings (it'll save them to the floppy) then it'll continue with setup. Obviously next time the boot disk boots you won't have to hold the left mouse button in as the correct config will be loaded when the driver is run.
I have a FastATA, but I don't use 3.9 so I've never had to install the OS from CD to a real Amiga.
Edit:
Those instructions in the link refer to incorrect (old) files. I believe it's ata3.driver, and ata3prefs, but check your FastATA floppy for correct filenames (my Amiga still needs a PSU or I'd check). Just manually copy those files onto (a copy of your) emergency disk into C and Prefs respectively, then use Ed or some other text editor to modify the startup-sequence (as per link but with correct driver and prefs filenames.
-
You say you've put CD2 in Devs. Could it be a naming issue?
-
Just executing the ATA3.driver command won't just make it work you also need a CD Filesystem setup with the dosdriver pointing to allegrocdfs which should be in L: or other cdfilesystem and also pointing to the correct unit number for the CD drive.
If you are using the CD2 DosDriver from the fastata package it should be pointing to the secondary master device and to use L:allegrocdfs for the CD filesystem so you need to make sure allegrocdfs is in L.