Cory Smelosky <b4 at gewt.net> writes:
Afternoon all,
What started that myth? I've managed to get a 146G drive working in a
VAXstation 4000/60 (10,000 RPM, too!). Unless I did my maths wrong, it's
showing up as 136G as a FILES-11 volume(~700M in SHOW DEVICES at the
tripel chevron prompt)
There also seems to be no 1G boot drive limit on this as my boot drive is
about 4G.
Was this a limit that existed in earlier VAXstations?
VMS, generally, doesn't have any issues unless you're booting the system
with older built-in controllers. Even then, if you can organize the VMS
files needed for bootstrap, you can probably boot from a larger system
drive too.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On Sat, 26 Oct 2013 13:58:57 -0400, Cory Smelosky wrote:
Was this a limit that existed in earlier VAXstations?
As others have already pointed out, the limit was in some 3100 models ROM.
The good news is that there is a famous patch for those ROMs. Here it is:
http://ftp.gwdg.de/pub/vms/ka420/
He is the guy who also patched VAXstation/MicroVAX 2000 ROM and VAX PKDRIVER
in order to use the internal SCSI "tape controller" for disks too:
http://ftp.gwdg.de/pub/vms/pk2k/
HTH, :)
G.
AFAIK it's not a myth for the microVAX 3100 series, except the models 8x and 9x. The same for the VAXstations 3100. The VAX 4x00 models and the VS4000s have no limit, at least not today.
The limit is a little over 1.0 GB btw.
Large capacity SCSI drives usually have SCA interfaces. So a converter is required to match the 50 pin connectors in a VAX. Not all converters work and the faulty ones fed the myth, I think.
Van: Cory Smelosky
Verzonden: zaterdag 26 oktober 2013 19:59
Aan: hecnet at update.uu.se
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] What started the modern VAX drive limit myth?
Afternoon all,
What started that myth? I've managed to get a 146G drive working in a
VAXstation 4000/60 (10,000 RPM, too!). Unless I did my maths wrong, it's
showing up as 136G as a FILES-11 volume(~700M in SHOW DEVICES at the
tripel chevron prompt)
There also seems to be no 1G boot drive limit on this as my boot drive is
about 4G.
Was this a limit that existed in earlier VAXstations?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
There we go - found it:
http://labs.hoffmanlabs.com/node/541
But it's on the 3100. The 4000 seems to be okay.
Ian
On Oct 26, 2013, at 11:05 AM, Ian McLaughlin <ian at platinum.net> wrote:
I seem to recall reading somewhere (but I'm unable to find the reference at the moment) that there was some event that caused a problem. Something like a system crash or bugcheck, which causes a ROM routine to be called which will dump RAM to disk for later analysis. The problem is that the ROM routine has a maximum size issue, and it may wrap around and overwrite a lower section of the hard drive.
I really wish I could find the reference, though...
Ian
On Oct 26, 2013, at 10:58 AM, Cory Smelosky <b4 at gewt.net> wrote:
Afternoon all,
What started that myth? I've managed to get a 146G drive working in a VAXstation 4000/60 (10,000 RPM, too!). Unless I did my maths wrong, it's showing up as 136G as a FILES-11 volume(~700M in SHOW DEVICES at the tripel chevron prompt)
There also seems to be no 1G boot drive limit on this as my boot drive is about 4G.
Was this a limit that existed in earlier VAXstations?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=558FD5B43E6811E3B…
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=4FF6ADD43E6911E3B…
There also seems to be no 1G boot drive limit on this as my boot drive is
about 4G.
Was this a limit that existed in earlier VAXstations?
The ROM code in the VAXstation-3100s used only 32 bits for the SCSI LBA,
so that limited them to booting from disks less than 2Gb. Later models
(like the 4000 you mentioned) fixed this, and there was never a limit.
Actually even the 2GB limit on the 3100 could sometimes be ignored. It
would still work with bigger disks so long as all the files the ROM needed
to access for booting were in the first 2GB (i.e. the upper bits of the LBA
were zeros). If you'd just installed VMS on an empty disk, this was usually
the case.
And this was only a problem with the ROM in the 3100. Once you got VMS
booted the SCSI device driver had no issues with the disk size.
Bob
I seem to recall reading somewhere (but I'm unable to find the reference at the moment) that there was some event that caused a problem. Something like a system crash or bugcheck, which causes a ROM routine to be called which will dump RAM to disk for later analysis. The problem is that the ROM routine has a maximum size issue, and it may wrap around and overwrite a lower section of the hard drive.
I really wish I could find the reference, though...
Ian
On Oct 26, 2013, at 10:58 AM, Cory Smelosky <b4 at gewt.net> wrote:
Afternoon all,
What started that myth? I've managed to get a 146G drive working in a VAXstation 4000/60 (10,000 RPM, too!). Unless I did my maths wrong, it's showing up as 136G as a FILES-11 volume(~700M in SHOW DEVICES at the tripel chevron prompt)
There also seems to be no 1G boot drive limit on this as my boot drive is about 4G.
Was this a limit that existed in earlier VAXstations?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=558FD5B43E6811E3B…
Afternoon all,
What started that myth? I've managed to get a 146G drive working in a VAXstation 4000/60 (10,000 RPM, too!). Unless I did my maths wrong, it's showing up as 136G as a FILES-11 volume(~700M in SHOW DEVICES at the tripel chevron prompt)
There also seems to be no 1G boot drive limit on this as my boot drive is about 4G.
Was this a limit that existed in earlier VAXstations?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Guys, sorry about not having the VPN accounts up yet, my Internet connection SUCKS right now, anything interactive like an SSH session to the server is like pulling teeth.
I'll get them up as soon as I can, though.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 24 Oct 2013, at 09:25, Sampsa Laine <sampsa at mac.com> wrote:
Yup. I'll set you guys up around lunchtime GMT - provided I survive the trip in and out of town, the Bedus are driving even crazier than usual, it's like the chariot race scene in Ben Hur to go to the shops.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 23 Oct 2013, at 22:58, Michael Holmes <mholmes10 at hotmail.com> wrote:
Sampsa,
Can you support another non-static IP user?
Mike Holmes
From: md.benson at gmail.com
Date: Wed, 23 Oct 2013 15:53:54 +0100
Subject: Re: [HECnet] Need a non-static-IP link to HECNet. Anyone got one available.
To: hecnet at update.uu.se
Thanks, chief.
--
Mark Benson
On Wed, Oct 23, 2013 at 3:41 PM, Sampsa Laine <sampsa at mac.com> wrote:
Yup, I'll send it all to you in a tar ball when I get a chance to roll the account.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 23 Oct 2013, at 16:39, Mark Benson <md.benson at gmail.com> wrote:
Could you let me have the bash script you use? It'll be useful for a few things :)
--
Mark
On Wed, Oct 23, 2013 at 3:38 PM, Mark Benson <md.benson at gmail.com> wrote:
Ah right okay, I am not that familiar with VPN on Linux. I guess PTPP is a law unto itself :)
On Wed, Oct 23, 2013 at 3:29 PM, Sampsa Laine <sampsa at mac.com> wrote:
No idea, does it do PPTP?
I just use pptpd in a bash loop, check if it's alive and restart it if not.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 23 Oct 2013, at 16:11, Mark Benson <md.benson at gmail.com> wrote:
I guess I'll be okay connecting from OpenVPN on my RasPi?
On Wed, Oct 23, 2013 at 2:57 PM, Sampsa Laine <sampsa at mac.com> wrote:
Yup, you get a static IP on my 192.168.77.0/24 subnet, and the bridge is on that subnet so it'll just work.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 23 Oct 2013, at 15:48, Mark Benson <md.benson at gmail.com> wrote:
Thanks, Sampsa :)
Once on the VPN, I guess I can just bridge to an IP inside your DECnet LAN?
--
Mark
On Wed, Oct 23, 2013 at 2:25 PM, Sampsa Laine <sampsa at mac.com> wrote:
Yeah, I've got a PPTP setup for the bridge.
I'll set you up tomorrow and send you the details for the VPN and bridge.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 23 Oct 2013, at 15:00, Mark Benson <md.benson at gmail.com> wrote:
Hi,
Judgement day came early and we switched back to residential internet and now have no static IP BUT I'm getting a much faster line installed next week as a result so it's all good.
Does anyone have a VPN I could connect to in order to keep my HECnet connection up (for me to not use, like I've been not using it since April ;) ). Winter is coming and I'll need something to do in the evenings and weekends when it's too rainy and cold to cycle :P
Thanks!
--
Mark Benson
If the c compiler is distributed as a set of save sets, .A .B etc then do a back/ list on them to find the .cld file. Use the set command command to install the cc command. That may work for you perhaps.
Hans
Van: Cory Smelosky
Verzonden: zaterdag 26 oktober 2013 02:39
Aan: hecnet at update.uu.se
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Compiler issues continue
Evening,
After a little more fiddling I have determined for sure that something
isn't in a table it should be in.
MOIRA::CSMELOSKY$ run dka0:[vms$common.sysexe]decc$compiler
%CLI-F-SYNTAX, error parsing 'VCG$VERSION'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs
PC
7FF64BB9
7FF64BB9
7FF649BF
7FF649BF
7FF644E0
7FF644E0
001CB692
001CB692
0019B0ED
0019B0ED
00199CEA
00199CEA
00194F5A
00194F5A
COMPILE cc_driver 52136 00000247
0018F69F
(I just did that for a test...doing a full reinstall won't help. How
would I manually toss it in to DCLTABLES?)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Sat, 26 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
Evening,
After a little more fiddling I have determined for sure that something
isn't in a table it should be in.
MOIRA::CSMELOSKY$ run dka0:[vms$common.sysexe]decc$compiler
%CLI-F-SYNTAX, error parsing 'VCG$VERSION'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs
PC
7FF64BB9
7FF64BB9
7FF649BF
7FF649BF
7FF644E0
7FF644E0
001CB692
001CB692
0019B0ED
0019B0ED
00199CEA
00199CEA
00194F5A
00194F5A
COMPILE cc_driver 52136 00000247
0018F69F
(I just did that for a test...doing a full reinstall won't help. How
would I manually toss it in to DCLTABLES?)
The installation should add "CC" (the C Compiler) command to DCLTABLES.EXE.
Make sure that you have only one DCLTABLES.EXE in SYS$COMMON:[SYSLIB].
Reinstalling the compiler THIS time worked. No idea why it didn't the other 2 times...
You can not simply RUN the C compiler executable because it will look for
command information via CLI$routines/SYS$CLI callbacks. You *might* get
away with $ MCR DKA0:[VMS$COMMON.SYSEXE]DECC$COMPILER not giving you the
stack dump traceback but gawd only knows what qualifier defaults you will
be given.
When you have the C Compiler installed, try:
$ CREATE HELLO.C
#include <stdio.h>
main() { printf("Hello World\n");}
^Z <== Ctrl/Z to exit
$ CC HELLO
$ LINK HELLO
$ RUN HELLO
FYI, You also require a PAK for the DEC C compiler.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
