[Coco] How to import source code into NitrOS-9?

Fri Oct 9 17:31:40 EDT 2015

Stephen, try:
attr /dd/cmds/scdwv e pe

Those files may not have attributes set and OS9 will not "load" a non executable file (-e -pe). When they are used in a bootfile, it doesn't matter.. the boot doesn't care about attributes.
Also, when you "merge" files, it may be screwing with the attributes (don't remember).

Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com

-----Original Message-----
From: Stephen Pereira <spereira1952 at comcast.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Fri, Oct 9, 2015 4:47 pm
Subject: Re: [Coco] How to import source code into NitrOS-9?

Hi Bill,

Thank you *very* much for the details that you have provided me on my
issue with the ‘dw’ command.

You are remembering my previous situation with a
real physical CoCo 3.  I recently decided to go all in with the CoCo3FPGA
unit.

This new situation presents a bit of an issue for me.  I am using a
NitrOS-9 boot disk provided by Gary Becker that works on the CoCo3FPGA.  When I
did the MDIR, as you requested, I get a nice listing of all the modules
installed, and, of course, none of the scdwv, N or N1 are installed for me.  I
am very uncertain about my ability to create an entirely new boot disk, so I am
attracted to your “quick and dirty” way.

It appears to me from your
instructions that the method you describe starts with a new boot disk, and
merges the three files in question from places they reside way down in the …/scf
subdirectory up into the /DD/CMDS subdirectory as one scdwv file.

So, I went
looking on my existing boot disk from Gary, and, yes, those files are there down
in the …/scf subdirectory.

So, I then entered your lengthy merge command on my
own boot disk…  yes!  the merge command worked.  I can now see a file called
scdwv in my /DD/CMDS subdirectory.

When I move on and try LOAD SCDWV, I get an
ERROR 214.  I don’t have permission to do this.

When I type ATTR
/DD/CMDS/SCDWV, I get:  ----r-wr

I tried: ATTR /DD/CMDS/SCDWV PERM R W E and
that command returned the same ----r-wr.  And the LOAD SCDWV still generates an
ERROR 214.

I am not completely certain I’m doing this right.  What should be
the proper ATTR command to fix the permissions so I can LOAD SCDWV and LINK
SCDWV?

Thanks a million for all your attention and advice.

smp
--
Stephen M.
Pereira
Bedford, NH  03110
KB1SXE

> On Oct 4, 2015, at 10:22 PM, Bill Pierce
via Coco <coco at maltedmedia.com> wrote:
> 
> Stephen, first... run "mdir"... Look
for "scdwv", "N", "N1"-"N13". You must at least have "scdwv", "N', & "N1" to run
the "dw" cmd.
> 
> If your boot is created from the NitrOS9 repo disks, these
files should be there already. I think I remember you mentioning CocoSDC, so I
haven't a clue what was included in that boot.
> 
> If these files are not
there, get a disk image from the repo (anything containing "L2", your cpu type
(6809, 6309) and ending in "dw"). If you know how to make a new boot, then add
these files to the boot. If not, there is a quick and dirty way:
> Put the repo
disk in /X0 in the DW4 server
> Type: (all one line)
> merge
/x0/nitros9/6x09L2/modules/scf/scdwv.dr
/x0/nitros9/6x09L2/modules/scf/n_scdwv.dd
/x0/nitros9/6x09L2/modules/scf/n1_scdwv.dd >/dd/cmds/scdwv
> 
> Once this is
done, type:
> load scdwv
> link scdwv
> Now try the dw cmd again (on the Coco)
>
dw server list C:/file.xxx >/dd/file.xxx
> 
> 
> 
> 
> 
> 
> Bill Pierce
>
"Charlie stole the handle, and the train it won't stop going, no way to slow
down!" - Ian Anderson - Jethro Tull
> 
> 
> 
> My Music from the Tandy/Radio
Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
>
Co-Contributor, Co-Editor for CocoPedia
>
http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator for
TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
> 
>
E-Mail: ooogalapasooo at aol.com
> 
> 
> 
> 
> 
> 
> -----Original Message-----
>
From: Stephen Pereira <spereira1952 at comcast.net>
> To: CoCoList for Color
Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Sun, Oct 4, 2015 5:27 pm
>
Subject: Re: [Coco] How to import source code into NitrOS-9?
> 
> 
> I’ve spent
some time today attempting to use the Drivewire commands…
> 
> From the
>
command line in NitrOS-9, if I attempt the command:
> 
> dw server list
>
d:\filename.ext >/d1/filename.ext
> 
> First I get: ERROR #221 
> 
> I see that
means
> module not found, so I tried LOAD DW, but I still get ERROR #221 after
>
that.
> 
> So, I went onto my PC running the DW Server.  In the UI input line,
I
> type in the same command.
> Here I get: ERROR 201: Could not read from
>
“file:///d:/filename.ext <file:///d:/filename.ext> >d1/filename.ext" because
it
> is not a file.
> 
> On my PC in the DW input line I can issue the command
dw server
> dir d:  and I get the directory of my drive D: so I know that
something
> works…
> 
> Anyway, is this enough information for someone to advise
me on what I am
> doing wrong?
> 
> Thanks very much for listening.
> 
> smp
>
--
> Stephen M.
> Pereira
> Bedford, NH  03110
> KB1SXE
> 
> 
>> On Oct 3, 2015,
at 8:58 PM, K. Pruitt
> <pruittk at roadrunner.com> wrote:
>> 
>> 
>> -----
Original Message ----- From:
> "Stephen Pereira" <spereira1952 at comcast.net>
>>
To: "CoCoList for Color Computer
> Enthusiasts" <coco at maltedmedia.com>
>> Sent:
Saturday, October 03, 2015 4:21 PM
>> 
> Subject: Re: [Coco] How to import
source code into NitrOS-9?
>> 
>> 
>> <…snip…>
> 
>> 
> Hi Stephen.
>> 
>> The
DW commands are issued from the NitrOS-9 command prompt on
> the CoCo. The dw
commands themselves are located in the CMDS directory of your
> NitroOS-9
disk.
>> 
>> The working directory is just whatever directory you
> currently
have set as the working directory. You can send the file to any
> directory you
want.  The way I showed is just the shortest way as it just copied
> the file to
the directory I was in when issuing the command. You can just ignore
> the
entire mention of the default directory.
>> 
>> Let's say you have a directory
>
called SOURCE on the coco on drive /D1, and you wanted to copy a file from a
>
directory called C:\Source on your PC to that directory.
>> 
>> You would
type:
>> 
> 
>> dw server list c:\source\filename.asm
>/d1/source/filename.asm
>> 
>> 
> Everything before the > and after the list
command is the source path,
> everything after the > is the destination path.
>>

>> But if I typed:
>> 
>> dw
> server list c:\source\filename.asm
>filename.asm
>> 
>> it would copy the file
> from the PC to whatever directory
I happened to be in on the CoCo when I typed
> the command as I am not providing
a pathname to a different destination drive
> and directory.
>> 
>> Hopefully
this help clarify it a little bit.
>> 
> 
> 
> -- 
> Coco
> mailing
> list
>
Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
> 
> 
>

> -- 
> Coco mailing list
> Coco at maltedmedia.com
>
https://pairlist5.pair.net/mailman/listinfo/coco

-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco