CraigAB69 wrote on 2023-01-05, 12:56:

Hi, […]
Show full quote

Hi,

I was trying to understand why 386MAX.vxd is included with Windows for Workgroups 3.11.
There is mention that MS C/C++ 7.0 included 386MAX in a KB. (Can anyone confirm that it came with c/c++ 7.0 in the box?)
But why just include the VXD and not the rest of the software?

Is there any references about 386MAX and MS in any articles?

Regards,
Craig

Hi,
I have just checked and none of my Win 3.11 installations includes 386MAX.vxd in any system folder . It seems it is only used when Win 3.11 setup detects an already installed 386MAX:
https://jeffpar.github.io/kbarchive/kb/083/Q83401/

Falcosoft wrote on 2023-01-05, 13:42:

Hi,
I have just checked and none of my Win 3.11 installations includes 386MAX.vxd in any system folder . It seems it is only used when Win 3.11 setup detects an already installed 386MAX:
https://jeffpar.github.io/kbarchive/kb/083/Q83401/

Thanks for the link.

Yes, after reading that KB it makes sense, I wonder what the deal was between Qualitas and MS?

EDIT: I see the source up on GitHub, but I don't know how to contact the owner.

CraigAB69 wrote on 2023-01-05, 12:56:

But why just include the VXD and not the rest of the software?

I'm not sure, perhaps the code in the file is based on source code that's confidential or it's because of copyright concerns.

If so, it would make sense that the file is shipped by Microsoft and merely used by Qualitas.

Anyway, it's just a wild guess.
All those 386/V86/DPMI related things are rooted very deeply within system, down to the kernal level.

So it makes theoretically sense that they might had to be provided/tested by Microsoft itself because of this.

I think I have a possible solution.
In the c:\dos\readme.txt (dos 6.22) Section 6.3 It appears that CV.exe (CodeView debugger) Ver. 3.0 and 3.13 and lower have issues with EMM386.exe.
So perhaps 386MAX was included to get around the issue of not being able to use Expanded Memory (EMS).
VB for DOS, MASM5.x have early versions of CV.exe.

EDIT:

6.3 CodeView ----------- CAUTION Using versions […]
Show full quote

6.3 CodeView
-----------
CAUTION Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has an 80386 memory
manager (such as EMM386.EXE) and device drivers or programs
that use extended memory. To determine which version you
have, type CV.EXE at the command prompt.

Just to add to this, Microsoft C/C++ 7.0 needs a DPMI server to run CV (CodeView) and PWB (Programmers Workbench) correctly under DOS.
Of course PWB and CV run correctly in a DOS win under Windows 3.1.

1========================< IMPORTANT REQUIREMENT >==========================
2
3     Microsoft C/C++ version 7.0 requires DPMI services.  If you wish 
4     to use Windows as your development environment, Windows provides 
5     DPMI services for you.  TO USE MS-DOS AS YOUR DEVELOPMENT 
6     ENVIRONMENT YOU MUST INSTALL 386-Max TO PROVIDE THESE SERVICES. 
7