Dennis,
It sounds like you are looking for an Ultrix 3.0 standalone boot tape. While
I found a number of people who claim to have a physical tape, with some
claiming to have imaged the tape, I was unable to find an image on-line. That
being said, it’s possible to use the Ultrix 2.0
On Wed, Apr 24, 2019 at 8:51 PM Al Kossow via cctalk
wrote:
>
>
>
> The keyboard controller is an 8049. Firmware not readable.
>
> It may actually be compatible with the 955 keyboard, which I was able to
> read.
> Key layout is the same, though the manuf is different
>
The 924 should be
OK, I have figured out how to modify TSGEN.MAC, use PUTR to make a disk
image, load it in SIMH, reassemble, relink, and *finally* send it to an RL02
pack via vtserver!
TIme-consuming but doable. I've been wrestling with this all day.
BUT - TSX+ 6.50 just will not run. At all.
Using RT-11SJ
The keyboard controller is an 8049. Firmware not readable.
It may actually be compatible with the 955 keyboard, which I was able to read.
Key layout is the same, though the manuf is different
On 04/24/2019 08:47 PM, Al Kossow via cctalk wrote:
>
> On 4/24/19 5:46 PM, allison via cctalk wrote:
>
>> The 8049 is readable just like the 8048 save for 2k device. I worked
>> for NEC back then and had access to intel parts too.
> is that true for "HC" parts or just NMOS?
>
>
All! The HC were
And even more bizarrely... it crawled its way up to the 7400K block, and now
it's going at normal speed again! 10MB should be done soon.
I have no idea what could be causing this major slowdown from 6.6-7.4 MB.
It's not the drive because two different ones do the same thing (and they
work
On 4/24/19 5:46 PM, allison via cctalk wrote:
> The 8049 is readable just like the 8048 save for 2k device. I worked
> for NEC back then and had access to intel parts too.
is that true for "HC" parts or just NMOS?
On 04/24/2019 07:55 PM, Guy Dunphy via cctalk wrote:
> At 08:14 AM 24/04/2019 -0700, you wrote:
>>
>> On 4/24/19 5:39 AM, Guy Dunphy wrote:
>>
>>> The keyboard controller is an 8049. Firmware not readable.
>> 8049s aren't protected. they are 2k versions of the 8048
>> and can be read as 8749s
> I
-Original Message-
But there is some kind of bug that always appears at the same point, in the
middle of the next 100K block after "6600K written".
The data transfer stops (no more head motion/ready light flicker on the
RL02), and the character that vtserver uses to indicate a write
But there is some kind of bug that always appears at the same point, in the
middle of the next 100K block after "6600K written".
The data transfer stops (no more head motion/ready light flicker on the
RL02), and the character that vtserver uses to indicate a write operation
just repeats endlessly
Thanks, I'll check that.
At 07:48 AM 24/04/2019 -0500, wrco...@wrcooke.net wrote:
>
>> On April 24, 2019 at 7:39 AM Guy Dunphy via cctalk
>> wrote:
>>
>
>> I haven't dumped the chargen chip yet, because I don't know what it is, and
>> suspect it's more complex than just a ROM.
>> 24 pin
At 08:14 AM 24/04/2019 -0700, you wrote:
>
>
>On 4/24/19 5:39 AM, Guy Dunphy wrote:
>
>> The keyboard controller is an 8049. Firmware not readable.
>
>8049s aren't protected. they are 2k versions of the 8048
>and can be read as 8749s
I did try reading it as an 8749. By 'not readable' I meant it
I sometimes use vtserver to download disk images to the RL02's on my
PDP-11/23+. Takes quite a while at 9600 baud, too :)
But there is some kind of bug that always appears at the same point, in the
middle of the next 100K block after "6600K written".
The data transfer stops (no more head
On Wed, 24 Apr 2019 at 05:08, Charles via cctalk wrote:
> Thanks... unfortunately I'm running 64-bit Windows and just discovered PUTR
> will only run on a 32-bit (or even older) machine.
32-bit code _should_ run on 64-bit Win7/8.x/10. 16-bit code won't.
Win7 has "XP Mode", which is a free
On 4/24/19 10:14 AM, Paul Koning via cctalk wrote:
On Apr 24, 2019, at 11:05 AM, Noel Chiappa via cctalk
wrote:
From: Glen Slick
when I wanted to assemble some code with the RT-11 assembler but wanted
to edit the source code elsewhere and then transfer the code into a
SIMH disk image.
> On Apr 24, 2019, at 11:05 AM, Noel Chiappa via cctalk
> wrote:
>
>> From: Glen Slick
>
>> when I wanted to assemble some code with the RT-11 assembler but wanted
>> to edit the source code elsewhere and then transfer the code into a
>> SIMH disk image.
>
> Someone should write the SIMH
On 4/24/19 5:39 AM, Guy Dunphy wrote:
> The keyboard controller is an 8049. Firmware not readable.
8049s aren't protected. they are 2k versions of the 8048
and can be read as 8749s
Anyone have a copy of the RK611 Technical Manual (EK-RK611-TM-001 is the
version that's attested)? It's not online.
(I have a copy in my fiche set, but my fiche reader died - no, it's not
the bulb, already changed that! :-)
Noel
At 05:14 AM 4/24/2019, David Griffith via cctalk wrote:
>When I first noticed that the binary wasn't stripped, I tried poking around
>with assorted disassemblers and decompilers hoping to get something resembling
>C code out of it.
And you found what?
- John
> On April 24, 2019 at 7:39 AM Guy Dunphy via cctalk
> wrote:
>
> I haven't dumped the chargen chip yet, because I don't know what it is, and
> suspect it's more complex than just a ROM.
> 24 pin character gen ROM/? at U10 is marked:
>
> VTi (logo)
> 350 RN 118
> 2333-5006
> 8000142
>
At 04:34 PM 23/04/2019 -0700, you wrote:
>
>
>On 4/23/19 3:35 PM, Guy Dunphy via cctalk wrote:
[my Televideo 924]
>
>I have maint manuals for the 925.
>
>Some photos of the boards and dumps of the keyboard firmware and controller
>would be nice to add to bitsavers, since I've not come across
My reply is at the bottom. Please put your reply there too.
On Wed, 24 Apr 2019, Ethan Dicks wrote:
On Tue, Apr 23, 2019 at 9:58 PM David Griffith via cctalk
wrote:
In one of the repositories of Infocom game source code recently uploaded
to Github, there's an executable that appears to have
22 matches
Mail list logo
