HECnet

hecnet@lists.dfupdate.se

15589 discussions

Need help with VT220 down-line loadable characters (DECDLD)

by bqt＠softjar.se

On 2013-07-21 20:03, Julian Wolfe wrote: I know this is a bit off-topic, but I was playing around with the DECDLD commands in the VT220 programmer's reference guide to make character graphics on the VT220 (I'm actually using Mac240, a VT220 emulator that has full DECDLD support at a VT220 level) I'm having a problem getting characters to join at the top of the cell. The top two pixels don't seem to meet. I see some material about VT320 but the addressing of the matrix seems quite different on that terminal. I'm using 7-bit encoding to create the characters. Do I need to use 8-bit in order to use the full matrix? I'd be surprised if anyone on here has actually messed with this, but I thought it was worth a shot. I can also toss my work at whoever has a VT220 lying around to see if they can test it as well. Any input is appreciated (as long as I can decode it, ha ha) MIM::DU:[FED] Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

12 years, 6 months

HECnet cisco

by b4＠gewt.net

On Sun, 21 Jul 2013, Brian Hechinger wrote: On Jul 20, 2013, at 20:44, "Cory Smelosky" <b4 at gewt.net> wrote:

12 years, 6 months

Need help with VT220 down-line loadable characters (DECDLD)

by julian＠twinax.org

I know this is a bit off-topic, but I was playing around with the DECDLD commands in the VT220 programmer's reference guide to make character graphics on the VT220 (I'm actually using Mac240, a VT220 emulator that has full DECDLD support at a VT220 level) I'm having a problem getting characters to join at the top of the cell. The top two pixels don't seem to meet. I see some material about VT320 but the addressing of the matrix seems quite different on that terminal. I'm using 7-bit encoding to create the characters. Do I need to use 8-bit in order to use the full matrix? I'd be surprised if anyone on here has actually messed with this, but I thought it was worth a shot. I can also toss my work at whoever has a VT220 lying around to see if they can test it as well. Any input is appreciated (as long as I can decode it, ha ha) Julian

12 years, 6 months

HECnet cisco

by wonko＠4amlunch.net

On Jul 20, 2013, at 20:44, "Cory Smelosky" <b4 at gewt.net> wrote:

12 years, 6 months

HECnet cisco

by b4＠gewt.net

On 20 Jul 2013, at 20:36, Brian Hechinger <wonko at 4amlunch.net> wrote: On Sun, Jul 21, 2013 at 12:26:00AM -0000, Cory Smelosky wrote: On 20 Jul 2013, at 20:23, Cory Smelosky <b4 at gewt.net> wrote: On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote: 65.19.130.45 I used the address the email told me to use. ;) New config pulled. Is something not working on my end or has nobody else?s tunnel to me come up? I think you aren't the only person to now follow directions. :) Ah. ;)

12 years, 6 months

HECnet cisco

by b4＠gewt.net

On 20 Jul 2013, at 20:35, Brian Hechinger <wonko at 4amlunch.net> wrote: On Sun, Jul 21, 2013 at 12:23:22AM -0000, Cory Smelosky wrote: On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote: 65.19.130.45 I used the address the email told me to use. ;) The email told you to use 65.19.130.45, so no you didn't. :) Mail.app sucks at sorting. ;) The one you were using is the old one. The one you were supposed to STOP using. :) -brian

12 years, 6 months

HECnet cisco

by wonko＠4amlunch.net

On Sun, Jul 21, 2013 at 12:26:00AM -0000, Cory Smelosky wrote: On 20 Jul 2013, at 20:23, Cory Smelosky <b4 at gewt.net> wrote: On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote: 65.19.130.45 I used the address the email told me to use. ;) New config pulled. Is something not working on my end or has nobody else?s tunnel to me come up? I think you aren't the only person to now follow directions. :)

12 years, 6 months

HECnet cisco

by wonko＠4amlunch.net

On Sun, Jul 21, 2013 at 12:23:22AM -0000, Cory Smelosky wrote: On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote: 65.19.130.45 I used the address the email told me to use. ;) The email told you to use 65.19.130.45, so no you didn't. :) The one you were using is the old one. The one you were supposed to STOP using. :) -brian

12 years, 6 months

HECnet cisco

by b4＠gewt.net

On 20 Jul 2013, at 20:23, Cory Smelosky <b4 at gewt.net> wrote: On 20 Jul 2013, at 20:15, Brian Hechinger <wonko at 4amlunch.net> wrote: 65.19.130.45 I used the address the email told me to use. ;) New config pulled. Is something not working on my end or has nobody else s tunnel to me come up?

12 years, 6 months

HECnet cisco

by b4＠gewt.net

On 20 Jul 2013, at 20:16, Brian Hechinger <wonko at 4amlunch.net> wrote: On Sun, Jul 21, 2013 at 12:09:54AM -0000, Cory Smelosky wrote: On 20 Jul 2013, at 20:08, Brian Hechinger <wonko at 4amlunch.net> wrote: On Sun, Jul 21, 2013 at 12:04:48AM -0000, Cory Smelosky wrote: Do you need OSPF? If not, your network isn't crazy enough! :) I did for IPv6. I had to stop using it when I enabled a bride-group for LAT. Know a way around this? Why did you need to stop using it? What exactly was the issue? I'll need to know that first before I can help you work around it. :) It seems the OSPF packets weren?t actually flowing. RIPng had the same issue. IPv4 stuff (eigrp) still can pass fine. Oh, so it flat out just stops working on an interface that's in a bridge-group? Hmm, I'll have to look into that. Never did that before. I go out of my way to avoid bridge groups if at all possible. Yeah. It could be multicast related. Not sure. I need the bridge group for LAT. -brian

12 years, 6 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet