A bit off topic other than tips for anyone else trying to travel cheaply. I
have a trip to California in a month although the final destination isn't
San Jose.
I can fly in to SJC and Google is sounding like I might be able to get a
few bus hops from the airport and find my way there? Any tips, tricks or
warnings?
*(more off-topic below, feel free to stop above for helping anyone venture
around to CHM).
No idea if I'm testing my luck neighborhood wise and debating taking a bus
or train from Mountain view to Pasadena after my free day.
Feel free to email me offline if this is too far from list interest. Mostly
if anyone was to benefit it would be what's the cheapest route to spend a
day at the CHM and then return to the airport again.
- John
From: Dale H. Cook
Sent: Wednesday, September 14, 2016 9:52 AM
> Please do not change the subject line in a thread. The subject line of
> this thread has been changed twice since it began as "68K Macs with MacOS
> 7.5 still in production use..." When you change a subject line the header
> information concerning the subject is unchanged, and that is what the
> list archives and some email clients go by. There are now three threads
> concerning different subjects archived as one thread at classiccmp.org.
> If you want to change a subject please start a new thread, and if you
> wish you can give the new thread a subject line such as "New Subject (was
> Old Subject)" to reflect its origin.
Actually, Mr. Cook, the standard for the last 35 years or so has been to
change the subject line, with the old subject in SQUARE BRACKETS with the
characters "was: " prepended. Any decent newsreader or threading mail
reader knows how to deal with that, and threading is unbroken. What was
broken in the messages about which you complain is the substitution of
parentheses () for brackets [].
See the subject line on this message for an example.
Rich
Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computer Museum
2245 1st Avenue S
Seattle, WA 98134
mailto:RichA at LivingComputerMuseum.orghttp://www.LivingComputerMuseum.org/
On 09/14/16 09:52, Dale H. Cook wrote:
>
> Please do not change the subject line in a thread. The subject line
> of this thread has been changed twice since it began as "68K Macs
> with MacOS 7.5 still in production use..." When you change a subject
> line the header information concerning the subject is unchanged,
> and that is what the list archives and some email clients go by.
> There are now three threads concerning different subjects archived
> as one thread at classiccmp.org.
And what's so horrible about that? I miss entire conversations because
somebody starts discussing something I *would* find interesting under a
misleading Subject: and never changes it. Oh well - people will do what
they do, thank goodness for search...
How do you justify making everybody conform to your preferred behavior?
Even though I did what you wanted in this reply/new topic. ;) But now
nobody can see what I didn't quote from your original message without
going off and running a search - isn't that annoying too?
--S.
Just thought I'd share with you all one of my pet projects for the past few
years. I have written an HP-35 and HP-45 simulator for the PDP-8, which
uses the original microcode from these calculators. Thus, it is just as
accurate as the original calculators, I would believe.
Not really sure why I decided to do this, but I suppose I enjoy both HP
calculators and PDP-8 programming. I guess it's nice to have a scientific
calculator at one's disposal too while sitting in front of a PDP-8, too. It
also shows that something like this could've existed back in the early
1970s if one were so inclined to do it. Perhaps it's also a bit of homage
to the Expensive Desk Calculator for the TX-0 and PDP-1.
Anyways, you can grab the code from here:
https://github.com/drovak/hpcalcpdp8
The HP-45 support is new as of the past couple of days; I went ahead and
through in a help function to explain the keys. Toggle between 4XXX and
0XXX on the switch register to toggle between HP-45 and HP-35 modes,
respectively. Feel free to give feedback; I've tested it fairly extensively
in SimH with no major issues other than no error indication on the HP-35. I
have a debug mode which prints each register every instruction cycle, but I
haven't used it too much in recent times; I went ahead and IFDEF'ed it as
it also reads from the switch register.
OS/8 support will come soon, as that shouldn't be challenging. You need 8k
to run this, though I also uploaded my original hp35pdp8.pal code which
runs in 4k. It lacks the help function (and obviously the HP-45 simulator),
but otherwise, works pretty much the same.
Big thanks to Eric Smith for his 'nonpareil' work which inspired much of
the simulator.
Kyle
Rich Alderson wrote:
> Actually, Mr. Cook, the standard for the last 35 years or so has been to
> change the subject line, with the old subject in SQUARE BRACKETS with the
> characters "was: " prepended. Any decent newsreader or threading mail
> reader knows how to deal with that, and threading is unbroken. What was
> broken in the messages about which you complain is the substitution of
> parentheses () for brackets [].
I had no idea that there was a standard. Is it in an RFC or something?
I've commonly seen either parenthesis or square brackets used, and
I've normally used parenthesis myself, but if there's a documented
standard, I'll consider switching.
Chuck Guzis wrote:
> I was a bit surprised to
> find that my home thermostat was running BusyBox.
Cameron Kaiser wrote:
> s/surprised/alarmed/
> Remember, it's going to be the Internet of Pwned Things before too long.
Unfortunately most people elide the first two letters of the
initialism, leaving only "IoT".
It is actually the "Insecure Dangerous Internet of Things".
On Tue, Sep 13, 2016 at 3:38 PM, Doug Ingraham <dpi at dustyoldcomputers.com>
wrote:
>
> Thanks for an interesting bit of optimization!
Need some more optimization fun? :) Vince and I were working on some code
to add two signed 12 bit numbers and detect overflow, returning MAX_INT or
MIN_INT in AC in the case of overflow, or the sum in AC otherwise. Here's
what Vince came up with so far:
CHKOVF, 0
TAD OVFA /GET A
TAD OVFB /ADD B
DCA OVFSUM /SAVE IT
TAD OVFA /A XOR B
AND OVFB
CMA IAC
TAD OVFA
TAD OVFB
SPA CLA /IF SIGNS DIFFER...
JMP NOPROB /WE'RE DONE
TAD OVFA /MIGHT BE OVERFLOW, A XOR SUM
AND OVFSUM
CMA IAC
TAD OVFA
TAD OVFSUM
SMA /DID WE OVERFLOW (DIFFERENT SIGNS)?
JMP NOPROB /NO, NO PROBLEM
CLA CLL CMA RAR /YES, AC=3777 (MAX INT)
DCA OVFSUM /SAVE IT
TAD OVFA /GET THE SIGN OF CORRECT RESULT
SPA CLA /SHOULD IT BE NEGATIVE?
ISZ OVFSUM /YES, 3777 -> 4000 (MIN INT)
NOPROB, CLA /GET CORRECTED SUM
TAD OVFSUM
JMP I CHKOVF /OUTTA HERE
OVFA, 0
OVFB, 0
OVFSUM, 0
This tests the signs of both numbers; if they differ, there's no chance of
overflow. If they're the same, it checks the signs of the augend with the
sum; if they differ, an overflow occurred, and MAX_INT or MIN_INT will be
returned depending on the sign of the augend.
We tried clever tricks previously, using SNL/SZL and SMA/SPA after shifting
the sign of the augend into the link and keeping the addend in the AC, but
found these to be longer.
Kyle
On Tue, 13 Sep 2016, Liam Proven wrote:
> Whereas my Mac mini has 3rd party RAM and both an SSD and an HD
> (upgrades from a Toshiba desktop-replacement notebook that the Mac
> replaced) on a 3rd party bracket, and I'm using a Dell 5-button mouse
> and an Apple Extended keyboard from '97 or so, on a 3rd-party ADB-USB
> adaptor. And a pair of mismatched 2nd hand 23" LCDs.
...
> And with the original '80s keyboard, it _feels_ (and sounds) like a
> proper (i.e. '80s) Mac when I'm typing on it. :-)
My Mac Mini has been treated to new modern keyboard purchased at
rediculous expense upon the recommendation of my long time friend
G.L.Nerenberg II. And it says underneath "WASD Model: V2 Type: Cherry MX
Green". It is gloriously noisy!
I have an aluminum Apple keyboard in the box this keyboard came out of,
those Apple chicklet keyboard are just plain horrible.
--
Richard Loken VE6BSV, Systems Programmer - VMS : "...underneath those
Athabasca University : tuques we wear, our
Athabasca, Alberta Canada : heads are naked!"
** rlloken at telus.net ** : - Arthur Black
Hi all,
I?m working on debugging an FP11-B floating point option in a PDP-11/45. I?ve just discovered that in the engineering drawings for this on bitsavers, sheets 1 and 2 of the FRL board prints are missing :-(
Does anybody have a complete set of FP11-B drawings? I can work around the missing sheets if I have to because sheet 1 is just the IC layout sheet and sheet 2 is probably quite similar to sheet 3, but it sure would be convenient to have the whole set?
cheers,
?-FritzM.
Agree. It's quite easy to telnet to a port to see if you get a response.
Do it a lot.
> Are ifconfig, netstat, traceroute, et al really insecure? (Maybe a case
> could be made for traceroute) These types of changes to the core of
> userland are epic dumb IMHO. Telnet is very useful for debugging, and
> certainly dropping telnetd is a good thing - which everyone has done.