also, i had forgot to set which sid to use in the prefs window... haha sorry for that.
now i just need to hook up the card to some kind of speakers. i didn't get the audio cable with the card and it doesn't look like a standard connector... do you know where i can get that catweasel<>soundcard cable?
Is touch not standard then? That's strange. Maybe it's part of the SDK. It'll run fine without it, it just won't flush the device and thereby reload the settings.
You're using a Mk4 (non-plus) aren't you? I don't have one of them (they're identical as far as software is concerned), but I thought it used the same audio connector as the plus, i.e. a bog-standard Cd audio (analogue) cable. I have about 10 of them, I think, and you can get them on eBay for next to nothing, I'm sure.
indeed, it was a bog standard cable. it just didn't look like it.
eh.. i have the cable connected, and vice running as i type this, but i don't get any sound.. the audio cable can be connected in two ways, side shall the red cable be at?..
Doesn't matter. If it's in the wrong way you'll just get the L/R channels reversed.
Try going into the Catweasel prefs file and toggling them, so if you had 0 Enabled and 1 Disabled, then put it to 0 Disabled and 1 Enabled.
Also try turning the volume up quite high. Some Catweasels are fussy with certain SID chips. I personally test with Thing Bounces Back and some little demo programs.
Odd question; Has anybody else managed to get a classic keyboard running via Catweasel on a Sam? I think I had it working once but after I powered off the system it's never worked again.
Wizz.
Rev 1D3 Amiga 1200, Apollo 1240 (40Mhz '040, 64MB RAM), Indivision MKII, Fast ATA MK V, Rapid Road USB, PCMCIA WIFI & OS 3.9.
Run Sashimi first, then run x64 (not x64.exe which is the non-CW build). Open the SID prefs, and select Catweasel. Wait a few seconds. Close x64. Go into a shell and type "Status". This'll give you the task number of Sashimi. Then type "break 6 all" (except put the Sashimi task number in place of '6'). Then send me the t:sashimi.out file! Email or if it's short enough just put it here.
7.RAM Disk:Sashimi> Sashimi Sashimi installed ([Ctrl]+C or "Break 7" to remove) Opening device! FAIL. Probably no SID in prefs. Opening device! Opening catweaselsid.device unit 1 Opening catweasel.device with flags 0 starting task for controller 0 Creating msgport. Checking controller unit for controller 666786B0 unit number 0 flags 0 unit address 0 Creating unit for number 0 Allocated. Now initing 6659F000 Allocating drive geometry.Inited. Init unit: 0 unit adr: 6659F000 LibOpenLight success. open unit no 0 IO units now set to 6659F000 Received IORequest D009 unit hex no 6659F000 Waiting for completion. SysBase is 0 contr->MsgPort is 666786C4 Found message. Execute!!!! ETD_CLEAR = 8005 Command D009 CW_GET_PCI_DEV IO CMD DONE, return code 0 Done request. Received IORequest D00A unit hex no 6659F000 Waiting for completion. Found message. Execute!!!! ETD_CLEAR = 8005 Command D00A CW_GET_PCI_ADDR IO CMD DONE, return code 0 Done request. LibOpenLight success. Unit opening 666A63D8 Reqs are 0 and 66caedc0. CatweaselSID device opening Done. Disk has been changed!No soft Interrupt
something that is really weird is that only 1/3 of the times i press rmb to access the menues in ibrowse it works, the other clicks seem to be eaten by something. this started happening since i put the catweasel in the box. this is not the mk4 plus, this is the mk4. i remember reading that people had problems with weird computer behaviour under windows... maybe there is some bug in the hw?
edit: i know that the sid worked the last time i used the c128. but i haven't tested it in the 128 since i got the catweasel.
OK, try: http://www.retroreview.com/iang/SpotUpSid.lha Run Sashimi, fire up x64 and load a program which you know uses the SID (preferably Thing Bounces Back as that's what I use - the music kicks in on the main title screen). Then get me the sashimi output as before.
yea i do have the c128d it came from. only mui apps are affected by the eaten rmb clicks... this could also be due that fact that i am an os4 betatester, so some update might have screwed something up. gimme a min and i will test.