• Re: Booting process 0: how to find out its full path?

    From Mateusz Viste@mateusz@xyz.invalid to comp.os.msdos.programmer on Tue Nov 16 20:46:01 2021
    From Newsgroup: comp.os.msdos.programmer

    2021-11-16 at 18:49 -0000, Auric__ wrote:
    The MS-DOS 2.0 source code is on Github, where you might look into
    the file SYSINIT.ASM, available here:

    https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/SYSINIT.ASM

    Actually I did glance at the MS-DOS 2.0 code already, and my
    understanding is that they didn't even try addressing this, just relied
    on COMSPEC (if defined, either through SET or by feeding it as an
    argument to command.com), and if no COMSPEC then using the default
    location.

    That sounds okay when it's MS that does it, because it's their OS, but
    an alternative shell does not have this luxury.

    HACK: when 4DOS.COM is the shell and it doesn't have an environment
    from which to obtain its original program name, it grovels through
    all of memory to find the filename that was used to exec it; it
    wants to find the SHELL= line in the in-memory copy of CONFIG.SYS,
    and it knows that sysinit converts the SHELL= keyword to an 'S', so
    it expects to find an 'S' immediately before the filename, but since
    we are now storing line # info in the config.sys memory image, 4DOS
    fails to find the 'S' in the right spot.
    So, on the final pass of CONFIG.SYS, copy the command code (eg, 'S')
    over the line number info, since we no longer need that info anyway.
    This relies on the fact that getchr leaves ES:SI pointing to the
    last byte retrieved.

    That is very interesting indeed, thanks for sharing! This at least
    confirms that there is no "clean" way to do what I wanted... So I will
    probably give up on that. MS compatibility was only a bonus, my primary
    target is working with the DOS-C kernel, and there I do not have any
    such problems.

    Nonetheless, thank you for your kind research.

    As for other flavors of DOS, most of them are open source, so I think
    it would be worth it to download some source code and search for
    "shell".

    Under DOS-C it is a no-brainer: the kernel actually allocates a tiny
    (96 bytes) environment and passes it to COMMAND.COM. There, the entire
    path is present.

    Mateusz

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From JJ@jj4public@gmail.com to comp.os.msdos.programmer on Wed Nov 17 08:23:43 2021
    From Newsgroup: comp.os.msdos.programmer

    On Tue, 16 Nov 2021 10:44:16 +0100, Mateusz Viste wrote:
    Hello,

    I am working on a shell that would replace COMMAND.COM and I wonder: is
    there any way I can figure out where my shell is, once it is executed
    by the MS-DOS kernel?

    By default MS-DOS launches whatever it finds at [BOOTDRV]:\COMMAND.COM.
    This situation is easy, but there is also the possibility that the shell
    was configured through a "SHELL" or "SHELLHIGH" CONFIG.SYS directive: SHELL=X:\EXOTIC\PATH\CUSTOM.COM

    I am unable to find a way to discover the above path. Any ideas if this
    is feasible at all? I went through RBIL but with no luck so far.

    The environment contains the full path/name of the executed program,
    but this does not apply to process 0, as the MS-DOS kernel does not
    allocate any environment for it (env segment in PSP = 0x0000).

    Mateusz

    You may want to walk the MCB chain to find the master environment block.
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Mateusz Viste@mateusz@xyz.invalid to comp.os.msdos.programmer on Wed Nov 17 09:11:09 2021
    From Newsgroup: comp.os.msdos.programmer

    2021-11-17 at 08:23 +0700, JJ wrote:
    On Tue, 16 Nov 2021 10:44:16 +0100, Mateusz Viste wrote:
    Hello,

    I am working on a shell that would replace COMMAND.COM and I
    wonder: is there any way I can figure out where my shell is, once
    it is executed by the MS-DOS kernel?

    By default MS-DOS launches whatever it finds at
    [BOOTDRV]:\COMMAND.COM. This situation is easy, but there is also
    the possibility that the shell was configured through a "SHELL" or "SHELLHIGH" CONFIG.SYS directive: SHELL=X:\EXOTIC\PATH\CUSTOM.COM

    I am unable to find a way to discover the above path. Any ideas if
    this is feasible at all? I went through RBIL but with no luck so
    far.

    The environment contains the full path/name of the executed program,
    but this does not apply to process 0, as the MS-DOS kernel does not allocate any environment for it (env segment in PSP = 0x0000).

    Mateusz

    You may want to walk the MCB chain to find the master environment
    block.

    No, because such an environment simply does not exists at the time
    process 0 is being loaded.

    Mateusz

    --- Synchronet 3.21d-Linux NewsLink 1.2