@@ -54,12 +54,11 @@ The highly optional k95cinit.exe utility requires Visual C++ 1.5 to be built.
54
54
</tr >
55
55
<tr >
56
56
<td>ARM64</td>
57
- <td></td>
58
-
57
+ <td>Windows 10</td>
59
58
</tr >
60
59
<tr >
61
60
<td>ARM32</td>
62
- <td></td>
61
+ <td>Windows RT 8.0 </td>
63
62
<td>❌</td> <!-- Tested often: not really -->
64
63
</tr >
65
64
<tr >
@@ -77,12 +76,12 @@ The highly optional k95cinit.exe utility requires Visual C++ 1.5 to be built.
77
76
</tr >
78
77
<tr >
79
78
<td>ARM64</td>
80
- <td></td>
79
+ <td>Windows 10 </td>
81
80
<td>❌</td> <!-- Tested -->
82
81
</tr >
83
82
<tr >
84
83
<td>ARM32</td>
85
- <td></td>
84
+ <td>Windows RT 8.0 </td>
86
85
<td>✅</td> <!-- Tested -->
87
86
</tr >
88
87
<tr >
@@ -100,12 +99,12 @@ The highly optional k95cinit.exe utility requires Visual C++ 1.5 to be built.
100
99
</tr >
101
100
<tr >
102
101
<td>ARM64</td>
103
- <td></td>
102
+ <td>Windows 10 </td>
104
103
<td>❌</td> <!-- Tested -->
105
104
</tr >
106
105
<tr >
107
106
<td>ARM32</td>
108
- <td></td>
107
+ <td>Windows RT 8.0 </td>
109
108
<td>❌</td> <!-- Tested -->
110
109
</tr >
111
110
<tr >
@@ -123,12 +122,12 @@ The highly optional k95cinit.exe utility requires Visual C++ 1.5 to be built.
123
122
</tr >
124
123
<tr >
125
124
<td>ARM64</td>
126
- <td></td>
125
+ <td>Windows 10 </td>
127
126
<td>❌</td> <!-- Tested -->
128
127
</tr >
129
128
<tr >
130
129
<td>ARM32</td>
131
- <td></td>
130
+ <td>Windows RT 8.0 </td>
132
131
<td>❌</td> <!-- Tested -->
133
132
</tr >
134
133
<tr >
@@ -450,19 +449,30 @@ link.exe, you may also need to grab cvtres.exe (link.exe version 3.0 from
450
449
Visual C++ 4.0 is incompatible with the version of cvtres.exe included in the
451
450
NT 3.1 SDK, possibly earlier versions of link.exe might be ok.)
452
451
453
- Both the MIPS and i386 compilers should be correctly detected and configured
452
+ The MIPS and i386 compilers should be correctly detected and configured
454
453
to statically link against the C runtime and set the subsystem version to 3.1.
455
454
455
+ Note that the MIPS compiler is currently unable to build K95G, the GUI version
456
+ of Kermit 95. The compiler fails on Ikui.cxx with the error:
457
+ ` opening u-code output C:\TEMP\000057.M.writing u-code output C:\TEMP\000057.M.rename: No such file or directory `
458
+ The cause of this error is currently unknown, but it does not affect building the
459
+ console version of Kermit 95.
460
+
456
461
### Windows NT 3.50
457
462
458
463
As found on the * Microsoft Solutions Development Kit* , the only compiler or linker
459
464
included is for the Alpha platform and is at a similar level to Visual C++ 1.0 32bit
460
465
(MSC 8.0). The compiler works but the linker does not, so you'll need a newer
461
466
linker from Visual C++ 2.0 or 4.0. You may also need an updated cvtres.exe.
462
467
463
- This Alpha cmopiler should be correctly detected and configured to statically
468
+ This Alpha compiler should be correctly detected and configured to statically
464
469
link against the C runtime and set the subsystem version to 3.1.
465
470
471
+ Note that while the Alpha compiler is capable of building K95G (the GUI version of
472
+ Kermit 95), the resulting executable crashes the Win32 subsystem when run on Alpha
473
+ Windows NT 3.50. As a result it is recommended that this compiler only be used to
474
+ build the console version of Kermit 95.
475
+
466
476
### January 2000 Platform SDK
467
477
468
478
The January 2000 Platform SDK includes a very early version of Visual C++ 2002
@@ -480,4 +490,4 @@ be run on any publicly released version of Windows.
480
490
481
491
While the compiler in this SDK is capable of doing 32bit builds, the Platform
482
492
SDK headers have some issues (complains about size_t being redefined) and the
483
- required import libraries are not present.
493
+ required import libraries are not present.
0 commit comments