I am not sure if anyone is interested, but I've scanned the manual
for the Trend
HSR500 and HSR500P optical paper tape readers. If I've got the
permissions right,
then you can get it from my google drive on :
https://drive.google.com/open?id=0B5uNCTLB4VsqRU9TWDIzWnZYaU0
It's a large file, I don't think the scanner software has heard of
compression!. If anyone
can make it a more reasonable size, feel free...
This is a proper manual with schematics, parts lists, adjustment info, etc.
I've also scanned the circuit diagrams for the Trend Paper Tape Station, here
https://drive.google.com/open?id=0B5uNCTLB4VsqemRFMnVNb0l5WU0
The Paper Tape Station is a rack unit containing an HSR500 reader, power supply,
GNT34 punch and a driver card for the punch. Those diagrams are for
the punch driver
and power supply, you need the HSR500 manual as well.
Let me know if it all works...
-tony
Hi folks,
I'm at the point of troubleshooting this 8085 board where I need to test all
the RAM.
The code loops at an IN looking for....something. Based on other assembly
programs I've looked at the code is very similar to eg a disk controller
looking for a READY signal from a drive. Trouble is I have no idea what's
expected to be at I/O port 0xE3. If it was one of the peripheral chips I'd
expect a chip select line to go low. The 74LS139 that does chip select is OK
- I've tested it off-board and all traces going to it buzz out OK.
The code uses upper RAM as a scratch pad so what I'd like to do is replace
the $0000 ROM with an EPROM containing RAM test code. I've found incomplete
examples that need to be tailored so before I go reinventing the wheel has
anyone got a working example I can use? Warnings of things I should and
shouldn't do?
RAM is at $8000-$FFFF, and at least some of it is ok since the stack pointer
is up at 0xF0B3 and I can trace the code by watching which addresses it's
reading.
Cheers!
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
I am working on the disassembly and commenting of the 98228A disk ROM for the 9825T, and my disassembler flagged two instructions as invalid. They are used inside a routine that copies blocks of words from various banks of the ROM into low RAM. The first, bit pattern 070113, is used immediately after a dir (disable interrupt) instruction. The second, bit pattern 070117, is used immediately before an eir (enable interrupt) instruction. The ?invalid? instructions do not match any instructions described in the 9825A patent, nor are present in the 9835 or 9845 assemblers instruction descriptions. From the surrounding code, it doesn?t appear that these instructions reference any of the user visible CPU registers, but are used in some way that enhances the effect of dir/eir and ensures the block copy is not interfered with.
Anyone have any ideas? Possibly a DMA request ignore/resume pair?
Hey all,
Is anyone out there familiar with disassembly of the Data General DG One
portable? I have one of the EL models - it looks so cool! - and the hard
drive is stuck. I want pull it out and repair it, but I've reached an
impasse. I have the machine disassembled and the HD case is accessible, but
there is no obvious way to remove it. I don't like to just force things,
for obvious reasons. Thanks to anyone with some advice. -- Ian
--
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School <http://ischool.uw.edu>
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens
Archivist, Voices From the Rwanda Tribunal <http://tribunalvoices.org>
Value Sensitive Design Research Lab <http://vsdesign.org>
University of Washington
There is an old Vulcan saying: "Only Nixon could go to China."
Friends,
tu58fs 1.1 now supports oversized TU58 tape images, with capacity up to
32MB instead of 256KB.
This was easy to made for XXDP. Under RT-11 the DD.SYS driver must be
patched and reinstalled, tu58fs now handles this
automatically.
The GITHUB release at https://github.com/j-hoppe/tu58fs/releases
contains 2 new demos:
"demo_xxdp_oversize" packs the whole XXDP25 RL02 disk content onto an
emulated tu58
"demo_rt11_oversize" boots a full RT-11 installation from TU58, and
mounts a 2nd tape full of games.
Docs at http://retrocmp.com/tools/tu58fs were updated.
And I feel pretty empty now ... hope you love it!
Joerg
I know it's a "newer" PC compatible machine, but I was wondering if
anyone had a 20MB PC110 Palmtop and could tell me (or send me pics) of
the 16MB RAM upgrade. I have a non working unit here I can liberate the
4MB module from, and I believe I can replace the RAM ICs with larger ones.
The DRAMs on the board are HM51W16160ATT7, which are 70nS FP DRAM
1Mbx16 I assume there are similar 4Mbx16 DRAMs I could solder in
(A0-A11 Row/Col)
Jim
--
Jim Brain
brain at jbrain.comwww.jbrain.com
Hi,
I recently acquired an old Sun3 with a Fujitsu Eagle disk. This disk has
SunOS 3.5 on it. Parts of the installation were missing, though. I wanted
to build a new kernel with SCSI support and extracted the sys stuff
>from a 3.5EXPORT release tape. My machine however runs plain 3.5.
I can build a new kernel, but some things won?t worked like allowing
logins when a password is set.
Is there anyone out there who could provide me with a tar of /usr/sys
>from a complete working SunOS 3.5 running on sun3?
As a second question: The SunOS boot disk is a Fujitsu Eagle that
often reports errors. I have a second Eagle that I might use as a backup,
but I would have to reformat the second disks. How can I do that with
SunOS 3.5? There is no ?format? command apparently.
thanks,
Dennis
--
Don't suffer from insanity...
Enjoy every minute of it.
> From: Paul Koning
>> When did V7 come out, BTW?
> The files on the SYSGEN tape have a timestamp of 26-Sep-79, so "Fall
> 1979" sounds right.
Ow. I was looking for something a lot earlier than that. I used RSTS-11 in
the '72-'74 timeframe, so it's a version from that era I'd like to have. Any
idea what version that would be - and if it's still extant?
> I've used the V4A kit (DECtapes) to build that ... (There's a V4A
> sysgen manual on Bitsavers too ...)
When was that one?
>> It would be really nice to have sources - are they gone forever?
> Some still exist. I know someone who has a RSTS source kit, not sure
> which version. I have pieces of source.
OK, better than nothing.
> A complication with all of this is the question of licensing. There's a
> hobbyist license for RSTS to build and run it, but whether that carries
> over to making sources available is an interesting question. I'm not
> sure who to ask these days, either.
Hmm. I guess technically HP owns it now?
Noel
> > > Apple is slightly different -- the licence for Mac OS X stipulates
> > > that you're only allowed to run it on Apple-branded hardware. This is
> > > somewhere between rare and unique, though, and it has recently been
> > > relaxed slightly to permit use of hypervisors.
> >
> > EULAs have the same value as toilet paper and should be used for the same
> > purpose.
> >
> > Legally, they can and have been enforced. So their value is not nil
> > when it comes to screwing up someone.
I was always under the impression that EULAs existed, at this point, solely to scare corporate/commercial users into license compliance in order to avoid lengthy and draining court expenses, since they've been shown to be entirely unenforceable on individuals since the 90s. That's why Adobe stopped trying to prevent piracy of Photoshop on a single-user basis long ago, as an example. License compliance is irrelevant for individual users and particularly so for long obsolete software, i.e. anything that might reasonably be emulated. Even emulating a more recent video game system such as the Wii would be impossible to prevent given that the courts have decided that it is acceptable to create backups of software that you own and the original creator cannot prevent you from using that backup on a different platform than originally intended (recent example being ripping a CD you own and listening to it on an mp3 player, or more distant example, creating mixtapes for your personal use).
Not that it would prevent you from having to deal with a court case, but in virtually every case I'm aware of over the last decade or so it's usually just been a cease and desist letter to show the company still intends to maintain copyright, but actually taking someone to court for emulation would be catastrophic for any corporation's public image and virtually guaranteed to be thrown out.