Anyone want to test Catweasel Mk4 drivers under OS4?

I would be happy to help you. I have AmigaONE G4, AmigaOS4.1 and Catweasel Mk4.

@Spirantho

Is anyone else getting GR's when trying to mount the DOSDrivers?

@Valiant

Rzaiel did until he realised that the CW had fallen out of its slot. :)

If you're still getting it when you're sure it's fitted right (in UBoot you should get "Catweasel Mk4 initialised" or something like that printed) send me a debug log ("kdebug "console memory"" then "mount pd0:" followed by "dumpdebugbuffer ram:test.out" when it crashes) and I'll see if I can see what's happening.

@Spirantho

Quote:



Quote:

@Valiant
If it's something like this:

Symbol info:
Instruction pointer 0x7FD94AC8 belongs to module "cw.device" (PowerPC)
Symbol: __libOpen_light + 0x3F8 in section 1 offset 0x00006AA8

Stack trace:
__libOpen_light()+0x3F8 (section 1 @ 0x6aa8)
libOpen()+0xA4 (section 1 @ 0x6e88)
native kernel module kernel+0x00020064
native kernel module ramlib.kmod+0x0000116c
native kernel module ramlib.kmod+0x000017ac
module C:SetPatch at 0x7FFC5994 (section 5 @ 0x4974)
module L:CrossDOSFileSystem at 0x7FDA2970 (section 6 @ 0x9950)
module L:CrossDOSFileSystem at 0x7FDA3EFC (section 6 @ 0xAEDC)
module L:CrossDOSFileSystem at 0x7FDA4DEC (section 6 @ 0xBDCC)
native kernel module dos.library.kmod+0x0001ea6c
native kernel module kernel+0x0003cbf0
native kernel module kernel+0x0003cc70

then your CW is dislodged, try to plug it in firmly and reboot

@Spirantho

It's not a problem with the h/w as I can mount the old CW DOSDriver without any problems. Just as soon as I finish repairing my programs partition I'll get a debug log.

@Spirantho

I have found a little odd behaviour, but it seems this is OS related

If i keep a disk in the drive and do a hard/soft reboot (with NO floppy mountlists at all in Devs/Dosdrivers) an icon comes up showing FD0: Unitialized

The disk was prepared to be a PCDD (PD0) formatted empty disk

The strange thing about it is, that no floppy driver/mountlists have been started, still the icon shows up, looks like a fallback plan in the OS or CrossDOS?

EDIT: If i try to format it, it is incorrectly found to be a 720KB Amiga(!) disk (It lets me choose, FFS, Intl. Mode, Dir Cache and Long Names)
Formatting works and results in a 720KB disk ... hmm, still PC or Amiga?

EDIT2: After formatting with FD0: and mounting the cw DODDrivers the disk is not seen by them. IIRC that is because OS4 uses a new fs for floppys which is not backwards compatible?

Overall it works awesome, no bugs found so far, no data loss or anything, great job...

Feature Requests:

the only thing left i'd love to have now would be some kind of "hide NDOS/Unitialized and such" icons from WB and only show useable/formatted ones when having more than one with mountlists (PD0, PH0, TD0, TH0) installed

(There is a commodity called Ghostbuster on Aminet (even with source) which does ecxactly that (i think, can't test as it obviously crash on OS4), but of course, an option in Workbench Prefs would be even nicer

And it would be neat if it actually used the "default floppy disk icon" when showing up on WB and not the HD one

@Spirantho


Heck yes, I'd like to test it! I've had my MK4 laying around in it's box for the past 6 months. I wanted to install it in my Peg2 but wasn't going to waste my time since no OS4 drivers existed for it.

@Valiant

Can you send me the output of PCIScan too please?

Thanks!

@Spirantho

OK, I PM'd you the output from my PCIScan. The latest situation is that after having to rebuild my programs: partition I'm no longer getting GR's when mounting the DOSDrivers, but now when I switch disks it only shows the first disk that was put in. Let me try the latest drivers and see it that's still happening.

@Valiant

That's "normal" behaviour right now.

The polling of the CW seems to be a bit picky.
I have it too here.

As a workaround you can do a "diskchange TD0:" in a shell

New version uploaded to the same place as before but called "cw_aos4_20091105.lha"!

@ferrels

Quote:

It has existed for years...

@Spirantho

Any chance of also adding support for using the joystick ports under OS4 to your Catweasel mk4 driver effort? It would be nice to also be able to use the joystick port for connecting regular digital Amiga joysticks under OS4 and the catweasel mk4 has 2.

@Dwyloc

Why only the joy ports?

There is an optional SID chip sitting on the CW, lets support that too...

tbh, i would be happy if i'd get the same useability of CW floppys thanb i already have with AOne floppys (and be even happier if features exists that can only be used by the CW )

@Liveforit

Your drivers were cool and working...

@Raziel

Quote:

... and without them there's no way I could have modified them to support reading and writing.

Edit: Incidentally, writing support for the joysticks would require not only CW technical docs - which I don't have - but also AmigaInput SDK docs - which I believe I don't have. As for SID support, that's up to the emulator writers...

@Raziel

Quote:

Thanks.

@Spirantho

Quote:

You can translate the calls in to KEY presses, most OS4.x games use keyboard anyway.

(I think you can find some hits on this in the E-UAE source code, if you have a Amiga joystikk)

Quote:

It has to be tread safe, its there for logical to have some part or some kind of minimum support of emulator writes. (I did not have the SID or any Amiga joysticks so thats is way I never did it), and yes you need some more docs for that.

@Spirantho

Awesome job on the current work on the cw.device.

I have been testing it all day, with Amiga 880kb disks and images. Reading and Writing worked flawless as did non dos disk games.

Would it be possible to use the original Amiga keyboard with the Mk4 and OS4.1?

@LiveForIt

Quote:

And I have used it for years without any problems. I don't think I've thanked you enough, LiveForIt, for all the times when your CW driver saved my bacon. If you're working on anymore cool sw for OS4, I'd sure like to help test it for you.

In the process of rebuilding my system, I've reinstalled your driver and it's still working flawlessly for me the first time. Now to see if I can get Spirantho's to work for me also...