On 02/12/2015 12:23 PM, Johnny Billquist wrote:
Console TRANSMIT is fine...but RECEIVE is receiving gibberish from my
end...can't figure out why. ? works, every other symbol is either | } or
w or y.
Makes it a liiiiiittle hard to boot.
Sigh... I suspect the standard problems. Check your character length,
parity, stop bits...
Have people totally forgotten how to use a serial line???
Please give Cory a bit more credit than that, man. Seriously. This
guy has gotten some truly outlandish systems up and running in no time
with almost no assistance. He wrangles serial lines with the best of 'em.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Thursday, February 12, 2015 at 7:59 AM, Fred wrote:
On Thu, 12 Feb 2015, Johnny Billquist wrote:
You haven't loaded a different message file? You can do that in VMS,
and there is this classic april fools message file that I wouldn't be
surprised if it holds that fish message...
To my knowledge, no - whatever ships with 8.3 is what is there, although I'm
not sure how to tell.
However, at $previous_job where they ran OpenVMS in production and I
had access to DCL, the DS15 ran 8.3 and that is where I originally discovered
this easter egg. I can't believe they would have had anything other than the
standard message file.
My IA64 OVMS 8.4 test system also has this message in the standard message file.
I wonder what facility returns status this and possibly other equally interesting status values... :-)
Poking around a bit yields another interesting one:
WRITE SYS$OUTPUT F$MESSAGE (3000)
%SYSTEM-W-REMINDER, Andy, remember to turn off the lights when you leave...
How did this diversion get injected into this discussion?
Fred, is this merely part of one of your signatures?
- Mark
On 2015-02-12 17:27, Cory Smelosky wrote:
On Thu, 12 Feb 2015, Peter Lothberg wrote:
Need a little help with the boot process. THis is the output...it hangs
afterwards.
It looks like you are echoing the characters from the console back to
itself, "half duplex"?
Alright. It loaded microcode now! 16MWord!
However...
Console TRANSMIT is fine...but RECEIVE is receiving gibberish from my
end...can't figure out why. ? works, every other symbol is either | } or
w or y.
Makes it a liiiiiittle hard to boot.
Sigh... I suspect the standard problems. Check your character length, parity, stop bits...
Have people totally forgotten how to use a serial line???
Johnny
> I tried every one my 420 offers...not all shown in video though
What kind of console terminal plug is on the SC40? Are you sure your cable is wired correctly? I ve seen this kind of funny business happen when the ground was swapped with the data pins that s not uncommon with homemade MMJ cables.
Bob
Check later on, I tried every one my 420 offers...not all shown in video though
Sent from my iPhone
On Feb 12, 2015, at 12:15, Jim Carpenter <jim at deitygraveyard.com> wrote:
On Feb 12, 2015 12:11 PM, "Cory Smelosky" <b4 at gewt.net> wrote: > https://www.youtube.com/watch?v=2LAPAwzoeiQ > > Here's a video of what it does. > >
Typing some letters works but others don't? Check your parity.
Jim
On Feb 12, 2015 12:11 PM, "Cory Smelosky" <b4 at gewt.net> wrote: > https://www.youtube.com/watch?v=2LAPAwzoeiQ > > Here's a video of what it does. > >
Typing some letters works but others don't? Check your parity.
Jim
On Thu, 12 Feb 2015, Cory Smelosky wrote:
Console TRANSMIT is fine...but RECEIVE is receiving gibberish from my
end...can't figure out why. ? works, every other symbol is either | } or
w or y.
Makes it a liiiiiittle hard to boot.
https://www.youtube.com/watch?v=2LAPAwzoeiQ
Here's a video of what it does.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 12 Feb 2015, Peter Lothberg wrote:
Need a little help with the boot process. THis is the output...it hangs
afterwards.
It looks like you are echoing the characters from the console back to
itself, "half duplex"?
Alright. It loaded microcode now! 16MWord!
However...
Console TRANSMIT is fine...but RECEIVE is receiving gibberish from my
end...can't figure out why. ? works, every other symbol is either | } or
w or y.
Makes it a liiiiiittle hard to boot.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 12 Feb 2015, Johnny Billquist wrote:
You haven't loaded a different message file? You can do that in VMS, and there is this classic april fools message file that I wouldn't be surprised if it holds that fish message...
To my knowledge, no - whatever ships with 8.3 is what is there, although I'm not sure how to tell.
However, at $previous_job where they ran OpenVMS in production and I had access to DCL, the DS15 ran 8.3 and that is where I originally discovered this easter egg. I can't believe they would have had anything other than the standard message file.
Fred
On 2015-02-12 16:22, Fred wrote:
On Thu, 12 Feb 2015, Robert Armstrong wrote:
Hmm... On OVMS 7.1 I get the standard " %SYSTEM-W-NOMSG, Message number
00000B70". Did you just make this up, or is the really an Easter Egg in
some version of VMS?
I swear I did not make this up:
MISER$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
MISER$ show sys /noproc
OpenVMS V8.3 on node MISER 12-FEB-2015 10:19:47.86 Uptime 70 13:37:37
However, on 7.3:
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-NOMSG, Message number 00000B70
$ show sys/noproc
OpenVMS V7.3 on node FRUGAL 12-FEB-2015 10:20:56.80 Uptime 70 11:00:39
Looks like 8.3 is required! ?
You haven't loaded a different message file? You can do that in VMS, and there is this classic april fools message file that I wouldn't be surprised if it holds that fish message...
Johnny
On Thu, 12 Feb 2015, Robert Armstrong wrote:
Hmm... On OVMS 7.1 I get the standard " %SYSTEM-W-NOMSG, Message number
00000B70". Did you just make this up, or is the really an Easter Egg in
some version of VMS?
I swear I did not make this up:
MISER$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
MISER$ show sys /noproc
OpenVMS V8.3 on node MISER 12-FEB-2015 10:19:47.86 Uptime 70 13:37:37
However, on 7.3:
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-NOMSG, Message number 00000B70
$ show sys/noproc
OpenVMS V7.3 on node FRUGAL 12-FEB-2015 10:20:56.80 Uptime 70 11:00:39
Looks like 8.3 is required! ?
P.S. Cory now has his own SC40?? I am sooooo jealous :-)
*drool*. <AOL>Me too!</AOL>
Fred
Sent from my iPhone
On Feb 12, 2015, at 09:41, Robert Armstrong <bob at jfcl.com> wrote:
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
Hmm... On OVMS 7.1 I get the standard " %SYSTEM-W-NOMSG, Message number
00000B70". Did you just make this up, or is the really an Easter Egg in
some version of VMS?
Bob
P.S. Cory now has his own SC40?? I am sooooo jealous :-)
Yup. ;)
Come hack on it one day if you'd like!
Sent from my iPhone
On Feb 12, 2015, at 09:20, Fred <fcoffey at misernet.net> wrote:
On Wed, 11 Feb 2015, Cory Smelosky wrote:
Image the boot drive from a CompuServe SC-40.
Whoa.
Please keep the list posted on your progress. This is relevant to my interests! :)
Fred
---
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
Sent from my iPhone
On Feb 12, 2015, at 05:07, Peter Lothberg <roll at Stupi.SE> wrote:
Need a little help with the boot process. THis is the output...it hangs
afterwards.
It looks like you are echoing the characters from the console back to
itself, "half duplex"?
Yeah...trying to figure out why it's echoing them back. Can't hurt to drag out a VT420
NSP has a "dir" command.
-P
Unit 00: loading 0003CED0 bytes 00005AA8 syms 000047AC strings ok
[System serial number: 43605]
SC-40 Supervisor Program V1.01
[PFR: Automatic restart in 5 seconds - Hit a key to abort]
[PFR: Automatic restart has been aborted]
NSP>[System serial number: 43605]
?Not confirmed - "[System"
CMD error
NSP>
000001/ 80
NSP>SC-40 Supervisor Program V1.01
?Not confirmed - "SC-40"
CMD error
NSP>
000002/ 04
NSP>
NSP>
000003/ 06
NSP>[PFR: Automatic restart in 5 seconds - Hit a key to abort]
?Not confirmed - "[PFR:"
CMD error
NSP>
000004/ 01
NSP>
NSP>
000005/ 00
NSP>[PFR: Automatic restart has been aborted]
?Not confirmed - "[PFR:"
CMD error
NSP>
000006/ 00
NSP>NSP>[System serial number: 43605]
?Not confirmed - "NSP>[System"
CMD error
NSP>
000007/ 00
NSP>? Command, one of the following:
ASSIGN AUTOBOOT BP
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
Hmm... On OVMS 7.1 I get the standard " %SYSTEM-W-NOMSG, Message number
00000B70". Did you just make this up, or is the really an Easter Egg in
some version of VMS?
Bob
P.S. Cory now has his own SC40?? I am sooooo jealous :-)
On Wed, 11 Feb 2015, Cory Smelosky wrote:
Image the boot drive from a CompuServe SC-40.
Whoa.
Please keep the list posted on your progress. This is relevant to my interests! :)
Fred
---
$ WRITE SYS$OUTPUT F$MESSAGE (2928)
%SYSTEM-W-FISH, my hovercraft is full of eels
NSP>? Command, one of the following:
ASSIGN AUTOBOOT BP CH
CLEAR CM CONTINUE COPY
DDT DEASSIGN DEBUG DEFINE
DELETE DEPOSIT DF DIRECTORY
DISCONNECT DN DUMP EN
EXAMINE EXECUTE FILL FORMAT
GET HALT HISTORY IF
IM LCR LCRX LOAD
MARGIN MS OFF ON
PM REBOOT RENAME RESET
REWIND RUN SEARCH SELECT
SET SHOW SHUTDOWN SM
START STEP TAKE TALK
TEST TYPE UNDEFINE WHAT
Need a little help with the boot process. THis is the output...it hangs
afterwards.
It looks like you are echoing the characters from the console back to
itself, "half duplex"?
NSP has a "dir" command.
-P
Unit 00: loading 0003CED0 bytes 00005AA8 syms 000047AC strings ok
[System serial number: 43605]
SC-40 Supervisor Program V1.01
[PFR: Automatic restart in 5 seconds - Hit a key to abort]
[PFR: Automatic restart has been aborted]
NSP>[System serial number: 43605]
?Not confirmed - "[System"
CMD error
NSP>
000001/ 80
NSP>SC-40 Supervisor Program V1.01
?Not confirmed - "SC-40"
CMD error
NSP>
000002/ 04
NSP>
NSP>
000003/ 06
NSP>[PFR: Automatic restart in 5 seconds - Hit a key to abort]
?Not confirmed - "[PFR:"
CMD error
NSP>
000004/ 01
NSP>
NSP>
000005/ 00
NSP>[PFR: Automatic restart has been aborted]
?Not confirmed - "[PFR:"
CMD error
NSP>
000006/ 00
NSP>NSP>[System serial number: 43605]
?Not confirmed - "NSP>[System"
CMD error
NSP>
000007/ 00
NSP>? Command, one of the following:
ASSIGN AUTOBOOT BP
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Need a little help with the boot process. THis is the output...it hangs afterwards.
Unit 00: loading 0003CED0 bytes 00005AA8 syms 000047AC strings ok
[System serial number: 43605]
SC-40 Supervisor Program V1.01
[PFR: Automatic restart in 5 seconds - Hit a key to abort]
[PFR: Automatic restart has been aborted]
NSP>[System serial number: 43605]
?Not confirmed - "[System"
CMD error
NSP>
000001/ 80
NSP>SC-40 Supervisor Program V1.01
?Not confirmed - "SC-40"
CMD error
NSP>
000002/ 04
NSP>
NSP>
000003/ 06
NSP>[PFR: Automatic restart in 5 seconds - Hit a key to abort]
?Not confirmed - "[PFR:"
CMD error
NSP>
000004/ 01
NSP>
NSP>
000005/ 00
NSP>[PFR: Automatic restart has been aborted]
?Not confirmed - "[PFR:"
CMD error
NSP>
000006/ 00
NSP>NSP>[System serial number: 43605]
?Not confirmed - "NSP>[System"
CMD error
NSP>
000007/ 00
NSP>? Command, one of the following:
ASSIGN AUTOBOOT BP
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Wed, 11 Feb 2015, Peter Lothberg wrote:
Ahhh. That's based on really old T10 stuff. So it's 576 or 2304 byte
sectors. I guess this is a IBM drive (0666)? If it does not spin up-
hit it on the side.. (You can have a BIG drive or a 3.5 in drive..)
C1247/C2247 or something like that.
Fotnote on the SC40. The "other" SCSI connectors can use 512b sector
disks, the microcode on the chanels will flip things. But it can't
boot from them..
Ahhhh. That makes sense.
Someone else to explain what it takes for Unix or any other OS to read
something other than 512Byte sectors. The SCSI protocol don't care, so
maybe a program reading a block at the time and write it to 512b
blocks and pad the last one?
I just need to get a clean image ASAP in the event the drives fail.
I belive I could mount the file-system and make a T10 backup tape from
T10.
Let me knew if I can be of any help, and don't loose the bits..
-P
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Wed, 11 Feb 2015, Peter Lothberg wrote:
Looks like I'm gonna need a low-level SCSI driver patch to copy 'em then, no?
What exactly are we trying to do here? What do we have and what kind
of result are we expecting?!
Image the boot drive from a CompuServe SC-40.
I also assumed it was a T20 system, there is also T10 stuff.
It was running the CompuServe monitor.
Ahhh. That's based on really old T10 stuff. So it's 576 or 2304 byte
sectors. I guess this is a IBM drive (0666)? If it does not spin up-
hit it on the side.. (You can have a BIG drive or a 3.5 in drive..)
Fotnote on the SC40. The "other" SCSI connectors can use 512b sector
disks, the microcode on the chanels will flip things. But it can't
boot from them..
Someone else to explain what it takes for Unix or any other OS to read
something other than 512Byte sectors. The SCSI protocol don't care, so
maybe a program reading a block at the time and write it to 512b
blocks and pad the last one?
I belive I could mount the file-system and make a T10 backup tape from
T10.
Let me knew if I can be of any help, and don't loose the bits..
-P
On Wed, 11 Feb 2015, Peter Lothberg wrote:
Looks like I'm gonna need a low-level SCSI driver patch to copy 'em then, no?
What exactly are we trying to do here? What do we have and what kind
of result are we expecting?!
Image the boot drive from a CompuServe SC-40.
I also assumed it was a T20 system, there is also T10 stuff.
It was running the CompuServe monitor.
-P
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2015-02-11 20:27, Cory Smelosky wrote:
Coming today:
Images of SC-40 boot drives assuming they weren't 36-bit low-level
I don't think they are, but Peter Lothberg should have all the details,
since he already have an SC40 on HECnet...
The SCSI drive that is used for boot is formatted with 2304 byte
sectors, and has a T20 file system. The "FE are" is not used.
(one sector=1 pdp10 page)
They can be 576 byte to.
Looks like I'm gonna need a low-level SCSI driver patch to copy 'em then, no?
What exactly are we trying to do here? What do we have and what kind
of result are we expecting?!
I also assumed it was a T20 system, there is also T10 stuff.
-P
Looks like I'm gonna need a low-level SCSI driver patch to copy 'em then, no?
Sent from my iPhone
On Feb 11, 2015, at 15:21, Peter Lothberg <roll at Stupi.SE> wrote:
On 2015-02-11 20:27, Cory Smelosky wrote:
Coming today:
Images of SC-40 boot drives assuming they weren't 36-bit low-level
I don't think they are, but Peter Lothberg should have all the details,
since he already have an SC40 on HECnet...
The SCSI drive that is used for boot is formatted with 2304 byte
sectors, and has a T20 file system. The "FE are" is not used.
--P
(one sector=1 pdp10 page)
On 2015-02-11 20:27, Cory Smelosky wrote:
Coming today:
Images of SC-40 boot drives assuming they weren't 36-bit low-level
I don't think they are, but Peter Lothberg should have all the details,
since he already have an SC40 on HECnet...
The SCSI drive that is used for boot is formatted with 2304 byte
sectors, and has a T20 file system. The "FE are" is not used.
(one sector=1 pdp10 page)
I think (memory failing) that you can do with 576 byte sectors to.
-P
