Hyperion Entertainment Message Boards

Hi All,
As I mentionned in another thread, I have a Catweasel MK2 anniversary edition and was wondering if it is supported under AOS4.1.
I would assume YES since X-1000 owners can put a CW MK2 in their monster.

Mine was connected to the clockport of the XSurf3 but not recognized. I then connected it to the clockport of my ZorroIV and the cable started to burn
Although the red wire was correct, a quick view on the CW manual said that the number 1 on the clockport of the ZorroIV is by no mean the 1 for the red wire

I now have another cable and connected it to the ZorroIV and no burning

I then installed the driver but the loading of the system hangs with the multidisk.device and TD1 and TH1 in DEVS:DOSdrivers folder. I put the multidisk.device in the black list but still the boot process hangs...
so anyone has any idea whether this board is supported and what is the installation process ?

Lio wrote:Hi All,
As I mentionned in another thread, I have a Catweasel MK2 anniversary edition and was wondering if it is supported under AOS4.1.
I would assume YES since X-1000 owners can put a CW MK2 in their monster.

If you have the catweasel software installed, you can see from the Prefs program that comes with it, that it is supported.
Catweasel type: Catweasel Mk2 or Anniversary Edition "requires CatweaselMk2.library"

Mine was connected to the clockport of the XSurf3 but not recognized. I then connected it to the clockport of my ZorroIV and the cable started to burn
Although the red wire was correct, a quick view on the CW manual said that the number 1 on the clockport of the ZorroIV is by no mean the 1 for the red wire

Ouch...

I now have another cable and connected it to the ZorroIV and no burning

No wonder, i guess...

I then installed the driver but the loading of the system hangs with the multidisk.device and TD1 and TH1 in DEVS:DOSdrivers folder. I put the multidisk.device in the black list but still the boot process hangs...

so anyone has any idea whether this board is supported and what is the installation process ?

Err...to be perfectly honest...i think you fried your Catweasel...

The cable "burning" (whatever that means? I guess it started fuming?) does only mean that that the weakest spot fried while the rest of the card weren't as far.
Still, like you describe it the card might be toast.

I'm surprised you didn't blow your board...


Anyway, if you are still brave enough to keep that card in your amiga you can try to move everything that starts the catweasel out of DosDrivers and into Storage.

Then after you booted Workbench, grab a simple DF0: mount file and double-click (you do have the floppy drive connected properly, haven't you?).
If it still crash, there is a good chance the board is scrap metal

All Individual Computers porducts are reversed to normal products.
Dont ask why but Jens decided that other end of clock port is pin 1.
I would agree, you have proberly cooked your CW, hence its not smoking anymore.

Just hope people don't do this to the prisma cards.

Thanks both for your replies.

I must be lucky then since under AOS3.9 the device still works !
I was trying to locate the MK2.library you mentionned but it does not exist either in Ian package and nor in Jens package...
is it on the card itself like a ROM ?

UPDATE : I can confirm that the CW MK2 anniversary edition is working on AOS4.1 on my A1200PPC.

The board is connected to the clockport of the Elbox ZorroIV and I am using the latest official 68k drivers from Individual computers.
It works if you dont tick "enhanced error correction" in the multidisk prefs.
No need to put multidisk.device and mfm.device in the compatibility list (blacklist)
It is also more stable if you dont put the corresponding dosdrivers (td1 for instance) in DEVS: for rather in Storage and mount them manually (if activated at boot time, it generates a GR with no way to pass beyond)
It is also behaving correctly when a disk is inserted/ejected (icon appears/disappears), not like my original df0 !!!

Hmm, i don't know if it is possible to catch the serial debug output on the classic from your mount crash...but if you should be able to, please save and send it to Ian Gledhill so he could maybe fix that crash...

serial debug should work, according to http://www.hd-zone.com/2011/05/how-to-s ... 1-classic/

but I dont see how Ian Gledhill could help... I asked him at first and he said his work for the CW on the X-1000 was commissioned by AmigaKit, and that the catweaselmk2.library is not free. He was in the opinion that the 68k drivers should work (and he was right, at least partially) !).

Lio wrote:serial debug should work, according to http://www.hd-zone.com/2011/05/how-to-s ... 1-classic/

but I dont see how Ian Gledhill could help... I asked him at first and he said his work for the CW on the X-1000 was commissioned by AmigaKit, and that the catweaselmk2.library is not free. He was in the opinion that the 68k drivers should work (and he was right, at least partially) !).

He can help if the crash happens inside the driver, because iirc he still develops it...but i think i misunderstand you there