FastATA V 1200 - hard drive issues

[kreciu]

I'm just got new FastATAV and I'm trying to put my AmigaOS3.9 "from scratch".

I wanted to use OS3.1 to install it and so I boot it from Install disc and used to HDToolbox to partition my hard drive. After reboot I was expecting to see my not formatted partitions. There is not any partitions?! I started HDToolBox and partitions are there.

I used my "recovery disc" for AmigaOS3.9 and and I can see partitions, I even did install OS3.9 (so DVD rom works fine).

I can't boot this installation (in only booted from HDD after soft reset when installation was finished, after hard reset Amiga will not boot!?!). I also can't see my boot partition in boot menu.

My FastATA sits under Mediator with ROM riser. Is this possible issue, ROM riser?!? My previous FastATA II (I think) did not have any issues.

What is happening?! I really don't understand this issue.

[giZmo350]

I had a similar symptom with my FasyATA-IV when installing the OS. The default PIO mode was set too high and SYS wouldn't boot. HDInstTools would always report everything OK. If I remember correctly, hold down both mouse buttons - or maybe right mouse button (don't recall sequence - maybe google - my instructions are buried away) at power on and you should be able to get to the FastATA hardware menu to lower or change the PIO mode. Just a thought but worked for me.

[kreciu]

I had a similar symptom with my FasyATA-IV when installing the OS. The default PIO mode was set too high and SYS wouldn't boot. HDInstTools would always report everything OK. If I remember correctly, hold down both mouse buttons - or maybe right mouse button (don't recall sequence - maybe google - my instructions are buried away) at power on and you should be able to get to the FastATA hardware menu to lower or change the PIO mode. Just a thought but worked for me.

The only problem is that there is NO hard drive detected AT ALL in boot menu, system will not boot at all.

Magic.

[giZmo350]

Obvious question.... but, did you install the driver before the reboot? Did you get instructions? If so, does it mention how to get to the FastATA menu? Maybe the menu won't show up if no HDD is present. Maybe perform another recovery and install the driver before you soft reboot? Man, it's been so long since I installed my FastATA. And my mega A1200 is still in pieces since getting back my repaired motherboard.

[kreciu]

Obvious question.... but, did you install the driver before the reboot? Did you get instructions? If so, does it mention how to get to the FastATA menu? Maybe the menu won't show up if no HDD is present. Maybe perform another recovery and install the driver before you soft reboot? Man, it's been so long since I installed my FastATA. And my mega A1200 is still in pieces since getting back my repaired motherboard.

Yes,  but I'm trying to tell you that there is no hard drive detected in early boot menu (you got there pushing two mouse buttons), so Amiga is not even trying to boot.

[giZmo350]

Well, maybe problem is the ROM risers... I had trouble with mine also because the riser pins were too thick for the ROM sockets and I kind of ruined the sockets. Sometimes I would have to jiggle them a bit (which wasn't;t easy as everything was really stuffed in the case). I am going to change the ROM sockets for machined hole type before I install the FastATA again. Sorry I'm not helping much.

[kreciu]

Sorry I'm not helping much.

I'm thinking the same. I'm disassembling all of it right now. It is interesting that HDToolBox will still see HDD?

You are helping for sure, it is more psychological help "talk to me" type of help

[giZmo350]

Well, had this discussion 4 years ago with XDelusion...

http://www.amiga.org/forums/showthread.php?t=65860&page=2

After you install your OS, cold reboot, hold down the LEFT mouse button to bring up the Elbox menu (it's real finicky). Set PIO mode to 3. Continue boot process.

This function was not available with MK-II.

If PIO is higher than 3 you'll never see the hard drive in the A1200 early startup menu because you're going thru a new controller (unless you have a very fast HDD).

Yes, the PIO mode can also be set later in software after the OS, the driver & the Elbox software is installed.

Alas, in the end XDulusion had a connection problem...

[kreciu]

When I do cold boot, I can only see screen asking for floppy disc or I can access early startup menu and there is no any partition listed. Nothing else.

I tried to use OS3.1 install. When I boot from floppy I can format HDD but partitions will never show up in Workbench, so I can't even install AOS3.1.

[kreciu]

So, I again what is happening is that when I disconnected DVD rom, THEN I can see my hard drive in early boot menu. When I connect is back... NO hard drive and system will not boot.

When I will boot system with "recovery disc" from AOS3.9 everything works fine?!

Is my FastATA bad or something? Now it is without risers.

When I do soft reset (after loading AmigaOS3.9 from floppy), system will boot?! It looks like something (scsi.device??) is already "loaded" so soft reset is letting FastATA work.

EDIT: When I connect my Blizzard 030... then I can boot WITH DVD rom?! (but my 4MB memory expansion is not visible in system at all).

EDIT2: I did drivespeed test and got 1690097bytes/s, with compact flash memory?!


I think I will write to Elbox...

[kreciu]

OK. I installed my old FastATA and it works fine. I needed to change PIO mode to lover then FastATA V but now I can connect DVD rom...

As far as speed, I forgot that in AmigaOS3.9 I need to tweak startup-sequence to make FastATA driver to work... problem is I forgot how to do it .

I think I need to return my new FastATA

[kreciu]

One problem solved. My old FastATAII now is doing 5Mb/s under OS3.9 with CF card (PIO3 only). I needed to update driver to newest possible, nothing else was needed.

Elbox CS is helping me to solve issue with my new FastATA V.

[kreciu]

Now my FastATA V works fine. I disassembled everything, put back... and it works. 7Mb/s on my CF memory in PIO4, PIO5 about 8.5Mb/s

FastATA is good, there was some "other issue".