No edit summary |
Ahmed Jebara (talk | contribs) No edit summary |
||
| 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. | '''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. | ||
==Existence== | |||
Chicago build 224 exists in both free and checked/debug versions, and its SDK is available to download. | |||
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. | |||
[[File:Windows 95 224 Fre English.PNG|200px|thumb|right]] | [[File:Windows 95 224 Fre English.PNG|200px|thumb|right]] | ||
Some information about why Windows won't boot using checked USER.EXE after lot of kernel-debugging onto it: | |||
*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). | |||
Revision as of 09:30, 25 May 2013
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.
Existence
Chicago build 224 exists in both free and checked/debug versions, and its SDK is available to download. 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.
Some information about why Windows won't boot using checked USER.EXE after lot of kernel-debugging onto it:
- 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).
