Thanks, Oleg!!
Thats it! I wasted a day trying to find an answer..
You can convert these images to simh .tap files using VCP command and the simh itself :)
at tq f77.tap
at rq rsx11mplus_4_6_bl87.dsk
b rq
...
>VCP CON F77.TAP/TAP/DRV:MU/MOU:FOR
>MOU MU:/FOR
>VCP COP MU1: MU:
14.03.2013 19:39, Oleg Safiullin :
If you mount or boot this image,
you can find in [200,200] directory:
Directory DU0:[200,200]
14-MAR-2013 19:35
RT57MU.TAP;1 7040. 03-NOV-1999 21:53
F77.TAP;2 2440. 03-NOV-1999 19:53
DNMP46EN.TAP;1 41840. 03-NOV-1999 20:43
These TAP images are for RSX VF: driver and can be mounted under RSX-11M-PLUS V4.5 and 4.6 using VCP command:
>VCP CON F77.TAP/TAP/RO/DRV:MU/MOU:FOR
VCP - Device VF0: (MU1:) has been assigned.
>BRU /REW/DIR MU1:
VOL1. AUT101.A F77V52 23-FEB-90 15:48:05
VOL1. AUTVER.BCK F77V52 23-FEB-90 15:49:29
VOL1. F77F77.BCK F77V52 23-FEB-90 15:50:51
VOL1. F77REL.BCK F77V52 23-FEB-90 15:52:19
VOL1. F77504.A F77V52 23-FEB-90 15:53:39
BRU - Completed
>
Thanks, Oleg!!
Thats it! I wasted a day trying to find an answer..
If you mount or boot this image,
you can find in [200,200] directory:
Directory DU0:[200,200]
14-MAR-2013 19:35
RT57MU.TAP;1 7040. 03-NOV-1999 21:53
F77.TAP;2 2440. 03-NOV-1999 19:53
DNMP46EN.TAP;1 41840. 03-NOV-1999 20:43
These TAP images are for RSX VF: driver and can be mounted under RSX-11M-PLUS V4.5 and 4.6 using VCP command:
>VCP CON F77.TAP/TAP/RO/DRV:MU/MOU:FOR
VCP - Device VF0: (MU1:) has been assigned.
>BRU /REW/DIR MU1:
VOL1. AUT101.A F77V52 23-FEB-90 15:48:05
VOL1. AUTVER.BCK F77V52 23-FEB-90 15:49:29
VOL1. F77F77.BCK F77V52 23-FEB-90 15:50:51
VOL1. F77REL.BCK F77V52 23-FEB-90 15:52:19
VOL1. F77504.A F77V52 23-FEB-90 15:53:39
BRU - Completed
>
14.03.2013 19:25, Johnny Billquist :
On 2013-03-14 16:07, blmink wrote:
Dear All,
I found several pdp-11 tape image files on the net which have ".tap"
suffix.
It isn't well known simh/e11/tap/tpc tape images.
Please help to identify which format they have.
How such file can be converted to simh .tap or .tpc or how it can be
used/mounted?
Below is the beginning of hexdump of one of these files named "F77.TAP":
[...]
Where did you find them? They look totally broken. I can't see any reasonable format in them at all. The first 512 bytes might be some kind of meta-information, but it's really weird.
Get some proper images instead, as from trailing-egde.
Johnny
There's file on trailing-egde:
ftp://ftp.trailing-edge.com/pub/rsxdists/rsx11mplus_4_6_bl87_dsk.zip
It contains rsx11mplus_4_6_bl87.dsk disk image.
If you mount or boot this image,
you can find in [200,200] directory:
Directory DU0:[200,200]
14-MAR-2013 19:35
RT57MU.TAP;1 7040. 03-NOV-1999 21:53
F77.TAP;2 2440. 03-NOV-1999 19:53
DNMP46EN.TAP;1 41840. 03-NOV-1999 20:43
I found several pdp-11 tape image files on the net which have ".tap"
suffix. It isn't well known simh/e11/tap/tpc tape images. Please help
to identify which format they have. How such file can be converted to
simh .tap or .tpc or how it can be used/mounted?
It looks to me like some gomer "imaged" a tape with dd or similar tool,
possibly on a drive set to fixed 512-byte block size. See, for example,
the 80 byte VOL1 record all alone in a 0x200-sized chunk with zero
padding.
If the original tape actually WAS fb512, and there was only one tape
"file" on the media, you might be able to convert this into an actual
.tap file by simply wrapping each chunk of 512 bytes in the proper
record length field. That is, place a word 0x00000200 (note:
little-endian) before and after each 512 byte chunk of the input file,
and the words 0x00000000 and 0xffffffff at the end of the file.
If the tape wasn't fb512, or contains multiple logical files, then about
the only way to save the image would be to grovel through it trying to
intuit record boundaries based on intimate knowledge of the habits of
the tool used to write the original.
De
On 2013-03-14 16:07, blmink wrote:
Dear All,
I found several pdp-11 tape image files on the net which have ".tap"
suffix.
It isn't well known simh/e11/tap/tpc tape images.
Please help to identify which format they have.
How such file can be converted to simh .tap or .tpc or how it can be
used/mounted?
Below is the beginning of hexdump of one of these files named "F77.TAP":
[...]
Where did you find them? They look totally broken. I can't see any reasonable format in them at all. The first 512 bytes might be some kind of meta-information, but it's really weird.
Get some proper images instead, as from trailing-egde.
Johnny
Al 14/03/13 12:39, En/na Jordi Guillaumes i Pons ha escrit:
Hi,
I have built another little simulated machine:
Name: BITXOX
Address: 7.60
The correct address is 7.76... Damn multitasking!
Hi,
I have built another little simulated machine:
Name: BITXOX
Address: 7.60
This one simulates a small VAX 11/730 running VMS 5.5. This machine has RSX11/VMS running and the GUEST account has MCR as default CLI. It's a little weird thing I have set up just as a curiosity. If someone pays a visit, please consider it is SLOW, with just 4M of RAM (several processes are swapped out just after startup), and sharing its host (a Rasp-pi) with several other virtual machines...
Username: GUEST
Password:
Welcome to VAX/VMS version V5.5-2 on node BITXOX
Last interactive login on Thursday, 14-MAR-2013 12:29
>@ <EOF>
> pip
PIP>/li
Directory SY0:[GUEST]
14-MAR-13 12:37
BUILD.CMD;1 1. 01-MAR-13 23:20
HELLO.EXE;1 38. C 01-MAR-13 23:22
HELLO.FTN;2 1. 01-MAR-13 23:16
HELLO.LST;2 2. 01-MAR-13 23:21
HELLO.MAP;2 17. 01-MAR-13 23:22
HELLO.OBJ;2 1. 01-MAR-13 23:21
LOGIN.CMD;1 1. 01-MAR-13 23:04
Total of 61./72. blocks in 7. files
PIP>
