The 1541 mountlist doesn't fully work yet - you can read ok, but writing seemed to be ignored last I tried it. Will look into it properly soon.
The latest version of 1541-Handler is v2.2 and is now called CBM1541FileSystem. Among new features and fixes is support of ACTION_SHUTDOWN packet so that the filesystem can be dismounted. You will have to modify your mountlist a little to make it work with this filesystem as it doesn't use a handler startup string anymore but needs to be passed a full FileSysStartupMsg instead.
Is it possible to access real Amiga disks from within E-UAE, i.e. set the Catweasel floppy drive as DF0: in E-UAE config and boot a game from the original floppy?
I don't remember for sure but if E-UAE supports mounting a filesystem directory as a device within the emulation, then you can mount TD0: and use that. It won't be full emulation, but it'll kind of work.
In fact, in theory, it's possible with the Mark IV to emulate DF0: precisely, but the problem is the emulation would have to have absolutely accurate timing, otherwise it just wouldn't work at all; on a real Amiga, Paula is guaranteed a regular clock, in the emulation, it's not a real clock, whereas the disk rotation is in real time. If the emulation is running with the right timing, though, it could work!
Janus UAE supports the Catweasel as an emulated expansion, so you can mount TD0: from within the emulation. I don't know if E-Uae supports this, it may well do, albeit with a little tweaking....
If what you want is to boot directly from the Catweasel disk exactly as if it were an A500, though, the answer is it could work sometime if the emulation is accurate and fast enough, and I may yet have a look at it, as it would be rather cool...!
The latest version of 1541-Handler is v2.2 and is now called CBM1541FileSystem. Among new features and fixes is support of ACTION_SHUTDOWN....
Update:
tried this but get "Please insert volume ICBM0 in any drive..Process Mount" requester at boot up ?..i changed tooltypes to Unit 0 as per docs & put required files in sys:L/ and into sys:Devs/DosDrivers....any ideas?...having problems reading 1541 disks..nice 1541 icon shows up on my wb and when I clikc on it it appears to be reading the disk but nothing comes up after ages of searching the disk my 3.5 drive works flawessly with my Amiga disks though
playing wity dual SIDS but cannot get the MIxer to work..volume always on one high level??
I assume you changed the device setting to catweasel.device as well? In addition to this I think you need to add the following setting to the DOSDriver file (not in the tooltypes): Flags = 16
diskimage.device ignores the flags field but I think catweasel.device needs this to know what format the disk should be treated as. This value is from the cbm0 dosdriver that's in the catweasel driver archive.
If you're using "ICBM0:" then you're using a mountlist from the C64 filesystem, not the catweasel archive. Any device names beginning with "I" are from the diskimage archive, rename the one for the catweasel to, say, CBM0:, and make sure that unit is set correctly, device is set to catweasel.device, and flags are set to the correct format, in this case 16. The CBM0: mountlist in the catweasel archive should work (though you may need to change the name of the filesystem as it's been updated).
- installed catweasel hardware @ slot 2 on the Pegasos II board - installed floppycable from PegII-Board to the CW-Hardware as described - installed a floppycable with 4 ports from the CW-Hardware - connected first (or second) 3,5" port to a pc-floppydrive (some drives tested) - installed your driver-archive in the prefered places - doubleclicked th0 or th1
The CBM0: mountlist in the catweasel archive should work (though you may need to change the name of the filesystem as it's been updated).
Actually it has changed more than that. While for 1541-Handler you should only set Handler/Startup settings (it generates it's own FSSM from the info in Startup setting), for CBM1541FS you should use FileSystem/Device/Unit/Flags/... settings in mountlist instead like with other filesystems. BTW I just noticed that your cbm0 mountlist for 1541-handler was broken: Flags = 16 Startup = "DEVICE catweasel.device UNIT 0" This should have been: Startup = "DEVICE catweasel.device UNIT 0 FLAGS 16"
Maybe this is why you had trouble with write support?
No, the write support was my fault entirely. The latest archive (today's) seems to work, anyway.
@huepper
Maybe. :)
Have you read my dev page for it? Looks under "Instructions for setting up...": Quote:
First, set up your Catweasel Mk4 as directed in the instruction manual. You shouldn't connect the Catweasel to the motherboard floppy interface, this isn't supported yet.
Are you connecting your Catweasel to your motherboard, did you say?
Remember TH0: is a trackdisk (Amiga) high density disk - make sure your disk is therefore formatted as an Amiga HD disk, and that you have your preferences set correctly according to the dev page (if you don't have "High Density 3.5" " then it's probably wrong! :) )
- CW installed in the 3rd PCI-Port - 1 PC-Floppy installed and connected to the 2nd connector (behind the twist) - installed last archive of your driverpackage
now tell me please what i have to do. :(
i have changed floppies and cabels .... and cabels and floppies ....
Go to the catweasel prefs program, and select "3.5" High Density" for both units 0 and 1 (to be safe).
Put a known good PC HD disk which is formatted to 1.44MB FAT12 (standard PC format) into the drive. mount PH0:. See if it works. If it doesn't, try running SuperDiskImage and set the file gadget to ram:test.dsk, then set the format type to MS-DOS High Density, and click read disk. If the lights turn green, it's working.
Last possibility: Mount PH0: and try and format it (this should work with the latest drivers from today). Check the disk light is going on as you'd expect. If it's not, try doing the same with PH1:.
If that doesn't work, I'm running out of ideas. In the latest archive you'll find "catweasel.device.debug" - copy that to devs:catweasel.device and run sashimi as before. Try and image the disk as I mentioned above, and when it's failed, send me the sashimi output (from another shell, type "break x" where x is the task number of sashimi that status reports)
Have you tried changing the floppy cable? What make is your floppy? Is the Catweasel detected correctly in scout or ranger or something (it's called a TigerJet modem interface!)
The CBM0: mountlist in the catweasel archive should work (though you may need to change the name of the filesystem as it's been updated).
Actually it has changed more than that. While for 1541-Handler you should only set Handler/Startup settings (it generates it's own FSSM from the info in Startup setting), for CBM1541FS you should use FileSystem/Device/Unit/Flags/... settings in mountlist instead like with other filesystems. BTW I just noticed that your cbm0 mountlist for 1541-handler was broken: Flags = 16 Startup = "DEVICE catweasel.device UNIT 0" This should have been: Startup = "DEVICE catweasel.device UNIT 0 FLAGS 16"
Maybe this is why you had trouble with write support?
tried this but get a guru at wb startup.(adding the Flags16 after Unit0)..
@ Ian,
-what do you mean by 'changing the name of the filesystem as it's been updated"? - any idea how I can adjust the volume when in Vice64 using dual SID settings?
getting awesome sound out of only 1 speaker and can't control the volume via mixer. noticed when loading up the stereo sid player i get following in output window: "Translate Error:ID1281 was requested & would be returning null" "sound warning: buffer drained" ..any settings I'm missing? (btw, both SIDS were firmly seated in the CW and were tested in my 64 as working)
Are you configuring your SID player properly? Remember to make the C64 program use the same address. In the StereoSidPlayer archive I posted earlier, on the C64 once the stereo player has loaded, you need to press the Commodore key (usually Ctrl I think), and change the address to the correct one, usually 0xDE00 I think, and make sure the Stereo Sids address in the Vice SID prefs are set to the same address. Also of course make sure the CW prefs program has both SIDs enabled.
As for your CBM0:, is it working now then? Remember to check your icon tooltypes for the mountlist!
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
