To be honest, though... the software is working. I can see it's writing to the registers, it seems correctly. Are you absolutely sure that you have the sound connected correctly and that the SID chip is working (you did earth yourself taking it out of the C128 yes? And you definitely jumpered it correctly, i.e. 9V not 12V for the socket with your chip in?
Don't forget to run mixer and up the volume on the correct input to full - the SID output is quite soft through the audio cable (it's a lot louder on the Mk4+ through the headphone jack). Listen for any sound at all, as sometimes SIDs that the CW doesn't like will play but very very softly. Try removing the mono jumper if you have it set.
Not sure what else I can suggest, I'm afraid. Have you tried the SID in both sockets (remember to change the jumpers)?
the mixer ... i haven't ran that... in ages... dont know if i have it installed.. but the audio from the cdrom was fine. i have pumped up the volume a loooot... no sound. i have jumpers set on both slots even though i inly use one... could that confuse it you think? i dont have the mono jumper set i think.
Just gone onto irc - you're not there. If you go online maybe we can think of something else.
Edit: Thought - can you try playing the CD just like you did to test the cable, please? Only this time do it without the cable attached, just to make sure there's no sound!
Can you get us a close-up photo of the card with your jumper settings?
Also, try running Mixer and set the inputs (all of them) up to full!
Another idea: get http://www.retroreview.com/iang/TestSid2.d64 Run this with x64 set to use the normal software SID, i.e. FastSID or something. Autorun the D64 image, and you should get a sawtooth pattern of numbers, starting from 0 going up to 255, then back down to 0, then 255 and so on. Change the prefs to use the Catweasel Mk3. If the numbers all become zero, then it's not finding the SID. If the sawtooth pattern continues, the SID is good! If it's zero, go into your catweasel prefs and switch the SIDs over. Save this, then reboot (to be sure), and do the same again. Then let us know the results!
Edited by Spirantho on 2010/9/15 23:09:00 Edited by Spirantho on 2010/9/15 23:09:58
Can you get us a close-up photo of the card with your jumper settings?
Another idea: get http://www.retroreview.com/iang/TestSid2.d64 Run this with x64 set to use the normal software SID, i.e. FastSID or something. Autorun the D64 image, and you should get a sawtooth pattern of numbers, starting from 0 going up to 255, then back down to 0, then 255 and so on. Change the prefs to use the Catweasel Mk3. If the numbers all become zero, then it's not finding the SID. If the sawtooth pattern continues, the SID is good! If it's zero, go into your catweasel prefs and switch the SIDs over. Save this, then reboot (to be sure), and do the same again. Then let us know the results!
Quote:
Just gone onto irc - you're not there. If you go online maybe we can think of something else.
i guess i went to bed. i will be on irc this evening, also to work with xeron to try to add cw mk4 keyboard support to os4.
Quote:
Thought - can you try playing the CD just like you did to test the cable, please? Only this time do it without the cable attached, just to make sure there's no sound!
i did that already ofcourse. without the cable all i got was silence.
Quote:
Also, try running Mixer and set the inputs (all of them) up to full!
I need the result of running TestSid2.d64 now, that's the next step. That'll tell us if the SID chip is working. I'll try and be on IRC most of the day (#amigadev)
That sounds like your SID is either faulty or not connected properly (you did put it in the right way round, yes? :) ). What happens when you toggle the enable/disable SIDs in the prefs and run TestSid again?
Just missed you in IRC, sorry - was away for a bit! Try again if you can!
For the first part, you want ENVARC:sys/def_CW_AMIGA_DD.info (a copy of any other disk icon, i.e. def_PC0.info will do).
As for the second... the device doesn't get a CloseDevice() request from Assign dismount for some reason. If the device is closed properly, the task closes down, but as there's no close message received, it doesn't quit the task. Have no idea why, maybe someone who knows more about the filesystem can help.
hehe my lucky day ..finished work a bit early today so passed by the garage sale extra early & at first the guy had only 2 mint 'in the box' VIC 20's but said he had a bunch of old computer parts in a few boxes...well lucky me if I didnt find a mangled up 64 motherboard with solder flux all over it and a 6581 SID chip ...a whopping $2 later and I had the 6581 in hand!
ok get home and test the SID in one of my 'test' 64's and it works great
so moving on I put my 2 6581's into my Catweasel MK4+, make sure jumper settings are per manual, and then load up the installation program on the Catweasel CD then download Ian's latest driver and transfer all stuff in devs drawer BUT now when I boot up OS4.1 all I get is a white WorkBench screen ...my mouse is active but I can't do anything at all
so what can I do to get my system back up?? I'll try booting with the OS4.1 CD to at least have access to the WB....
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.
Edit: Just tried to replicate the error - no joy, I'm afraid, it boots just fine here. Try putting "run SYS:Utilities/Sashimi" (or wherever you put Sashimi) in your s:startup-sequence, directly after SetPatch, and when the machine crashes, reboot with no Startup-sequence. Then remove the Sashimi line again using Ed or something (in case you don't know, Esc followed by 'x' to save), and run "Sashimi recover sys:sashimi.out" from the shell. When that's done (it should find debug output) reboot and send me sys:sashimi.out! That should help a little!
Please remember to run the prefs program and save the settings before anything else so the prefs are in sync with the driver. Probably safest to reboot too after installing.
This version 1.7 contains: * support for 40-track drives on all formats now * support for drives with a RDY signal on pin 34 (assumes always a disk present) * Bug fixes and tidy-ups to SuperDiskImage * Catweasel prefs file now allows specification of pin 34 (RDY or DSKCHG - the default values are normally correct).