Windows 95/4.00.224: Difference between revisions

From BetaArchive Wiki
No edit summary
No edit summary
Line 9: Line 9:
}}
}}


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


===Checked/debug problems===
==Checked/debug problems==
This build exists in both free and checked/debug versions, and its SDK is available to download.
This build exists in both free and checked/debug versions, its SDK is also available.
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.
However, the checked/debug version has issues booting with checked <code>USER.EXE</code>. To fix it USER.EXE from the free release needs to replace the checked USER.EXE.


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 in taskbar).


*The free <code>USER32.DLL</code>, 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. It should have a value of 0EAAh, but unfortunately the value taken is 6763h ("gc" in ASCII). Hence it'll lead to invalid paging of the segment. Because of that Windows will show a BSOD.
*After changing the pointer to correct position, you'll 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 explorer.exe, though some issues remain (including system time in the taskbar).


==External links==
==External links==
*[http://en.wikipedia.org/wiki/Windows_95#Beta  Description of Microsoft Chicago]
*[http://en.wikipedia.org/wiki/Windows_95#Beta  Description of Microsoft Chicago]
*[http://www.thecollectionbook.info/builds/windows/build/11 Windows 95 #4.00.224 on the The Collection Book]
*[http://www.thecollectionbook.info/builds/windows/build/11 Windows 95 #4.00.224 on the The Collection Book]

Revision as of 21:32, 5 July 2015

{{{title}}}
Windows 95 224 Fre English.PNG
Windows 95 Build 224
Kernel version Windows 9x 4.00
CPU architecture x86
Edition n/a
BIOS date 28th October 1994


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

Checked/debug problems

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

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. It should have a value of 0EAAh, but unfortunately the value taken is 6763h ("gc" in ASCII). Hence it'll lead to invalid paging of the segment. Because of that Windows will show a BSOD.
  • After changing the pointer to correct position, you'll 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).

External links