Welcome, Guest. Please login or register.

Author Topic: CF card errors  (Read 2338 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline stanlongTopic starter

  • Full Member
  • ***
  • Join Date: Aug 2008
  • Posts: 129
    • Show only replies by stanlong
CF card errors
« on: December 09, 2008, 06:59:46 AM »
please oh tecchnoid gods of the Amiganoid heaven
oh great ones give me a sighn
I can understand

any idea what would coase rigid disk block errors on a cf card
only seem to happen when
i tried to instsll wb 3.5
 

Offline darksun9210

Re: CF card errors
« Reply #1 on: December 09, 2008, 10:12:49 AM »
have you installed the boing bag updates? what values have you got for the max transfer?
RDB errors sounds like a hard disk problem, but your'e using a CF card... hmmmm  :-?

A500, A600, A1200x3, A2000, A3000, A4000 & a CD32.
and probably just like the rest of you, crates full of related "treasure" for the above XD
 

Offline alexh

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 3645
    • Show only replies by alexh
    • http://thalion.atari.org
Re: CF card errors
« Reply #2 on: December 09, 2008, 01:33:24 PM »
Max transfer needs to be less than 128Kbytes or perhaps even less than 64Kbytes.

In HDToolbox change the MAX TRANSFER to 0x1FE00 or worst case 0xFE00

You'll undoubtedly have to start again and partition, format and install workbench all over. :-(
 

Offline xeron

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 2533
    • Show only replies by xeron
    • http://www.petergordon.org.uk
Re: CF card errors
« Reply #3 on: December 09, 2008, 01:40:04 PM »
It could be that you have a duff card. It does happen.
Playstation Network ID: xeron6
 

Offline Crom00

Re: CF card errors
« Reply #4 on: December 09, 2008, 01:42:04 PM »
Had similar problems and they subsided when I used a brand of cards approved for use by the good blokes at the english Amiga Board. They have a whole thread dedicated to CF card use. Good Stuf, saved me time and money.

My Black A1200 is all set and soon...CD32 with sx-1 :)
 

Offline xeron

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 2533
    • Show only replies by xeron
    • http://www.petergordon.org.uk
Re: CF card errors
« Reply #5 on: December 09, 2008, 01:48:05 PM »
My employer actually produces embedded hardware that boots from Compact Flash cards, and have extensively tested many, many cards. The difference in quality, reliability and read/write speed across brands (and even sometimes within a brand) is remarkable.

We have found Kingston cards to be the best for reliability and read speed. In fact we've not found any other brand match them for speed, but I don't think the CF card is the bottle neck when using it in an A1200, so that might be less of a concern ;-)
Playstation Network ID: xeron6
 

Offline klx300r

  • Amiga 1000+AmigaOne X1000
  • Hero Member
  • *****
  • Join Date: Sep 2007
  • Posts: 3262
  • Country: ca
  • Thanked: 20 times
  • Gender: Male
    • Show only replies by klx300r
    • http://mancave-ramblings.blogspot.ca/
Re: CF card errors
« Reply #6 on: December 09, 2008, 02:38:25 PM »
90% its an incompatible CF card....use SanDisk as they appear to be the best for Amigas..& also try the max transfer settings that Alex recommended..i would also check out a great thread on EAB on this topic
____________________________________________________________________
c64-dual sids, A1000, A1200-060@50, A4000-CSMKIII
Indivision AGA & Catweasel MK4+= Amazing
! My Master Miggies-Amiga 1000 & AmigaOne X1000 !
--- www.mancave-ramblings.blogspot.ca ---
  -AspireOS.com & Amikit- Amiga for your netbook-
***X1000- I BELIEVE *** :angel:
 

Offline alexh

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 3645
    • Show only replies by alexh
    • http://thalion.atari.org
Re: CF card errors
« Reply #7 on: December 09, 2008, 02:44:33 PM »
I've never known incompatible cards do this. They either work fully or they are not even detected.
 

Offline darksun9210

Re: CF card errors
« Reply #8 on: December 09, 2008, 05:14:19 PM »
i had a sandisk ultra3 card that was not detected. stuck it in a PC, created a partition, formatted, rebooted and to test, installed winXP on there. then stuck it in an A1200. worked fine. is there a switch in the firmware of the CF card to toggle removable/fixed?

A500, A600, A1200x3, A2000, A3000, A4000 & a CD32.
and probably just like the rest of you, crates full of related "treasure" for the above XD
 

Offline Crom00

Re: CF card errors
« Reply #9 on: December 09, 2008, 06:40:21 PM »
I had a CF card work fine on UAE on the pc, when transfered to the A1200 it was riddled with read/ write errors.

Stuck it in the PCMCIA adapter after a fat partition format on the PC and it still had slow reads and writes, and hung up the A1200.

So this it's hit and miss. Just happy I found a brand that works well.

 

Offline taunusand

  • Hero Member
  • *****
  • Join Date: Oct 2007
  • Posts: 512
  • Country: dk
  • Gender: Male
    • Show only replies by taunusand
    • www.amiga.dk
Re: CF card errors
« Reply #10 on: December 09, 2008, 08:20:49 PM »
Quote

alexh wrote:
I've never known incompatible cards do this. They either work fully or they are not even detected.


I agree, same thing here.
Mostly I use Apacer & adata.
A1200, Blizzard 030, 2+32MB ram, 4GB CF, pcmcia netcard, Kickstart 3,1
A600, 2MB chip ram+4Mb pcmcia S-RAM, Kickstart 3,1
CD32 - Just for fun  :-D
 

Offline stanlongTopic starter

  • Full Member
  • ***
  • Join Date: Aug 2008
  • Posts: 129
    • Show only replies by stanlong
Re: CF card errors
« Reply #11 on: December 09, 2008, 08:33:04 PM »
Oh Blessed Ones of The Amiganoidal Worlds
Thank you for your Devine Amigadvice
The EAB certainly helped with the pain I was experiencing in the CF regions all the sighns point to the brand of CF cards I was inserting I will in future only use the Sansdisk and other recommended by the EAB who seem to have visited the outer worlds of CFdom
I can say that Sansdisk works where ever you put it
and I was using three another brands  as Hard discs, pcmcia would continually pop as write protected,
thanks one again