[Coco] bootlink progress

[Chris Hawks]

On Sat, 20 Oct 2012 00:30:24 -0400
Gene Heskett <gheskett at wdtv.com> wrote:

> First, it's been since early 2008 when I last wrote any os9 assembly stuff, 
> meaning my wet ram is bright red with rust. ;)
> 
> But I'm making progress I think.
> 
> The first thing it needs in the way of data is a copy of /dd's LSN0, and I 
> have that working, with proof being I have it dumping the readlsn0 buffer 
> back to a file that can be inspected with ded.
> 
> So now I have maybe 2 bugs, as it appears that dump doesn't like a filename 
> like bootlink-trace, it won't dump it, but doesn't return an error either!
> ded can look at it just fine, and the data is correct.
> 
> Yes, its a bug in dump, I renamed the file from bootlink-trace to 
> bootlink.trace, and dump works just fine.  Makes me wish I had a gallon jug 
> of an old insect killer called Cooks Real-Kill.
> 
> Tomorrows project will be to parse the command line and recover the vdisk 
> number entered and convert it to a hex number in one byte.
> 
> No one has said whether they think this utility might be useful to them.  
> Perhaps I haven't explained it enough?

	Sounds handy Gene! I'm waiting with 'breathed bait'.

-- 
Christopher R. Hawks
HAWKSoft
------------------------
We pointed the error out to the cashier, who was probably barely old
enough to be legally employed, and her response, if she speaks for her  
generation, was ominous, even terrifying: `It does that because...
because it's a computer.' An entire generation is growing up believing
that the current sorry state of affairs in information technology could
ever be accepted as _normal_!
	-- Zygo Blaxell, RISKS-20.89