It seems the PE format didn't exist in October 1991:



The MZ header is there, but where is the PE header?

linuxlove, we officially have the build

-_________________________________________-

KenOath has given me a scan of the oct 91 cd.. this should prove it's real enough.

Well, you all may have the build in a pre-installed virtual hard drive, but I've still got the full installation CD
Anyway, have fun picking apart NT October 1991. I think I'll post a bunch of Setup screenshots soon.

MegaUpload hates my ISP.

Isn't it in line 3 after the "$" char?

Seems this build is no different than 239, so yeah, I can make an installation CD.

Wahey! Right, time to get digging...

Of note - the WAV directory includes way more sounds than made it into later versions of Windows. Of note are timpani.wav and glass.wav, the sound effects later used in Hearts (for when the Queen of Spades is played and for when hearts are broken respectively).

Wallpapers are derived from Windows 3.0 rather than 3.1 as in the December build.

So it is. Immastupid. While it exists, it's primitive as it doesn't get as far as showing a Windows message box when you run it, like in 239. It only gets as far as showing "This program cannot be run in DOS mode." and quits.


Won't be a true install CD unless you've got the SDK, Free and Debug files.

Here are screenshots of the DOS based setup program. I'll try to get screenshots of the GUI based setup program later.

GUI setup? How can I make that work with 239?

Anyway as I said at least it is very similar, ISO soon guys!

More OS/2 references in this build - more than in the December one, that's for sure. It's still there in NTOSKRNL.EXE, but also creeping in elsewhere. For example, NETAPI.DLL:

"NT OS/2 Software version %s"

and there's some source code for OS/2 supplied with the SDK examples:

"/* BEEP.C illustrates timing and port input and output functions
* including:
* inp outp clock
*
* Also keyword:
* enum
*
* Only the DOS version of this program uses inp and outp, since these
* are not normally used in OS/2. In addition to the delay use shown here,
* clock can be used as a timer as shown in SIEVE.C.
*
* The example also illustrates similar techniques under OS/2. To do
* compile the OS/2 version, define the symbol OS2 (using CL /D option
* or Defines field on the PWB C Compiler Options dialog).

*/"

Please upload full CD on fileshare!!!

No.

I'll try and get the GUI setup running later today, if BetaArchive's download server will ever rise above 900B/s -.-

don't worry German, I prepared a ISO for installing.

This build has no build number.

KenOath says he looked at every file on the cd when he got the build and there are no resource headers. The most probable reason of this is that this build was rushed out for comdex and almost all of the NT OS/2 references were stripped from it/

sorry no ISO, can't create directories

I bet they commented them out, .. which explains the weird blue screen & why the checked build doesn't say anything... it's one thing for it to say NT OS/2 version 1.blabla on the inside, but on the outside.....

Not to mention how MS was trying to push NT as something new, and if they could build the 'lore' as it having nothing to do with OS/2 the better. What is kind of funny is how OS/2 for the PowerPC is IBM's version of OS/2 3.0 .....

You may have a point there! Some more "hits":

G:\ntoct\DLL\NETMSG.DLL(1387): Trying to start default shell: C:\OS2\PMSHELL.EXE

G:\ntoct\DLL\NETH.DLL(882): SET COMSPEC=c:\os2\cmd.exe
G:\ntoct\DLL\NETH.DLL(2883): The UPS service couldn't access the UPS driver (UPSDRV.OS2). The UPS driver might not be configured properly.

From SMSS.EXE:

section invalid in %S
i386 Mips NtOs2_

From NET.EXE:

C:\nt\private\net\netcmd\netcmd\os2cmd.c

Hmm taking on your lead...

---------- BIN\NET.EXE
g♥C:\nt\private\net\netcmd\netcmd\os2cmd.c
_os2cmd
_NetpMakeWkstaLevelForOS2orDOS
_NetpSplitWkstaForOS2orDOS
_NetpMakeServerLevelForOS2
_NetpSplitServerForOS2
---------- BIN\SMSS.EXE
NtOs2_
_SmpHandleNtos2Keyword

---------- DLL\BASE.DLL
OS2 /P
---------- DLL\CSRSRV.DLL
os2
---------- DLL\NETAPI.DLL
_NetpMakeServerLevelForOS2
_NetpSplitServerForOS2
_NetpMakeWkstaLevelForOS2orDOS
_NetpSplitWkstaForOS2orDOS
---------- DLL\NETH.DLL
SET COMSPEC=c:\os2\cmd.exe
The UPS service couldn't access the UPS driver (UPSDRV.OS2). The UPS driver migh
t not be configured properly.
The UPS service couldn't access the UPS driver (UPSDRV.OS2). The UPS driver migh
t not be configured properly.
The UPS service couldn't access the UPS driver (UPSDRV.OS2). The UPS driver migh
t not be configured properly.
The UPS service couldn't access the UPS driver (UPSDRV.OS2). The UPS driver migh
t not be configured properly.
---------- DLL\NETMSG.DLL
Trying to start default shell: C:\OS2\PMSHELL.EXE
Error %1 occurred starting default shell: C:\OS2\PMSHELL.EXE
---------- NTOSKRNL.EXE
NT OS/2 Kernel


and looking at the kernel....

*** KeBugCheck( 0x%08lX ) \DosDevices\D:\ \DosDevices\E:\ NTVDM: We don't do protected mode instruction emulationyet.
NTVDM: An invalid opcode %lx was encountered at address %x:%x
NTVDM: A 0F opcode %lx was encountered at address %lx
NTVDM: An INSB opcode %lx was encountered at address %lx
NTVDM: An INSW opcode %lx was encountered at address %lx
NTVDM: An INTO opcode %lx was encountered at address %lx
NTVDM: An HLT opcode %lx was encountered at address %lx

Is NTVDM built directly into the kernel?

And the boot strings...

Microsoft(R) Windows(TM)
32-Bit Development Kit October 1991
C\BootDevice \SystemRoot \SystemDisk \Device \DosDevices \Device\Harddisk%d\Partition0 \Device\Harddisk%d\Partition%d \Device\Harddisk%d\Partition%d \Device\CDRom%d Dll \SystemRoot\Bin \smss.exe %c: Executive: Resource initialization failed
Executive: Worker thread initialization failed
Executive: Event initialization failed
Executive: Event Pair initialization failed
Executive: Mutant initialization failed
Executive: Semaphore initialization failed
Executive: Timer initialization failed
Executive: Profile initialization failed

oops!!!!

If that's the Comdex 91 build then it looks like the roughness of it isn't due to frantic commenting out of OS/2 references - rather there were four candidate builds and once one was chosen there wasn't much time to polish it up!

This excerpt from Showstopper explains it:



The big switch from OS/2 to Windows took place in late 1990/early 1991 and development of NT using tools running on NT machines didn't even reach the GUI stage until February 1991.

When upload full CD of NT October 1991 Pre-Release???

He will upload it if he has successfully tested the GUI setup phase of October 1991. Anyway, you must test the smaller version:

that is without the SDK installed.