Canon MDD210

2019-12-11 Thread Jeffrey S. Worley via cctalk
I've got a thoroughly tested and working Canon Mdd210 5.25" floppy
mechanism here.  I don't need such a special mech, any 360k drive would
do.  If you want this particular mechanism for some reason, just let me
know and we can arrange a trade for a more ordinary one.

Best,

Jeff




Re: Converting C for KCC on TOPS20

2019-12-11 Thread Guy Sotomayor Jr via cctalk
I think the challenge will be does binutils (where nm, objcopy and objdump 
live) support for the object file format used by TOPS20.

I haven’t looked at the TOPS20 object file format but it seems like the best 
approach would be to have the C compiler generate symbols as it normally would 
and write a utility to “fixup” the too long symbols rather than munging the 
source (which is basically what you’re proposing using the stuff from 
binutils…just a bit more work.

TTFN - Guy

> On Dec 11, 2019, at 9:07 AM, Guy N. via cctalk  wrote:
> 
> On Wed, 2019-12-11 at 00:25 +, David Griffith via cctalk wrote:
>> I'm trying to convert some C code[1] so it'll compile on TOPS20 with KCC. 
>> KCC is mostly ANSI compliant, but it needs to use the TOPS20 linker, which 
>> has a limit of six case-insentive characters.  [...] Does anyone here have 
>> any knowledge of existing tools or techniques to do what I'm trying to do?
> 
> Is "objcopy --redefine-syms" any help?  Compile the code as-is to
> produce object files, use nm or objdump to find all of the global
> symbols, generate unique six-character names for them, and then use
> objcopy to create new object files with the new names.
> 
> Or have I completely missed the point?  I'm not familiar with KCC, does
> it produce object modules in a format objcopy doesn't support?
> 
> I know someone who was working on gcc support for the PDP-10, I wonder
> if he's still doing that or has given up
> 



Re: Converting C for KCC on TOPS20

2019-12-11 Thread Phil Budne via cctalk
> KCC is mostly ANSI compliant, but it needs to use the TOPS20 linker, which 
> has a limit of six case-insentive characters.

LINK has support for long (up to 72 character) symbols, and it appears
FORTRAN v11 can generate them, but the MACRO assembler may never have
gotten support;

http://pdp-10.trailing-edge.com/bb-r775d-bm_tops20_ks_upd_4/01/sources/lnknew.mac.html

SUBTTL  BLOCK TYPE 1002 - LONG SYMBOL ENTRY


;   
;   ! 1002 ! COUNT !
;   
;   !  SYMBOL  !
;   
;   ! MORE SYMBOL  !
;   


in lnkpar.mac:

ND MAXSYM,^D72  ;[2210] Max number of characters in a symbol
ND SYMSIZ, ;[2210] Number of words of storage for long symbols


Re: Converting C for KCC on TOPS20

2019-12-11 Thread Guy N. via cctalk
On Wed, 2019-12-11 at 00:25 +, David Griffith via cctalk wrote:
> I'm trying to convert some C code[1] so it'll compile on TOPS20 with KCC. 
> KCC is mostly ANSI compliant, but it needs to use the TOPS20 linker, which 
> has a limit of six case-insentive characters.  [...] Does anyone here have 
> any knowledge of existing tools or techniques to do what I'm trying to do?

Is "objcopy --redefine-syms" any help?  Compile the code as-is to
produce object files, use nm or objdump to find all of the global
symbols, generate unique six-character names for them, and then use
objcopy to create new object files with the new names.

Or have I completely missed the point?  I'm not familiar with KCC, does
it produce object modules in a format objcopy doesn't support?

I know someone who was working on gcc support for the PDP-10, I wonder
if he's still doing that or has given up



ZedRipper

2019-12-11 Thread Tomasz Rola via cctalk
Hello,

Surfaced on Ycombinator. This one looks good. Something old, something
new, etc. Like my kind of project :-)

 :: ZedRipper: A 16-core Z80 laptop

http://www.chrisfenton.com/the-zedripper-part-1/

and some comments:

https://news.ycombinator.com/item?id=21756243

-- 
Regards,
Tomasz Rola

--
** A C programmer asked whether computer had Buddha's nature.  **
** As the answer, master did "rm -rif" on the programmer's home**
** directory. And then the C programmer became enlightened...  **
** **
** Tomasz Rola  mailto:tomasz_r...@bigfoot.com **