ppgrainbow

That's pretty interesting. The other day when I created a MS-DOS partition of 8,036 MB, only 8,025 MB of those would be usable. If I wanted to directly access more than one logical hard disk, I had to use IMDisk and enter the image file offset in blocks and the size of the virtual disk. Since the primary partition has 2,047 MB, the extended partition having 5,977 MB (or 12,241,529 sectors), IMDisk would only mount the primary DOS partition (starting in sector 63 and ending on sector 4,192,964) and the first logical DOS partition (starting on sector 4,192,964 and ending on sector 8,385,929) in extended DOS partition. IMDisk wouldn't even display info for the second logical DOS partition or even the third logical DOS partition. So, I had to enter the information manually for the following: For the second logical DOS partition, the LBA image offset will start at sector 8,385,993 blocks and end on sector 12,578,894. For the third logical DOS partition, the LBA image offset will start at sector 12,578,958 and end on sector 16,434,494). The third logical DOS partition has a capacity of 1,882.59 MB or 3,855,535 sectors. One thing to note that for some reason when there is too much FAT on the hard disk partition, Windows 3.1 will eventually fail to boot properly with memory managers installed. Update: I tested Windows 3.1 on a 3 GB hard disk with a FAT32 partition, but here's what I had to do in order to get Windows 3.0 or Windows 3.1 running on a FAT32 partition: 1. Create a virtual hard disk partition between 2,048 MB to 8,032 MB. 2. Use the Windows 95 OSR2, Windows 98, Windows 98SE (MS-DOS 7,1) or Windows Millennium boot disk to boot from the virtual floppy disk. 3. Partition the whole hard disk using FDISK with FAT32 support and make the partition active. 4. Format the hard disk. 5. Copy the following files from the Windows 95 OSR2, Windows 98 or Windows Millennium installation in order to use commands under MS-DOS 7.1 or MS-DOS 8.0. The following files found in \WINDOWS\COMMAND are from MS-DOS 7.1 when used with Windows 98 Second Edition for example: ANSI SYS 9,719 04-23-99 10:22p ATTRIB EXE 15,252 04-23-99 10:22p CHKDSK EXE 28,096 04-23-99 10:22p CHOICE COM 5,239 04-23-99 10:22p COUNTRY SYS 30,742 04-23-99 10:22p DBLSPACE SYS 2,135 04-23-99 10:22p DELTREE EXE 19,083 04-23-99 10:22p DISKCOPY COM 21,975 04-23-99 10:22p DISPLAY SYS 17,175 04-23-99 10:22p DOSKEY COM 15,495 04-23-99 10:22p EDIT COM 69,902 04-23-99 10:22p EDIT HLP 10,790 04-23-99 10:22p EGA CPI 58,870 04-23-99 10:22p EMM386 EXE 125,495 04-23-99 10:22p EXTRACT EXE 93,242 04-23-99 10:22p FC EXE 20,574 04-23-99 10:22p FDISK EXE 63,916 04-23-99 10:22p FIND EXE 6,658 04-23-99 10:22p FORMAT COM 49,575 04-23-99 10:22p HIMEM SYS 33,191 04-23-99 10:22p KEYB COM 19,927 04-23-99 10:22p KEYBOARD SYS 34,566 04-23-99 10:22p KEYBRD2 SYS 31,942 04-23-99 10:22p KEYBRD3 SYS 31,633 04-23-99 10:22p KEYBRD4 SYS 13,014 04-23-99 10:22p LABEL EXE 9,324 04-23-99 10:22p MEM EXE 32,146 04-23-99 10:22p MODE COM 29,271 04-23-99 10:22p MORE COM 10,471 04-23-99 10:22p MOVE EXE 27,299 04-23-99 10:22p MSCDEX EXE 25,473 04-23-99 10:22p NLSFUNC EXE 6,940 04-23-99 10:22p SCANDISK EXE 143,818 04-23-99 10:22p SCANDISK INI 7,329 04-23-99 10:22p SCANREG EXE 165,502 04-23-99 10:22p SORT EXE 25,882 04-23-99 10:22p START EXE 28,672 04-23-99 10:22p SUBST EXE 17,904 04-23-99 10:22p SULFNBK EXE 45,056 04-23-99 10:22p SYS COM 18,967 04-23-99 10:22p XCOPY EXE 3,878 04-23-99 10:22p XCOPY32 EXE 3,878 04-23-99 10:22p XCOPY32 MOD 41,472 04-23-99 10:22p 6. The following files that you can copy are the CD-ROM drive, mouse driver and the CPU idling driver, those are optional: CDROM SYS 11,202 06-07-96 5:30p IDLE COM 128 03-11-04 3:03p MOUSE COM 9,169 08-03-04 12:00p 7. The following files that you can copy are from a MS-DOS 5 to 6.22 installation, those are optional as well: MONEY BAS 46,225 05-31-94 6:22a GORILLA BAS 29,434 05-31-94 6:22a DOSSHELL COM 4,620 05-31-94 6:22a DOSSHELL EXE 236,378 05-31-94 6:22a DOSSHELL GRB 4,421 05-31-94 6:22a DOSSHELL HLP 161,323 05-31-94 6:22a DOSSHELL VID 9,462 05-31-94 6:22a MSD EXE 165,864 05-31-94 6:22a NIBBLES BAS 24,103 05-31-94 6:22a QBASIC EXE 194,309 05-31-94 6:22a QBASIC HLP 130,881 05-31-94 6:22a REMLINE BAS 12,314 05-31-94 6:22a 8. Download and run Win3XStart 1.57 to get Windows 3.0 or Windows 3.1 working on a FAT32 partition. 9. Install Windows 3.0 or Windows 3.1. After that, reboot. You'll notice that you will have to reboot after Windows 3.x is installed. 10. In CONFIG.SYS, add the following: FILES=30 BUFFERS=30 DEVICE=C:\DOS\HIMEM.SYS /testmem:off DEVICE=C:\DOS\EMM386.EXE NOEMS I=B000-B7FF LASTDRIVE=Z 11. In AUTOEXEC.BAT, add the following: @ECHO OFF PATH C:\DOS;C:\WINDOWS; SET TEMP=C:\TEMP 12. Grab the WINA20.386 file from a MS-DOS-based installation and place it in the root directory on the boot drive. 13. Grab the IFSHLP.SYS either from a Windows for Workgroups 3.11 or Windows 0x/Me installation and place it in the \WINDOWS directory. Windows 3.x should now run as usual. Please note that Windows 3.1's File Manager will report a hard disk drive larger than 2 GB as 2,097,088 KB. However, the File Manager used in Windows 3.0 will end up reporting negative numbers or not report the drive as the correct size if the drive is over the 2 GB limit. This is the case, because File Manager used signed 32-bit numbers to store hard disk space capacity in bytes and any number beyond 2,147,483,647 will wrap as a negative number and misrepresent the size of the hard disk over 2 GB. I would also like to mention that some of the 16-bit DOS and 16-bit Windows-based software that relies on hard disks of 2 GB or small may not even work correctly, if not at all.

I strongly recommend that you use version 10.3. v 11.x even have many bug on Windows XP and 7. The flash players from v 11.2 to v11.4 have so many security holes that it is too dangerous. You can download v10.3 flash player for Windows 2000 installer from my blog. Lastest v10.3 is fixed many security holes. I already have Flash Player 11.5 with UURollup v10d or KernelEx and so far, there aren't any issues with it at all.

You're welcome. I'm really glad to help you out.

I have a dual-boot DOS 6.2/Windows 98 system with an 8GB and 64GB Hard Drives. I developed a DDO that runs with DOS 6.2 that makes the 64GB Hard Drive appear as 8 8GB Hard Drives. With careful partitioning of the 64GB Hard Drive, including creating dummy partitions, I was able to share 12 2GB Partitions between both OSes. I could have shared 24 but I needed some larger FAT32 Partitions for data. With Patches, DOS 7.1 can handle 8MB Clusters (256 Sectors of 32KB each), and can handle up to 3PB Hard Drives with a DDO, 48TB without. Wow! That's pretty interesting. I kinda find it really weird to see MS-DOS 6.2 fully recongise the 64 GB hard disk as 8 8 GB hard drives with a Dynamic Drive Overlay that you developed, even if MS-DOS 6.22 and below will not support hard disks over 7.8 GB.

Here's what I found about MS-DOS and here are the fact that I've learned so far. Some of the information regarding FDISK hard disk limitations is not documented elsewhere. Memory limitations MS-DOS 4 and 5 include the HIMEM.SYS XMS 2.x driver which will not allow the OS itself to address more than 16 MB of system memory. This is the case when those operating systems came out. If the HIMEM.SYS XMS 3.x is used from MS-DOS 6 through MS-DOS 6.22, then the system memory ceiling would be raised from 16 MB to 64 MB. MS-DOS 6 through 6.22 include the HIMEM.SYS XMS 3.x driver which raises the system memory ceiling from 16 MB to 64 MB. 64 MB or 65,536 KB is very common, because MS-DOS 6.x used a unsigned 16-bit value to store the physical amount of memory in kilobytes. If more than 64 MB of system memory is reported to MS-DOs 6.x, then only 64 MB will be usable. The system memory limit ceiling was raised to 4 GB in MS-DOS 7, MS-DOs 7.1 and MS-DOS 8. However, up to around 3.6 GB of system memory will be usuable to the OS. Hard disk size limitations in MS-DOS 2.x to MS-DOS 6.22 FDISK from MS-DOS 2.x only had FAT12 support with support for single hard disks up to 16 MB at 4,096 bytes per cluster. In MS-DOS 3.0 to MS-DOS 3.2, the limit was raised to 32 MB when FAT16 support was introduced. FDISK from MS-DOS 3.3 allowed partition sizes of up to 32 MB (or 65,535 sectors at 512 bytes per sector) and recognises hard disks of up to 504 MB (1,024 cylinders, 16 heads and 64 sectors per track). For this instance, drive C as the primary partition and drives D through R would need to be created - 15 32 MB partitions and a 24 MB logical partition on drive R. However, in November 1987 Compaq shipped Compaq MS-DOs 3.31 with support for hard disks up to 504 MB. Partitions over 32 MB used the partition type (0x06) which later became present in MS-DOs 4.0 and later. FDISK from MS-DOS 4 and MS-DOS 4.01 is limited to a partition size of up to 4,095 MB per hard disk split to a 2,047 MB primary partition (drive C) and a 2,039 MB logical partition (drive D). MS-DOS 4.0x had a serious bug where as if the size of the hard disk is greater than 4,095 MB, the OS would refuse to boot...even from a floppy disk. This bug was due to Microsoft programmers using 32-bit unsigned numbers to store hard disk drive capacity detection in FDISK which would cause the value (in megabytes) to wrap back to zero, meaning that a hard disk larger than 4 GB in capacity will be reported significantly less. IBM's PC-DOS 4.0 only supported partitions of up to 1,024 MB with up to four partitions. The 4,095 MB bug was fixed in MS-DOS 5.0 and later where as the capacity limit was raised to 1,024 cylinders, 255 heads and 63 sectors per track for a total of 16,450,560 sectors. At 512 bytes per sector, this totals 8,422,686,720 bytes or more commonly - 8,032.5 MB (7.84 GB). The hard disk with the maximum capacity of 7.8 GB must be split into four partitions, the 2,047 MB primary partition on drive C would first be created and a Extended DOS partition of 5,977 MB, consisting of two 2,047 MB logical partitions on drive D and E and one 1,883 MB partition on drive F. If a hard disk has a capacity of 8,032 MB or more, then only 8,032 MB will be usable under MS-DOS 5 and 6. Also, when it says "Do you wish to use the maximum available size for a Primary DOS partition?", if you try to select the whole hard disk if the size of the drive is more than 2,047 MB then only the first 2,047 MB will be used and the remaining 5,977 MB will be reserved for a Extended DOS partition. Hard disk size limitations in MS-DOS 7, MS-DOS 7.1 and MS-DOS 8 In MS-DOS 7 (Windows 95 and 95A) FDISK, the 7.8 GB partition size limit was removed, however only FAT16 partition sizes of up to 2 GB could be created. MS-DOS 7 FDISK also cannot correctly display the size of large drives as the value is limited to 9,999 MB. If the size of the drive is over 10,000 MB, the last digit will be dropped. For example, a Quantum 12 GB with a partition size of 11,497 MB would be displayed as "1149". Let me warn you that in MS-DOS 7 FDISK, there is a rather annoying bug where if you try to partition FDISK on a hard disk larger than 32,767 MB, FDISK will NOT report the correct size of the drive as the total disk space will end up showing negative numbers! MS-DOS 7 FDISK used signed 16-bit values internally to calculate the size of the drive in megabytes. And some of these variables will overflow when the size of the drive itself is equal to or larger than 32 GB. For example, if the size of the physical drive is 48 GB in size, FDISK will use the first 2,047 MB for the primary partition and 47,104 MB for the Extended DOS Partition. However, FDISK will end up reporting the drive as being a -18,431 MB drive when a Extended DOS partition is created! A series of logical drives, drives D all the way to drive Z would need to be created and formatted. However, after partitioning logical drive R, FDISK under MS-DOS 7.0 will stop responding (hang) when attempting to partition logical drive S! The solution when using MS-DOS 7 FDISK is use a hard disk smaller than 32 GB in size and create 2 GB partitions or use MS-DOS 7.1 which added FAT32 support and support for hard disks up to 2 TB. In MS-DOS 7.1 when used with Windows 95 OSR2.x or Windows 98, there is a bug where FDISK will not recognise the full size of the hard disk larger than 64 GB: http://support.microsoft.com/kb/263044 The fix that I pointed out only applies to MS-DOS 7.1 when used with Windows 98 and Windows 98 Second Edition, because MS-DOS 7.1's FDISK uses unsigned 16-bit values internally to calculate the size of the drive in megabytes. However, even if the fix is applied, MS-DOS 7.1 when used with Windows 98 and MS-DOS 8.0 cannot correctly display the size of large drives as the value is limited to 99,999 MB. If the size of the drive is over 100,000 MB, the last digit will be dropped. Also, FDISK when used with MS-DOS 7.1 will be unable to properly create a hard disk larger than 512 GB. For example when you attempt to set up a 640 GB hard disk with MS-DOS 7.1, you will not be able to use a partition of 610,352 MB, instead it will only end up as a partition size of 86,063 MB. Such a issue will occur, because MS-DOS 7.1 FDISK uses signed 20-bit values to calculate partition creation sizes which limits the size of the partition to 512 GB. To work around this solution, you will either have to use the MS-DOS 8.0 FDISK (from the Windows Millennium boot disk), use the FreeDOS FDISK or use a third-party partition to create a FAT32 formatted hard disk of up to 2 TB. Lastly, in FreeDOS, the size of the drive is limited to a six-digit value of 999,999 MB. If FreeDOS is used to partition a 1.5 TB or 2 TB hard drive then the last digit will be dropped. Testing MS-DOS limitations Okay, I create three 8,036 MB hard disk images for use in MS-DOS 6.22 under VMware Player. I allocated 64 MB of system memory and 4 MB of video RAM. Since the CD-ROM is present on the secondary master channel, MS-DOS FDISK will report three IDE hard drives as 8,025 MB each. The drives are partitioned as the following: DISK 1 DISK 2 DISK 3 In short, when running MS-DOS under VMware, QEMU, Bochs, VirtualBox or Virtual PC: 1. If a CD-ROM is present, MS-DOS will use up to three IDE hard disks with a total of up to 24,075 MB of total disk space. 2. When a CD-ROM not present, MS-DOS will use up to four IDE hard disks with a total of up to 32,100 MB of total disk space. 3. If MS-DOS is set up on a SCSI virtual disk, MS-DOS will use up to 8 SCSI hard drives or up to 6 SCSI hard drives with a capacity of 8,032 MB each with the highest possible total of 48,192 MB of disk space (or up to 46,304 MB of disk space with a virtual CD-ROM). The absolute highest limitation maybe less if removable media is present. Has anyone experienced testing hard disk and memory limits before in MS-DOS? If so, please share your experience. Update: I tested running MS-DOS 6.22 with 80 MB of system memory allocated to the VM and with the following example output: C:\>memMemory Type Total = Used + Free---------------- ------- ------- -------Conventional 640K 24K 616KUpper 115K 96K 19KReserved 0K 0K 0KExtended (XMS) 65,985K 450K 65,535K---------------- ------- ------- -------Total memory 66,739K 569K 66,170KTotal under 1 MB 755K 120K 635KLargest executable program size 616K (630,288 bytes)Largest free upper memory block 9K (9,696 bytes)MS-DOS is resident in the high memory area.C:\>As described above, MS-DOS will report the total amount of memory up to a little more than 1 MB over 65,535 KB leaving the maximum amount of XMS that MS-DOS can use to no more than 65,535 KB and with 640 KB of base memory and up to 128 KB of upper memory, that works out to a absolute maximum of 66,303 KB of total memory available to DOS!

Adobe Flash Player 10.1.102.64 is the last officially supported version of the player under Windows 2000. Unofficially, Flash Player 11.1.102.55 is the last version of the Flash Player shown to work on Windows 2000 and Windows XP RTM. Starting with Flash Player 11.1.102.62, the installer and the executable will use the SetDllDirectoryW entry point dependency that only exists in Windows XP SP1 (absolute lowest) and later. Additionally, the Flash Player applet in the Control Panel may not work correctly due to code that may only exist on Windows XP SP2 and up. With UURollup or KernelEx for Windows 2000, you can have the current version of Adobe Flash installed.

That's good to hear that! I'm glad that Silverlight is working now.

Thank you for releasing a update to your KernelEx project! I found that GetThreadPrefferedUILanguages is only present on Windows Vista and later. Windows XP is not even supported with this function.

Me too. v11 of UURollup is already stable in this latest beta...so if there is a way to get Silverlight working on other locales with a upcoming fix to UURollup v11, we'll see what happens. Update: blackwingcat has concluded that the reason why Microsoft Silverlight crashed in all browsers is that the plugin threw an exception and terminated with the entry point GetThreadPreferredUILanguages linked to KERNEL32.DLL. This entry point is only present on Windows Vista and higher. Update 2: I can confirm that Silverlight crashes in the UURollup v11 2012-11-18 update, because it threw the GetThreadPreferredUILanguages entry point as I don't think that it didn't with UURollup v10d. I sure hope that it will get fixed in UURollup v11 2012-12-02 update. blackwingcat already fixed the issue in KernelEx v22k3. For now, until further notice, it would be good to set the system locale to Japanese.

Here's a followup to my previous forum thread on how to install and update Windows 2000 and now I'm about read to provide a guide on how to install and update Windows NT 4.0 Workstation. Here's how. In the past, when you first installed Windows NT 4.0 Workstation or Server, you would get updates for Windows NT 4.0 Workstation, however the updates were from Windows Update v3, which first appeared on Windows 95. Unfortunately, in the summer of 2011, Microsoft de-commissioned older versions of Windows Update (v3 and v4), thus withdrawing updates for Windows 95, 98, Me, NT 4.0 and Windows 2000 < SP3. Users who want to receive updates are now required to use Windows Update v6, however as Windows Update v6 does not work on Windows NT 4.0 and other OSes, users of these operating systems do not have any method of either automatically detecting and installing updates or doing it manually via the Windows Update website. This is not a limitation for existing installations of Windows NT 4.0, because Microsoft pulled the plug the OS years ago and as such, no new updates are being produced. However, it has became a serious and crippling limitation for anyone re-installing Windows NT 4.0. This is especially the case, when it has became increasingly difficult to do research and find all of the updates that once appeared on the Windows Update website as Microsoft withdrew the updates for Windows NT 4.0. To get around this, here are the instructions on how you can re-apply the updates that once appeared in Windows Update after installing Windows NT 4.0 Workstation (i386 version): A. INSTALLATION PROCEDURES --------------------------------- 1. If you're planning to run Windows NT 4.0 Workstation in a virtualised environment (such as VMWare, Qemu, Virtual PC, etc.), apply the appropriate settings on how much disk space to use for a virtual hard disk, how much memory to allocate as well other important settings such as floppy drives, CD-ROM, sound card and networking. Be warned that Windows NT 4.0 (pre-SP4) will NOT support hard disks and other media over 7.8 GB (1023 cyl/255 heads /63 spt) on install. And in the original release, Windows NT 4.0 will not even partition the boot hard disk over 4 GB. Furthermore, by default, Windows NT 4.0 will only support either FAT or NTFS partitions. You will need to install the FastFAT driver for FAT32 support. More about that later. 2. Install Windows NT 4.0 Workstation as usual. B. UPDATING WINDOWS NT 4.0 COMPONENTS ---------------------------------------------- 3. Download and install Windows NT 4.0 Service Pack 6a with 128-bit encryption (ftp://ftp.vsi.ru/pub/win/winnt4/sp6a/sp6i386_128b.exe). You can apply the previous five service packs (SP1_400I.EXE, SP2_400I.EXE, SP3_400I.EXE, NT4SP4I.128.EXE and SP5128I.exe) in a incremental step, but it is time consuming and not recommended. 4. Download and install Internet Explorer 4.01 SP2 first which includes support for Active Desktop and the QuickLaunch toolbar: http://browsers.evolt.org/?dir=archive/ie/win32/4.01-sp2 (Internet Explorer 4.01 SP2 can be found on other websites where it is archived for historical purposes. After setting up and installing IE 4.01 SP2, reboot. 5. After rebooting, download and install the full version of Internet Explorer 6 Service Pack 1: http://www.jcu.edu.au/pub/Microsoft/ie/6.0sp1/ie60sp1.exe After installing Internet Explorer 6 SP1, reboot. After rebooting, IE6 will finish up the installation. 6. Download and install the following security updates that were taken from wuhistv3.log, the Windows Update v3 history log. Here's a copy of what the wuhistv3.log looks like: Total number of inital updates applied: 40 (45 if applying Service Packs 1 through 5) Total download size of all updates: 206.7 MB (up to 304.6 MB if applying the first five service packs) C. ADDITIONAL NOTES ----------------------- It is recommended that you apply the updates by the incrementing sorted date of when the update came out. When these updates are applied, you will have to do a series of reboots and continue updating the files, one by one. Applying updates by hand can be time consuming, but it is worth it. The only side effect is that after applying the Q313829 update (on Windows NT 4.0 with Active Desktop), you will lose the ability to disable the shortcut arrows using TweakUI. And attempting to replace SHELL32.DLL with a unofficial fix may cause icon display corruption! This page workarounds on how to replace the defective SHELL32.DLL with the one that will have the ability to add or remove arrow shortcuts on desktop: http://www.mdgx.com/98-5.htm#PSBF If you want to keep the ability to add or remove shortcut arrows on icons on the desktop, do not install Q313829 update. Also, I've noticed that check-boxing Show icons using all possible colors found in the Plus! tab in Display Properties has no effect on the My Computer and Recycle Bin icons. I'm wondering if there is a way to fix that? If you want to have Windows NT 4.0 access a hard disk or other media with a FAT32 partition, you will need to install the FAT32-enabled FAT filesystem driver: http://ashedel.chat.ru/fat32/ To use the driver, copy FASTFAT.SYS and FS_REC.SYS to %systemroot%\system32\drivers and reboot. If you want to boot Windows NT 4.0 on a partition greater than 7.8 GB (and up to 2 TB), you will need to copy the NTDETECT.COM and NTLDR from a Windows 2000 or Windows XP partition. Go to this page for instructions: http://www.nu2.nu/fixnt4/ If you have any questions regarding this guide on how to install and update Windows NT 4.0, please let me know and I will get back to you! I will probably need to update this thread if there are any errors found. Coming soon, I will provide a guide for installing and updating Windows NT 3.51 Workstation and Windows 95 which should be a very easy thing to do!

Update: At this time, I just got word that Silverlight 4.1 and Silverlight 5.x will work with UURollup v11 20120915+ ONLY if the system locale is set to the Japanese language and in Japanese versions of Windows 2000. It will NOT work in languages other than Japanese: http://www.msfn.org/board/topic/149233-kernelex-for-win2000/page__view__findpost__p__1019919 I think it would be good to do some investigation into the DLLs that caused Silverlight to not work in languages other than Japanese. ;p

Really? How did you know that Microsoft Silverlight works when the system locale is set to only Japanese? Do you know which of the DLLs that were used to make Silverlight work when it is only in the Japanese language?

One example is KB2724197: MS blabing mumbo-jumbo about 'security', but said nothing that it would impact EMS availabilty on NTVDM. Well, the previous "security" update, KB2707511 already caused NTVDM to crash on opening a pipe, an issue that hasn't been fixed. Since security updates are cumulative, KB2724197 must have both issues. Now, ain't those latest updates really awesome? Just to yet again point out that maybe two rollbacks may be in order, not just one... KB2633171 being the last non-flawed krnl set. I can't believe that Microsoft hasn't been very helpful remedying the issue of EMS not working for 16-bit apps under Windows XP as I personally believe that the important of the 16-bit Windows subsystem is increasingly deprecated. True enough. BTW, if you really need EMS, EMS Magic seems to be the way to go... That's a very good idea!

One example is: KB2724197 MS blabing mumbo-jumbo about 'security', but said nothing that it would impact EMS availabilty on NTVDM. Well, the previous "security" update, KB2707511 already caused NTVDM to crash on opening a pipe, an issue that hasn't been fixed. Since security updates are cumulative, KB2724197 must have both issues. Now, ain't those latest updates really awesome? Just to yet again point out that maybe two rollbacks may be in order, not just one... KB2633171 being the last non-flawed krnl set. I can't believe that Microsoft hasn't been very helpful remedying the issue of EMS not working for 16-bit apps under Windows XP as I personally believe that the important of the 16-bit Windows subsystem is increasingly deprecated.

Yes but please read this post. I'd rather uninstall the update and just add to the registry: HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2724197","Installed",0x10001,1 This should prevent WU from asking for it. Thanks for telling me. I appreciate it

I'm sorry that I didn't get to this post, because I was tired and got only five hours of sleep. Here are the exact instructions below: 1. Download the latest release of MAME from http://mamedev.org; select either mame0???b.exe or mame0???b_i686. 2. Download the non-commercial public domain ROMs provided only by MAME. I must stress to the fullest extent that I am NOT allowed to provide links to ROMs and/or other copyrighted material as it is against MSFN's terms of service. 3. Extract the MAME contents to the \MAME directory. 4. Place the zip file containing the name of the ROM to the \MAME\ROMS directory. 5. Execute mamepp.exe found in the \MAME directory and select one of the games with the mouse button. 6. You will then receive the warning: The end result is that for some reason, clicking on ESC or OK doesn't work in either MAME or MESS. I'm wondering if this has got to do with UURollup or not and that I don't get a Event 9 in the Event log. Note, the instructions that I provided are for testing purposes only. I did test MAME under Win2k without the UURollup and it worked okay. For some reason, this issue either has to do with my USB keyboard or UURollup itself.

Woah! Thank you for telling me. At the moment, it looks like that fixing the Microsoft Silverlight plugin is infeasible right now so I had to uninstall it.

I agree. It's something with ntdll.dll and v11d120915 and up that's causing Silverlight to crash. But what's complicated is that simply replacing older versions of the ntdll.dll would break applications, because kernel32.dll and other files from 5.0.2195.7193 depend on ntdll.dll. As for the recommendation, I'm with you on this one. I either need to downgrade to v11d120911 or uninstall Silverlight until a update from v11d121104 is made, that is if there is one.

I too received a crash in Microsoft Silverlight affecting Internet Explorer and the offending module name appears to be kernel32.dll (module version 5.0.2195.7193), the exception information output are as follows: I'm guessing that a lot of files in version 5.0.2195.7193 broke Silverlight support and it's not just kernel32.dll or ntdll.dll.

I knew it. I kinda have a feeling that the final version of UURollup v11 will most likely break Silverlight support as far as I know. According to the error details, the crash in Microsoft Silverlight caused by the latest update to UURollup v11 has the offending module name of kernel32.dll (module version 5.0.2195.7193), the exception information output are as follows: So, until there is any word on how to get Silverlight fixed, I'm afraid that we're stuck, which means that we may have to use the older workable version of UURollup (with the version of the files older than 5.0.2195.7193) or uninstall Silverlight completely.

As you may have already noticed, if you have Windows XP with SP3 and if you install update KB2724197, you'll notice that in the update that it will prohibit the use of EMS memory for 16-bit applications in Windows XP SP3. The security update for Windows XP states that: The file versions of the files listed below will be updated to version 5.1.2600.6284 in Windows XP SP3: File Name Size Date Time Branch ntkrnlmp.exe 2,148,864 2012-08-21 13:33 SP3GDR ntkrnlpa.exe 2,069,632 2012-08-22 01:28 SP3GDR ntkrpamp.exe 2,027,520 2012-08-21 12:58 SP3GDR ntoskrnl.exe 2,192,896 2012-08-21 13:29 SP3GDR ntkrnlmp.exe 2,148,864 2012-08-21 13:52 SP3QFE ntkrnlpa.exe 2,069,632 2012-08-21 13:05 SP3QFE ntkrpamp.exe 2,027,520 2012-08-21 13:05 SP3QFE ntoskrnl.exe 2,193,024 2012-08-21 13:48 SP3QFE Prior to installing the update, I have found older versions of the following Windows XP SP3 files in version 5.1.2600.6223: File Name Size Date Time Branch ntkrnlmp.exe 2,148,352 2012-05-04 06:16 SP3QFE ntkrnlpa.exe 2,069,120 2012-05-04 05:32 SP3QFE ntkrpamp.exe 2,026,496 2012-05-04 05:32 SP3QfE ntoskrnl.exe 2,192,640 2012-05-04 06:12 N/A ntkrnlmp.exe and ntkrpamp can be found in \WINDOWS\Driver Cache\i386 while ntkrnlpa.exe and ntoskrnl.exe can both be found in \WINDOWS\SYSTEM directory. If you look in this controversal thread and search for the threads mentioning KB2724197, there has been numerous complaints regarding KB2721497 and how such an update dropped EMS support apparently as a part of a phase-out of support for 16-bit DOS and Windows apps in 32-bit versions of Windows XP through Windows 8. And as a part of the phase out of support for Windows XP, it is turning out that the moderators in the Microsoft forums haven't been too unhelpful. By the way, for anyone who still wants to use EMS for use in 16-bit DOS-based apps in Windows XP, the files are placed in a hidden directory called \WINDOWS\$NtUninstallKB2724197$. I'm just wondering this...it is possible to replace the current versions of ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe and ntoskrnl.exe with older versions found in \WINDOWS\$NtUninstallKB2724197$ by hand rather than uninstalling the update? I have backed up the files to the \EMS directory incase I want to do this. Also, if I don't want the 16-bit subsystem in Windows XP anymore, is it possible to remove the NTVDM 16-bit subsystem? I have installed the update in a Windows XP SP3 VMware Player VM, by the way.

I don't know if the latest version of UURollup is causing problems with the keyboard, but I checked the event log and found a Event 9 error. The error that I'm getting is this: Event ID 9 Source: kbdclass Description: Could not enable interrupts on connected port device \Device\KeyboardClass0. As such, I can't use some of the software that rely on kbdclass (found in \SYSTEM32\drivers\kbdclass.sys; datestamp 2003-11-19 11:22:24) such as MAME/MESS (keyboard does not function correctly when typing OK for example) for example, except that it works in VMware or VirtualPC for example. This is on a USB connected keyboard that appears to be working fine. I used to have a PS/2 keyboard, but for some reason, it constantly stopped working. I extracted the Windows2000-UURollup-v11-w121104-x86-ENU.exe file and it doesn't even mention kbdclass or other files related to the keyboard. I'm sorry if I'm failing to provide enough information, but is there a way to fix this?

Thank you for telling me. I could be wrong, but I think that the problem might be due to the latest version of ntdll.dll which is version 5.0.2195.7103 (2012-10-05 20:48:18). I'm wondering if it is possible to either use a older version of ntdll.dll or investigate parts of the ntdll.dll file to determine what caused Silverlight to not work anymore either. I don't think that Silverlight 5.x even works with this version of the Extended Kernel, but I could be wrong here. Edit: I heard that blackwingcat got Silverlight 5.x working with the latest version of UURollup v11. If that's the case, I will need to somehow get it working to see if this will remedy the problem.

I sure hope that you got the router fixed by the way. I suspect that there could a bit of a problem with UURollup v11 causing sites that use Microsoft Silverlight to crash.

Alrighty! I think that it would be good to investigate which DLL is causing Microsoft Silverlight to either not work correctly or crash and if you found the problem, let me know.