Re: 2.11bsd rogue can't build

2020-03-05 Thread ben via cctalk

On 3/6/2020 12:06 AM, Warner Losh via cctalk wrote:

On Thu, Mar 5, 2020, 11:15 PM Keven Miller(3k) via cctalk <
cctalk@classiccmp.org> wrote:


I don't have knowledge of the system - just a programmer.
But could it be the difference of static vz dynamic libraries?



2.11 and all pdp-11 unix have no shared libraries. The hardware makes this
super hard to dom

pulling in libnnn.a  instead of libnnn.so /.sl / ??  runtime library?

That would make the text larger, if static linking.



No. It's almost certainly the overlay structure is overflowing and needs to
be redone.

Warner

Keven Miller


Can curses be stripped down just for the terminals used?



Re: 2.11bsd rogue can't build

2020-03-05 Thread Warner Losh via cctalk
On Thu, Mar 5, 2020, 11:15 PM Keven Miller(3k) via cctalk <
cctalk@classiccmp.org> wrote:

> I don't have knowledge of the system - just a programmer.
> But could it be the difference of static vz dynamic libraries?
>

2.11 and all pdp-11 unix have no shared libraries. The hardware makes this
super hard to dom

pulling in libnnn.a  instead of libnnn.so /.sl / ??  runtime library?
> That would make the text larger, if static linking.
>

No. It's almost certainly the overlay structure is overflowing and needs to
be redone.

Warner

Keven Miller
>
> - Original Message -
> From: "Jacob Ritorto via cctech" 
> To: "General Discussion: On-Topic and Off-Topic Posts"
> 
> Sent: Wed 04 Mar 2020 06:01 PM
> Subject: 2.11bsd rogue can't build
>
>
> > Wonder why I can't make(1) rogue on my 11/83, 2044KW, latest patch
> > release from sms.
> >
> > [16] root--> make
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c curses.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c hit.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c init.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c inventory.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c level.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c machdep.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c main.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c message.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c monster.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c move.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c object.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c pack.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c play.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c random.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c ring.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c room.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c save.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c score.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c spec_hit.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c throw.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c trap.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c use.c
> >
> > cc -O -DUNIX -DUNIX_BSD4_2 -c zap.c
> >
> > cc -i curses.o   hit.o   init.o  inventory.o
> > level.o machdep.o   main.o  message.o
> > monster.o   move.o  object.opack.o
> > play.o  random.oring.o  room.o  save.o
> > score.o spec_hit.o  throw.o
> >  trap.o  use.o   zap.o -o rogue -lcurses -ltermlib
> >
> > ld:/usr/lib/libcurses.a(refresh.o): text overflow
> >
> > *** Exit 4
> >
> >
> > Stop.
> >
> > [17] root-->
> >
>


Re: 2.11bsd rogue can't build

2020-03-05 Thread Doc Shipley via cctalk

On 3/4/20 8:01 PM, Jacob Ritorto via cctech wrote:

Wonder why I can't make(1) rogue on my 11/83, 2044KW, latest patch
release from sms.

[16] root--> make





ld:/usr/lib/libcurses.a(refresh.o): text overflow

*** Exit 4


Stop.

[17] root-->



  I'm going on 15-years-ago recollection here, but if that's the 
problem I think it is, it can be fixed by reallocating driver 
distribution in the overlays.


  I tried to build 2.11 with ethernet support and piled all the extra 
includes into one overlay.  A more even distribution across overlays 
fixed it.



Doc


Re: 2.11bsd rogue can't build

2020-03-05 Thread Keven Miller(3k) via cctalk

I don't have knowledge of the system - just a programmer.
But could it be the difference of static vz dynamic libraries?
pulling in libnnn.a  instead of libnnn.so /.sl / ??  runtime library?
That would make the text larger, if static linking.

Keven Miller

- Original Message - 
From: "Jacob Ritorto via cctech" 
To: "General Discussion: On-Topic and Off-Topic Posts" 


Sent: Wed 04 Mar 2020 06:01 PM
Subject: 2.11bsd rogue can't build



Wonder why I can't make(1) rogue on my 11/83, 2044KW, latest patch
release from sms.

[16] root--> make

cc -O -DUNIX -DUNIX_BSD4_2 -c curses.c

cc -O -DUNIX -DUNIX_BSD4_2 -c hit.c

cc -O -DUNIX -DUNIX_BSD4_2 -c init.c

cc -O -DUNIX -DUNIX_BSD4_2 -c inventory.c

cc -O -DUNIX -DUNIX_BSD4_2 -c level.c

cc -O -DUNIX -DUNIX_BSD4_2 -c machdep.c

cc -O -DUNIX -DUNIX_BSD4_2 -c main.c

cc -O -DUNIX -DUNIX_BSD4_2 -c message.c

cc -O -DUNIX -DUNIX_BSD4_2 -c monster.c

cc -O -DUNIX -DUNIX_BSD4_2 -c move.c

cc -O -DUNIX -DUNIX_BSD4_2 -c object.c

cc -O -DUNIX -DUNIX_BSD4_2 -c pack.c

cc -O -DUNIX -DUNIX_BSD4_2 -c play.c

cc -O -DUNIX -DUNIX_BSD4_2 -c random.c

cc -O -DUNIX -DUNIX_BSD4_2 -c ring.c

cc -O -DUNIX -DUNIX_BSD4_2 -c room.c

cc -O -DUNIX -DUNIX_BSD4_2 -c save.c

cc -O -DUNIX -DUNIX_BSD4_2 -c score.c

cc -O -DUNIX -DUNIX_BSD4_2 -c spec_hit.c

cc -O -DUNIX -DUNIX_BSD4_2 -c throw.c

cc -O -DUNIX -DUNIX_BSD4_2 -c trap.c

cc -O -DUNIX -DUNIX_BSD4_2 -c use.c

cc -O -DUNIX -DUNIX_BSD4_2 -c zap.c

cc -i curses.o   hit.o   init.o  inventory.o
level.o machdep.o   main.o  message.o
monster.o   move.o  object.opack.o
play.o  random.oring.o  room.o  save.o
score.o spec_hit.o  throw.o
 trap.o  use.o   zap.o -o rogue -lcurses -ltermlib

ld:/usr/lib/libcurses.a(refresh.o): text overflow

*** Exit 4


Stop.

[17] root-->





Re: RDI BriteLite

2020-03-05 Thread Alan Perry via cctalk




On 3/5/20 7:44 AM, Alan Perry via cctech wrote:




On Mar 5, 2020, at 05:20, Plamen Mihaylov via cctech  
wrote:

 Does anyone have such machine ? I miss the PSU adapter as well as the Sbus
framebuffer which connects the LCD panel to the mainboard. Any info is
appreciated.



I had one, but sold it to someone on this list last year.

I used a generic power supply, one with multiple cord tips and selectable 
output. However, when I exhibited the BriteLite and had it running all day, the 
power supply died after a day and a half.

Good luck on finding a frame buffer for it. I don’t remember the details about 
it, but I took lots of photos of it.


Here is a Flickr album of the insides of what was my BriteLite IPX, 
including the LCD frame buffer - https://flic.kr/s/aHsmLNnBuU


alan



alan




Best regards,
Plamen




Re: VCF PNW 2020: Cancelled

2020-03-05 Thread Alan Perry via cctalk
Given that the venue is closed and it is unknown whether it will reopen before 
the show date, there is a good reason to reschedule at a minimum.

alan

> On Mar 5, 2020, at 21:40, Richard Pope via cctalk  
> wrote:
> 
> Hello all,
>The Covid-19 threat is being over sold. Children don't seem to be at risk. 
> It is the elderly that seem to get really sick. If you are sick just stay 
> home. You can also wear a mask and that will protect others. The flu is more 
> of a threat than Covid-19. If you are not sick wearing a mask is a waste of 
> money and resources for you can be infected through the eyes. No reason to 
> cancel. Just request that sick people please stay home.
> GOD Bless and Thanks,
> rich!
> 
>> On 3/5/2020 11:30 PM, John Herron via cctalk wrote:
>> Tough choice and I saw the museum closing announcement today also. Is there
>> a way to still buy any swag and show support for all of you folks' hard
>> work?
>> 
>> Probably too soon to say but any chance of a reschedule vs cancel?
>> 
>> On Thu, Mar 5, 2020, 7:34 PM Michael Brutman via cctalk <
>> cctalk@classiccmp.org> wrote:
>> 
>>> The short story: COVID-19
>>> 
>>> More details at http://vcfed.org/vcf-pnw.
>>> 
>>> 
>>> Mike
>>> 
> 



Re: VCF PNW 2020: Cancelled

2020-03-05 Thread Richard Pope via cctalk

Hello all,
The Covid-19 threat is being over sold. Children don't seem to be 
at risk. It is the elderly that seem to get really sick. If you are sick 
just stay home. You can also wear a mask and that will protect others. 
The flu is more of a threat than Covid-19. If you are not sick wearing a 
mask is a waste of money and resources for you can be infected through 
the eyes. No reason to cancel. Just request that sick people please stay 
home.

GOD Bless and Thanks,
rich!

On 3/5/2020 11:30 PM, John Herron via cctalk wrote:

Tough choice and I saw the museum closing announcement today also. Is there
a way to still buy any swag and show support for all of you folks' hard
work?

Probably too soon to say but any chance of a reschedule vs cancel?

On Thu, Mar 5, 2020, 7:34 PM Michael Brutman via cctalk <
cctalk@classiccmp.org> wrote:


The short story: COVID-19

More details at http://vcfed.org/vcf-pnw.


Mike





Re: VCF PNW 2020: Cancelled

2020-03-05 Thread John Herron via cctalk
Tough choice and I saw the museum closing announcement today also. Is there
a way to still buy any swag and show support for all of you folks' hard
work?

Probably too soon to say but any chance of a reschedule vs cancel?

On Thu, Mar 5, 2020, 7:34 PM Michael Brutman via cctalk <
cctalk@classiccmp.org> wrote:

> The short story: COVID-19
>
> More details at http://vcfed.org/vcf-pnw.
>
>
> Mike
>


Re: For those with 6809 experience

2020-03-05 Thread Jim Brain via cctalk

On 3/3/2020 8:39 AM, osi.superboard via cctalk wrote:
My assumption is, that the LDA address access is too late at the end 
of the instruction cycle, and the CPU already started the next 
instruction cycle internally. HALT will be acknowledged only during 
the instruction cycle following the LDA.
It would be interesting to measure, when the LDA pulls down the HALT 
compared to the last instruction cycle signal (LIC). Maybe using LDD 
will work better, because the HALT signal will be asserted one clock 
before the instruction cycle ends.


Which is exactly what I ended up doing:

http://www.go4retro.com/2020/03/05/coco-dma-fighting-on-the-bus/

Jim


VCF PNW 2020: Cancelled

2020-03-05 Thread Michael Brutman via cctalk
The short story: COVID-19

More details at http://vcfed.org/vcf-pnw.


Mike


Re: 2.11bsd rogue can't build

2020-03-05 Thread Glen Slick via cctalk
>
> I'm pretty sure I built this successfully in the past. I'll have to
> try it again later with the generic installation before any patches
> are applied, in case that makes a difference for some reason.
>

I took another look to refresh my memory. I assume now that I never
successfully built rogue on 2.11BSD in the past, and what I actually
did was just run the already built hack binary.

If you look at the hack binary it is built with 5 text overlays in
addition to the base text:

# pwd
/usr/games

# ls -l hack
-rws--x--x  1 daemon 195175 Nov 26  1999 hack

# size hack
textdatabss dec hex
37952   32424   12450   82826   1438a   total text: 148608
overlays: 24512,24192,22528,18688,20736

If you look at the Makefile for hack it defines the BASE object files
and the OV1 - OV5 overlay objects files, then uses the ld -Z switch to
link the executable with the BASE object files plus the 5 overlay
object files OV1 - OV5.

If the total text size for rogue is slightly beyond 64KB after pulling
in object files from the libraries then the Makefile for rogue needs
to be modified to move some of the object files into overlays somewhat
similar to the way it is done for hack, for example.

# Hack overlay structure (PDP-11/{44,45,70})
#
#   The BASE (should) occupy 5 segments, but extreme care has to be taken when
# any code is changed as those five segments have been filled to within bytes
# of that limit.  Each of the overlays occupies 3 segments with similar
# restrictions on changing code (most have been filled to within a few hundred
# bytes).  The wise and cautious programmer would be well advised to use
# size(1) heavily ...
#
BASE =  strings.o hack.monst.o hack.Decl.o\
hack.invent.o hack.dog.o hack.mon.o\
hack.engrave.o rnd.o hack.track.o

OV1 =   hack.shk.o hack.topl.o hack.o hack.end.o hack.trap.o

OV2 =   hack.do_wear.o hack.main.o hack.eat.o hack.timeout.o hack.vault.o\
hack.wizard.o hack.topl.o hack.tty.o\
hack.do.o hack.search.o alloc.o\
hack.cmd.o hack.termcap.o hack.unix.o hack.ioctl.o

OV3 =   hack.do_name.o hack.fight.o hack.mkobj.o hack.o_init.o hack.mhitu.o\
hack.makemon.o hack.worn.o hack.rumors.o hack.objnam.o hack.pri.o

OV4 =   hack.zap.o hack.read.o hack.apply.o hack.potion.o\
hack.options.o hack.pager.o hack.wield.o

OV5 =   hack.save.o hack.lev.o hack.mklev.o hack.mkshop.o hack.mkmaze.o\
hack.shknam.o hack.u_init.o\
hack.rip.o hack.bones.o hack.worm.o hack.steal.o hack.version.o

# Crypt *MUST be listed BEFORE $(HOBJ)
$(GAME): crypt $(HOBJ)
@echo "Loading ..."
@ld -i -X -x -o $(GAME) /lib/crt0.o $(BASE)\
  -Z $(OV1)  -Z $(OV2)  -Z $(OV3)  -Z $(OV4) -Z $(OV5) -Y\
  $(TERMLIB) -lc
@echo "Load complete"


RE: SWTPC 6800, FLEX and Percom Floppy

2020-03-05 Thread William Sudbrink via cctalk
Hi Mike,

You really want to ask this on the fufu list:

http://www.flexusergroup.com/flexusergroup/fufusub.htm

I did about a year ago, but didn't get anything definite.  The list tends to be 
bursty.
It's been pretty quiet for the last couple of weeks.

Bill S.

-Original Message-
From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Mike Douglas 
via cctalk
Sent: Wednesday, March 04, 2020 10:02 PM
To: cctalk@classiccmp.org
Subject: SWTPC 6800, FLEX and Percom Floppy

Now that I have my SWTPC 6800 loading and saving programs with paper tape, 
cassette, and floppy disk (using the Percom LFD-400 controller and their 
MiniDOS and MPX “operating systems”), the next logical step is getting FLEX up 
and running. Unfortunately, I only have the Percom floppy controller and I 
don’t know if FLEX compatible disk drivers and boot code were ever written for 
it. Before I go create Percom support for FLEX from scratch, does anyone have 
any leads?

Mike




Re: RDI BriteLite

2020-03-05 Thread Alan Perry via cctalk



> On Mar 5, 2020, at 05:20, Plamen Mihaylov via cctech  
> wrote:
> 
>  Does anyone have such machine ? I miss the PSU adapter as well as the Sbus
> framebuffer which connects the LCD panel to the mainboard. Any info is
> appreciated.


I had one, but sold it to someone on this list last year.

I used a generic power supply, one with multiple cord tips and selectable 
output. However, when I exhibited the BriteLite and had it running all day, the 
power supply died after a day and a half.

Good luck on finding a frame buffer for it. I don’t remember the details about 
it, but I took lots of photos of it.

alan


> 
> Best regards,
> Plamen