DS10: "failed to load execlet"? - VMS

This is a discussion on DS10: "failed to load execlet"? - VMS ; VMSers -- So I have a DS10 that I bought from Island and left in a box for months. (We foolishly bought it without a video card, and then I was fussing with an unsupported old card for too long, ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: DS10: "failed to load execlet"?

  1. DS10: "failed to load execlet"?

    VMSers --

    So I have a DS10 that I bought from Island and left in a box for
    months. (We foolishly bought it without a video card, and then I was
    fussing with an unsupported old card for too long, and now I have a
    nice ATI card that succeeds in driving a VGA display with the
    console.) Any warranty is already over.

    Console software is 7.2-1 with a 2006 date.

    The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    drive.

    When I attempt to boot from the CD (dqbo) it sees a boot block,
    reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    setting affinity, reports jumping to bootstrap code, and then
    %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054

    What's going on here? Do I have a CD drive problem? A CPU problem?
    A duff copy of the OS? How do I tell?

    (If I need to MOP boot this puppy in order to be able to tell, can
    somebody point me to a step-by-step guide? I've never done MOP for
    anything but terminal servers and Xterms, and it's been a long time.)


    Thanks,

    -- Alan


  2. Re: "failed to load execlet"?


    "Alan Winston - SSRL Central Computing"
    wrote in message news:00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU...
    > VMSers --
    >
    > When I attempt to boot from the CD (dqbo) it sees a boot block,
    > reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    > setting affinity, reports jumping to bootstrap code, and then
    > %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >
    > What's going on here? Do I have a CD drive problem? A CPU problem?
    > A duff copy of the OS? How do I tell?
    >

    Status 54 can be
    %SYSTEM-?-BADATTRIB, bad attribute control list

    Is CD ok? I sometimes get stuck with errors on CD caused by dirth and grese
    from fingers.


    If you have a SCSI CD drive, try with it.

    Best, Gorazd



  3. Re: "failed to load execlet"?

    In article <%7O3j.1774$HS3.61713@news.siol.net>, "Gorazd Kikelj" writes:
    >"Alan Winston - SSRL Central Computing"
    >wrote in message news:00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU...
    >> VMSers --
    >>
    >> When I attempt to boot from the CD (dqbo) it sees a boot block,
    >> reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >> setting affinity, reports jumping to bootstrap code, and then
    >> %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >>
    >> What's going on here? Do I have a CD drive problem? A CPU problem?
    >> A duff copy of the OS? How do I tell?
    >>

    >Status 54 can be
    >%SYSTEM-?-BADATTRIB, bad attribute control list


    No. It is %SYSTEM-F-CTRLERR, fatal controller error

    >Is CD ok? I sometimes get stuck with errors on CD caused by dirth and grese
    >from fingers.


    Could be.

    >If you have a SCSI CD drive, try with it.


    I second this and add the suggestion for InfoServer (or InfoServer S/W on VMS8)

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  4. Re: DS10: "failed to load execlet"?

    What kind of CD are you trying to boot? I suppose VMS, but which
    version? Make sure you have a version that supports the system.

    Jur.

    Alan Winston - SSRL Central Computing wrote:
    > VMSers --
    >
    > So I have a DS10 that I bought from Island and left in a box for
    > months. (We foolishly bought it without a video card, and then I was
    > fussing with an unsupported old card for too long, and now I have a
    > nice ATI card that succeeds in driving a VGA display with the
    > console.) Any warranty is already over.
    >
    > Console software is 7.2-1 with a 2006 date.
    >
    > The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    > drive.
    >
    > When I attempt to boot from the CD (dqbo) it sees a boot block,
    > reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    > setting affinity, reports jumping to bootstrap code, and then
    > %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >
    > What's going on here? Do I have a CD drive problem? A CPU problem?
    > A duff copy of the OS? How do I tell?
    >
    > (If I need to MOP boot this puppy in order to be able to tell, can
    > somebody point me to a step-by-step guide? I've never done MOP for
    > anything but terminal servers and Xterms, and it's been a long time.)
    >
    >
    > Thanks,
    >
    > -- Alan
    >


  5. Re: DS10: "failed to load execlet"?

    Alan Winston - SSRL Central Computing wrote:
    > (If I need to MOP boot this puppy in order to be able to tell, can
    > somebody point me to a step-by-step guide?



    Do you have a cluster already setup ?
    Can you read that CD on another node ?

    @CLUSTER_CONFIG will do the trick to add a satellite node to your boot
    node. It creates a new root and adds the required stuff in the LANCP
    database.

    But you can also do this manually:

    MC LANCP
    LANCP> SET NODE newone -
    /BOOT_TYPE=ALPHA_SATELLITE -
    /FILE=APB.EXE-
    /ROOT=DISK$SYSTEM: -
    /address=08-00-2B-87-3D-64

    (you may wish to do this once with /PERM and once with /VOLATILE)

    What this will do is cause it to look for:
    DISK$SYSTEM:[SYSCOMMON.SYSEXE]APB.EXE


    (replace disk$system with whatever disk drive has the system sotware it
    in. but use the < and > instead of [ ] for the directory specs.

    in you will want to have some ALPHAVMSSYS.PAR file with
    wnataver sysgen parameters for the new node (including SCSNODENAME )

    You also want to make sure that CLUSTER_AUTHORIZE.DAT is going to be
    accessible to the new node if you plan to have it join the cluster. (put
    it in sys$common:[sysexe].

    APB.EXE gets you to a point where there is some sort of MSCP access that
    allows the boot to continue. I have managed to have an alpha boot from a
    VAX without the alpha having VMSCLUSTER set to 0 and it completed the
    boot. It saw its system drive but no other drives.

    To get a VAX to act as boot node for an alpha, you need to have a
    separate disk to hold the alpha system software, and then use LANCP as
    above to point to that disk in the /ROOT.


    On the alpha side:

    >>> BOOT EWA0

    or
    >>> BOOT EWA0 -flags 1,1


    first 1 is the root number aka [.SYS1]
    second 1 is the request to get to SYSBOOT. You can set it to 0 to skip that.

  6. Re: DS10: "failed to load execlet"?

    In article <474fc2d6$0$240$e4fe514c@news.xs4all.nl>, Jur van der Burg <"lddriver at digiater dot nl"> writes:
    >What kind of CD are you trying to boot? I suppose VMS, but which
    >version? Make sure you have a version that supports the system.


    VMS 8.3 Alpha for the DS10.

    -- Alan

    >
    >Jur.
    >
    >Alan Winston - SSRL Central Computing wrote:
    >> VMSers --
    >>
    >> So I have a DS10 that I bought from Island and left in a box for
    >> months. (We foolishly bought it without a video card, and then I was
    >> fussing with an unsupported old card for too long, and now I have a
    >> nice ATI card that succeeds in driving a VGA display with the
    >> console.) Any warranty is already over.
    >>
    >> Console software is 7.2-1 with a 2006 date.
    >>
    >> The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    >> drive.
    >>
    >> When I attempt to boot from the CD (dqbo) it sees a boot block,
    >> reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >> setting affinity, reports jumping to bootstrap code, and then
    >> %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >>
    >> What's going on here? Do I have a CD drive problem? A CPU problem?
    >> A duff copy of the OS? How do I tell?
    >>
    >> (If I need to MOP boot this puppy in order to be able to tell, can
    >> somebody point me to a step-by-step guide? I've never done MOP for
    >> anything but terminal servers and Xterms, and it's been a long time.)
    >>
    >>
    >> Thanks,
    >>
    >> -- Alan
    >>


  7. Re: DS10: "failed to load execlet"?

    On Nov 30, 1:11 am, wins...@SSRL.SLAC.STANFORD.EDU (Alan Winston -
    SSRL Central Computing) wrote:
    > VMSers --
    >
    > So I have a DS10 that I bought from Island and left in a box for
    > months. (We foolishly bought it without a video card, and then I was
    > fussing with an unsupported old card for too long, and now I have a
    > nice ATI card that succeeds in driving a VGA display with the
    > console.) Any warranty is already over.
    >
    > Console software is 7.2-1 with a 2006 date.
    >
    > The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    > drive.
    >
    > When I attempt to boot from the CD (dqbo) it sees a boot block,
    > reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    > setting affinity, reports jumping to bootstrap code, and then
    > %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >
    > What's going on here? Do I have a CD drive problem? A CPU problem?
    > A duff copy of the OS? How do I tell?
    >
    > (If I need to MOP boot this puppy in order to be able to tell, can
    > somebody point me to a step-by-step guide? I've never done MOP for
    > anything but terminal servers and Xterms, and it's been a long time.)
    >
    > Thanks,
    >
    > -- Alan


    Alan,

    First, I would recommend doing some fundamentals.

    Since the machine was shipped from Georgia to California, I would do
    two things:

    - I would disconnect and re-connect each of the cables relating to the
    CDROM
    - I would bootstrap a different copy of the any usable version of the
    standalone CDROM
    - I would invest in a call to Island, with an explanation of your
    situation. I would not presume that they will not assist you.

    I would suspect dirt, a disconnected cable, or some other plebeian
    problem before I went on to the more exotics.

    - Bob Gezelter, http://www.rlgsc.com

  8. Re: "failed to load execlet"?

    In article <%7O3j.1774$HS3.61713@news.siol.net>, "Gorazd Kikelj" writes:
    >
    >
    >
    >"Alan Winston - SSRL Central Computing"
    >wrote in message news:00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU...
    >> VMSers --
    >>
    >> When I attempt to boot from the CD (dqbo) it sees a boot block,
    >> reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >> setting affinity, reports jumping to bootstrap code, and then
    >> %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >>
    >> What's going on here? Do I have a CD drive problem? A CPU problem?
    >> A duff copy of the OS? How do I tell?
    >>

    >Status 54 can be
    >%SYSTEM-?-BADATTRIB, bad attribute control list


    BzzT! Wrong. When the execlet loader reports, it is reporting a hexadecimal
    error code.

    54(16) is: %SYSTEM-F-CTRLERR, fatal controller error


    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  9. Re: DS10: "failed to load execlet"?

    In article <00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU>, winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) writes:
    >
    >
    >VMSers --
    >
    >So I have a DS10 that I bought from Island and left in a box for
    >months. (We foolishly bought it without a video card, and then I was
    >fussing with an unsupported old card for too long, and now I have a
    >nice ATI card that succeeds in driving a VGA display with the
    >console.) Any warranty is already over.
    >
    >Console software is 7.2-1 with a 2006 date.
    >
    >The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    >drive.
    >
    >When I attempt to boot from the CD (dqbo) it sees a boot block,
    >reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >setting affinity, reports jumping to bootstrap code, and then
    >%SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >
    >What's going on here? Do I have a CD drive problem? A CPU problem?
    >A duff copy of the OS? How do I tell?
    >
    >(If I need to MOP boot this puppy in order to be able to tell, can
    >somebody point me to a step-by-step guide? I've never done MOP for
    >anything but terminal servers and Xterms, and it's been a long time.)


    Alan,

    Try booting with B -fl 0,30000 (assuming your boot root is 0)

    This will enable some VERY VERY VERBOSE bootstrap logging! Record this
    (and it will be vast) and then search for your error message in the log.
    This should help to pinpoint WHICH execlet (or driver) is in play when
    this error is emitted. Don't assume it is the CD until you are certain
    that it is the CD.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  10. Re: DS10: "failed to load execlet"?

    In article , VAXman- @SendSpamHere.ORG writes:
    >In article <00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU>, winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) writes:
    >>
    >>
    >>VMSers --
    >>
    >>So I have a DS10 that I bought from Island and left in a box for
    >>months. (We foolishly bought it without a video card, and then I was
    >>fussing with an unsupported old card for too long, and now I have a
    >>nice ATI card that succeeds in driving a VGA display with the
    >>console.) Any warranty is already over.
    >>
    >>Console software is 7.2-1 with a 2006 date.
    >>
    >>The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    >>drive.
    >>
    >>When I attempt to boot from the CD (dqbo) it sees a boot block,
    >>reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >>setting affinity, reports jumping to bootstrap code, and then
    >>%SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >>
    >>What's going on here? Do I have a CD drive problem? A CPU problem?
    >>A duff copy of the OS? How do I tell?
    >>
    >>(If I need to MOP boot this puppy in order to be able to tell, can
    >>somebody point me to a step-by-step guide? I've never done MOP for
    >>anything but terminal servers and Xterms, and it's been a long time.)

    >
    >Alan,
    >
    >Try booting with B -fl 0,30000 (assuming your boot root is 0)
    >
    >This will enable some VERY VERY VERBOSE bootstrap logging! Record this
    >(and it will be vast) and then search for your error message in the log.
    >This should help to pinpoint WHICH execlet (or driver) is in play when
    >this error is emitted. Don't assume it is the CD until you are certain
    >that it is the CD.


    That was very cool. (I don't spend a lot of time with the pre-SYSTARTUP_VMS
    parts of the startup, so seeing the early bits of the system load was really
    fun.)

    Tried it several times; died in different places each time.

    Took the CD to our PC support people; they tried to make an image copy and
    Nero reported unrecoverable read errors. So whatever else might be the
    case, I think I do definitely have a duff disc, and will try again to get a
    good one before bugging comp.os.vms again.

    Thanks to all for their suggestions and help!

    -- Alan


  11. Re: DS10: "failed to load execlet"?

    Alan Winston - SSRL Central Computing wrote:
    > In article , VAXman- @SendSpamHere.ORG writes:
    >> In article <00A7165D.408F7686@SSRL.SLAC.STANFORD.EDU>, winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) writes:
    >>>
    >>> VMSers --
    >>>
    >>> So I have a DS10 that I bought from Island and left in a box for
    >>> months. (We foolishly bought it without a video card, and then I was
    >>> fussing with an unsupported old card for too long, and now I have a
    >>> nice ATI card that succeeds in driving a VGA display with the
    >>> console.) Any warranty is already over.
    >>>
    >>> Console software is 7.2-1 with a 2006 date.
    >>>
    >>> The CD drive reports itself as CD-224E 9.9A and looks like the OEM
    >>> drive.
    >>>
    >>> When I attempt to boot from the CD (dqbo) it sees a boot block,
    >>> reports reading 1226 blocks from dqb0.0.1.13.0, goes through to
    >>> setting affinity, reports jumping to bootstrap code, and then
    >>> %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000054
    >>>
    >>> What's going on here? Do I have a CD drive problem? A CPU problem?
    >>> A duff copy of the OS? How do I tell?
    >>>
    >>> (If I need to MOP boot this puppy in order to be able to tell, can
    >>> somebody point me to a step-by-step guide? I've never done MOP for
    >>> anything but terminal servers and Xterms, and it's been a long time.)

    >> Alan,
    >>
    >> Try booting with B -fl 0,30000 (assuming your boot root is 0)
    >>
    >> This will enable some VERY VERY VERBOSE bootstrap logging! Record this
    >> (and it will be vast) and then search for your error message in the log.
    >> This should help to pinpoint WHICH execlet (or driver) is in play when
    >> this error is emitted. Don't assume it is the CD until you are certain
    >> that it is the CD.

    >
    > That was very cool. (I don't spend a lot of time with the pre-SYSTARTUP_VMS
    > parts of the startup, so seeing the early bits of the system load was really
    > fun.)
    >
    > Tried it several times; died in different places each time.
    >
    > Took the CD to our PC support people; they tried to make an image copy and
    > Nero reported unrecoverable read errors. So whatever else might be the
    > case, I think I do definitely have a duff disc, and will try again to get a
    > good one before bugging comp.os.vms again.
    >
    > Thanks to all for their suggestions and help!
    >
    > -- Alan
    >


    FWIW...

    I booted my XP900 (very similar to a DS10, I think) using the 8.2
    CD in the DQB0 device ("device type Compaq CRD-8402B,...").
    Had no particular problems and the system is running just fine
    on 8.2 right now. Sh CPU says "AlphaStation XP900 466 MHz".

    B.t.w, you wrote "dqbo" in your first post, should be "dqb0",
    right ?

    Jan-Erik.

  12. Re: DS10: "failed to load execlet"?

    In article , =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= writes:
    >Alan Winston - SSRL Central Computing wrote:
    >> In article , VAXman- @SendSpamHere.ORG writes:
    >>> Alan,
    >>>
    >>> Try booting with B -fl 0,30000 (assuming your boot root is 0)
    >>>
    >>> This will enable some VERY VERY VERBOSE bootstrap logging! Record this
    >>> (and it will be vast) and then search for your error message in the log.
    >>> This should help to pinpoint WHICH execlet (or driver) is in play when
    >>> this error is emitted. Don't assume it is the CD until you are certain
    >>> that it is the CD.

    >>
    >> That was very cool. (I don't spend a lot of time with the pre-SYSTARTUP_VMS
    >> parts of the startup, so seeing the early bits of the system load was really
    >> fun.)
    >>
    >> Tried it several times; died in different places each time.
    >>
    >> Took the CD to our PC support people; they tried to make an image copy and
    >> Nero reported unrecoverable read errors. So whatever else might be the
    >> case, I think I do definitely have a duff disc, and will try again to get a
    >> good one before bugging comp.os.vms again.
    >>
    >> Thanks to all for their suggestions and help!
    >>
    >> -- Alan
    >>

    >
    >FWIW...
    >
    >I booted my XP900 (very similar to a DS10, I think) using the 8.2
    >CD in the DQB0 device ("device type Compaq CRD-8402B,...").
    >Had no particular problems and the system is running just fine
    >on 8.2 right now. Sh CPU says "AlphaStation XP900 466 MHz".
    >
    >B.t.w, you wrote "dqbo" in your first post, should be "dqb0",
    >right ?
    >


    Yup, should have been dQbo.

    My newly burnt 8.3 CD copy works fine, and I was able to boot.
    I've installed 8.3, configured DECnet, typed in the DW-MOTIF
    license and have DECwindows up, so that's all good.

    It's kind of weird that in min boot / interactive session on
    console mode, the keyboard (a new seeming LK461-A2) stops working
    after some indeterminate amount of time.

    Other than that, I seem to be on the path to goodness.

    Thanks again to everybody!

    -- Alan



  13. Re: DS10: "failed to load execlet"?

    Alan Winston - SSRL Central Computing wrote:
    >>
    >> B.t.w, you wrote "dqbo" in your first post, should be "dqb0",
    >> right ?
    >>

    >
    > Yup, should have been dQbo.
    >


    :-)

    Jan-Erik.

+ Reply to Thread