[Coco] I am back to not being able to format a floppy, help plz

[Tormod Volden]

On Thu, Oct 23, 2014 at 12:21 AM, Gene Heskett <gheskett at wdtv.com> wrote:
> On Wednesday 22 October 2014 16:28:30 Tormod Volden did opine
>> I am confused to what you are trying to do. Is your posted floppy
>> format issue something to do with level3? The rest of the world is
>> using level 1 or 2 as far as I know. Try to solve one thing at a time,
>> would be my suggestion.
>>
> I rebooted it again after coming home from the Dr's, this for about the
> 20th time in the last 2 days, and it formatted the disk as expected.
> Fluke I can't repeat? Damnedifiknow.
>
> If I can make a floppy boot disk that works with these newer, smaller
> drivers, then I will make a floppy to backup to the default HD boot vdisk.
>
> But I am still running down drivers & descriptors for stuff that is not
> available in the 3.3.0 I just built.  I finally did find r0.dd, to work
> with myram.dr, but had to go back to a disk I'd taken apart with vfy years
> ago to find that.  That disk was, is, about 22 years old.  I probably have
> it 4 or 5 other places on my hd, but stuff is hard to find w/o a 2 pane
> file manager.  Yeah, I'd spoiled by mc on linux. :)

It's there: level2/coco3_6309/modules/mr0.dd
mr0.dd goes with myram (the ram disk you wrote)
r0.dd goes with rammer (another ram disk implementation)
Their format is slightly different.

>> > My default hd boot is from $80/128, and bootlink has me set for that
>> > atm. I don't want to ruin what I have until I know for a fact that
>> > it works because I'd have to restart from a floppy scratch.  That is
>> > years back up the log obviously.
>> >
>> > I'll study the bailout message & see if I can figure out where it
>> > came from:
>> > make[3]: *** No rule to make target `defsfile.asm', needed by
>> > `defsfile'. Stop.
>> > make[3]: Leaving directory `/opt/nitros9/level3/coco3_6309/defs'
>> > make[3]: Entering directory `/opt/nitros9/level3/coco3_6309/sys'
>> > make[3]: Nothing to be done for `all'.
>> > make[3]: Leaving directory `/opt/nitros9/level3/coco3_6309/sys'
>> > make[3]: Entering directory
>> > `/opt/nitros9/level3/coco3_6309/bootfiles' make[3]: Nothing to be
>> > done for `all'.
>> > make[3]: Leaving directory `/opt/nitros9/level3/coco3_6309/bootfiles'
>> > rm -f nos96309l3v030300coco3_40d_1.dsk
>> > os9 format -e -t40 -ds -dd -q nos96309l3v030300coco3_40d_1.dsk -
>> > n"NitrOS-9/6309 Level 3 Disk 1"
>> > os9 gen nos96309l3v030300coco3_40d_1.dsk -b=bootfiles/bootfile_40d -
>> > t=bootfiles/kernel_1773
>> > Boot track written!
>> > Bootfile Linked!  LSN: 12, size: 30911
>> > os9 makdir nos96309l3v030300coco3_40d_1.dsk,CMDS
>> > os9 makdir nos96309l3v030300coco3_40d_1.dsk,SYS
>> > os9 makdir nos96309l3v030300coco3_40d_1.dsk,DEFS
>> > os9 copy -o=0 modules/sysgo_dd nos96309l3v030300coco3_40d_1.dsk,sysgo
>> > os9 attr -q -pe -npw -pr -e -w -r
>> > nos96309l3v030300coco3_40d_1.dsk,sysgo cd cmds; os9 copy -o=0
>> > make[2]: Entering directory
>> > `/opt/nitros9/level3/coco3_6309/cmds' shell utilpak1 asm attr backup
>> > binex build cmp cobbler copy cputype date dcheck debug ded deiniz
>> > del deldir devs dir dirsort disasm display dmem dmode dsave dump
>> > echo edit error exbin format free grfdrv help ident iniz irqs link
>> > list load login makdir mdir megaread merge mfree mmap modpatch
>> > montype mpi os9gen padrom park pmap proc procs prompt pwd pxd reboot
>> > rename save setime shell_21 sleep smap sfree tee tmode touch tsmon
>> > tuneport unlink verify wcreate xmode make[2]: Leaving directory
>> > `/opt/nitros9/level3/coco3_6309/cmds'
>> > ../nos96309l3v030300coco3_40d_1.dsk,CMDS
>> > /bin/sh: Syntax error: Unterminated quoted string
>> > make[2]: *** [nos96309l3v030300coco3_40d_1.dsk] Error 2
>> > make[2]: Leaving directory `/opt/nitros9/level3/coco3_6309'
>> > make[1]: *** [dsk] Error 2
>> > make[1]: Leaving directory `/opt/nitros9/level3'
>> > make: *** [dsk] Error 2
>>
>> Probably something in the makefile you made. Maybe you should start
>> with what I suggested in a previous mail.
>>
> That _is_ the output of what you suggested.  It destroyed everything I had
> done.  The first thing I have to do is fix the defsfiles, level 3's

No, running make doesn't change any source files, so that did not
destroy your work. You messed that up when changing branches and
"resolving" the conflicts. If you have uncommitted changes, it is best
to save them somewhere before experimenting with mercurial.

And no, the above errors are not what results of doing what I
suggested on a clean nitros9 repo.

> makefiles and defsfiles are so old they are still calling them by the
> microware names!
>
> But what good does it do me to fix it when I haven't the foggiest what my
> old srcfrg login and passwords were 3 or 5 years back.  So I am locked out
> from committing such fixes as the makefiles & defsfile's.  That obviously
> is self defeating.

Just post the diffs or send patches to me like last time. I will
review and commit them to the repo.

Regards,
Tormod