ok I want to erase all the files installed by the installer on the disk that came with the MK4+ and get my system to boot up normally again so what files do I erase from where ?
once I get it up and running fine again then I'll go step by step to get the drivers going...think i got to excited and started messing with too many things
Someone said to me yesterday or so that his Workbench didn't like having Catweasel drivers in DEVS:Dosdrivers for some reason - something I need to look into. In the meantime, put your mountlists in SYS:Storage/DOSDrivers, not DEVS:DOSDrivers and mount them manually. That should fix it. You can do that by booting with no startup-sequence, and just copying the files from the shell there. No need to boot off CDs.
That was me
Problem is that if i have the ml in DOSDrivers (Amiga DD and HD, PC DD and HD) it will search for a disk in drive and if not found display a requester that the disk in drive x is unreadable (all of that with a white WB screen waiting in background). Only if one clicks the requester away, the normal WB boot will return
Maybe if possible add a delay on startup or check if WB has already started or something like that or suppress the requesters (back to my MFS remark from IRC )
i have also problems with Catweasel in my PegasosII under OS4.1.2. The driver won't run. Floppies are from PC. (changed 5 or 6) If the ML starts (automatic or manual) a Message pops up:
"Disk in drive TD0 has readerrors in disk-block 0"
Same thing on TH0 (or 1)
The driver is version 1.6 and the Mountlists are also from here. If the Message pops up, the WB is blocked.
OK, first thing to do is to check that your prefs are set correctly. I'm assuming you're using the latest version of the drivers.
Run sashimi, and try using SuperDiskImage to read an Amiga DD disk. Then send me the output from Sashimi! I mentioned earlier in the thread how to do this.
Yes, someone pointed out that touch isn't part of the normal AmigaOS, it's part of the SDK. Just ignore that message, it just means you need to reboot after saving prefs, that's all. I'm working on making it so you don't need to.
ah ok at least I know my CW is ok as I tried the 'read' file on the OS4 CW drivers and away went the lights on 5.24 and 3.5 inch drives and the old clicking noise is back
ok still getting only a black screen at startup though..gonna try the sashimi thing you mentioned later on..the 68k install i did messed something up me thinks..as the prefs program you made is asking for touch now?
btw, how do i get to the early star up menu again to boot without the startup sequence ???
Opening catweasel.device with flags 1 Checking controller unit for controller 6659E9E0 unit number 0 flags 1 unit address 0 Creating unit for number 2 Allocated. Now initing 652F3000 Allocating drive geometry.Inited. Init unit: 2 unit adr: 652F3000 LibOpenLight success. open unit no 0 IO units now set to 652F3000 Received IORequest 9 unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 9 TD_MOTOR CMD_MOTOR: Motor is 0 Turning motor off. Motor is now 0 motor length set to 0 motor was 0 IO CMD DONE, return code 0 Done request. Received IORequest 14 unit hex no 652F3000 Waiting for completion. Done request. Received IORequest F unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 14 TD_ADDCHANGEINT Found message. Execute!!!! ETD_CLEAR = 8005 Command F TD_PROTSTATUS IO CMD DONE, return code 0 Done request. Received IORequest E unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command E TD_CHANGESTATE Seek to 0 Current is 0 Never found track 0. Error 30 Offset 0 Len 0 Block 0 IO CMD DONE, return code 1E Done request. Received IORequest 16 unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 16 TD_GETGEOMETRY IO CMD DONE, return code 0 Done request. Received IORequest F unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command F TD_PROTSTATUS IO CMD DONE, return code 0 Done request. Received IORequest 9 unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 9 TD_MOTOR CMD_MOTOR: Motor is 0 Requesting turning motor on. Turning motor on now...catweasel_set_motor 1 Done. Motor is now 1 motor length set to 1 motor was 0 IO CMD DONE, return code 0 Done request. Received IORequest 2 unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 2 CMD_READ index 0length 200 Reading Track 0 Side 0 Sector 0 Seek to 0 Current is 0 Never found track 0. Exiting read_track with error 30 Done read/write Error code was 30 Actual bytes 200 Error 1E Error 30 Offset 0 Len 512 Block 0 IO CMD DONE, return code 1E Done request. Received IORequest 9 unit hex no 652F3000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command 9 TD_MOTOR CMD_MOTOR: Motor is 1 Turning motor off. Motor is now 0 motor length set to 0 motor was 1 IO CMD DONE, return code 0 Done request. catweasel_set_motor 0
thats my way for the output:
- run sashimi - doubleclick TH0 - close the upcomming requester - start a shell an type "break 6 all" - post the sashimi.out here ;)
in catweasel prefs i have 3,5" Double Sided 80 track saved.
Now with more fixes, and enhancements: * Atari ST 720KB support * SAM Coupe support (Try this with the Sam Coupe filesystem on OS4Depot!)
I've also included a mountlist for Sam Coupe disks so they can be mounted as SAM0:
@SpotUp
To disable the startup-sequence, hold down both mouse buttons when you reboot with Ctrl+Amiga+Amiga (or directly after the "booting kickstart" progress bar in UBoot... then select "Boot with no Startup-Sequence".
Move all the files from DEVS:Dosdrivers/ which are to do with the catweasel into SYS:Storage/dosdrivers, then reboot.
@huepper
You're trying to mount a high density disk in a double density drive! :)
Flags of 1 means Amiga HD, but if you set the Catweasel prefs to "3.5" 80 track double sided" you're telling it that you have a double density drive there. The Catweasel prefs should be set to "3.5" High Density" if your drive is a standard high density drive (as it almost certainly is). If your drive really is a DSDD disk you whipped out of an A2000, then you can't read HD disks in it, sorry. :)
Remember: TD0 is double density, TH0 is high density, PD0/PH0 the same but for MS-DOS, but if catweasel prefs is being told you have a double density drive it won't know what to do to read high density.
When I get a full release version all this will be documented. :)
Thanks for this testing, though - it's very valuable as it lets me see where people are going to get confused. I'll make Catweasel prefs a bit clearer now.
To disable the startup-sequence, hold down both mouse buttons when you reboot with Ctrl+Amiga+Amiga (or directly after the "booting kickstart" progress bar in UBoot... then select "Boot with no Startup-Sequence".
Move all the files from DEVS:Dosdrivers/ which are to do with the catweasel into SYS:Storage/dosdrivers, then reboot.
oh damn how can I forget that man..must have done it a zillion times!..anyhow just did it but still get a black screen...but strange that i boot up with OS4.1 CD no problem
If you've taken out all the Catweasel mountlists, then it's not the Catweasel drivers that's causing the trouble....
You can always try and rename catweasel.device in devs: to make sure it doesn't load it...
Edit: @huepper: I'm assuming you've got the disk drive in the right place - remember that to mount a device with unit 0 such as TH0:, you need the floppy drive at the end of the cable, after the twist. PC drives are all jumpered as unit 1 by default.
is there some basic test tool i can use to see that my catweasel works as it should? or could you write something that tries to talk to the catweasel and see if it gets a response? i am starting to suspect that my cw is faulty.
If you've taken out all the Catweasel mountlists, then it's not the Catweasel drivers that's causing the trouble....
.
nah I doubt it as it was working great until I started messing with CW drivers and nothing else has changed since..will experiment more once I'm home..thanks again
I'll try and be in #amigaworld on irc.amigaworld.net so people can ask me for help.
Can you take a screenshot of your Catweasel prefs, and tell me exactly how your disks are organised on the floppy cable (i.e. mine is: CW->5.25 HD->blank->blank->3.5 HD).
SuperDiskImage is the best tool for testing, make sure you use a known good floppy, set the format (e.g. format a floppy in an A500, then select Amiga DD 800KB on the correct unit) and then press Read. Then send me the Sashimi output. Try it with a different floppy drive (what make is yours?) If you have a 3.5 and 5.25, remove one of them and test the other. Try BOTH units, i.e. remove the 5.25, set your prefs to have a 3.5" HD (if that's what you have) on BOTH units, then use SuperDiskImage to read unit 0 and then unit 1. You'll see the drive light coming on on the unit it's reading (if you've disconnected the other, no lights will go on). Try using SuperDiskImage to read track 79 also, and see if you hear it seeking (you may not as it seems to not find track 0)
If that doesn't work, put exactly the same structure (cable and drives) onto a PC and check that it works there (remember to change the BIOS).
If that still doesn't work I'll try and put a diagnosis thingy in the Catweasel prefs.
@SpotUp
It looks like your CW is working from your sashimi output.
Are you testing the SID or the disk part at the moment? Is your SID chip verified working in a C64/C128 then? Can you take a photo of your board so we can see the jumpers please?