Catweasel MK 4????????

[Fester]

Stainy wrote:

Thanks for your suggestions.. I`m using the latest drivers.. I will have a fiddle with the cables..although I am using them as per the manual... original floppy cable and the teo headed one!  I`m guessing the three headed cable in the box isn`t used because it`s assuming you have that one already in your pc..
But I will try

The original cable in my pc does NOT work with the mk4. I finally tried the 3 connector cable supplied with the mk4. This might also be part of the problem in your setup.

Stainy wrote:

Also I remember before when I had a CW and had it working in Winuae.. I had to mount CAT in shell before it would pull up a disk  :-o

[/quote]

Mine is automatically mounted. My cat device setup is in dh0:devs/dosdrivers/ and my default startup-sequence included the following lines:

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

So when I type "mount cat:" in a shell window, I get the message that the cat is already mounted. Also, if I type "cat:", the device's icon appears on the workbench. It's not there by default when I boot up even though the cat is mounted. No big deal. I can live with that.

[Fester]

jalister wrote:
I see you can read Amiga disks in WinUAE using your Catweasel. I just got an MK4, and it works well. I am having one problem though. When I try to use the Catweasel in WinUAE to access CAT: I get the error "Not a DOS disk in device CAT". Any ideas?

Imagetool 2.3 has worked perfectly. I've tried the April and September drivers. I have also done the steps you have listed here, as best as I can tell.

Thanks.

Hi jalister,

I got the same error as you did but if I remember correctly, I wasn't able to make an ADF with the imagetool at that time. My cables were not connected correctly.

I'd check the cat device's file in devs/dosdrivers. See if the unit and flag is set to correct values.

I am using the last connector on the 3 connector cable so imagetool opens up with Unit 2 by default. (I assume that's the reason why). At any rate, I had to set the unit and flag in the cat file as shown below:

Device = multidisk.device
Unit = 1
Flags = 0
Surfaces = 2
BlocksPerTrack = 11
Reserved = 2
mask = 0x7ffffffc
MaxTransfer = 0x00200000
Interleave  = 0
LowCyl = 0
HighCyl = 79
Buffers = 5
BufMemType = 0
StackSize = 4096
Priority = 5
GlobVec = -1

Hope this helps.

[Fester]

zhulien wrote:
boy, am I glad this thread was ressurected!  if it weren't I wouldn't have known how bad this product was and would have bought it!  I was looking at it purely for C64 discs, but from this thread it seems no-one's got it working for this - perhaps Individual should fix their advertising up to mention the fact it doesn't really work as advertised?

Well it works reasonably well for me. I can do the things I purchased it for. Plus, I have a couple of those old command control joysticks connected to it.

Browsing the Internet, it seems people all have the same problems with this Catweasel. Same errors keep appearing in forums. Seems it's either the drivers or the cables. But I'm not into C64 so I don't know anything about that aspect.