[Coco] NitrOS9 DW boot

[Boisy G. Pitre]

The problems with the nightly build come from the fact that we've moved from mamou to lwasm.  mamou would allow definitions on the command line to override ones set in the source file.

lwasm does the opposite, which is causing these issues.

I've talked to WIlliam Astle who believes lwasm's behavior is proper, and I won't necessarily argue it, but it's going to be a major pain to go through all the source and set it up correctly.

I do not have the time to deal with this and won't for the next several months.   The quickest path to resolution would be to allow lwasm to go both ways and have a mode where it would let command line definitions override SET directives in the source.

On Oct 9, 2012, at 9:07 PM, Bob Devries <devries.bob at gmail.com> wrote:

> Hi Robert,
> 
> Actually, it's more a problem with rel than with the clock, but I'll check that out too.
> 
> Regards, Bob Devries
> Dalby, QLD, Australia
> 
> ----- Original Message ----- From: "Robert Gault" <robert.gault at att.net>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Wednesday, October 10, 2012 12:01 PM
> Subject: Re: [Coco] NitrOS9 DW boot
> 
> 
>> Bob Devries wrote:
>>> Hi all,
>>> 
>>> I noticed that there's no 50Hz version of the boot disk for DriveWire. Looks like I need to create my own?
>>> 
>>> Regards, Bob Devries
>>> Dalby, QLD, Australia
>>> 
>> 
>> I think all you would need to do is replace the clock_60hz module with the clock_50hz. If you can run the 60hz version, you could build a 50hz boot file with the scripts. If you can't run the 60hz version on hardware, you ought to be able to run it on an emulator.
>> 
>> 
>> --
>> 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