On Aug 9 2004, 22:28, quapla(a)xs4all.nl wrote:
> You should have told me earlier. I have a controller here which has
> those 2 roms on them. Mind you, the other 3 I have all have 23-248 &
> 23-249 on them.
Ah. That's a shame -- I could have copied them while you were here!
> BTW, what's so special about them (other than being having a higher
> firmware revision)?
Later versions of some OSs don't like some of the bugs in the earlier
ROMs, when you have a full complement of memory, so I want to upgrade
the TQK50 in my MicroVAX.
--
Pete Peter Turnbull
Network Manager
University of York
On Aug 9 2004, 14:35, trash3(a)splab.cas.neu.edu wrote:
> Pete,
> I have a few tqk50 controllers (at least they are qbus and run
tk50
> drives). I'll have to look up the numbers but I'm pretty sure they
say
> tqk50 on them. I am in the Boston, MA area. If I can fire up my
eprom
> programmer and they are of the 27xxx ilk, I can read them. If not,
I'll
> ship you a board, since I am a little closer.
Shipping would still be transatlantic, but the ROMs should be 27128s so
they should be easy to read. Intel HEX or a binary image are
preferred, but I can also handle S-record files if necessary.
Thank you!
--
Pete Peter Turnbull
Network Manager
University of York
We have used stabilant 22 for about 14 years now, mostly on 1/4 inch phone
jacks and plugs that get oxidized from infrequent use. Saw that trick in
a Byte magazine way back. Expensive but it works for us.
Joe Heck
Vintage Computer Festival <vcf(a)siconic.com> wrote:
> First of all, a pure DOS computer is a VERY handy tool to have around.
MS-DOS is really a program loader, which is actually extremely important
since PCs do not come with monitor program.
SUNs come with the Forth boot ROM which is arguably far more useful than
MSDOS, but not very popular. For this reason you won't see anything like
MSDOS for SUNs.
I have a VMware VM running MSDOS with network support and I use this
to compile TurboC programs (for some reason the tcc linker does not run
in a Windows 2000, or later DOS box, it does run on MS-DOS-based systems
like Windows 95/98/ME).
I also find the lack of any amount of resource management by MSDOS to be
invaluable for writing programs that explore the behaviour of hardware
systems (e.g. HP-IB devices).
Of course, I wouldn't use such a system for any real work :-) I am amazed
that people actually did so.
**vp
Hi Gang,
I'm looking for Commodore PET schematics, and any helpful info on troubleshooting
a PET.
The machine in question is a SuperPET 9000. This is basically a PET 4032 with an
extra pair of boards added that allows a 6809 processor.
I have two machines, one is fully functional, and one does not run on the "6502"
setting (works on the 6809 setting). I also have a working 4032 which has an identical
6502 board to the SuperPET.
I have stripped both SuperPET's down to the 6502 board only (ie: same as a 4032),
the working one continues to work, and the dead one continues to not work.
I suspect ROM's, as I have seen a lot of PET ROM's go bad ... unfortunately all
three machines are NOT socketed, so simple swap tests are "unfriendly".
All three machines when powered on, play a little "bee-dle-bee-dle-bee" in the
Pizo speaker, and clear the screen - the two working units then proceed to
display "Commodore BASIC version 4.0, .... READY", while the dead one does
not. Entering the command "print chr$(7)" on the dead one does NOT result in
a beep, indicating that BASIC is not running (it does beep on the other two).
I'm assuming that it does clear the screen, because if powered up without the
CPU plugged in it displays a screen full of "garbage" - ie: the video display
is "hard" and active all the time - (the CPU is one of only a few chips in
a socket due to it's being "moved" to the expansion board with a ribbon cable
in the full configuration).
Anyone have experience with these PET's? Anyone have schematics?
Suggestions, etc. welcome.
Regards,
Dave
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Vintage computing equipment collector.
http://www.parse.com/~ddunfield/museum/index.html
On Aug 9 2004, 7:46, Ed Kelleher wrote:
> At 07:23 AM 8/9/2004, Pete Turnbull wrote:
> >I'm looking for ROMs (or ROM images would be better) for a TQK50
> >controller. The ROMs I want are 23-330E5 and 23-331E5. Can anyone
> >help?
> Have 2 TQK50's K3 Rev with those ROM's on them I'm not using.
> Haven't fiddled with the EPROM machine for years, so no easy way to
>get the images.
> But I'll send you a board if nothing better turns up for you.
If no-one else offers, that would be great. Thanks! Is there anyone
out there who could read the (EP)ROMs to save Ed sending them across
the Atlantic to me?
--
Pete Peter Turnbull
Network Manager
University of York
ard(a)p850ug1.demon.co.uk (Tony Duell) wrote:
> Talking of HP using 555 timers, they used one to drive the power-on light
> in the HP86 (and I assuem the HP97). [...]
(nitpicking here, you are talking about the 87)
> So the LED is dark if the machine is off, on steadily if the machine is
> on and no error (555 is held reset, so the output is low all the time),
> and blinks (controlled by the 555) if there's an error.
Actually the LED blinks when the machine is busy (e.g. running a program).
This is very neat as with the HP85 you sometimes do not know whether the
program has finished or is still running.
**vp
