> The MSDOS Hard Drive partition utility on the DEC Rainbow gives you
> two partitions( E and F.)
> There's no choice, that's what you get. However neither E nor F are on
> the boot list.
> So the question is "How do I set the partitions to C and D and make C:
> bootable?"
On a Rainbow, drives C and D always refer to the third and fourth floppy
drives. Your hard drive is set up properly right now. To boot from the
hard drive, you'll need to choose 'W' for Winchester hard drive at the
boot menu. If you are using a Rainbow 100-A, this option is not present
in the boot menu, and you're out of luck as far as booting to the hard
disk is concerned (I beleive). If you have a 100-B or 100+ (which is just
a B anyway), The W option should be present on the main menu. SImply
select W and another menu may or may not appear allowing you to choose
which partition to boot from.
You can quickly tell if you have a 100 A or B by either:
1. Looking at the model number on the back of the unit near the power
plug (PC-100-A is a Rainbow 100 A, PC-100-B or -B2 is obviously a Rainbow
100 B)
2. Looking at the firmware version on the boot menu ( Version 4.XX or
less is a Rainbow 100 A, Version 5.XX or higher is a 100 B).
Hope this helps!
-Jeff
jba at sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Since I had a Kenbak I decided I wanted an assembler for it. It gets
pretty annoying writing code by hand... I spent a while researching and
found it would be a pretty big deal to write one from scratch. I found
"AS" and have written a target code file for the KENBAK. It is still in
beta, however so far it works perfectly. The only thing left to do is WARN
people when they do something stupid.
I designed the mnemonic set for maximum flexibility and readability. As
you can see my include file has the parameters in long hand. ; ) Its a
goal of mine to get these into schools. I think this assembly language
would be pretty easy for someone who has studied basic or C.
What do you think? Here is sample output from the assembler building a
program from the Kenbak Laboratory Exercises manual. Its the first one in
the book. (I threw in NOOP and HALT at the end for fun) I converted the
octal listing into opcodes, and then reassembled it. I get the same
results. ; ) I've e-mailed the author about including the Kenbak code
generator in the distribution and asked if he could add a command line
option for using octal in the program listing instead of HEX. ; ) If he
won't, I WILL!
Let me know what you guys think... Anyone here have a Kenbak? If not, and
you want one...I've got a few spots left. : ) http://www.kenbakkit.com
Before I include the program listing, here are all of the possible
instructions. This 132 IC TTL computer is purely amazing...
[ADD/SUB/LOAD/STORE] [Addressing Mode], [Register], [Address]
[OR/AND/LNEG] [Addressing Mode], [Register]
[JPD/JPI/JMD/JMI] [Register], [Condition], [Address]
SET [0/1], [Position], [Address]
SKIP [0/1], [Position], [Address]
BSHIFT [Direction], [Places], [Register]
ROTATE [Direction], [Places], [Register]
NOOP (no parameters)
HALT (no parameters)
macro assembler 1.42 Beta [Bld 55]
(i386-unknown-win32)
(C) 1992,2007 Alfred Arnold
68RS08-Generator (C) 2006 Andreas Bolsch
Mitsubishi M16C-Generator also (C) 1999 RMS
XILINX KCPSM(Picoblaze)-Generator (C) 2003 Andreas Wassatsch
TMS320C2x-Generator (C) 1994/96 Thomas Sailer
TMS320C5x-Generator (C) 1995/96 Thomas Sailer
KENBAK-1 TTL Computer Assembler (C) 2007 Grant Stockly
WARNING: KENBAK code generator still in beta
AS V1.42 Beta [Bld 55] - source file ./a/ken.asm - page 1 - 8/29/2007 0:00:48
assembling ./a/ken.asm
PASS 1
1/ 0 : page 0
2/ 0 : cpu KENBAK
3/ 0 : include kenbak.inc
22/ 0 : listing on
23/ 0 :
4/ 0 :
5/ 4 : ORG 004o ;First non-special address
6/ 4 :
7/ 4 : Loop:
8/ 4 : 03 01 ADD Constant, RegisterA, 1
9/ 6 : 1C 80 STORE Memory, RegisterA, Lamps
10/ 8 : E4 04 JPD Unconditional, Zero, Loop
11/ A :
12/ A : 00 HALT
13/ B : 80 NOOP
AS V1.42 Beta [Bld 55] - source file ./a/ken.asm - page 2 - 8/29/2007 0:00:48
symbol table (* = unused):
------------------------
*ARCHITECTURE : i386-unknown-win32 - | *BIGENDIAN : 0 - |
*BRANCHEXT : 0 - | *CASESENSITIVE : 0 - |
CONSTANT : 3 - | *CONSTPI
: 3.141592653589793 - |
*DATE : 8/29/2007 - | *FALSE : 0 - |
*FULLPMMU : 1 - | *HAS64 : 1 - |
*HASDSP : 0 - | *HASFPU : 0 - |
*HASPMMU : 0 - | *INDEXED : 6 - |
*INDIND : 7 - | *INDIRECT : 5 - |
*INEXTMODE : 0 - | *INLWORDMODE : 0 - |
*INMAXMODE : 0 - | *INSRCMODE : 0 - |
*INSUPMODE : 0 - | LAMPS : 80 - |
*LISTON : 1 - | LOOP : 4 C |
*MACEXP : 1 - | MEMORY : 4 - |
*MOMCPU : EBA - | *MOMCPUNAME : KENBAK - |
*NEGATIVE : 5 - | *NESTMAX : 100 - |
*NON_ZERO : 3 - | *PACKING : 0 - |
*PADDING : 1 - | *POSITIVE : 6 - |
*POSITIVE_NON_ZERO : 7 - | REGISTERA : 0 - |
*REGISTERB : 1 - | *REGISTERX : 2 - |
*RELAXED : 0 - | *TIME : 0:00:48 - |
*TRUE : 1 - | UNCONDITIONAL : 3 - |
*VERSION : 142F - | ZERO : 4 - |
44 symbols
37 unused symbols
AS V1.42 Beta [Bld 55] - source file ./a/ken.asm - page 3 - 8/29/2007 0:00:48
codepages:
----------
STANDARD (0 changed characters)
0.01 seconds assembly time
36 lines source file
1 pass
0 errors
0 warnings
>
>Subject: Re: INS4004D in Pro-Log M900 PROM Programmer
> From: "Ethan Dicks" <ethan.dicks at gmail.com>
> Date: Tue, 28 Aug 2007 14:16:18 -0500
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>On 8/27/07, dwight elvey <dkelvey at hotmail.com> wrote:
>> From what I've seen in the spec sheets, one would just use
>> a slightly modified 2716 socket of any machine. A few lines
>> of code should be enough. No special voltages, just special
>> sequences. All easily handled in software.
>
>My recollection is that the 2716 needs something like 21V or 26V on
>the programming pin. As for a modified socket, I have an old "Z-80
>Starter Kit" SBC that happens to have a built-in EPROM programmer on
>one of the three ROM sockets. There's a toggle switch to disconnect
>the programming voltage, but once enabled, you simply write to the
>address range of that EPROM socket, and after the data are presented
>to the ROM, the circuit wiggles the programming pin to write the
>EPROM.
It also requires the "write pulse" to be 50milliseconds long. Write
is accomplished by supplying VPP (12, 21 or 26V version dependent)
then playing the OE/ and CE/ pins.
Allison
>
>It would not be difficult, in principle, to add this feature to, say,
>one of the empty ROM sockets on a PET, especially if you had an
>external benchtop power supply injecting the programming voltage
>(rather than generating it inside the PET housing).
>
>-ethan
It seems that these Onyx 2 rack systems are pretty available. If I
wanted to max out the system configuration, what's the theoretical
max? I didn't even know they could gang 4 racks like the one I have.
As I understand it, they subdivide a rack into "bricks" and then
components (disk drives, graphics cards, etc.) plug into the brick.
I believe the bricks are identified by a single letter code. Does
anyone know of a reference for this sort of SGI stuff? I know SGI has
manuals online, but it helps to know the specific manual to use as a
starting point.
The racks have an integrated power supply, so maybe they identify the
amount of equipment per rack based on power consumption?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
Hi,
The 2716 requires the following signals/voltage for programming:-
Read Operation
/EP (Pin 18) => Logic 0
/G (Pin 20) => Logic 0
Vpp (Pin 23) => +5V DC
Program Operation
/EP (Pin 18) => Logic 0 to Logic 1 50mS (approx) pulse, per location to be
programmed
/G (Pin 20) => Logic 1
Vpp (Pin 23) => +25V DC
Verify Operation
/EP (Pin 18) => Logic 0
/G (Pin 20) => Logic 0
Vpp (Pin 23) => +25V DC or +5V DC
To program one, the sequence is...
1 - Raise Vpp to +25V DC
2 - /EP at Logic 0
3 - Raise /G to Logic 1
4 - Supply Address information
5 - Supply data information
6 - Provide a Logic 0 to Logic 1 45-55mS pulse on /EP
7 - Drop /G to Logic 0
8 - Read data to verify the contents
9 - Get next address location, and go back to step 3
Do this for the required locations you want to program/verfiy. When finished
burning/verifying the 2716, you can drop Vpp back to +5V DC for normal read
operations.
Seeyuzz
River
Hi,
I got two M900 programmers. One works, but the other one doesn't. I only
have the 2716 module for them, which is good, but I do not know where you
can get other personality modules for them.
I use a Microprofessor that has the EPROM Burner expansion for burning my
EPROMS. However, I am currently designing my own EPROM burner so I can do
2708 and 8755A chips.
I was going to make it all fancy-pants where it would do all the right
programming voltages and address translations (for different address pin
locations on different chips) etc, but I think it would be easier to make my
own "personality modules" which will ease the hardware design.
The chips I need/want to program are 2704, 2708, 2516, 2716, 2732, 2732A,
2532, 2564, 2764, 27128, 27256, 2816 and 8755A. I have checked out the
capabilities and prices of current EPROM burners, but they are far too
expensive for what I want, do much more than I need, and they usually do not
do the 2704/8 or 8755A without an expensive personality module.
So, in light of my enjoyment in building old computers, I'm building a
complete system just for the fun of it and to burn EPROMs for me. As the
2708 uses a few voltages, I decided to use a CPU that also requires a few
voltages - the 8080 chip. So, it will be an 8080 system, running 40K of RAM,
8-16K of ROM, a pair of 8255 for EPROM signals (plus extra logic etc as
required), an 8251 for comms, and I may even hook up an LCD so I can use it
without requiring a terminal.
Of course, I could get side-tracked and just use my expanded AIM65 system -
as it has all the monitor/debug software, enough IO ports and the built in
display...... ;)
I could always mod some of my older boards that use 2708 chips to use 2716
chips, but I like the historical accuracy of 2708 devices - and I've got
quite a few in stock.
Seeyuzz
River
>While I cannot help you with the catweasel northstar project, I do know
>that at least the linux cwtool toolkit is missing a number of disk
>definitions which are very useful and common.
>It does NOT normally support:
>SSDD 5.25 8 sectors/track 160k
>SSDD 5.25 9 sectors/track 180k
>DSDD 5.25 8 sectors/track 320k
>SSHD 3.5 18 sectors/track 720k <- very unusual format
>SSHD 5.25 15 sectors/track 600k
[snip]
Thanks Jonathan,
Those definitions you mentioned are all soft sector MFM encoded formats, I
believe. I suspect cw2dmk will already decode those since they have the
necessary sync marks, etc. Have you tried cw2dmk? It can extract dmk
images from any FM, MFM, or RX02 encoded soft sector disk.
It is good thing you are doing to add capability to the Linux cw driver for
more formats. Thanks for doing that. The more Catweasel support of any
kind, the better it is for everyone.
Unfortunately, writing software for the Catweasel to make images of
NorthStar hard sector format is an entirely different creature altogether.
The NorthStar controller has its own unique sync sequence which makes the
disks incapable of being read by NEC 765 or derivative FDCs. As a result,
it requires entirely custom software to decode. Thank you to those
individuals who have been of invaluable help to me in getting this far with
the project (you know who you are!).
Here is a bit of technical background on the problem from the NorthStar
floppy disk controller. The NorthStar double density sync sequence is 32
$00's followed by $FB, another $FB, 512 bytes of data, and then a one byte
checksum. The single density sync is similar. The NorthStar timing
sequences is based on the ten sector holes and one index hole. I found the
index hole because it is between two sector holes. The sequence is
something like this:
Gap 1 24 mS
Gap 2 24 mS
Gap 3 12 mS <- index hole passed by
Gap 4 12 mS <- start of sector 0
Gap 5 24 mS
.
.
.
Gap 11 24 mS
My prototype code is currently two parts: the first is a modified utility to
make a raw image, and the second is another utility which extracts the data
>from the bit sequence. I can make images with my code but it is only in the
"proof of concept" stage. It is way too crude for a general release and
that is why I am asking for some volunteers to help (re)write it and test it
to bring the code up to some reasonable level of decency before any release.
Here is a sample dump from the imaging tool of a disk. It is the NorthStar
DOS 5.0 Double Density boot disk. It is the one which comes with the Dave
Dunfield NorthStar Horizon simulator and tool set. I created an actual boot
floppy on my Horizon and used my Catweasel station to create the image.
http://www.geocities.com/lynchaj/out3.zip
>OP: Sending the original request message 3 times was unnecessary.
I entirely agree and I apologize for sending multiple posts. Believe me, it
was not my plan for three postings. I first posted Thursday last week but
my messages did not show up in the archive until today for some unknown
reason. I read the list by reading the archive of messages and I thought my
messages were going into the bit bucket. I suspect the cctech mailing list
was having some sort of problem. Sorry for the repeats.
Thanks!
Andrew Lynch
Hello, everyone. My name is Joe, I am 17 years old, and live in central NJ.
I would like to figure out how to build a retro-type computer, either from
plans or from a kit. I am currently considering the Micro-KIM, as well as
trying to build a mark-8. Not sure what I want to do. If anyone can help me
along with this, I would be very appreciative.
Thanks
Joe
