OS2LDR latest one causing problems? - OS2

This is a discussion on OS2LDR latest one causing problems? - OS2 ; Just upgraded the kernel to the latest level (14.104a) and it appears from what I can fathom OS2ldr is causing a problem with DOSCALL1 ending in an access violation on boot. The machine has 2048 MB Ram and booted fine ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: OS2LDR latest one causing problems?

  1. OS2LDR latest one causing problems?

    Just upgraded the kernel to the latest level (14.104a) and it appears
    from what I can fathom OS2ldr is causing a problem with DOSCALL1 ending
    in an access violation on boot. The machine has 2048 MB Ram and booted
    fine with 512MB. I found reference to patching the OS2LDR but nothing
    to explain if later versions have the same problem. Can anyone help me
    out here?

    Craig


  2. Re: OS2LDR latest one causing problems?

    On 1 Oct 2006 01:10:10 -0700, "Craig" wrote:

    >Just upgraded the kernel to the latest level (14.104a) and it appears
    >from what I can fathom OS2ldr is causing a problem with DOSCALL1 ending
    >in an access violation on boot. The machine has 2048 MB Ram and booted
    >fine with 512MB. I found reference to patching the OS2LDR but nothing
    >to explain if later versions have the same problem. Can anyone help me
    >out here?
    >
    >Craig


    My MCP2 with P4 3.2GHz and 2 GB RAM works fine
    with the combination of following OS2*:

    [C:\]dir os2*.*

    Datenträger, Laufwerk C, hat den Namen MCP3SYS.
    Datenträgernummer ist 697E:E015
    Verzeichnis von C:\

    30.06.06 14.08 8564 OS2
    11.08.05 11.48 846708 54 OS2KRNL
    29.12.04 11.32 849353 54 os2krnl.sav
    11.08.05 11.50 849262 271 os2krnl.w45
    16.06.05 15.18 44544 0 OS2LDR
    29.12.04 12.19 44544 0 os2ldr.sav
    17.06.05 14.10 44544 220 os2ldr.w45
    7 Datei(en) 2678955 Byte belegt
    21863412 K Byte frei


  3. Re: OS2LDR latest one causing problems?

    Hi Craig

    Craig wrote:
    > Just upgraded the kernel to the latest level (14.104a) and it appears
    > from what I can fathom OS2ldr is causing a problem with DOSCALL1 ending
    > in an access violation on boot. The machine has 2048 MB Ram and booted
    > fine with 512MB. I found reference to patching the OS2LDR but nothing
    > to explain if later versions have the same problem. Can anyone help me
    > out here?
    >
    > Craig
    >



    Try reverting to kernel 14.103a and see if that clears the problem.

    It seems there may be some problems with 14.104 on some systems - read
    somewhere that is why eCS use 14.103 in their current release.

    Regards

    Pete

  4. Re: OS2LDR latest one causing problems?


    Peter Brown wrote:

    > Try reverting to kernel 14.103a and see if that clears the problem.
    >
    > It seems there may be some problems with 14.104 on some systems - read
    > somewhere that is why eCS use 14.103 in their current release.



    Hi Pete,
    No dice on that one. Might have to try different combinations. Seems
    the OS2LDR file hasn't changed size for some time but the Kernel files
    are showing significant changes. Hmmm.....

    Craig


  5. Re: OS2LDR latest one causing problems?


    Rainer Doering wrote:
    > On 1 Oct 2006 01:10:10 -0700, "Craig" wrote:
    >
    >
    > My MCP2 with P4 3.2GHz and 2 GB RAM works fine
    > with the combination of following OS2*:
    >
    > [C:\]dir os2*.*
    >
    > Datenträger, Laufwerk C, hat den Namen MCP3SYS.
    > Datenträgernummer ist 697E:E015
    > Verzeichnis von C:\
    >
    > 30.06.06 14.08
    8564 OS2
    > 11.08.05 11.48 846708 54 OS2KRNL
    > 29.12.04 11.32 849353 54 os2krnl.sav
    > 11.08.05 11.50 849262 271 os2krnl.w45
    > 16.06.05 15.18 44544 0 OS2LDR
    > 29.12.04 12.19 44544 0 os2ldr.sav
    > 17.06.05 14.10 44544 220 os2ldr.w45
    >

    Hi Rainer,
    My files are different dates and sizes. OS2LDR is the same size but
    your kernel is quite different. Did you patch it at all? Would you
    send your OS2KRNL and OS2LDR files to me please?
    benbowc@attglobal.net

    Craig


  6. Re: OS2LDR latest one causing problems?

    In <1159690210.813101.132810@i42g2000cwa.googlegroups. com>, on 10/01/2006
    at 01:10 AM, "Craig" said:

    >Just upgraded the kernel to the latest level (14.104a) and it appears
    >from what I can fathom OS2ldr is causing a problem with DOSCALL1 ending
    >in an access violation on boot. The machine has 2048 MB Ram and booted
    >fine with 512MB. I found reference to patching the OS2LDR but nothing to
    >explain if later versions have the same problem. Can anyone help me out
    >here?


    I suspect the doscall1 trap a vdos driver trapping. You might try
    excphead.sys. This will not prevent the trap, but will tell you what is
    trapping. I don't have a link handy, but a Google for excphead.sys should
    find one.

    Since you are basically still running W4/FP15, what you may need to do is
    use to old os2ldr and Dani's patch to get it to detect all your RAM.
    Google for patchldr on hobbes.

    Of course, if you actually want detailed recommendations you are going to
    have to post some actual details regarding the kernel trap. Otherwise,
    everyone including me will just be providing general guidelines.

    Steven

    --
    --------------------------------------------------------------------------------------------
    Steven Levine MR2/ICE 2.67 #10183
    Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
    --------------------------------------------------------------------------------------------


  7. Re: OS2LDR latest one causing problems?


    Steven Levine wrote:

    Hi Steven,

    >
    > I suspect the doscall1 trap a vdos driver trapping. You might try
    > excphead.sys. This will not prevent the trap, but will tell you what is
    > trapping. I don't have a link handy, but a Google for excphead.sys should
    > find one.


    Sorry its taken a while to get to this again.....
    I put excphead.sys in and got a trap but in something else!
    Don't have the Popuplog.os2 entry for that but the trap screen is this:

    c0000005
    P1=00000008 P2=0000da9c P3=XXXXXXXX P4=XXXXXXXX
    EAX=00000000 EBX=00b50000 ECX=000005da EDX=bfeb9f45
    ESI=ffde0100 EDI=febf43f8
    DS=0000 DSACC=**** DSLIM=********
    ES=0130 ESACC=00f3 ESLIM=0000571f
    FS=0000 FSACC=**** FSLIM=********
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=09d3:00000124 CSACC=009f CSLIM=00000c7d
    SS:ESP=001f:00000f76 SSACC=00f3 SSLIM=00000fff
    EBP=00000000 FLG=00213246

    >
    > Since you are basically still running W4/FP15, what you may need to do is
    > use to old os2ldr and Dani's patch to get it to detect all your RAM.
    > Google for patchldr on hobbes.


    I'll try that next if no ideas come from this.
    >
    > Of course, if you actually want detailed recommendations you are going to
    > have to post some actual details regarding the kernel trap. Otherwise,
    > everyone including me will just be providing general guidelines.


    You asked for them:
    10-01-2006 10:24:31 SYS3171 PID 0001 TID 0006 Slot 0006
    sysinit
    c0000005
    1c02a455
    P1=00000001 P2=00000004 P3=XXXXXXXX P4=XXXXXXXX
    EAX=000300d2 EBX=00000000 ECX=000300c2 EDX=bfeb9f45
    ESI=ffde0100 EDI=febf43f8
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:1c02a455 CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:000300b2 SSACC=d0f3 SSLIM=3fffffff
    EBP=000300da FLG=00213202

    DOSCALL1.DLL 0002:0000a455

    ------------------------------------------------------------

    10-02-2006 13:25:49 SYS3171 PID 0001 TID 0006 Slot 0006
    sysinit
    c0000005
    1c02a455
    P1=00000001 P2=00000004 P3=XXXXXXXX P4=XXXXXXXX
    EAX=000300d2 EBX=00000000 ECX=000300c2 EDX=bfeb9f45
    ESI=ffde0100 EDI=febf43f8
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:1c02a455 CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:000300b2 SSACC=d0f3 SSLIM=3fffffff
    EBP=000300da FLG=00213202

    DOSCALL1.DLL 0002:0000a455

    Hope you can help,

    Craig


  8. Re: OS2LDR latest one causing problems?

    Hi Craig

    Craig wrote:
    > Steven Levine wrote:
    >
    > Hi Steven,
    >
    >> I suspect the doscall1 trap a vdos driver trapping. You might try
    >> excphead.sys. This will not prevent the trap, but will tell you what is
    >> trapping. I don't have a link handy, but a Google for excphead.sys should
    >> find one.

    >
    > Sorry its taken a while to get to this again.....
    > I put excphead.sys in and got a trap but in something else!
    > Don't have the Popuplog.os2 entry for that but the trap screen is this:
    >
    > c0000005
    > P1=00000008 P2=0000da9c P3=XXXXXXXX P4=XXXXXXXX
    > EAX=00000000 EBX=00b50000 ECX=000005da EDX=bfeb9f45
    > ESI=ffde0100 EDI=febf43f8
    > DS=0000 DSACC=**** DSLIM=********
    > ES=0130 ESACC=00f3 ESLIM=0000571f
    > FS=0000 FSACC=**** FSLIM=********
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=09d3:00000124 CSACC=009f CSLIM=00000c7d
    > SS:ESP=001f:00000f76 SSACC=00f3 SSLIM=00000fff
    > EBP=00000000 FLG=00213246
    >
    >> Since you are basically still running W4/FP15, what you may need to do is
    >> use to old os2ldr and Dani's patch to get it to detect all your RAM.
    >> Google for patchldr on hobbes.

    >
    > I'll try that next if no ideas come from this.
    >> Of course, if you actually want detailed recommendations you are going to
    >> have to post some actual details regarding the kernel trap. Otherwise,
    >> everyone including me will just be providing general guidelines.

    >
    > You asked for them:
    > 10-01-2006 10:24:31 SYS3171 PID 0001 TID 0006 Slot 0006
    > sysinit
    > c0000005
    > 1c02a455
    > P1=00000001 P2=00000004 P3=XXXXXXXX P4=XXXXXXXX
    > EAX=000300d2 EBX=00000000 ECX=000300c2 EDX=bfeb9f45
    > ESI=ffde0100 EDI=febf43f8
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:1c02a455 CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:000300b2 SSACC=d0f3 SSLIM=3fffffff
    > EBP=000300da FLG=00213202
    >
    > DOSCALL1.DLL 0002:0000a455
    >
    > ------------------------------------------------------------
    >
    > 10-02-2006 13:25:49 SYS3171 PID 0001 TID 0006 Slot 0006
    > sysinit
    > c0000005
    > 1c02a455
    > P1=00000001 P2=00000004 P3=XXXXXXXX P4=XXXXXXXX
    > EAX=000300d2 EBX=00000000 ECX=000300c2 EDX=bfeb9f45
    > ESI=ffde0100 EDI=febf43f8
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:1c02a455 CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:000300b2 SSACC=d0f3 SSLIM=3fffffff
    > EBP=000300da FLG=00213202
    >
    > DOSCALL1.DLL 0002:0000a455
    >
    > Hope you can help,
    >
    > Craig
    >



    I know where I have seen similar to the above: Have you applied fixpack5
    to an MCP or eCS system?

    I ask because the above results are very similar to those I got after
    applying fixpack5 to eCS1.1

    The cure was to backlevel pmmerge.dll and orexx.dll if I remember
    correctly - eCS actually have an "update" that can be applied by eCSMT
    to perform the backlevel so it was not just my systems affected.

    Also, as mentioned previously, eCS seem to have "standardised" on the
    14.103 kernel pack but I do not know if that is related...

    Regards

    Pete

  9. Re: OS2LDR latest one causing problems?

    In <1160120474.585594.262830@i3g2000cwc.googlegroups.c om>, on 10/06/2006
    at 12:41 AM, "Craig" said:

    >Sorry its taken a while to get to this again.....


    No problem. :-)

    >I put excphead.sys in and got a trap but in something else!


    That's what happens when the orginal trap is why excphead was built.

    >Don't have the Popuplog.os2 entry for that but the trap screen is this:


    You shouldn't. You still have a ring0 trap. The trap screen now reports
    the original trap address.

    >c0000005
    >P1=00000008 P2=0000da9c P3=XXXXXXXX P4=XXXXXXXX
    >EAX=00000000 EBX=00b50000 ECX=000005da EDX=bfeb9f45
    >ESI=ffde0100 EDI=febf43f8
    >DS=0000 DSACC=**** DSLIM=********
    >ES=0130 ESACC=00f3 ESLIM=0000571f
    >FS=0000 FSACC=**** FSLIM=********
    >GS=0000 GSACC=**** GSLIM=********
    >CS:EIP=09d3:00000124 CSACC=009f CSLIM=00000c7d
    >SS:ESP=001f:00000f76 SSACC=00f3 SSLIM=00000fff
    >EBP=00000000 FLG=00213246


    You need to figure out which driver is associated with the reported
    cs:eip. I usually just look at the trap dump file with pmdf or use
    Theseus, if the trap is intermittent.

    An alternative is exeinfo, which should be on Hobbes.

    You would run is as

    exeinfo -f -lc7f \os2\boot\*

    On this box, it claims that testcfg.sys matches. Since either you never
    mentioned what CPU you were running or I missed it, if you are running an
    Athlon64, you should should look at

    http://www.os2voice.org/VNL/past_iss...4H/vnewsft.htm

    If not, you should still rem out testcfg.sys and see what happens.

    Steven

    --
    --------------------------------------------------------------------------------------------
    Steven Levine MR2/ICE 2.67 #10183
    Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
    --------------------------------------------------------------------------------------------


+ Reply to Thread