[Coco] batch file processing

Bob Devries devries.bob at gmail.com
Sun Feb 7 01:02:10 EST 2010


Wayne, could you email me the disk images, so I can try them here on my copy
of VCC, to determine if I get the same results?

--
Besides a mathematical inclination, an exceptionally good mastery of one's
native tongue is the most vital asset of a competent programmer.

Edsger W.Dijkstra, 18 June 1975

----- Original Message -----
From: "Wayne Campbell" <asa.rand at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, February 07, 2010 4:56 PM
Subject: Re: [Coco] batch file processing



> Thanks for doing that, Bob. It helps me know that something else must be

> different, but I don't know what it is. I know that the os9l2_1.os9 image

> boots perfectly, with green background and border, black text and a

> magenta cursor. OS9SYSMR.os9 boots, but shows me a black screen. Updating

> to the newer version of MESS did not change it.

>

> Wayne

>

> ----- Original Message -----

> From: "Bob Devries" <devries.bob at gmail.com>

> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>

> Sent: Saturday, February 06, 2010 9:31 PM

> Subject: Re: [Coco] batch file processing

>

>

>>I just located the disk image you mentioned.

>>

>> I booted it using FCC. It boots into a VDG type screen. Black border,

>> green background and black characters, 32 x 16 size.

>>

>> This was the default screen for an unmodified copy of OS-9 Level 2.

>>

>> Why you're getting all black is a mystery to me.

>>

>> Regards, Bob Devries

>>

>>

>> --

>> Besides a mathematical inclination, an exceptionally good mastery of

>> one's native tongue is the most vital asset of a competent programmer.

>>

>> Edsger W.Dijkstra, 18 June 1975

>>

>> ----- Original Message -----

>> From: "Wayne Campbell" <asa.rand at gmail.com>

>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>

>> Sent: Sunday, February 07, 2010 3:49 PM

>> Subject: [Coco] batch file processing

>>

>>

>>> The easiest way I know to ask this is to just say what I want to do. The

>>> OS-9 L2 manual does not cover anything like this, so I don't know if the

>>> shell allows for it.

>>>

>>> I want to use the following as input to cmp:

>>>

>>> ls -rienac diska

>>> ls -rienac diskb

>>>

>>> This causes ls to produce a listing that contains one item per line. I

>>> still have to figure out how to tell the script to skip the directory

>>> entries in the listing, and only process what occurs within the

>>> directory.

>>>

>>> diska and diskb are copies of the contents of different disks that are

>>> similar (os9L2_1.os9 and OS9SYSMR.os9). The idea is I want to compare

>>> every file that occurs on both disks to see which ones may be different.

>>> Since I can boot both disks, and because both are almost identical,

>>> there has to be a reason why OS9SYSMR.os9 boots to a black screen (fore,

>>> back and border). I think I should be able to find something different

>>> between them, other than the files that exist on one, but not the other.

>>>

>>> I was hoping I could do something like (not in these words) "using input

>>> from ls/diska and ls/diskb, compare each file that occurs on both disks

>>> and state the results". By redirecting final output to a file, I can

>>> then find any and all differences between the disks. I'm not sure what

>>> version of shell I'm running. The ident of the module being loaded in

>>> startup (shell) is a merged module file. The shell ident itself shows a

>>> size of $1B42 #6978. The shell_21 file in the CMDS shows an ident of

>>> $0602 #1538, so it isn't the same shell.

>>>

>>> Anyone have ideas?

>>>

>>> Wayne

>>>

>>> --

>>> 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

>

>

> --

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco





More information about the Coco mailing list