[Coco] noswiz doesn't work for me...

[Brett Gordon]

Christopher,

CoCoBoot (and BASIC) is hanging on xroar anytime it writes to the
0xff50-0xff57 region of the io space.  CoCoBoot is trying to find an
IDE harddrive there.   Xroar reports a "WD2793  bad command error".
I'm assuming xroar is putting a FDC controller there (rather than at
0xff40 ?)  I am uncertain whether this can be disabled via a xroar
config setting.  It beleive this is the problem as CoCoBoot boots with
no problems without an IDE controller on a real CoCo2 or CoCo3, and on
Mess.   I'll keep dabbling an see if there's a work-around.

Sincerely,

Brett Gordon

On 2/13/12, Christopher Hawks <chawks at dls.net> wrote:
> Willard Goosey said the following on 02/12/2012 07:46 PM:
>> 512K CoCo3, MPI, glenside IDE (glenside driver) , drivewire4 server,
>> loads hdbdos off floppy, trying to boot cocoboot via drivewire,
>> boot.dsk is drivewire drive 0
>>
>> Gives me:
>> CoCoBoot 0.50a
>> RAM: -
>> ROM: -
>> HDB: -
>> DW: -
>> FD: -
>>   ok
>>
>>
>> Acts the same with or without MPI+IDE
>> ????
>>
>> Willard
>
> Doesn't work for me either.
>
> xroar boot.dsk gives:
>
> CoCoBoot 0.50a
> RAM: -
> ROM: -
> HDB:
>
> and HANGS (true, I only waited 5 minutes...)
> ROMs are Basic 1.3, Extended 1.1, and Disk 1.1 (NO HDB or Drivewire).
>
> Anything else with xroar (even FahrFall!!!) works fine.
>
>
> --
> Christopher R. Hawks
> HAWKSoft
> ---------------------------------------------------------
> Subtlety: the art of saying what you want to say and getting out of range
> before it is understood.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


-- 
Brett M. Gordon,
beretta42 at gmail.com