---------Original message:
Date: Sat, 24 Dec 2011 08:52:32 +0100
From: Jochen Kunz <jkunz at unixag-kl.fh-kl.de>
On Fri, 23 Dec 2011 01:07:46 -0200
"Alexandre Souza - Listas" <pu1bzz.listas at gmail.com> wrote:
>> AFAIK, the 712 uses common 486 (simm-72) memory
> No. The HP9000/7xx SIMMs look, smell, taste like PeeCee RAM, but they are
> different. You need the very special, propriatary HP9000 SIMMs for that
> machine.
Sometimes you just have to cut a trace or two and/or add a jumper or two;
for example here's how to convert a standard SIMM for use in an HP LJ:
www.keycruncher.com/blog/2003/12/14/making-standard-simm-s-work-memory-upgr…
I did the same sort of mod to use standard SIMMs to expand memory in my
Toshiba T3100e.
Neal wrote to me:
>> I was a developer way back when and still have my 5120 & Sys 23.
>>
>> I'd like to find these relics a nice home instead of the landfill.
>> They were painted funky colors (they look great - not the ugly grey)
>> and were used back to back with a glass top for a coffee table.
>>
>> Neal Lebar
>> nlebar at innovatefocus.com
>>
I have an Amiga keyboard (pcb says A3000) where the four
keys 1, q, a and z doesn't work. The rest of the keyboard
functions well.
This happened after a longer period where I didn't use the keyboard.
Does anybody have any ideas of things to check out to try
to get this working again?
Regards Eivind
Hey folks. Is there anyone here that'd be willing to pick up a DEC
LA180 printer for me in Cambridge, MA, and sit on it for me for a little
while?
-Dave
--
Dave McGuire
New Kensington, PA
[Resend with corrected Subject:]
Liam Proven <lproven at gmail.com> (in reply to a message from Fred Cisin) wrote:
>Steady on, old chap. Pop a few more dried frog pills and calm down.
Hah! Then I probably need some too ;-) Are those already on sale in the drugstore in Treacle Mine Road or do you still have to get them from the pharmaceutical institute of the Unseen University?
(Another appreciator of TP humor outs himself...)
>Joking aside, I have considered it. I honestly think a decent
>Win9x/NT-style DOS shell for Linux would help its adoption by Windows
> techies moving across.
This is somewhat akin to the ideas I've been pushing around for some years now. I'm thinking that porting a familiar OS to some 'obscure' (to the average DOS/Wintel user) vintage architecture could serve to keep lots of these machines in active service with the general public. (But then there wouldn't be so many around for us to hoard - so that's perhaps why it isn't done...)
Of course there would be a need for software portability as well, so you might want to include some sort of cross assembler or how-you'd-call-it in the package that, llke, takes a win32-x86 executable and turns out a win32-sparc (or whatever) executable. No idea if that's even remotely possible without excessive manual intervention...
> The main snag being that C21 Windows techies
>barely use the CLI at all and are not really skilled in it, whereas
>1990s or even 1980s MS techies probably know Unix already.
So don't contend yourself with just the CLI - you don't have to. There is an ongoing effort to create a FOSS Windows 2k/XP workalike named ReactOS. Currently that is targeted at x86 only but I'm holding high hopes that its code base will inspire such portery. "Windows" for all those systems that pack the horsepower to run it, including but not limited to those that once were NT's target platforms - Alpha, RS/6k (Siemens RM400), PPC (PowerStack) and Clipper (Intergraph) springing to mind immediately.
>But I'd love a DOS shell for Linux, yes. If I had the skills, I'd try to do it. Partly for the convenience, partly for fun, partly for the sheer joy
>of outraging traditional old-time Unix-heads. :?)
Well put. Any of these on ist own would make enough of a reason methinks ;-) Add the conservation and ongoing practical utility of vintage hardware to that and let's see where it goes.
Arno Kletzander
...sent from my HTC Magician PDA
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zur?ck-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
Liam Proven <lproven at gmail.com> (in reply to a message from Fred Cisin) wrote:
>Steady on, old chap. Pop a few more dried frog pills and calm down.
Hah! Then I probably need some too ;-) Are those already on sale in the drugstore in Treacle Mine Road or do you still have to get them from the pharmaceutical institute of the Unseen University?
(Another appreciator of TP humor outs himself...)
>Joking aside, I have considered it. I honestly think a decent
>Win9x/NT-style DOS shell for Linux would help its adoption by Windows
> techies moving across.
This is somewhat akin to the ideas I've been pushing around for some years now. I'm thinking that porting a familiar OS to some 'obscure' (to the average DOS/Wintel user) vintage architecture could serve to keep lots of these machines in active service with the general public. (But then there wouldn't be so many around for us to hoard - so that's perhaps why it isn't done...)
Of course there would be a need for software portability as well, so you might want to include some sort of cross assembler or how-you'd-call-it in the package that, llke, takes a win32-x86 executable and turns out a win32-sparc (or whatever) executable. No idea if that's even remotely possible without excessive manual intervention...
> The main snag being that C21 Windows techies
>barely use the CLI at all and are not really skilled in it, whereas
>1990s or even 1980s MS techies probably know Unix already.
So don't contend yourself with just the CLI - you don't have to. There is an ongoing effort to create a FOSS Windows 2k/XP workalike named ReactOS. Currently that is targeted at x86 only but I'm holding high hopes that its code base will inspire such portery. "Windows" for all those systems that pack the horsepower to run it, including but not limited to those that once were NT's target platforms - Alpha, RS/6k (Siemens RM400), PPC (PowerStack) and Clipper (Intergraph) springing to mind immediately.
>But I'd love a DOS shell for Linux, yes. If I had the skills, I'd try to do it. Partly for the convenience, partly for fun, partly for the sheer joy
>of outraging traditional old-time Unix-heads. :?)
Well put. Any of these on ist own would make enough of a reason methinks ;-) Add the conservation and ongoing practical utility of vintage hardware to that and let's see where it goes.
Arno Kletzander
...sent from my HTC Magician PDA
I am in need of a Dell 316LT laptop. This would be from the late 1980s.
Ideally it works. If you've got one and you want to make a deal, please
contact me directly.
Thanks!
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
> Date: Tue, 20 Dec 2011 14:53:12 -0500
> From: "B. Degnan" <billdeg at degnanco.com>
> To: <cctech at classiccmp.org>
> Subject: Re: Visual 1050 hard drive setup
> > On 12/19/2011 05:30 PM, Damien Cymbal wrote:
> > > Does anybody have a Visual 1050 with hard drive setup? I am looking
> > > for any doc/pointers on how to get a hard drive configured under
> > > CP/M for this system.
> > >
> > I do have two of them with HD, haven't powered it for a little while so
> > memory is fuzzy.
> >
> > As I remember it used a different copy of the bios (boot disk) to configure
> > as the bios had to be aware of the hard drive. I can look at docs but
> > powering it up would take weeks to get to as other projects are in the
> > forefront.
> >
>
> That's correct. There is a special disk to set up the hard drive. I think you
> have to have this disk in drive A in order to read the hard drive, I don't think
> one can simply boot a 1050 to harddrive. I plan to work on this system over
> the next few months, I will document the process on my site when I do. I
> also am knee-deep in projects at the moment.
> Bill
Thanks for the initial responses Allison and Bill.
Here's a summary of what I have been able to cull together so far:
(1) The Z80 BOOT PROM code (version 1.2 at least, which is the source listing
I have) appears to probe the Winchester, for boot e.g.
- try to read Winchester
- check result
- if error, try floppy
- if OK, check Winchester label
- if bad label, try floppy
- if good label load system and boot??? (this part is unclear to me)
(2) Not all of the v1050 CP/M BIOS versions appear to support the Winchester.
Versions up to 1.1 do not appear to contain the WINCH.ASM module which I
am assuming is required for support. I do not have access to version 1.2, but
I see this module showing up starting in version 1.3.
I would assume that with the 1.2 BOOT PROM and the 1.4 CP/M BIOS I could
support the Winchester (barring any bugginess - Bill I believe you have v2.0
of the CP/M BIOS and not sure on the BOOT PROM).
What isn't clear to me at this point is how to install CP/M onto the Winchester
and get the label setup so that the PROM would boot directly from the hard drive.
Maybe someone has a spare pair of mounting rails for a DEC RK05 drive, so
that I can finally mount it into my H950 rack?
Offers from all over the world accepted :) (I'm located in
Austria/Europe)
- Klaus
is anyone knowledgeable enough of their product line to give me (us) a rundown of these models, and characteristics (roughly) since their inception (1989 AFAIK).
I'm in the market for one, probably an older model, any condition, but not too shabby w/regards to sampling rate (let's say starting at 100mhz, they may not have gone any lower anyway).
> From: Brian Wheeler <bdwheele at indiana.edu>
> Subject: Re: Christmas cleanup! [Updated]
> To: cctalk at classiccmp.org
> Date: Wednesday, November 30, 2011, 8:46 AM
> I've updated the list below, and I've
> got a question for everyone.<snip>> > * DECserver 200/MC ($25, will ship)
> > 8 db25 portsDoes the DECserver 200/MC support DDCMP for system interconnects? Im reasonably new to the DECnet Phase IV protocol, and was looking to do some learning. If so, I'm interested.Kevin
From: Sean Conner
Sent: Wednesday, December 14, 2011 11:16 AM
> It was thus said that the Great Jochen Kunz once stated:
>> On Wed, 14 Dec 2011 00:48:15 +0000
>> Liam Proven <lproven at gmail.com>> wrote:
>>> Ditto, and a decent security measure too.
>> It would be acceptable as a security measure to restrict root login to
>> the local text console. This prevents "missuse" of the root account but
>> makes the system accessible in the event of a failure. If e.g. NIS
>> breaks you can't get into a Ubuntu machine to fix the problem. All you
>> can do in that situation is to hit the reset button and boot single
>> user. But that is an other story...
> GenericUbuntuNonRootUserPrompt% sudo vi
> (while in vi)
> :shell
> Have fun.
> -spc (Has had to do that a few times on fresh Ubuntu installs)
That's an awful lot of schratzing around to accomplish what a simple
GUNRUP% sudo /bin/bash
will do for you. (I use this frequently on my Snow Leopard system.)
Rich Alderson
Vintage Computing Sr. Server Engineer
Vulcan, Inc.
505 5th Avenue S, Suite 900
Seattle, WA 98104
mailto:RichA at vulcan.com
mailto:RichA at LivingComputerMuseum.orghttp://www.LivingComputerMuseum.org/
Hi Brian.
I just got on the list and I'm working backwards through the archives.
Couldn't reply on one of the existing ones. You did update the list,
so I'm guessing the vt220 and the 8" floppies actually are already
gone?
--
~ UNIX is basically a simple operating system,
? ? ? ? ? ?but you have to be a genius to understand its simplicity. ~ dmr
>
> On 12/19/2011 05:30 PM, Damien Cymbal wrote:
> > Does anybody have a Visual 1050 with hard drive setup? I am looking
for any doc/pointers on how to get a hard drive configured under CP/M for
this system.
> >
> > Thanks.
> >
> >
> >
> I do have two of them with HD, haven't powered it for a little while so
> memory is fuzzy.
>
> As I remember it used a different copy of the bios (boot disk) to
> configure as the bios had to be aware of the hard drive.
> I can look at docs but powering it up would take weeks to get to as
> other projects are in the forefront.
>
>
That's correct. There is a special disk to set up the hard drive. I
think you have to have this disk in drive A in order to read the hard
drive, I don't think one can simply boot a 1050 to harddrive. I plan to
work on this system over the next few months, I will document the process
on my site when I do. I also am knee-deep in projects at the moment.
Bill
If anyone bought any of those rl02 or other dec or classic disk packs
and media from ebay, please PLEASE read the contents out before
overwriting them!
I recently found a bunch of lost unix v5-era source code on erased space
on an image of a disk pack image from dennis ritchie, archived
unknowingly at tuhs, so who knows what other gems may be on those disks
in erased space?
dump them with dd, not with dump, since dump ignores or zeroes out blank
space. Tar obviously ignores blank space as well.
--
Jonathan Gevaryahu
jzg22 at drexel.edu
Hi,
I'm trying to re-create the source files for the Z8000 UNIX I have
on my Z8000 system (it is a S8000+ZEUS clone).
Easy programs like sync.c where easy. But when argc/argv is involved,
I'm not able to generate 1:1 matching binary code.
I'm working on /etc/unlink for now.
I tried the following C file:
char whatstr[] = "@[$]unlink.c 2.1 07/23/82 21:19:30 - 87wega3.2";
main(argc, argv)
int argc;
char **argv;
{
if(argc!=2) {
write(2, "Usage: /etc/unlink name\n", 24);
exit(1);
}
unlink(argv[1]);
exit(0);
}
The original ASM code for the beginning of main() until the argc
check is:
0042 abf3 dec r15,#4
0044 5df60000 ldl %0000(r15),rr6
0048 0b070002 cp r7,#%0002
The ASM code my C file generates is:
0042 abf3 dec r15,#4
0044 1df6 ldl @r15,rr6
0046 0b070002 cp r7,#%0002
keep in mine, that r15 is considered as the "stack pointer".
I wonder how to get the ldl from the original binary.
I also tried to declare argv with "char *argv[]" which
resulted in the same code. Forcing the compiler to store
argv into a register by using the "register" keyword results
in completly different code:
(sp = stack pointer = r15)
#17 adb unlink
ADB: P8000 1.6
? 0x0042/i
%0042: dec sp,#6
?
%0044: ld %0004(sp),r14
?
%0048: ld %0002(sp),r7
?
%004c: ld r14,r6
?
%004e: cp r7,#%0002
? $q
#18
Maybe the C compiler used to compile /etc/unlink differs from
the C compiler shipped with the system (maybe an older version)
but I don't want this to be true for now ;)
Anyone with deeper ASM and C knowledge than me sees what could
be done here?
Before someone asks - yes I'm sure the source file was in C
and not ASM based on the whatstr. Symboltable of the original
/etc/unlink is empty as well (striped binary).
Regards, Oliver