<div dir="ltr"><span style="font-size:12.8px">"Are the other LUN file sizes off by the same 20,480 amount?"</span><br><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Bruce, that is an excellent question! I'm going to go through them and figure that out. </span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 20, 2015 at 1:52 AM, Bruce Ray <span dir="ltr"><<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">G'day AJ -<br>
<br>
The cylinder/head/sector information was determined by monitoring the tape-to-disk LUN backup operation disk reads - these were the actual cyls/hds/sects actually written for the corresponding LUN backups.<br>
<br>
I just did the following quick (hopefully correct) calculation:<br>
<br>
Each cylinder has 81,920 bytes (5 heads * 32 sectors * 512 bytes = 81,920 bytes/cylinder), and LUN0 has 16 cylinders: 16 cylinders * 81,920 bytes/cylinder = 1,310,720.<br>
<br>
Are the other LUN file sizes off by the same 20,480 amount?<br>
<br>
<br>
LUN CYL HD SEC<br>
---- --- -- ---<br>
LUN 0: 0, 0, 0 disk start address<br>
15, 4, 31 disk end address<br>
<br>
LUN 1: 15, 0, 0<br>
111, 4, 31<br>
<br>
LUN 2: 112, 0, 0<br>
223, 4, 31<br>
<br>
LUN3: 224, 0, 0<br>
335, 4, 31<br>
<br>
LUN4: 336, 0, 0<br>
441, 4, 31<br>
<br>
<br>
On 11/19/2015 11:48 PM, Microtech Dart wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bruce, I am curious about our calculations on LU0.<br>
<br>
According to your calculations: 'the LUN byte sizes can be calculated<br>
from the previously-provided LUN "partition"'<br>
<br>
LUN 0: 1,310,720<br>
<br>
And then when I measure all the bytes in the blocks that make up the<br>
second file on the backup tape (marked LU0, pos1; LU1, pos2; LU2, pos3),<br>
where that 2nd file must be LU0, because the first file is the bootable<br>
Minicom utility, then I count:<br>
<br>
1,331,200 bytes.<br>
<br>
This is actually 20480 bytes larger than you calculate the LU0 partition<br>
to be, or 5 blocks of 4096 bytes.<br>
<br>
This is SO close, yet it is off by that precise amount. Can you think<br>
of any reason why this might be the case?<br>
<br>
I ask, because I want to be sure that I am reconstructing the file from<br>
the blocks correctly.<br>
<br>
<br>
<br>
<br>
On Wed, Nov 18, 2015 at 2:55 PM, Bruce Ray <<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>>> wrote:<br>
<br>
G'day AJ -<br>
<br>
Creating a separate disk file that contains the contents of one of<br>
the tape files is okay. We can figuratively 'stitch" the files<br>
together into a format compatible with SimH by using some of our own<br>
utilities.<br>
<br>
Since the DiskUtility is transfers data on a block-for-block basis,<br>
all tape records must be recognized even if the record contains<br>
errors. Otherwise, the required relative position between tape and<br>
disk "records" will become lost. Error records can be indicated a<br>
variety of ways, so<br>
<br>
According to a quick calculation, the LUN byte sizes can be<br>
calculated from the previously-provided LUN "partition" info as:<br>
<br>
LUN 0: 1,310,720<br>
LUN 1: 7,864,320<br>
LUN 2: 9,175,040<br>
LUN 3: 9,175,040<br>
LUN 4: 8,683,520<br>
<br>
LUN 0, 1 and 2 can fit on boot tape according to DiscUtility hints,<br>
LUN 3 and 4 fit on separate (2nd) backup tape.<br>
<br>
<br>
Bruce<br>
<br>
<br>
On 11/18/2015 10:40 AM, Microtech Dart wrote:<br>
<br>
"What other file(s) am I missing?" I haven't sent the other 3<br>
LU files<br>
on the tape yet. Sorry, I should have made that more clear.<br>
Also, I<br>
didn't show the filemarks I was speaking of, that is where I<br>
ended one<br>
file and started the next, when I constructed them from the bits<br>
on the<br>
tape.<br>
<br>
Please keep in mind that I wrote the program that does this, so the<br>
method of what I'm doing here is understandably confusing...I barely<br>
understand it.<br>
<br>
There are a few block errors that I'm working on correcting in<br>
each of<br>
the files.. Shall I send those over to you even with the handful of<br>
block errors, or shall I continue to work on correcting them?<br>
<br>
I just looked at the first paragraph of your email...I'll read<br>
the rest now.<br>
<br>
On Wed, Nov 18, 2015 at 11:29 AM, Bruce Ray <<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a> <mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>>>> wrote:<br>
<br>
G'day AJ -<br>
<br>
There is only one program on the 'MinicomDiskUtility.bin'<br>
file -<br>
there is no data beyond the 8KB (the file size is only).<br>
There is no<br>
"filemark" or other pseudo-/meta- data that I detect in the<br>
file,<br>
just a single stream of 4096 words (as appropriate for the DG<br>
word-oriented architecture [big-endian]). What other<br>
file(s) am I<br>
missing?<br>
<br>
<br>
Regardless, dissecting and running the utility reveals further<br>
program assumptions:<br>
<br>
The 40 MB disk drive has a geometry of 442 cylinders, 5<br>
heads, 32<br>
sectors/track (head).<br>
<br>
The IRIS logical unit to physical disk address assignments are:<br>
<br>
<br>
LUN CYL HD SEC<br>
---- --- -- ---<br>
<br>
LUN 0: 0, 0, 0 disk start address<br>
15, 4, 31 disk end address<br>
<br>
LUN 1: 15, 0, 0<br>
111, 4, 31<br>
<br>
LUN 2: 112, 0, 0<br>
223, 4, 31<br>
<br>
LUN3: 224, 0, 0<br>
335, 4, 31<br>
<br>
LUN4: 336, 0, 0<br>
441, 4, 31<br>
<br>
<br>
Total disk formatted size: 36,308,640 bytes<br>
<br>
Data is transferred to/from the disk to the tape drive in 4KB<br>
records during backup/restore operations.<br>
<br>
Only logical units 0, 1 and 2 can fit on a tape; a second<br>
tape was<br>
required for backing up logical units 3 and 4.<br>
<br>
Next step: obtain data files that contain the LUNx<br>
information...<br>
<br>
<br>
Bruce<br>
<br>
<br>
<br>
On 11/18/2015 2:21 AM, Microtech Dart wrote:<br>
<br>
Bruce! This is very exciting...you actually RAN the<br>
file! I'm so<br>
excited to know that this is possible.<br>
<br>
I received the screen shots in my MightyFrame email,<br>
thank you<br>
for those.<br>
<br>
Most of what you are talking about is still Greek to<br>
me, but<br>
I'll catch up.<br>
<br>
"The tape file itself needs to be created in the SimH<br>
tape if it<br>
is to<br>
be used with the default SimH tape driver. The QIC<br>
format may<br>
exist as a<br>
single large data record of 16,384 bytes, or of<br>
multiple 512-byte<br>
records followed by a file mark. (I can not tell its<br>
original format<br>
given only the .bin file to work with.)"<br>
<br>
OK, so I know exactly how the data format was written<br>
to this tape.<br>
(For detail on the format itself, I outline it in<br>
exhaustive<br>
detail on<br>
this page: <a href="http://bit.ly/1RhcdK2" rel="noreferrer" target="_blank">http://bit.ly/1RhcdK2</a> ) The format is neither<br>
QIC-11 nor<br>
QIC-24, but some very weird format that I've traced<br>
back to a<br>
specific<br>
model of Kennedy QIC tape drive.<br>
<br>
The Minicom Disk Utility file that you ran was in one<br>
single<br>
block of<br>
data, which was 8192 bytes long. It was, as you<br>
indicate, the very<br>
first block of data on the tape. This block was<br>
followed by a<br>
filemark.<br>
<br>
The next block after the filemark was also 8192 bytes (with<br>
nearly, but<br>
not exactly the same content as this Minicom utility<br>
file), but<br>
thereafter, every other block on the tape was only 4096<br>
bytes<br>
long, as<br>
was all of the other blocks on the entire tape. (Notice<br>
that this is<br>
either 8 or 16 times the length of a "normal" QIC-11 or<br>
QIC-24<br>
512-byte<br>
data block).<br>
<br>
This tape was marked "LU0, position 1; LU1, position 2;<br>
LU2,<br>
position<br>
3", so I expect this tape to have those 3 logical units<br>
on it.<br>
<br>
It seems that there are 3 more filemarks on this tape<br>
(if I counted<br>
correctly), so then this tape has 4 files, one file for the<br>
Minicom Disk<br>
Utility, and one file for each of the Logical Units.<br>
<br>
I can tell you right now that the LU0 file (if that is<br>
really<br>
what it<br>
is), is 1,331,200 bytes, or exactly 1,300 Mb (if I did<br>
the math<br>
right).<br>
The other 2 files I need to study more deeply to tell<br>
for sure,<br>
as they<br>
span the tape tracks, and are more complicated for me<br>
to assemble.<br>
<br>
Would it be best to just work with those as files, or<br>
do they<br>
need to be<br>
kept in their original "Kennedy" block formation, or<br>
another block<br>
formation or format?<br>
<br>
Bruce, it is my goal to restore these tapes, and get a<br>
machine<br>
to run<br>
again as close as possible to the way it would have<br>
when these<br>
backups<br>
were made. With your ability to run the Minicom file,<br>
it gives<br>
me great<br>
hope that this is possible.<br>
<br>
What would be my next steps to get myself working on a<br>
system<br>
that has<br>
the capability of doing this? I'm open to whether that<br>
is SimH,<br>
reNOVAte, or other.<br>
<br>
Thank you again, Bruce, this is very exciting news!<br>
<br>
-AJ<br>
<br>
<br>
<br>
<br>
<br>
On Wed, Nov 18, 2015 at 1:42 AM, Bruce Ray<br>
<<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a> <mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a> <mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>>><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>> <mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a><br>
<mailto:<a href="mailto:Bruce@wild-hare.com" target="_blank">Bruce@wild-hare.com</a>>>>> wrote:<br>
<br>
G'day AJ -<br>
<br>
Briefly...<br>
<br>
The tape contains a disk/tape backup/restore<br>
utility that is<br>
somewhat representative of those used with Point<br>
4, and other<br>
3rd-party DG lookalike systems. It is a<br>
stand-alone utility<br>
that is<br>
bootable if it exists as the first record of the<br>
first file<br>
of a mag<br>
tape or cartridge.<br>
<br>
The usual procedure is to bootstrap the tape using<br>
the Nova APL<br>
function (or just toggling in simple 2-instruction<br>
'fat-finger'<br>
program). Once the program is read into memory,<br>
it starts<br>
execution<br>
and displays its introductory message. At this<br>
point another<br>
tape/cartridge may be loaded onto the tape drive<br>
for backup or<br>
restore purposes.<br>
<br>
I used our reNOVAte software for doing my<br>
investigations<br>
rather than<br>
SimH due to convenience, and was able to run the<br>
program and<br>
exercise its various functions. (Screen shots are<br>
attached.)<br>
<br>
This particular utility is very specific regarding<br>
the type<br>
of disk<br>
drive and IRIS logical units it supports.<br>
<br>
The utility assumes two devices exist: a tape<br>
controller using<br>
device code <022> and a disk controller using<br>
device code<br>
<027>. The<br>
tape controller may or may not perform QIC to<br>
DG-style file<br>
handling<br>
emulation since the original tape is not available<br>
to me.<br>
The disk controller appears to use the standard DG<br>
"Zebra"<br>
controller (Model 6060/6061/6067) programming model.<br>
However, it<br>
assumes a non-standard disk geometry of 16<br>
cylinders, 5<br>
heads, and<br>
32 sectors.<br>
<br>
The tape file itself needs to be created in the<br>
SimH tape<br>
if it is<br>
to be used with the default SimH tape driver. The QIC<br>
format may<br>
exist as a single large data record of 16,384<br>
bytes, or of<br>
multiple<br>
512-byte records followed by a file mark. (I can<br>
not tell its<br>
original format given only the .bin file to work<br>
with.)<br>
<br>
The utility also makes assumptions about tape read<br>
timing<br>
and CPU<br>
instruction execution speed. Horrible programming<br>
technique, but<br>
unfortunately not uncommon practice. Any such timing<br>
dependencies<br>
must be found and compensated for in the device<br>
driver or<br>
instruction emulation.<br>
<br>
Since there is no disk backup tape to load onto<br>
the disk, I<br>
used<br>
dummy disk data for testing the disk-to-tape and<br>
tape-to-disk<br>
functions. Real backup tape(s) would obviously be<br>
needed<br>
to restore<br>
the original system.<br>
<br>
<br>
Bruce<br>
<br>
<br>
<br>
On 11/14/2015 3:35 PM, Microtech Dart wrote:<br>
<br>
Thank you, Dell, and Sandy Strain, both of your<br>
responses were<br>
EXTREMELY<br>
helpful to me, and these all worked!<br>
<br>
Do either of you have any additional thoughts<br>
about how<br>
I could make<br>
what I believe to be a bootable file<br>
(extracted from a<br>
Microtech/Point4<br>
QIC tape) into a bootable device for the Nova?<br>
<br>
I'll start with the Minicom Disk To Tape Utility:<br>
<br>
<a href="http://microtechm1.blogspot.com/2015/09/minicom-disk-to-tape-copy-utility.html" rel="noreferrer" target="_blank">http://microtechm1.blogspot.com/2015/09/minicom-disk-to-tape-copy-utility.html</a><br>
<br>
I've attached a .zip of the binary file that I<br>
extracted from<br>
this tape<br>
for reference. It's very small, so I zipped<br>
it up only<br>
so that the<br>
emailing process didn't interfere with or<br>
reject it.<br>
<br>
Thanks, all!<br>
<br>
-AJ<br>
<br>
On Sat, Nov 14, 2015 at 7:23 AM, Dell Setzer<br>
<<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>>><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>>>><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>>><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>><br>
<mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a> <mailto:<a href="mailto:dsetzer@panix.com" target="_blank">dsetzer@panix.com</a>>>>>> wrote:<br>
<br>
It's actually pretty easy. After booting<br>
RDOS,<br>
press ^E to<br>
return to<br>
the sim> prompt. Then, attach a host file<br>
to the<br>
MTA0 unit.<br>
If you<br>
give a host filename that doesn't yet<br>
exist, SIMH will<br>
create an<br>
empty tape file and attach it to MTA0:<br>
<br>
sim> attach mta0 testtape.tap<br>
MTA: creating new file<br>
sim><br>
<br>
Then, give the simh G command to return<br>
to RDOS<br>
and init/f<br>
the MT0<br>
tape unit. Note that at the sim> prompt,<br>
the unit<br>
is called<br>
"MTA0"<br>
(or MTA1, MTA2, etc), while in RDOS the<br>
unit is called<br>
"MT0" (or<br>
MT1, MT2, etc):<br>
<br>
sim> g<br>
<presss return to get the RDOS prompt again><br>
R<br>
init/f mt0<br>
CONFIRM? <press Y to confirm><br>
R<br>
<br>
Now you can dump or copy files to the MT0<br>
device:<br>
dump/v mt0:0 -.sr<br>
<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">LITMACS.SR</a> <<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>> <<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
<<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
<<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
<a href="http://OSID.SR" rel="noreferrer" target="_blank">OSID.SR</a> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>><br>
<<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>><br>
<a href="http://NSID.SR" rel="noreferrer" target="_blank">NSID.SR</a> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>><br>
<<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>><br>
<a href="http://PARS.SR" rel="noreferrer" target="_blank">PARS.SR</a> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>><br>
<<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>><br>
<a href="http://ALMSPD.SR" rel="noreferrer" target="_blank">ALMSPD.SR</a> <<a href="http://ALMSPD.SR" rel="noreferrer" target="_blank">http://ALMSPD.SR</a>> <<a href="http://ALMSPD.SR" rel="noreferrer" target="_blank">http://ALMSPD.SR</a>><br>
<<a href="http://ALMSPD.SR" rel="noreferrer" target="_blank">http://ALMSPD.SR</a>> <<a href="http://ALMSPD.SR" rel="noreferrer" target="_blank">http://ALMSPD.SR</a>><br>
<etc.><br>
R<br>
dump/v mt0:1 -.sv<br>
<a href="http://BURST.SV" rel="noreferrer" target="_blank">BURST.SV</a> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>><br>
<<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>><br>
<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">INITIALIZE.SV</a> <<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>> <<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
<<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
<<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">SEDIT.SV</a> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>><br>
<<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>><br>
<a href="http://MACXR.SV" rel="noreferrer" target="_blank">MACXR.SV</a> <<a href="http://MACXR.SV" rel="noreferrer" target="_blank">http://MACXR.SV</a>> <<a href="http://MACXR.SV" rel="noreferrer" target="_blank">http://MACXR.SV</a>> <<a href="http://MACXR.SV" rel="noreferrer" target="_blank">http://MACXR.SV</a>><br>
<<a href="http://MACXR.SV" rel="noreferrer" target="_blank">http://MACXR.SV</a>><br>
<a href="http://EDIT.SV" rel="noreferrer" target="_blank">EDIT.SV</a> <<a href="http://EDIT.SV" rel="noreferrer" target="_blank">http://EDIT.SV</a>> <<a href="http://EDIT.SV" rel="noreferrer" target="_blank">http://EDIT.SV</a>> <<a href="http://EDIT.SV" rel="noreferrer" target="_blank">http://EDIT.SV</a>><br>
<<a href="http://EDIT.SV" rel="noreferrer" target="_blank">http://EDIT.SV</a>><br>
<etc.><br>
R<br>
release mt0<br>
R<br>
<br>
After releaseing the tape, press ^E again<br>
to get<br>
to the<br>
sim> prompt<br>
and detach the tape file:<br>
^E<br>
sim> detach mta0<br>
sim><br>
Now you can inspect the testtape.tap tape<br>
image.<br>
<br>
Attaching an existing tape file is<br>
similar, except<br>
that at<br>
the RDOS<br>
prompt you'd do INIT rather than INIT/F:<br>
<br>
sim> attach mta0 testtape.tap<br>
sim> g<br>
R<br>
init mt0<br>
R<br>
load/n mt0:0<br>
<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">LITMACS.SR</a> <<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>> <<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
<<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
<<a href="http://LITMACS.SR" rel="noreferrer" target="_blank">http://LITMACS.SR</a>><br>
10/20/83<br>
<a href="http://OSID.SR" rel="noreferrer" target="_blank">OSID.SR</a> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>> <<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>><br>
<<a href="http://OSID.SR" rel="noreferrer" target="_blank">http://OSID.SR</a>><br>
01/10/84<br>
<a href="http://NSID.SR" rel="noreferrer" target="_blank">NSID.SR</a> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>> <<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>><br>
<<a href="http://NSID.SR" rel="noreferrer" target="_blank">http://NSID.SR</a>><br>
10/20/83<br>
<a href="http://PARS.SR" rel="noreferrer" target="_blank">PARS.SR</a> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>> <<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>><br>
<<a href="http://PARS.SR" rel="noreferrer" target="_blank">http://PARS.SR</a>><br>
01/31/85<br>
<etc><br>
R<br>
load/n mt0:1<br>
<a href="http://BURST.SV" rel="noreferrer" target="_blank">BURST.SV</a> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>> <<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>><br>
<<a href="http://BURST.SV" rel="noreferrer" target="_blank">http://BURST.SV</a>><br>
05/09/85<br>
<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">INITIALIZE.SV</a> <<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>> <<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
<<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
<<a href="http://INITIALIZE.SV" rel="noreferrer" target="_blank">http://INITIALIZE.SV</a>><br>
05/02/85<br>
<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">SEDIT.SV</a> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>> <<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>><br>
<<a href="http://SEDIT.SV" rel="noreferrer" target="_blank">http://SEDIT.SV</a>><br>
05/02/85<br>
<etc><br>
R<br>
release mt0<br>
R<br>
<br>
Hope this helps,<br>
...dell<br>
<br>
On Sat, 14 Nov 2015, Microtech Dart wrote:<br>
<br>
Hi, I am completely new here, although I<br>
recognize the<br>
names of<br>
several who<br>
post here.<br>
<br>
I am trying to resurrect an extinct<br>
Microtech<br>
machine<br>
from 1982,<br>
which<br>
likely used the Point 4 processor,<br>
and the<br>
SimH DG Nova<br>
simulator *should*<br>
be compatible with the Point 4.<br>
<br>
I'm running the NOVA simulator now, with:<br>
<br>
NOVA simulator V4.0-0 Beta git<br>
commit<br>
id: 3be5125d<br>
sim> ATTACH DKP0 *rdos_d31.dsk*<br>
sim> set tti dasher<br>
sim> boot DKP0<br>
<br>
I'm teaching myself RDOS now with the<br>
RDOS_Command_Line_Interpreter Manual.<br>
<br>
<br>
<br>
<<a href="http://www.mirrorservice.org/sites/www.bitsavers.org/pdf/dg/software/rdos/093-000109-01_RDOS_Command_Line_Interpreter.pdf" rel="noreferrer" target="_blank">http://www.mirrorservice.org/sites/www.bitsavers.org/pdf/dg/software/rdos/093-000109-01_RDOS_Command_Line_Interpreter.pdf</a>><br>
<br>
Would anybody here be able to suggest<br>
some<br>
methods by<br>
which I could<br>
*create* a magnetic tape device on<br>
this SimH Nova<br>
simulator, and<br>
how I<br>
might write some files to that?<br>
<br>
I think that would be an excellent<br>
experiment<br>
for me to<br>
attempt. Then I<br>
can inspect the binary file in a hex<br>
editor,<br>
and see<br>
what it<br>
looks like,<br>
then compare to the binaries I've<br>
pulled off my<br>
Microtech/Point<br>
4 tapes.<br>
<br>
--<br>
<br>
Thanks,<br>
-AJ<br>
<a href="http://MicrotechM1.blogspot.com" rel="noreferrer" target="_blank">http://MicrotechM1.blogspot.com</a><br>
<br>
<br>
<br>
<br>
--<br>
<br>
Thanks,<br>
-AJ<br>
<a href="http://MicrotechM1.blogspot.com" rel="noreferrer" target="_blank">http://MicrotechM1.blogspot.com</a><br>
<br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br>
<br>
<br>
<br>
--<br>
<br>
Thanks,<br>
-AJ<br>
<a href="http://MicrotechM1.blogspot.com" rel="noreferrer" target="_blank">http://MicrotechM1.blogspot.com</a><br>
<br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a>>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br>
<br>
<br>
<br>
--<br>
<br>
Thanks,<br>
-AJ<br>
<a href="http://MicrotechM1.blogspot.com" rel="noreferrer" target="_blank">http://MicrotechM1.blogspot.com</a><br>
<br>
<br>
<br>
<br>
--<br>
<br>
Thanks,<br>
-AJ<br>
<a href="http://MicrotechM1.blogspot.com" rel="noreferrer" target="_blank">http://MicrotechM1.blogspot.com</a><br>
<br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br>
</blockquote>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><br><div>Thanks,</div><div>-AJ</div><div><a href="http://MicrotechM1.blogspot.com" target="_blank">http://MicrotechM1.blogspot.com</a></div></div></div>
</div>