muta...@gmail.com
2023-06-24 14:52:05 UTC
I am interested in 32-bit windows console mode
applications that are dependent on msvcrt.dll.
Basically simple C programs. I am using this as
an example:
2021-10-18 18:54 3,584 hexdump.exe
This ships with PDOS/386.
I know that it works with win95 so long as msvcrt.dll
is installed (it is on the win95 CDROM but is not installed
by default, but if you copy it across manually, it works
fine).
Now I want to know whether I can go back even further
and have it run on windows for workgroups 3.11 with
win32s installed.
I received wfw from ebay yesterday, and downloaded
pw1118.exe from a microsoft mirror and was able to
install win32s and run the demo program freecell.
This was done under qemu. The floppy disks I read
with a USB floppy disk and running pdos/386 and
the "copy" command to read drv0:
Running hexdump at an MSDOS prompt either before
running windows or after clicking on the msdos icon
reported that I needed to run windows (hexdump has
a custom message I created).
Using file manager and clicking on hexdump came up
with a nice error about msvcrt.dll not being found. I
produce my own as part of pdpclib so I copied that
across. Now clicking on hexdump doesn't do anything
that can be visibly seen.
No error about kernel32.dll not being found either, even
though it is a dependency yet doesn't appear on the
disk (must be recognized elsewhere).
Any suggestions on what I can do to see something
from hexdump? It is supposed to produce this:
C:\winpath>hexdump
Usage: HEXDUMP file_name [start] [length]
I suspect it is starting and finishing quickly, so what I
need is to run a shell. Rather than try to organize that,
I just added an fgets from stdin to see if it would stay
active so that I could see it.
However - still no. Still the same effect of clicking in
file manager just has a delay suggesting it is doing
some work, but it behaves as if nothing happened.
Any idea whether I can obtain output from this:
__stdout->hfile = GetStdHandle(STD_OUTPUT_HANDLE);
#define STD_OUTPUT_HANDLE ((DWORD)-11)
GetStdHandle must exist, otherwise msvcrt.dll
would have failed to load (presumably, anyway).
But it apparently has nowhere to go.
I'm happy with any solution that doesn't alter hexdump.exe
itself. ie the physical executable on disk.
Thanks. Paul.
applications that are dependent on msvcrt.dll.
Basically simple C programs. I am using this as
an example:
2021-10-18 18:54 3,584 hexdump.exe
This ships with PDOS/386.
I know that it works with win95 so long as msvcrt.dll
is installed (it is on the win95 CDROM but is not installed
by default, but if you copy it across manually, it works
fine).
Now I want to know whether I can go back even further
and have it run on windows for workgroups 3.11 with
win32s installed.
I received wfw from ebay yesterday, and downloaded
pw1118.exe from a microsoft mirror and was able to
install win32s and run the demo program freecell.
This was done under qemu. The floppy disks I read
with a USB floppy disk and running pdos/386 and
the "copy" command to read drv0:
Running hexdump at an MSDOS prompt either before
running windows or after clicking on the msdos icon
reported that I needed to run windows (hexdump has
a custom message I created).
Using file manager and clicking on hexdump came up
with a nice error about msvcrt.dll not being found. I
produce my own as part of pdpclib so I copied that
across. Now clicking on hexdump doesn't do anything
that can be visibly seen.
No error about kernel32.dll not being found either, even
though it is a dependency yet doesn't appear on the
disk (must be recognized elsewhere).
Any suggestions on what I can do to see something
from hexdump? It is supposed to produce this:
C:\winpath>hexdump
Usage: HEXDUMP file_name [start] [length]
I suspect it is starting and finishing quickly, so what I
need is to run a shell. Rather than try to organize that,
I just added an fgets from stdin to see if it would stay
active so that I could see it.
However - still no. Still the same effect of clicking in
file manager just has a delay suggesting it is doing
some work, but it behaves as if nothing happened.
Any idea whether I can obtain output from this:
__stdout->hfile = GetStdHandle(STD_OUTPUT_HANDLE);
#define STD_OUTPUT_HANDLE ((DWORD)-11)
GetStdHandle must exist, otherwise msvcrt.dll
would have failed to load (presumably, anyway).
But it apparently has nowhere to go.
I'm happy with any solution that doesn't alter hexdump.exe
itself. ie the physical executable on disk.
Thanks. Paul.