Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
MSVC 1.5 does not work anymore in Windows 10 build 18342
206 views
Skip to first unread message
Jean-Francois Larvoire
Mar 11, 2019, 11:08:10 AM3/11/19
to
I've always been using MSVC 1.5 to build DOS apps, and this worked in
all versions of Windows until now. (The MSVC 1.5 C compiler and linker
are WIN32 apps, even if they build DOS apps that do not run in Windows.)
But last week, my version of Windows 10 got upgraded to build 18342, and
MSVC 1.5 executables don't work anymore. :-(
cl.exe silently fails after a few seconds.
link.exe displays an error:
C:\MSVC\BIN>link /?
Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
LINK : fatal error L5000 : internal failure - access violation
C:\MSVC\BIN>
I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
introduced an incompatible change.
Anybody else still using MSVC 1.5?
Any fix already available?
Else any idea on how to debug this?
Jean-François
all versions of Windows until now. (The MSVC 1.5 C compiler and linker
are WIN32 apps, even if they build DOS apps that do not run in Windows.)
But last week, my version of Windows 10 got upgraded to build 18342, and
MSVC 1.5 executables don't work anymore. :-(
cl.exe silently fails after a few seconds.
link.exe displays an error:
C:\MSVC\BIN>link /?
Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
LINK : fatal error L5000 : internal failure - access violation
C:\MSVC\BIN>
I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
introduced an incompatible change.
Anybody else still using MSVC 1.5?
Any fix already available?
Else any idea on how to debug this?
Jean-François
T. Ment
Mar 11, 2019, 12:42:59 PM3/11/19
to
On Mon, 11 Mar 2019 16:08:09 +0100, Jean-Francois Larvoire
<jf.la...@free.fr> wrote:
>I've always been using MSVC 1.5 to build DOS apps, and this worked in
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>But last week, my version of Windows 10 got upgraded to build 18342, and
>MSVC 1.5 executables don't work anymore. :-(
>cl.exe silently fails after a few seconds.
>link.exe displays an error:
Microsoft C 7.00 requires DPMI for command line executables. I don't
<jf.la...@free.fr> wrote:
>I've always been using MSVC 1.5 to build DOS apps, and this worked in
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>But last week, my version of Windows 10 got upgraded to build 18342, and
>MSVC 1.5 executables don't work anymore. :-(
>cl.exe silently fails after a few seconds.
>link.exe displays an error:
have MSVC 1.5 installed to look at, are they really WIN32 and not DOS
DPMI?
If your Win10 is 64-bit I suppose they must be.
Sjouke Burry
Mar 11, 2019, 1:12:43 PM3/11/19
to
Ross Ridge
Mar 11, 2019, 2:53:09 PM3/11/19
to
Jean-Francois Larvoire <jf.la...@free.fr> wrote:
>I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
>introduced an incompatible change.
If a DLL was missing you'd get an error saying so, but Microsoft has
>I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
>introduced an incompatible change.
broken MSVCRT.DLL compatibility before so that could be a problem.
You can try using compatibility mode on it to see if that fixes the
problem. Finding an old version of MSVCRT.DLL and sticking in the same
directory as the executable might also work, assuming that's the problem.
You might also see if you can't find the Windows XP DDK (Device Driver
Kit) anywhere. It has an updated version of the segmented linker and
maybe the compiler as well.
--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] rri...@csclub.uwaterloo.ca
-()-/()/ http://www.csclub.uwaterloo.ca/~rridge/
db //
T. Ment
Mar 11, 2019, 5:00:18 PM3/11/19
to
>I've always been using MSVC 1.5 to build DOS apps, and this worked in
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>link.exe displays an error:
>
>C:\MSVC\BIN>link /?
>
>Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
>LINK : fatal error L5000 : internal failure - access violation
>C:\MSVC\BIN>
>I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
>introduced an incompatible change.
I installed MSVC 1.5 to have a look.
>
>C:\MSVC\BIN>link /?
>
>Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
>LINK : fatal error L5000 : internal failure - access violation
>C:\MSVC\BIN>
>I suppose that the upgrade removed a DLL that MSVC 1.5 depends on, or
>introduced an incompatible change.
My link.exe version is 5.60.339 Dec 5 1994, same as yours. These are
not WIN32 apps, they are 32-bit DPMI, you can see "Phar Lap" in each
executable. They work on DOS or Windows 3.1, and later Windows versions
which support DPMI in a DOS command prompt.
You must be using 32-bit Windows, given the link.exe version string you
posted above. I've heard Microsoft broke DPMI support, so you may be out
of luck with Windows 10.
You might try Microsoft C 6.00a. It does not require DPMI.
Maxe
Mar 15, 2019, 8:51:29 PM3/15/19
to
Jean-Francois Larvoire wrote:
> I've always been using MSVC 1.5 to build DOS apps ...
me too. msvc is good, but msc6.0a is more stable, but you know that
better than me.
> ...The MSVC 1.5 C compiler and linker ...
IIRC, msvc link is a pharlap executable (dpmi) and msvc 1.52 and
components needs a full compatible win3x environment, last seen in
virtual xp machine under win7.
> Anybody else still using MSVC 1.5?
yes!
> Any fix already available?
I assume know.
> Else any idea on how to debug this?
unfortunately no.
> I've always been using MSVC 1.5 to build DOS apps ...
me too. msvc is good, but msc6.0a is more stable, but you know that
better than me.
> ...The MSVC 1.5 C compiler and linker ...
IIRC, msvc link is a pharlap executable (dpmi) and msvc 1.52 and
components needs a full compatible win3x environment, last seen in
virtual xp machine under win7.
> Anybody else still using MSVC 1.5?
> Any fix already available?
I assume know.
> Else any idea on how to debug this?
Steve Nickolas
Mar 15, 2019, 9:51:02 PM3/15/19
to
On Sat, 16 Mar 2019, Maxe wrote:
> Jean-Francois Larvoire wrote:
>
>> I've always been using MSVC 1.5 to build DOS apps ...
>
> me too. msvc is good, but msc6.0a is more stable, but you know that
> better than me.
>
>> ...The MSVC 1.5 C compiler and linker ...
>
> IIRC, msvc link is a pharlap executable (dpmi) and msvc 1.52 and
> components needs a full compatible win3x environment, last seen in
> virtual xp machine under win7.
>
>> Anybody else still using MSVC 1.5?
>
> yes!
>
>> Any fix already available?
>
> I assume know.
<snip>
> Jean-Francois Larvoire wrote:
>
>> I've always been using MSVC 1.5 to build DOS apps ...
>
> me too. msvc is good, but msc6.0a is more stable, but you know that
> better than me.
>
>> ...The MSVC 1.5 C compiler and linker ...
>
> IIRC, msvc link is a pharlap executable (dpmi) and msvc 1.52 and
> components needs a full compatible win3x environment, last seen in
> virtual xp machine under win7.
>
>> Anybody else still using MSVC 1.5?
>
> yes!
>
>> Any fix already available?
>
> I assume know.
I wonder if this would help any ;p, or if it still needs work.
I don't use VC, I prefer Borland. But anyway, I've run some Win3.x apps
with it and it's actively under development.
https://github.com/otya128/winevdm/releases/
-uso.
T. Ment
Mar 16, 2019, 2:00:58 PM3/16/19
to
>I've always been using MSVC 1.5 to build DOS apps, and this worked in
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>But last week, my version of Windows 10 got upgraded to build 18342, and
>MSVC 1.5 executables don't work anymore. :-(
>Any fix already available?
>all versions of Windows until now. (The MSVC 1.5 C compiler and linker
>are WIN32 apps, even if they build DOS apps that do not run in Windows.)
>But last week, my version of Windows 10 got upgraded to build 18342, and
>MSVC 1.5 executables don't work anymore. :-(
While searching for something else, I found this:
> I believe there is a shim in recent versions of Windows limiting the
> available DPMI memory to 32 MB, for yet more ancient software incapable
> of unprepared such wast quantities of RAM. You may try creating a
> DpmiLimit key under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW in the registry
> to adjust this with the limit in bytes as a DWORD
https://stackoverflow.com/questions/42303118/dos-4gw-fatal-error-1307-not-enough-memory
That was for Windows 7, but it might be worth a try on Windows 10.
Michae...@none.i2p
Jun 17, 2019, 4:59:26 AM6/17/19
to
I just confirmed the link (Microsoft Segmented Executable Linker Version 5.60.339 Dec 5 1994) worked in the June update of Windows 10 1903.
The version of Windows is OS Build 18362.175.
The version of Windows is OS Build 18362.175.
T. Ment
Jun 17, 2019, 1:24:58 PM6/17/19
to
thing. A minimal install of Windows 10 is what, 20GB or more?
And why? To be all things to all people?
Windows 7 will be my last. There has to be a better way.
0 new messages