OS2COM issues - OS2

This is a discussion on OS2COM issues - OS2 ; _____ Hello All OS/2 Users, I have recently reinstalled OS/2 Warp V4 on a modest i586 server box, then added fixpack 15. Installed OS2COM (Norton Commander clone) from OS2C-124.EXE found in one of my old archives. PROBLEM: OS2COM will come ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: OS2COM issues

  1. OS2COM issues

    _____
    Hello All OS/2 Users,

    I have recently reinstalled OS/2 Warp V4 on a modest i586 server box,
    then added fixpack 15. Installed OS2COM (Norton Commander clone) from
    OS2C-124.EXE found in one of my old archives.

    PROBLEM:
    OS2COM will come up fine in OS/2 or 4OS2 shell window. On the command
    line at the bottom of the OS2COM screen i get a string of upper case "D"
    letters as if i am holding down the "D" key. Eventually the keyboard
    buffer fills up and the speaker begins to complain. Hitting
    clears the buffer, then the "D"s come back. OS2COM in a window is
    essentially useless with this behaviour. The program runs correctly in
    full screen mode! No "D"s appear. On a virgin OS/2 install (no
    fixpacks) the OS2COM program runs fine. No "D"s appear.

    QUESTION:
    Is this a known problem that is caused by fixpack 15? If yes, what does
    one do to solve the problem?
    --
    Regards / JCH

  2. Re: OS2COM issues

    Sir:

    jch wrote:
    > _____
    > Hello All OS/2 Users,
    >
    > I have recently reinstalled OS/2 Warp V4 on a modest i586 server box,
    > then added fixpack 15. Installed OS2COM (Norton Commander clone) from
    > OS2C-124.EXE found in one of my old archives.
    >
    > PROBLEM:
    > OS2COM will come up fine in OS/2 or 4OS2 shell window. On the command
    > line at the bottom of the OS2COM screen i get a string of upper case "D"
    > letters as if i am holding down the "D" key. Eventually the keyboard
    > buffer fills up and the speaker begins to complain. Hitting
    > clears the buffer, then the "D"s come back. OS2COM in a window is
    > essentially useless with this behaviour. The program runs correctly in
    > full screen mode! No "D"s appear. On a virgin OS/2 install (no
    > fixpacks) the OS2COM program runs fine. No "D"s appear.
    >
    > QUESTION:
    > Is this a known problem that is caused by fixpack 15? If yes, what does
    > one do to solve the problem?

    I am going to suggest that you update the kernel to one of the latest,
    either 14.100c or 14.103a
    . Also get dd02
    installed, then update the os2dasd.dmd, etc. as shown on Oliver Rick's
    site . The kernel is the fix.
    --
    Bill
    Thanks a Million!

  3. Re: OS2COM issues

    William L. Hartzell wrote:
    > Sir:
    >
    > jch wrote:
    >> _____
    >> Hello All OS/2 Users,
    >>
    >> I have recently reinstalled OS/2 Warp V4 on a modest i586 server box,
    >> then added fixpack 15. Installed OS2COM (Norton Commander clone) from
    >> OS2C-124.EXE found in one of my old archives.
    >>
    >> PROBLEM:
    >> OS2COM will come up fine in OS/2 or 4OS2 shell window. On the command
    >> line at the bottom of the OS2COM screen i get a string of upper case
    >> "D" letters as if i am holding down the "D" key. Eventually the
    >> keyboard buffer fills up and the speaker begins to complain. Hitting
    >> clears the buffer, then the "D"s come back. OS2COM in a
    >> window is essentially useless with this behaviour. The program runs
    >> correctly in full screen mode! No "D"s appear. On a virgin OS/2
    >> install (no fixpacks) the OS2COM program runs fine. No "D"s appear.
    >>
    >> QUESTION:
    >> Is this a known problem that is caused by fixpack 15? If yes, what
    >> does one do to solve the problem?

    > I am going to suggest that you update the kernel to one of the latest,
    > either 14.100c or 14.103a
    > . Also get dd02
    > installed, then update the os2dasd.dmd, etc. as shown on Oliver Rick's
    > site . The kernel is the fix.

    _____
    William,

    Thanks very much for this. Will give it a go this weekend, and report back.
    --
    Regards / JCH

  4. Re: OS2COM issues

    William L. Hartzell wrote:
    > Sir:
    >
    > jch wrote:
    >
    >> _____
    >> Hello All OS/2 Users,
    >>
    >> I have recently reinstalled OS/2 Warp V4 on a modest i586 server box,
    >> then added fixpack 15. Installed OS2COM (Norton Commander clone) from
    >> OS2C-124.EXE found in one of my old archives.
    >>
    >> PROBLEM:
    >> OS2COM will come up fine in OS/2 or 4OS2 shell window. On the command
    >> line at the bottom of the OS2COM screen i get a string of upper case
    >> "D" letters as if i am holding down the "D" key. Eventually the
    >> keyboard buffer fills up and the speaker begins to complain. Hitting
    >> clears the buffer, then the "D"s come back. OS2COM in a
    >> window is essentially useless with this behaviour. The program runs
    >> correctly in full screen mode! No "D"s appear. On a virgin OS/2
    >> install (no fixpacks) the OS2COM program runs fine. No "D"s appear.
    >>
    >> QUESTION:
    >> Is this a known problem that is caused by fixpack 15? If yes, what
    >> does one do to solve the problem?

    >
    > I am going to suggest that you update the kernel to one of the latest,
    > either 14.100c or 14.103a
    > . Also get dd02
    > installed, then update the os2dasd.dmd, etc. as shown on Oliver Rick's
    > site . The kernel is the fix.


    While I agree in general that it is good to keep these things up to
    date, things like DASD drivers have NOTHING to do with a keyboard
    interface for a VIO app in a window. There's a chance that the kernel
    will help, but let's not tell him something that might introduce
    problems into his system and offer a 0% chance at solving his original
    problem!

    --
    [Reverse the parts of the e-mail address to reply.]

  5. Re: OS2COM issues

    jch wrote:
    > William L. Hartzell wrote:
    >> Sir:
    >>
    >> jch wrote:
    >>> _____
    >>> Hello All OS/2 Users,
    >>>
    >>> I have recently reinstalled OS/2 Warp V4 on a modest i586 server box,
    >>> then added fixpack 15. Installed OS2COM (Norton Commander clone)
    >>> from OS2C-124.EXE found in one of my old archives.
    >>>
    >>> PROBLEM:
    >>> OS2COM will come up fine in OS/2 or 4OS2 shell window. On the
    >>> command line at the bottom of the OS2COM screen i get a string of
    >>> upper case "D" letters as if i am holding down the "D" key.
    >>> Eventually the keyboard buffer fills up and the speaker begins to
    >>> complain. Hitting clears the buffer, then the "D"s come
    >>> back. OS2COM in a window is essentially useless with this
    >>> behaviour. The program runs correctly in full screen mode! No "D"s
    >>> appear. On a virgin OS/2 install (no fixpacks) the OS2COM program
    >>> runs fine. No "D"s appear.
    >>>
    >>> QUESTION:
    >>> Is this a known problem that is caused by fixpack 15? If yes, what
    >>> does one do to solve the problem?

    >> I am going to suggest that you update the kernel to one of the latest,
    >> either 14.100c or 14.103a
    >> . Also get dd02
    >> installed, then update the os2dasd.dmd, etc. as shown on Oliver Rick's
    >> site . The kernel is the fix.

    > _____
    > William,
    >
    > Thanks very much for this. Will give it a go this weekend, and report
    > back.

    _____
    Installed kernel version 14.100c. System runs fine, but problem with
    OS2COM program was NOT fixed. Still getting "D" characters in command
    line running VIO application mode. Will try kernel 14.103a next.
    --
    Regards / JCH

  6. Re: OS2COM issues

    jch wrote:

    >>> QUESTION:
    >>> Is this a known problem that is caused by fixpack 15? If yes, what
    >>> does one do to solve the problem?

    >> I am going to suggest that you update the kernel to one of the latest,
    >> either 14.100c or 14.103a
    >> . Also get dd02
    >> installed, then update the os2dasd.dmd, etc. as shown on Oliver Rick's
    >> site . The kernel is the fix.

    > _____
    > William,
    >
    > Thanks very much for this. Will give it a go this weekend, and report
    > back.

    _____
    Installed kernel version 14.104a_W4. System runs fine, but problem with
    OS2COM was _not_ resolved. Anybody have some more ideas?
    --
    Regards / JCH

  7. Re: OS2COM issues

    Sir:

    jch wrote:
    > jch wrote:
    >
    >>>> QUESTION:
    >>>> Is this a known problem that is caused by fixpack 15? If yes, what
    >>>> does one do to solve the problem?
    >>> I am going to suggest that you update the kernel to one of the
    >>> latest, either 14.100c or 14.103a
    >>> . Also get dd02
    >>> installed, then update the os2dasd.dmd, etc. as shown on Oliver
    >>> Rick's site . The kernel is
    >>> the fix.

    >> _____
    >> William,
    >>
    >> Thanks very much for this. Will give it a go this weekend, and report
    >> back.

    > _____
    > Installed kernel version 14.104a_W4. System runs fine, but problem with
    > OS2COM was _not_ resolved. Anybody have some more ideas?

    Try this later version
    .
    --
    Bill
    Thanks a Million!

  8. Re: OS2COM issues

    William L. Hartzell wrote:

    >> Installed kernel version 14.104a_W4. System runs fine, but problem
    >> with OS2COM was _not_ resolved. Anybody have some more ideas?

    > Try this later version
    > .

    _____
    Although that is not quite what i had in mind, i installed it, and it
    works fine. Thanks for the tip.
    --
    Regards / JCH

+ Reply to Thread