[Coco] BLOB or something else?

[George Ramsower]

 By the way. The basic controller address is still $FF40. The $FF74 and FF58 
are for using the "No Halt" part. The device descriptor does not have 
anything to do with that. This is what made me think that perhaps the jumper 
may be involved. Or even worse, an address decoder..

 George

> ----- Original Message ----- 
> From: "Bob Devries"
>
>> There are four different versions of the Disto SCI driver IIRC.
>> One pair is the IRQ version, and the other pair the sleep version. The 
>> pairs are split up between the address location which is selected by a 
>> pin header on the SCII board. This changes the extended IO capability of 
>> the SCII from FF74-FF77 to FF58-FF5F.
>>
>> If you have the pin header set to 1-2,  the address range FF74-FF77 is 
>> used. 2-3 selects FF58-FF5F. If you choose the wrong driver, the system 
>> will boot, but once the driver is initialised, it will not continue. That 
>> switch is hard coded in the driver, I believe, not in the descriptor as 
>> it should be. Someone correct me if I'm wrong here.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>>
>> ----- Original Message ----- 
>> From: "George Ramsower" <georgeramsower at gmail.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Tuesday, March 18, 2008 5:26 AM
>> Subject: Re: [Coco] BLOB or something else?
>>
>>
>>> I was mistaken. The bootlist file didn't put the Disto driver in it.
>>> DOH! Anyway, I simply replace the tandy driver with the Disto driver and 
>>> again, it crashed during boot.
>>> I've tried many different bootlist order and each time, using the Disto 
>>> driver, it crashes at the same point. Each time, I made another boot 
>>> with the original driver ant it would boot fine.
>>> I'm wondering if something may be wrong with the controller.
>>>
>>> Suggestions?
>>>
>>>
>>> ----- Original Message ----- 
>>> From: "George Ramsower"
>>>
>>>>
>>>> I was exploring in my SYS directory and looking into the subdirectory 
>>>> named "PATCHEDMODULES" I found the same bootlist. So I created a new 
>>>> bootfile from that directory and the new boot works.
>>>> The disto now is NoHalt and it's working goodly.
>>>>
>>>
>>>
>>> --
>>> 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