Windows 95/4.00.224: Difference between revisions

Latest revision as of 14:34, 7 November 2023

**{{{title}}}**

4.00.224
Kernel version	Windows 9x (4.00)
CPU architecture	x86
Edition	N/A
BIOS date	29th October 1994
TCB	Beta ID: 186349 Password: 94730fb34

Windows 95 build 224 is a Beta 2 build of Windows 95, compiled on the 28th of October 1994. It was demonstrated at Fall COMDEX 1994. It is very similar to build 222.

Installation

Installing from Windows 95 boot floppy:

Prepare disk with fdisk, reboot, then format (format C:).
Change path to the CD-ROM and run setup.
Accept the default settings, fill in required information and then continue to the file copying process. You may also customize the features to be installed.
When complete, remove floppy and reboot.

Checked/debug problems

This build exists in both free and checked/debug versions. Its SDK is also available. However, the checked/debug version has boot issues with checked USER.EXE. To fix it, USER.EXE from the free version needs to replace the checked one.

Some information about why Windows won't boot using checked USER.EXE after lot of kernel-debugging:

The free USER32.DLL, when loading the Segment 21h from USER.EXE, which has the "Debug Windows 4.00.224" string. It checks for a word inside the segment to ensure it is valid. It should have a value of 0EAAh, but unfortunately the value taken is 6763h ("gc" in ASCII). Hence it will lead to invalid paging of the segment. Because of that Windows will show a BSOD.
After changing the pointer to correct position, you will be able to see the GUI with the watermark "Debug Windows" in right-bottom. However, hWnd pointers are done inside the same segment, hence EXPLORER.EXE will fail to load and will show an error or send "Invalid hWnd" to the kernel debugger. Setting the hWnd in debugger to 0 will let it run EXPLORER.EXE, though some issues remain (including system time in the taskbar).

Gallery

System properties (fail-safe mode)

@@ Line 1: / Line 1: @@
-'''Chicago Build 224''' is a consumer-oriented [[graphical user interface]]-based [[operating system]]. It was released on 5 November 1994 by Microsoft, under the name Windows 95.
+{{Infobox Buildinfo
+|image = Windows 95 224 Fre English.PNG
+|imagecaption = 4.00.224
+|kernel = Windows 9x (4.00)
+|arch = x86
+|sku = N/A
+|bios = 29th October 1994
+|tcb = [http://www.thecollectionbook.info/builds/windows/build/11 Beta ID: 186349<br>Password: 94730fb34]
+}}
+'''Windows 95 build 224''' is a Beta 2 build of [[Windows 95]], compiled on the 28th of October 1994. It was demonstrated at Fall COMDEX 1994. It is very similar to build 222.
-==Existence==
+== Installation ==
-Chicago build 224 exists in both free and checked/debug versions, and its SDK is available to download.
+''Installing from Windows 95 boot floppy:''
-However the checked/debug version had issues in booting using checked USER.EXE. To fix it the free USER.EXE needs to replace the checked USER.EXE to boot it.
+# Prepare disk with <code>fdisk</code>, reboot, then format (<code>format C:</code>).
+# Change path to the CD-ROM and run <code>setup</code>.
+# Accept the default settings, fill in required information and then continue to the file copying process. You may also customize the features to be installed.
+# When complete, remove floppy and reboot.
-[[File:Windows 95 224 Fre English.PNG|200px|thumb|right]]
+== Checked/debug problems ==
+This build exists in both free and checked/debug versions. Its SDK is also available.
+However, the checked/debug version has boot issues with checked <code>USER.EXE</code>. To fix it, <code>USER.EXE</code> from the free version needs to replace the checked one.
-Some information about why Windows won't boot using checked USER.EXE after lot of kernel-debugging onto it:
+Some information about why Windows won't boot using checked USER.EXE after lot of kernel-debugging:
-*The free USER32.DLL, when loading the Segment 21h from USER.EXE, which has the "Debug Windows 4.00.224" string. It checks for a word inside the segment to ensure it's valid. Which should have value 0EAAh, but unfortunately the value taken is 6763 ("gc" from a string). Hence it'll lead to invalid paging of the segment. By that, Windows will show the BSOD.
-*After changing the pointer to correct position, you'll be able to see the GUI with the watermark "Debug Windows" in right-bottom. But again hWnd pointers are done inside the same segment. Hence EXPLORER.EXE will fail to load and will show error screen, or "Invalid hWnd" into the kernel debugger. However, setting the hWnd into debugger to 0 will let it able to run explorer.exe, with some issues again (Including time gadget in taskbar).
+*The free <code>USER32.DLL</code>, when loading the Segment 21h from <code>USER.EXE</code>, which has the "Debug Windows 4.00.224" string. It checks for a word inside the segment to ensure it is valid. It should have a value of 0EAAh, but unfortunately the value taken is 6763h ("gc" in ASCII). Hence it will lead to invalid paging of the segment. Because of that Windows will show a BSOD.
+*After changing the pointer to correct position, you will be able to see the GUI with the watermark "Debug Windows" in right-bottom. However, hWnd pointers are done inside the same segment, hence <code>EXPLORER.EXE</code> will fail to load and will show an error or send "Invalid hWnd" to the kernel debugger. Setting the hWnd in debugger to 0 will let it run <code>EXPLORER.EXE</code>, though some issues remain (including system time in the taskbar).
-==External links==
+== Gallery ==
-*[http://en.wikipedia.org/wiki/Windows_95#Beta  Description of Microsoft Chicago]
+<gallery>
-*[http://mcb.betaarchive.co.uk/index.php?page=content/sites/1632/400224 Chicago #4.00.224 on the Microsoft Collection Book]
+Chicago 224.png|System properties (fail-safe mode)
+</gallery>