[Coco] System gen problem

Steven Hirsch snhirsch at gmail.com
Sun Feb 7 18:22:36 EST 2010


On Sun, 7 Feb 2010, Gene Heskett wrote:

>> I actually think I'm not even getting far enough to worry about the
>> descriptors.  The server is not even getting a request from the CoCo.  The
>> Coco hangs immediately when I try to access the dw drive, but clearly no
>> communication with the server is actually taking place.  Something more
>> fundamental is wrong, but what?
>>
> Possibly a /p descriptor and scbbp.dr have already grabbed the bitbanger
> port,

I tried it without them as well.

> or the cable is foobar.  Since we're only talking about a 3 wire &
> ground cable,

The cable works fine when I switch to the HDB ROM and boot from Drivewire. 
If the basics weren't operational I wouldn't be trying the fancy stuff.

Let's look at this another way, what is the suggested sequence for setting 
up DW when you are building a system from scratch?  I have RTFM - in fact, 
every such manual I have.  Sure looks like the new system is being put 
together in the recommended manner: edited a standard.bl bootlist and run 
the script against it.  It boots and logs the hard drive correctly. 
'mdir' tells me that all the DW modules are there.

Certainly possible that I have the descriptor mismatched with the virtual 
drive  on the DW server, but I would at least expect the counters in the 
DW display to show an incoming command.  Nothing appears, which implies no 
communication from the new system.

When I boot over DW using the pre-made image, things march along as you'd 
expect.

Very much open to suggestions!

Steve



-- 



More information about the Coco mailing list