[Coco] Interbank Incident for Drivewire ?

[Retro Canada]

maybe with edtasm from cassette we can make simple dskcon read oh boy this suxs! every crash needs to reload dw and edtasm from cassette! :P



Sent from my iPhone

On 2012-11-27, at 9:50 PM, Aaron Wolfe <aawolfe at gmail.com> wrote:

> "unknown opcode" is the entire error.  240 is the decimal value the
> byte that triggered it contained.
> something is making the machine spit out a byte containing 240 at a
> time when it should not.
> 
> On Tue, Nov 27, 2012 at 9:46 PM, Daniel Campos <daniel.campus at gmail.com> wrote:
>> I have a similar problem here. The Color64 doesn't work either with DW3 or
>> DW4. I have tried to configure the server as CoCo1 and CoCo2 but no avail...
>> The DW server log always appear "UNKNOWN OPCODE: 240" when I try a "DSKINI
>> 0" on the CoCo side. There is anywhere a list with those DW errors ?
>> 
>> Thanks,
>> Daniel
>> 
>> Em 27/11/2012 21:34, Juan Castro escreveu:
>> 
>>> Is there a neat POKE I could use to change the speed to a lower value
>>> when loading CoCo 1 DW from the Cloud9 site WAV? I'm having difficulty
>>> making it work. Whereas the CoCo 3 version works like a breeze. And
>>> yes, I tried changing the server speed to 38400.
>>> 
>>> On Tue, Nov 27, 2012 at 9:01 PM, Darren A <mechacoco at gmail.com> wrote:
>>>> 
>>>> On Tue, Nov 27, 2012 at 3:13 PM, Robert Gault wrote:
>>>>> 
>>>>> Arthur Flexser wrote:
>>>>>> 
>>>>>> Out of curiosity, why would it work with a CoCo 2 but not a CoCo 1?
>>>>>> 
>>>>>> Art
>>>>>> 
>>>>> Actually I don't know what will happen and made an assumption based on
>>>>> the
>>>>> NitrOS-9 project. If you look at the Level1/coco section, you will see
>>>>> that
>>>>> two types of disks get built, coco1_dw3.dsk and coco2_dw3.dsk. There is
>>>>> no
>>>>> such distinction for non-Drivewire disks.
>>>>> 
>>>>> Aaron, Boisy, or Darren Atkinson would be the ones to ask about this
>>>>> difference, and what it is.
>>>>> 
>>>> The bit-banger routines in DriveWire for the CoCo 1 are timed to
>>>> operate at 38400 bps. This is because the CoCo 1 uses an OpAmp to
>>>> shift the voltage of the TxD output, whereas the CoCo 2/3 have the
>>>> SALT chip. The CoCo 1 OpAmp can't handle the faster 57600/115200 rates
>>>> used in the CoCo 2/3 routines.
>>>> 
>>>> Darren
>>>> 
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>> 
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>> 
>> 
>> 
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco