> Welcome. :-)
Thanks!
> Do you think that we stopped enhancing the user input experience more
> because we were content with what we had or because we didn't see a
> better way to do what we wanted to do?
Both. In the beginning we were content, because the keyboard was well
suited to the capab
> Back on topic, the tools exist, but they are often seen as toys and
> not serious software
> development tools. Are we at the point where the compiler for a visual
> programming
> language is written in the visual programming language?
>
> - Keelan
>
Hi Keelan,
I was going to mention this furth
On 11/30/2018 11:34 AM, Keelan Lightfoot via cctalk wrote:
Thanks!
:-)
Both. In the beginning we were content, because the keyboard was well
suited to the capabilities of the technology available at the time it was
invented. We didn't see a better way, because when compared to using a pen
a
On 11/30/2018 02:33 PM, Jim Manley via cctalk wrote:
There's enough slack in the approved offerings that electives can be
weighted more toward the technical direction (e.g., user interface and
experience) or the arts direction (e.g., psychology and history). The idea
was to close the severely-gr
It was thus said that the Great Keelan Lightfoot via cctalk once stated:
> > I see no reason that we can't have new control codes to convey new
> > concepts if they are needed.
>
> I disagree with this; from a usability standpoint, control codes are
> problematic. Either the user needs to memorize
On 11/30/2018 03:57 PM, Sean Conner via cctalk wrote:
There are several problems with this. One, how many bits do you set
aside per character? 8? 16? There are potentially an open ended set
of stylings that one might use.
I acknowledge that the idea I shared was incomplete and likely has
On Sun, 25 Nov 2018, Liam Proven via cctalk wrote:
> > > For example, right now, I am in my office in Křižíkova. I can't
> > > type that name correctly without Unicode characters, because the ANSI
> > > character set doesn't contain enough letters for Czech.
> >
> > Intriguing. Is there an old MS
On Sat, 1 Dec 2018, Maciej W. Rozycki via cctalk wrote:
Be assured there were enough IBM PC clones running DOS around from 1989
onwards for this stuff to matter, and hardly anyone switched to MS Windows
before version 95 (running Windows 3.0 with the ubiquitous HGC-compatible
graphics adapters wa
Ouch, what was I thinking? Mentioning a project I fundamentally can't talk in
detail about yet; not very smart.
Thus spawning a thread guaranteed to go chaotic. Soy!
Also I've changed the title, since it's disrespectful to drag a deceased
person's name along with this.
I've been busy a coup
Yikes and I am complaining about trying to pick the lock on the UNIVAC
422 anyone have a key # for it? That type on that 8S looks tough...
Ed# www.smecc.org
In a message dated 11/30/2018 6:53:34 PM US Mountain Standard Time,
cctalk@classiccmp.org writes:
And now, back to
On Fri, Nov 30, 2018 at 5:53 PM Guy Dunphy via cctalk
wrote:
>
>
> And now, back to machining a lock pick for a PDP-8/S front panel cylinder
> lock.
> http://everist.org/NobLog/20181104_PDP-8S.htm#locks
Is that not just the standard DEC key used in *everything* (within rough
approximation) th
On Fri, Nov 30, 2018, 6:21 PM Josh Dersch via cctalk On Fri, Nov 30, 2018 at 5:53 PM Guy Dunphy via cctalk <
> cctalk@classiccmp.org>
> wrote:
>
> >
> > And now, back to machining a lock pick for a PDP-8/S front panel cylinder
> > lock.
> > http://everist.org/NobLog/20181104_PDP-8S.htm#locks
>
>
On Sat, 1 Dec 2018, Guy Dunphy via cctalk wrote:
And now, back to machining a lock pick for a PDP-8/S front panel cylinder lock.
http://everist.org/NobLog/20181104_PDP-8S.htm#locks
Are you sure that it's not an "XX2247"?
(Widely used on MOST PDP8's, and pretty much all keyed alike, unless ther
On Fri, 30 Nov 2018, Fred Cisin via cctalk wrote:
> I found the bad spot and put a SECTORS.BAD file there, and then was OK.
> The Microsoft Beta program wanted cheerleaders, and ABSOLUTELY didn't want any
> negative feedback nor bug reports, and insisted that the OS had no
> responsibility to reco
Or, if you prefer, I can dig through some old posts on this list, and tell
you the depths of the cuts for XX2247. It has been widely discussed a few
years back.
On Mon, 25 Apr 2011, Ethan Dicks wrote:
1 - 0.0155"
2 - 0.0310"
3 - 0.0465"
4 - 0.0620"
5 - 0.0775"
6 - 0.093"
7 - 0.1085"
8 - 0.124
It was thus said that the Great Guy Dunphy via cctalk once stated:
>
> Anyway, back on topic (classic computing.) Here's an ascii chart with some
> control codes highlighted.
>
> http://everist.org/ASCII/ascii_reuse_legend.png
>
> I'm collecting all I can find on past (and present) uses of the
At 07:05 PM 30/11/2018 -0800, you wrote:
>On Sat, 1 Dec 2018, Guy Dunphy via cctalk wrote:
>> And now, back to machining a lock pick for a PDP-8/S front panel cylinder
>> lock.
>> http://everist.org/NobLog/20181104_PDP-8S.htm#locks
>
>Are you sure that it's not an "XX2247"?
I wouldn't know. Ther
I found the bad spot and put a SECTORS.BAD file there, and then was OK.
On Sat, 1 Dec 2018, Maciej W. Rozycki wrote:
Well, ATA drives at that time should have already had the capability to
remap bad blocks or whole tracks transparently in the firmware, although
Not even IDE.
Seagate ST4096 (
At 07:23 PM 30/11/2018 -0800, you wrote:
>> Or, if you prefer, I can dig through some old posts on this list, and tell
>> you the depths of the cuts for XX2247. It has been widely discussed a few
>> years back.
>
>On Mon, 25 Apr 2011, Ethan Dicks wrote:
>> 1 - 0.0155"
>> 2 - 0.0310"
>> 3 - 0.046
> How come there are 8? The lock only has 7 pins.
> Also which is pin 1 and which direction do they number?
There are 8 possible depths, as Ethan listed.
The lock has seven pins, with the depth indexes Ethan listed.
Conventional pin numbering is to look into the lock, number from 1 CW
starting
Or, if you prefer, I can dig through some old posts on this list, and tell
you the depths of the cuts for XX2247. It has been widely discussed a few
years back.
On Mon, 25 Apr 2011, Ethan Dicks wrote:
1 - 0.0155"
2 - 0.0310"
3 - 0.0465"
4 - 0.0620"
5 - 0.0775"
6 - 0.093"
7 - 0.1085"
8 - 0.1240
On 11/30/2018 09:53 PM, Guy Dunphy via cctalk wrote:
How come there are 8? The lock only has 7 pins.
Those are the 8 possible DEPTHS of the grooves cut into the key.
So, that gives a possible combinations of 8 to the 7th
power, I think.
These depths correspond (with an offset) to the lengths
At 11:37 PM 30/11/2018 -0500, you wrote:
> > How come there are 8? The lock only has 7 pins.
> > Also which is pin 1 and which direction do they number?
>
>There are 8 possible depths, as Ethan listed.
>
>The lock has seven pins, with the depth indexes Ethan listed.
Ah, sorry, lacking the context
On Fri, 30 Nov 2018, Jon Elson via cctalk wrote:
Those are the 8 possible DEPTHS of the grooves cut into the key.
So, that gives a possible combinations of 8 to the 7th power, I think.
These depths correspond (with an offset) to the lengths of the tumblers
(pins) in the lock.
So, if you know wha
Once the pick is set to the lock cylinder, it is straightforward to
measure the depths. SOME duplicators can copy from the pick tool, but
some will knock sliders out of place.
On Sat, 1 Dec 2018, Guy Dunphy wrote:
Pins on mine will be individually solidly lockable, for that reason.
While you
25 matches
Mail list logo
