Commodore Retro Amiga Portal
Would you like to react to this message? Create an account in a few clicks or log in to continue.

We are C.R.A.P. & proud of it...

Most Recent Posts
Show Latest Posts
Who is online?
In total there are 2 users online :: 0 Registered, 0 Hidden and 2 Guests

None

[ View the whole list ]


Most users ever online was 226 on 17/9/2021, 15:51
Newest Member
https://crap.forumotion.co.uk/u105
Poll

Best / Worst Amiga Company...

 
 
 
 
 
 
 
 

View results

Search
 
 

Display results as :
 


Rechercher Advanced Search

Latest topics

» AmigaKit / A-EON Fanboys: Are They Really So Pathetic !!!
by Franko 13/6/2015, 15:49

» A-EON: The False Gawds & Self Proclaimed Saviours Of Amiga
by Franko 7/6/2015, 03:09

» Teh MooBunny Is Dead... OFFICIAL...
by Franko 6/4/2015, 06:53

» Best Solitaire...
by J_Golden 24/8/2013, 17:15

» Dirwork 2.1 informations, config files, and other fun stuff
by TheBilgeRat 9/5/2013, 17:29

» OFFICIAL: THE AMIGA IS DEAD...
by Franko 26/2/2013, 05:19


You are not connected. Please login or register

Go down  FastATA Mk4 Installation Part 2 [Page 1 of 1]

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
OK then! I have reinstalled the FastATA Mk4 adapter using the wire wrap sockets which worked perfect! Clipping the pins is a little tricky. There is NO reason to use tie-wraps on the sockets as all pins are very secure on both the top and bottom. I'm very concerned about the socket on top of the GAYLE chip popping off though, expecially with the machine running as it popped off all by itself just sitting there before power-up. Rolling Eyes

Now back to the problem during the pre-fit.
When I power up, all the hardware is definetely working properly. However, after installing the software during the pre-fit phase, I get this message at bootup:

Requester Box Heading: Software Failure
PSDLOADMODULE
Program Failed (error #80000004)
wait for disk activity to finish

I can boot the machine to a command line from the early startup sequence by bypassing startup files and I can get a directory list.

Not sure why the software installation went sour. Any help appreciated! Crying or Very sad

Franko

Franko
Admin
Admin
Ok...

Be handy to know the following info first...

Your system set up: ie: Kickstart 3.0 or 3.1, Workbench version, what you've got connected to the FastATA ie: HDs / DVD/ CDs

Have you got anything hooked up via the USB at bootup...

(I only run Posiedon when I need it)

Sounds to me like you'll need to edit your StartUp-Sequence by hand as it can be something as simple as it launching some things in the wrong order. Be handy if you could cut and paste your StartUp-Sequence here, that way I can have a look and even edit it for you...

I'll post my typical StartUp-Sequence in a couple of minutes so you can get an idea of how things should be "launched" in the right order but it could be lot's of different things causing your problems so best to start with the info I asked above... Smilie

https://crap.forumotion.co.uk

Franko

Franko
Admin
Admin
My StartUp-Sequence for my A1200 with BlizzardPPC/060 , FastATA MKIII , SubWay USB, 2 x 500GB HD's, 2 x DVD-CD Writers...


Code:
; $VER: Startup-Sequence_060+Blizkick 1.0 (31.08.06)
; Startup-Sequence for hard drive systems

C:+C/VInfo             ;My Virus Checker Prog
C:+C/SetPattern        ;Select Backdrop Picture (F1-F10)
;-----------------------------------------------------------------------------
; Remove OS 4.0 Partitions
;-----------------------------------------------------------------------------
C:Assign <>NIL: OS0: Dismount
C:Assign <>NIL: OS1: Dismount
C:Assign <>NIL: OS2: Dismount
C:Assign <>NIL: OS3: Dismount
C:Assign <>NIL: OS4: Dismount
;-----------------------------------------------------------------------------
; Create Vital OS Dirs
;-----------------------------------------------------------------------------
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
;-----------------------------------------------------------------------------
; Create Nessesary Assigns
;-----------------------------------------------------------------------------
Assign >NIL: ENV: RAM:ENV

Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards

Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER
Assign >NIL: Prefs: SYS:Prefs

Assign >NIL: C: SYS:C/+C ADD
Assign >NIL: Devs: SYS:Devs/+Devs ADD
Assign >NIL: L: SYS:L/+L ADD
Assign >NIL: Libs: SYS:Libs/+Libs ADD
Assign >NIL: Prefs: SYS:Prefs/+Prefs ADD

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities add

Path >NIL: C:+C Devs:+Devs L:+L Libs:+Libs Prefs:+Prefs SYS:System/+System SYS:Tools/+Tools SYS:Utilities/+Utilities add
;-----------------------------------------------------------------------------
; StartUp Any System Patches
;-----------------------------------------------------------------------------
C:SetPatch <>NIL: SKIPROMUPDATES QUIET    ;Standard Amiga Patch
C:+C/PatchControl.V2.3                    ;PatchControl (Controls Any Added Patches)
C:+C/CMQ060_Move16                        ;Patch For 060 Optimised Move
C:+C/BlazeWCP                              ;Patches Certain Blitter Routine
C:+C/FBlit                                ;FastBlit Patch (Speeds Up Blitter Routines)
C:+C/FText                                ;Patch For Faster Text Output
C:+C/MCP                                  ;MCP (Multiple Patches)
RUN <>NIL: C:+C/TitleShadow               ;Patch (Creates Window Title Shadows)
;-----------------------------------------------------------------------------
; BLIZZARD 060/PPC RemMap Rom Stuff
;-----------------------------------------------------------------------------
S:Bliz.PPC                                ;BlizKick Remap ROM 060/PPC
;-----------------------------------------------------------------------------
; Fast ATA3 Stuff
;-----------------------------------------------------------------------------
FailAt 10

C:+C/CheckLMB                              ;Check For Left Mouse Button

IF WARN                                    ;If Pressed - Run ATA3 Prefs
  SYS:Prefs/+Prefs/ATA3.prefs
ENDIF

C:ATA3.driver NOPART QUIET                  ;Start ATA3 Driver
C:Stack 8192
C:ATA3SetSplit                            ;Make Primary Slave NOSPLIT
;-----------------------------------------------------------------------------
; Protect From Writing To These Partitions
;-----------------------------------------------------------------------------
C:Lock <>NIL: Workbench: ON
C:Lock <>NIL: DH1: ON
C:Lock <>NIL: DH2: ON
;-----------------------------------------------------------------------------
; Usual Startup Stuff
;-----------------------------------------------------------------------------
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

IF EXISTS DEVS:Monitors
  IF EXISTS DEVS:Monitors/VGAOnly
    DEVS:Monitors/VGAOnly
  EndIF

  C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
  Execute T:M
  C:Delete >NIL: T:M
EndIF

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
C:ConClip

C:+C/FPprefs                                    ;FullPalette (Sets Up & Locks WB Colours)

IF EXISTS S:User-Startup
    Execute S:User-Startup
EndIF

C:IPrefs

Run >NIL: C:+C/Birdie ? <ENV:Birdie.Prefs   ;Birdie (Window Borders Patch)

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB -DEBUG

Avail <>NIL: FLUSH

EndCLI >NIL:

LAB END                                         ;Just A Jump Label For Testing
Echo "You Wanted to Stop Here"

Of course your StartUp-Sequence wont look much like this but it's really only to show you where in your StartUp-Sequence it is best to launch/ run the "ATADriver"...

It's always best for it to be launched/ run AFTER "SetPatch" and most other patching progs...

The first thing though I would suggest you do is...

Edit your StartUp-Sequence to comment out/ remove the launching of the Posiedon USB stack, as this seems to be what's giving you issues for now...

Just type from the CLI/ Shell

ED S:StartUp-Sequence (Return)

Then look for the lines that launch/ run the Posiedon USB Stack and comment them out by placing a ";" char in front of them. Save the edited StartUp-Sequence then reboot and see what happens... :-)

https://crap.forumotion.co.uk

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
Franko wrote:Ok...

Be handy to know the following info first...

Your system set up: ie: Kickstart 3.0 or 3.1, Workbench version, what you've got connected to the FastATA ie: HDs / DVD/ CDs

Have you got anything hooked up via the USB at bootup...

(I only run Posiedon when I need it)

Sounds to me like you'll need to edit your StartUp-Sequence by hand as it can be something as simple as it launching some things in the wrong order. Be handy if you could cut and paste your StartUp-Sequence here, that way I can have a look and even edit it for you...

I'll post my typical StartUp-Sequence in a couple of minutes so you can get an idea of how things should be "launched" in the right order but it could be lot's of different things causing your problems so best to start with the info I asked above... Smilie

OK.....
Kickstart 3.1, WB 3.5, Fast ATA MKIV, CF HDD, NO CD ROM connected at startup (via USB).

I commented out the ATA3.driver to get it to boot. Here's my StartUp-Sequence file.... Wink Also, I am NOT running IDEFIX.

;C:ATA3.driver QUIET
C:stack 8192
PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer
IF EXISTS SYS:S/AmigaKit
SYS:S/AmigaKit
ENDIF

IF EXISTS SYS:C/OS-Install
SYS:C/OS-Install -installed
ENDIF

IF EXISTS SYS:C/IDEFIX
C:IDEFIX
ENDIF

C:SetPatch Quiet

If EXISTS C:NSDPatch
C:NSDPatch Quiet
ENDIF

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

If Exists DEVS:Monitors
If Exists DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
EndIf

C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) To T:M LFORMAT "DEVS:Monitors/%s"
Execute T:M
C:Delete >NIL: T:M
EndIf

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH Quiet
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

If Exists S:User-Startup
Execute S:User-Startup
EndIf

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:

Franko

Franko
Admin
Admin
Noooooooo....

I said Comment out the PSD (Poseidon) line... Surprised

It's not the ATAdriver that causing the problems it's the posiedon USB stack that's giving you the error here...

Get rid of the IDEFIX too (It's not needed)...

https://crap.forumotion.co.uk

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
Franko wrote:Noooooooo....

I said Comment out the PSD (Poseidon) line... Surprised

It's not the ATAdriver that causing the problems it's the posiedon USB stack that's giving you the error here...

Get rid of the IDEFIX too (It's not needed)...

Yeah, I know.... I had looked at the file before I came back to read you response and thought "I bet it will boot if comment out the ata.driver" (which it did) so that I could copy the StartUp-Sequence file to post here! Whew!

So now I guess I'll go comment out the Poseidon. I was just waiting as I thought you were going to run my StartUp-Sequence file through the Amiga Universal Uniblab Terestrial Analyser and give me the definitive answer as to why we are here! Very Happy

Are we doing this to see if the Fast ATA software works? Embarassed

I agree that the Poseidon software does not need to startup every time I boot up. How do you start up you USB stack after you boot.

Also, yup I know that IDEFIX crap doesn't need to be there - this represents the best of AmigaKit when you buy one of their pre-installed CF cards! Surprised

BRB..........

OK, I commented out the Poseidon & all the AmigaKit stuff down to C:SetPatch Quiet and then I get the same error message as before. I'm thinking that the C:ATA3.driver neeeds to be moved somewhere else in the startup file? confused Maybe after the ASSIGN stuff like in your startup file?

Ummm, I moved the ATA3.driver around a little bit with diasterous results! Rolling Eyes LOL

Set everything back the way it was and will start fresh tomorrow... I'm thinkin you went beddy-bye anyway.

I'll check back when I get home from the SAM. Very Happy

Franko

Franko
Admin
Admin
Ok...

I'm confused... Exclamation

The "Error" you gave in your first post should have been caused by the Posiedon Stack loader launching too soon in your StartUp-Seqeunce (It needs the ENV: and other things set up first before it runs)...

The Posiedon USB line needs to be placed AFTER all the normal Workbench Assign are made in the StartUp-Seqence and not before them, otherwise it can't find the stuff it's looking for to run properly hence the error...

But if you say your still getting that very same error with the Posiedon line commented out (which you shouldn't be getting now) then you must have something else "Launching" the Posiedon USB stack, maybe in your "User-StartUp"...

Check your StartUp-Seqeunce again just to make sure you really have commented out the Posiedon Stack. You should also move that line towards the bottom/ end of your StartUp-Sequence (After all the normal "Assigns")...

I launch the Posiedon USB Stack from the Menubar in Workbench when I need it using "ToolPrefs", as there is no point in having the USB Stack running when you don't need it (It uses up memory & slows things down)...

https://crap.forumotion.co.uk

Franko

Franko
Admin
Admin
I've edited your StartUp Sequence to this...


Code:
C:ATA3.driver QUIET
C:stack 8192
;PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer
;IF EXISTS SYS:S/AmigaKit
;SYS:S/AmigaKit
;ENDIF

;IF EXISTS SYS:C/OS-Install
;SYS:C/OS-Install -installed
;ENDIF

;IF EXISTS SYS:C/IDEFIX
;C:IDEFIX
;ENDIF

C:SetPatch Quiet

If EXISTS C:NSDPatch
C:NSDPatch Quiet
ENDIF

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

If Exists DEVS:Monitors
If Exists DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
EndIf

C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) To T:M LFORMAT "DEVS:Monitors/%s"
Execute T:M
C:Delete >NIL: T:M
EndIf

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH Quiet
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

If Exists S:User-Startup
Execute S:User-Startup
EndIf

Resident Execute REMOVE
Resident Assign REMOVE

PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer

C:LoadWB
EndCLI >NIL:

Try using this version of your StartUp-Sequence (Cut & Patse it)...

https://crap.forumotion.co.uk

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
Ahh nice! Thanks for the modified StartUp-Sequence Franko! Yes, I looked at the User-Startup file too and there is all kind of Poseidon stuff in there. Plus a ton of other things. I'll post the User file tomorrow. The startup files would be a great thing to learn and understand. Gawd knows I use to write HUGE DOS batch files! Have a good evening Franko and as always thanks a ton for the help! Very Happy

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
Mornin Franko! Well, here in the big Mitten anyways!

Here's the User-Startup file.... as you can see this is also where the AsimCDFS is firing up... I'ts probably best to stop this from starting as I would like to use the Allegro CDFS (which I did not intall yet).

Code:
IF EXISTS SYS:ramdisk.info
      C:Copy SYS:ramdisk.info RAM:disk.info
ENDIF
;BEGIN Poseidon
ENVARC:PsdStackloader
;END Poseidon
;BEGIN MUI
if exists "HDD2:MUI"
  assign MUI: "HDD2:MUI"
  if exists MUI:Libs
      assign add LIBS: MUI:Libs
  endif
  if exists MUI:Locale
      assign add LOCALE: MUI:Locale
  endif
  version >nil: exec.library 39
  if not warn
      if exists MUI:Docs
        if exists HELP:dummy ; do not remove
        endif                ; this entry!
        assign add HELP: MUI:Docs
      endif
  endif
endif
;END MUI
;BEGIN AsimCDFS
echo "Mounting AsimCDFS..."
assign AsimCDFS: "SYS:AsimCDFS"
assign AsimCDFS_Buffer: "ADH1:AsimCDFS_Buffer"
mount >NIL: CD0:
;END AsimCDFS
;BEGIN JPEG DataType
Assign >NIL: JPEGTMP: RAM:t
;END JPEG DataType
;BEGIN Personal Paint
Assign >NIL: PPaint: HDD:PPaint
;END Personal Paint
;BEGIN Photogenics-SE
assign pgsse: "HDD:Photogenics-SE"
;END Photogenics-SE
;BEGIN DeluxePaint
Assign DPaintIV: HDD:DPaintIV
;END DeluxePaint
;BEGIN Aladdin 4D
Assign "Aladdin4D:" "HDD:Aladdin 4D/Aladdin4D"
Assign "Aladdin4DTools:" "Aladdin4D:Tools"
Assign "Aladdin4DHelp:" "Aladdin4D:Help"
Assign "Aladdin4DDef:" "Aladdin4D:Support/Def/Defaults"
;END Aladdin 4D

Cool

Franko

Franko
Admin
Admin
Good Morning, Afternoon,, Evening, Grief (delete as applicable)... Smilie

Code:
IF EXISTS SYS:ramdisk.info
      C:Copy SYS:ramdisk.info RAM:disk.info
ENDIF

;BEGIN Poseidon
;ENVARC:PsdStackloader
;END Poseidon

;BEGIN MUI
if exists "HDD2:MUI"
  assign MUI: "HDD2:MUI"
  if exists MUI:Libs
      assign add LIBS: MUI:Libs
  endif
  if exists MUI:Locale
      assign add LOCALE: MUI:Locale
  endif
  version >nil: exec.library 39
  if not warn
      if exists MUI:Docs
        if exists HELP:dummy ; do not remove
        endif                ; this entry!
        assign add HELP: MUI:Docs
      endif
  endif
endif
;END MUI

;BEGIN AsimCDFS
;echo "Mounting AsimCDFS..."
;assign AsimCDFS: "SYS:AsimCDFS"
;assign AsimCDFS_Buffer: "ADH1:AsimCDFS_Buffer"
;mount >NIL: CD0:
;END AsimCDFS

;BEGIN JPEG DataType
Assign >NIL: JPEGTMP: RAM:t
;END JPEG DataType

;BEGIN Personal Paint
Assign >NIL: PPaint: HDD:PPaint
;END Personal Paint

;BEGIN Photogenics-SE
assign pgsse: "HDD:Photogenics-SE"
;END Photogenics-SE

;BEGIN DeluxePaint
Assign DPaintIV: HDD:DPaintIV
;END DeluxePaint

;BEGIN Aladdin 4D
Assign "Aladdin4D:" "HDD:Aladdin 4D/Aladdin4D"
Assign "Aladdin4DTools:" "Aladdin4D:Tools"
Assign "Aladdin4DHelp:" "Aladdin4D:Help"
Assign "Aladdin4DDef:" "Aladdin4D:Support/Def/Defaults"
;END Aladdin 4D
Simply comment out the Poseidon line as above to disable it. I've no idea why PSD is trying to mount the "input.device" unless it's for a USB Keyboard but I suggest you set up/ reconfigure Poseidon before you use it as I doubt you would be using PSD for the "input device...

Like I say I only run Poseidon when I need it and this I do from the Workbench menu bar. The simplest way to start the USB stack when you actually need it can be done in any of the following ways...

From the Workbench menu bar like I do using "ToolPrefs" Version 2.1b

From the CLI/ Shell by typing the following...
ENVARC:PsdStackloader

(Of course you could put the above line in a script and save it, calling it something like MountUSB and launch it that way, if that would be easier to remember)...

I also use the following script to "switch off" the Poseidon USB stack if I've launched it for something and am finished with it, so that it frees up memory and resources...

Script Called "USBoff"... that switches off/ frees up the PSD Stack when not in use... Smilie
Code:
AddUSBclasses REMOVE QUIET
AddUSBhardware ALL REMOVE QUIET
Avail <>NIL: FLUSH
Avail <>NIL: FLUSH
Avail <>NIL: FLUSH
I simply call this script "USBoff" and it's launched (in my case) from the Workbench tool bar but of course it can be run from the CLI/ Shell too..

The rest of the assigns in your User-StartUp I have no idea if you need them but you should know and edit them as such...

I advise using the AllegoCDFS as it doesn't require anything in your StartUp-Sequence or User-StartUp and it's the best CD/ DVD filesystem for the Amiga... Smilie

https://crap.forumotion.co.uk

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
Again, thanks for the great info Franko! SetPatch error turned out to be way more than software related. I found this and was able to get the controller to fire right up at PIO3 but NO DICE under PIO4. http://www.amiga.org/forums/archive/index.php/t-31776.html
My A1200 is an Escom unit so I may have to do the timing fix (which I thought about asking about but, Meh)

But, it's working and things are noticably faster. I'll work on the speed/timing issue later. Now to install the new CDFS! Yeah! Smilie

Until next time! Thanks!

Franko

Franko
Admin
Admin
Not sure what error with SetPatch your taking about (as you didn't mention it) but I've emailed you the version of SetPatch that I use on all miggies with FastATA that works perfectly... Smilie

Even with an 060/PPC board I have never been able to use PIO5 and have only managed PIO4, except for some DVD/CD drives which seem to handle the PIO5 mode but you should be able to use PIO4 mode on your setup too without problems...

Then again a lot of other factors come into the equation like the HD itself (Manufacturer, Quality, Age etc...) so it might be a bit more tricky trying to solve that one for you...

Two of my A1200s are Escom ones and they both handle PIO4 fine without ever needing to have touched the motherboard so it could well be just down to the HDs your using (I generally only use 3.5" HDs myself and not 2.5" ones)...

Let me know how you get on anyway... cheers... Smilie

https://crap.forumotion.co.uk

Amiga4000

Amiga4000
A Wee Bit Chatty
A Wee Bit Chatty
It's not a SetPatch problem at all... other than the fact that loading the OS halts at SetPatch when the controller can't operate at the PIO mode selected. (Program Failed (error #80000004) confused I read posts for about 2 hours and there are all kinds of theories and solutions that helped acheive a higher PIO mode. i.e. HDD/CF Card typs, cable length/condition, ROM Socket length, Socket condition, power supply condition etc... you get the idea. This... replace the 33.3333 Mhz one by a 32 Mhz on the FastATA confused This helped alot: When miggy boots keep the left mouse button pressed and the fastata prefs page will come up. But if you never achieved anything higher than PIO4 and I got PIO 3 working that's encouraging to me. I have a NON-DESCRIPT (non-branded) CF Card from AmigaKit so who knows. Rolling Eyes

Actually I need to retract NON-DESCRIPT... It's a Kingston CF Card. Neutral



Last edited by Amiga4000 on 24/9/2012, 15:39; edited 1 time in total

Franko

Franko
Admin
Admin
Ah sorry, forgot you were using one of those CF card thingies (rubbish in my opinion)... Wink

That's most likely the cause for you only getting PIO3 speeds but even on a miggie that should be fast enough for everyday use, of course I would recommend using "real" HD's but I'm biased and simply don't like those CF card wotnots... Smilie

Never heard of any type of crashing before with SetPatch, read the other thread and can only come to the conclusion that they were doing something wrong to start with (aint easy trying to diagnose such problems over the internet)...

All I can tell you is that using the FastATA on any of my miggies (Escom ones included) is that I've never came across such problems and I've tested it with the 020, 030 & 060 chips. Use the version of SetPatch I sent you as it works perfect on all my set ups but at the end of the day it'll most likely be the CF card that's keeping you as PIO3 speeeds but like I say that should be fast enough for "normal" everyday Amiga use as it's not like the Amiga uses the HD as memory like PC's & Macs do... Smilie

https://crap.forumotion.co.uk

Sponsored content


Back to top FastATA Mk4 Installation Part 2 [Page 1 of 1]

Permissions in this forum:
You cannot reply to topics in this forum