Hello dir Amiga Users.

Today I installed the Catweasel MK4 in my X1000.
I connected the 880kb Amiga FloppyDrive to the
Cable with the three connectors.
I plugged behind the twist so my drive should be "df0".

After installing the latest OS4 Software from Ian Gledhill
(Yes I put the two devices manually into Devs: )
I configured via Prefs the right settings (Amiga DD)
on Port 0.

After a reboot and the activation of Storage:DosDrivers/td0:

The drive comes to live. And than I get the message:

"ReadError in Diskblock 0"

The funny thing I didn't even put a Floppy inside the drive.

Well I thought the drive may be defective and tried several
other ones. All with the same result.

Drives I used:

-Panasonic JU-253 (Amiga 880kb)
-Chinon FZ-357 (Amiga 1.76mb)
-Teac F 235 (with Amitrade "The real HD" PCB)

Who has an idea?


Regards
z!Erec

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec

Hi there (any news on the hdd front?)

If the error comes up right after starting the Mountfile it looks like the drive is wrongly attached.
Mine works fine in the X1000.

Either try to get a cable with only one connector on both sides (without the "twist") or, if you don't have such, try to plug the floppy drive *before* the twist.
You can also try to turn the cable around (twist on the catweasel side).
(I know i had some hassle back when i tried it first in the XE with a "three twist connector").

Plug it into the black connector on the Catweasel and to your floppy drive.

Also make sure the floppy drive is plugged in the "right" side...some floppy drives doesn't have a mounting bar anymore and one could easily plug the cable "upside down".

@Raziel

Hi.

Well I have all sorts of cables here.
Yes I pluged into the plack pluck of the catweasel
an yes I always used the red marked cable as Pin1.

That's all okay.

Now even using a one on one cable as suggested
the same problem appears.

Question: does the config program give you an error
when saving?

I get a "touch: unknown command" message"

Regards

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec

You've got a PM in your Inbox


Yes, i too get that error message when changing/saving the Prefs, thats an error in the prefs program where it relies on having the "touch" program installed (normally inside the SDK package) ... Ian knows about this aswell, but haven't got time to fix it yet.

My Prefs look like this:

Catwesel type: Catwesel Mk3/Mk4/Mk4+
Disk 0: 3.5" High Density (Standard PC drive) Step Time: 6 ms Pin 34: DSKCHG

@thread

I've done your cable-swap-trick
(twisted end plugged to Catweasel)
and switched from Amiga Floppy Drive
to 1.44MB PC Floppy Drive. That worked!!!

It now reads original Amiga Floppys and they
start right into RunInUAE.

Do you remember how cool FANTAVISION was?

Thanks alot.
Cheers
z!E

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec

Glad i could help

Have fun with the classics...

@zErec

Quote:

Amiga Floppy Drive

You mean you actually tested Amiga floppy drives? I didn't know these were supported. I thought this card was meant for the PC and a PC floppy drive. Well that explains it!

@Hypex

yup for PC 3.5 inch drives only is what I remember when I set mine up.

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

Y'know, you can always email me directly about problems. I don't bite. :)

First thing:
The "unknown command touch" is an annoying little bug because here's no real way round it except to install touch, which I'm not sure of licensing on.
The thing is that if you have the driver running like you did then when you change the drive type, the driver needs to be notified. By touching the driver it expunges it and reloads it from disk instead of from memory which makes it re-read the prefs. There's a very simple way to get round this without touch : just reboot. You can also just flush the device using scout or something.

The next thing is that the Catweasel will support whatever drive you put on it. I wrote support for Amiga DD drives (fresh from an A2000 for instance) and Amiga HD drives from an A4000. You can also configure it for old drives with RDY signals, or 3" drives, or just about anything else.

Hope that clears some things up :)

Oh, while I'm here... don't know if it helps anyone but did you know that Teac combo floppies with the 5.25" and 3.5" drives in the or bay.... they can read (probably write too) the flip side of c64 disks without modification. Don't know if that's of any help!

@Spirantho

Quote:

The "unknown command touch" is an annoying little bug because here's no real way round it except to install touch, which I'm not sure of licensing o

Why not just copy the behaviour? Should just be a simple case of a few DOS functions. My OS4 has Touch which it says modifies the file date to the current time. How that is useful I don't know. I also don't know how doing that to a driver would reload it. But I am thinking in terms of "touching" a device on disk causing a reload which doesnt make sense.

Quote:

There's a very simple way to get round this without touch : just reboot.

That doesn't sound very user friendly.

@Spirantho

/me nudges Spirantho to his list of CW bugs

@Spirantho

Quote:

The next thing is that the Catweasel will support whatever drive you put on it. I wrote support for Amiga DD drives (fresh from an A2000 for instance) and Amiga HD drives from an A4000. You can also configure it for old drives with RDY signals, or 3" drives, or just about anything else.

That was what I understood. The support of real Amiga Drives.
Have you got an idea why my DD and HD drives don't work here?
They where pulled from a working Amiga 500 and Amiga 4000.

I get this "ReadError in Diskblock 0" and this message comes up
even without a floppydisk inserted.



Regards
z!E

Last edited by zErec on 29-Aug-2015 at 09:47 AM.

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@Spirantho

"alias touch setdate []"

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php