[Coco] ASM newbie question

[Tim Fadden]

On 2/14/2010 3:44 PM, Gene Heskett wrote:
> On Sunday 14 February 2010, Tim Fadden wrote:
>    
>> Hi,
>>
>> I am trying to assemble a program called cron_vE.asm.  On my first try
>> it failed because it couldn't find  /dd/defs/os39defs.
>>      
> That is my code, and yes it depends on a 6309 aware defsfile.  The changes I
> made to the defsfile weren't done so as to be automatically adapting between
> the cpu differences.  It has been made to do so for many versions of nitros9
> now.
>
> Today that can probably be changed to just os9defs, IF the file and the make
> are properly configured such that at assembly time the environment variable
> passed to mamou has the symbol H6309 set equ 1.
>
> OTOH, and its been yonks since I walked around in that code, I imagine that
> if you do not have a 6309 in your coco, it can be made to assemble for a 6809
> with only a little work.
>
>    
>> I assumed it was a typo, and changed it to os9defs.
>>
>> No I get---    Error: Symbol Table Full.
>>
>> This program has a script to merge the crontab-datammodule to the exe so
>> that it can get its info from memory, instead of from disk.
>>      
> Yes, that was a later addition.  Having it access the floppy to see if it has
> anything to do this exact minute was a bit of a drag and wear on the floppy
> of course.  The disadvantage of course it that to edit the 'crontab', it was
> a total rebuild.
>
>    

Well, I do have a 6309 installed , but using 6809 build.  With the defs 
that come with the nitros build.
Perhaps I will put the 6309 defs on there with the name os39defs, and 
see what happens.

Seems  everybody has gone the linux, off platform build route, and 
forgotten us who still do it all on the original hardware. :-)

I am compiling  this on my coco.

I do have cron working to do nightly incremental backups with hdback to 
a drivewire image.  So, being able to compile
cron is not essential, just trying to give it a go.

Also, why would cron have to be re=compiled every time the datamod is 
changed?  couldn't the same one be used, and just merge a different 
datamod to it?

Perhaps I am doing some thing wrong.

The script compiles the cron program, and then merges the cron program 
and the datamod and puts it in /dd/cmds.
never mentions compiling the datamod in there any where.  So...
Im thinking the cron program never changes any way right.  If you did an 
ident on the merged cron/datamod you would get two.
seperate things the cron program and then the datamod.

You caould always use the saame cron, and then merge whatever datamod 
you wanted.  This make sense?

I think the script should not be mucking with cron, but compiling the 
datamod, and then  merging the two.  Eh?

I'll do some testing and see if thats so.  Don't really have much asm 
experience, and that was a long time ago.  Just gettin back into it.

Thanks for the input.

I'll let you know what I find out.

Tim


>> The archive already had an assembled cron_ve that works, so I can most
>> likely get it working OK.  But would like to be able to assemble it myself.
>> I can asm the datamodule just fine, but having problems with the exe
>> file.  I don't mind working it out myself, but a few pointer-directions
>> would be great!
>> Im running Nitros9L2-6809, 030209
>>
>>
>> Thanks,
>>
>> Tim
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>      
>
>