Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: 560SL on January 28, 2006, 10:39:13 AM
-
I just installed a 18 gig scsi3 HD with my Cyberstorm PPC card. I have OS 3.9 and all the Gigs are showing up brilliantly in AmigaDOS.
However, Opus seems pretty confused with this, the HD shows up as a 1gig disk with 0k free. Any interaction with the HD from Opus is upredictable, mostly hanging Opus after a while.
Is there any way around this problem, or is the only workaround to repartion the HD?
-
560SL wrote:
However, Opus seems pretty confused with this, the HD shows up as a 1gig disk with 0k free.
That's how it is. Just ignore it.
Any interaction with the HD from Opus is upredictable, mostly hanging Opus after a while.#
This shouldn't happen. Are you sure it's DOpus' fault ? Perhaps other programs have the same problem ?
Bye,
Thomas
-
Yapp, must be Opus related problems since hairy things start to happen when I try to copy files from or to the big HD. Typically, everything freezes with HD checksum errors as a result. There is no problem to copy things directly from CLI.
-
I have magellian2 version 5.81 on my Peg1
I've got two hardrives one of which has 2 partitions which are about 4 gigs each. I've never had a problem reading and writing to them. I've used this on my "real" amigas as well, of course.
my Amiga 2000 used OS3.9 and of course MOS is really based on 3.1 or something like that, but it still works just fine.
there's got to be something else wrong with your setup.
-
Agreed, I have DOpus 5.82 on ths A4000T, the largest disk is an 80Gb drive with the largest partition being 40Gb.
As expected, the "disk free" values shown by DOpus are wrong, so just ignore them. The whole system is completely reliable, no problems with DOpus.
I'd suggest using a decent disk filing system such as PFS3. Also check the MaxTransfer and mask are set correctly in HDtoolbox.
From PFS3's manual:
The MaxTransfer must be divisible by the sector size (usually 512) due to a bug in the Workbench format code. This is done by ending the value with 'e00'.
For example: instead of 0xffffff, use 0xfffe00.
Not sure if this still stands with OS3.9, but something to keep in mind.