ppgrainbow

Indeed.

A hard disk image that has 120 cylinders, 16 heads and 63 sectors per track would equal 59 MB. A hard disk image with the 936/4/35 CHS setting is custom and based on how the hard disk image was created using IMGMAKE. The internal physical hard disk image (hd0) is where Windows NT 4 boots at start up. The hard disk image (hd1 mapped as hd0), MSDOS.IMG is where it boots MS-DOS both as a RAM disk and for maintenance use. The portion of the setup code (found in lines 7 to 20 of menu.lst) that boots into MS-DOS 6.22 in RAM only consumes 64 MB of system memory and reducing the size of the total physical memory available to DOS from 144 MB to 80 MB. The eXtended Memory Specification Application Programming Interface (XMS API) version 3.0 that is used in MS-DOS has a 4 GB memory limitation. However, the HIMEM.SYS XMS 3.x driver that was used in MS-DOS 6.0 to MS-DOS 6.22 uses a unsigned 16-bit value (up to 65,535 KB of physical memory) to store the amount of physical memory to MS-DOS in kilobytes. If more than 64 MB of system memory is reported to MS-DOS, then only 64 MB will be usable to the OS. If the HIMEM.SYS XMS driver is version 2.x, then MS-DOS cannot even use the memory above the 16 MB limit. The HIMEM.SYS XMS 2.x drivers were shipped with MS-DOS 5.0 and Windows 3.0 respectively.. (Unfortunately, on a bit of a off-topic note, Windows 3.0 does not support system memory above this 16 MB limitation in both Standard Mode and 386 Enhanced Mode as the OS relies on the HIMEM.SYS XMS 2.x driver to enforce this limit. While Windows 3.0 will continue to work with more than 16 MB of memory in 386 Enhanced Mode, any attempts to run Windows 3.0 in Standard Mode with more than 16 MB of memory will cause the system to hang unless a RAM disk is installed to reduce the available memory to 16 MB of less.) By adding the lines "map --ram-drive=0x9f", "map --rd-base=0x5000000", "map --rd-size=0x100000" and adding (rd) to the end of "map (hd0) (hd1)", this reduces the total amount of available for MS-DOS to 80 MB. And along with a 64 MB hard disk image, it further cuts down the size of the physical memory available to MS-DOS to just 16 MB which is reasonable enough for most MS-DOS and Win16-based software. As for the need to re-enable A20 support, I can try to change the line that reads "map --a20-keep-on=0" to "map --a20-keep-on=1" to see if MS-DOS will boot with Gate A20 support enabled and remove the "--disable-a20" reference to the chainloader command.

If I get the chance to provide some documentation about mapping three (or more) drives), I'll let you know. The laptop has one removable hard disk. The hard disk image mounted on hd1 is mapped as hd0 when executing MS-DOS 6.22 at boot.

Well...I'm happy with the results. Creating a hard disk image using the IMGMAKE command with the custom cylinder-head-sector fixed the issue. As for making heads or tails on the menu.lst enter, there is no need for heads or tails. I'm very pleased with the results. ;p The undocumented commands mapped the first hard disk (hd0), the hard disk image (hd1) and the hidden RAM drive (rd) and swapped them completely. The floppy mapping remains unmodified as it is designed to map only one floppy. Lastly, as for not needing the "boot" command, I think that I will deprecate it. But along with that, everything is working now.

I'm awfully sorry for not focusing on this topic for days now, but I found a solution to the problem. Unfortunately, the solution is not 100% perfect... I used a smaller hard disk image of 64 MB and I even found a way to fix the CHS problem creating the hard disk image. I had to use DOSBox 0.74 Megabuild 6 to create a 64 MB hard disk image IMGMAKE. The input to create a 64 MB hard disk image will use 936 cylinders, 4 heads and 35 sectors per track for a total of 131,040 sectors and this works out to almost 64 MB (at 512 bytes per sector): However, when I attempted to access the hard disk image, I got this warning: To fix this, I had to use the FDISK utility to delete the partition and recreate it only to find that I was greeted with the Missing Operating System error, so what I did was to mount the BOOT.IMG disk image as drive A via DOSBox and reformat the hard disk image. I copied the hard disk image to the root directory on the hard disk of the Tecra 720CDT via a network and this is the result when I booted from the 64 MB hard disk image: Now that the size of the hard disk image has been reduced, WinImage is reporting that the size of the drive is 65,502 KB with 33,072 KB available. In the menu.lst file on the root directory of drive C, I added the following lines... In the first menu, I had to added the ability to boot MS-DOS 6.22 on a 64 MB hard disk image with LBA mode disabled with 4 heads and 35 sectors per track. The hard disk image is mapped in memory effectively occupying 64 MB of system memory. I also used the --ram-drive=0x9 map parameter to map a hidden RAM disk, set the --rd-base=0x5000000 parameter below it to reduce the total memory to 80 MB. With 80 MB allocated for a RAM disk and 64 MB occupied for a hard disk mapped in memory, this reduced the size of the system memory to 16 MB. In maintenance mode, the parameter --rd-base=0x400000 is used to reduce the system memory all the way down to just 4 MB of system memory. If I select "Microsoft MS-DOS 6.22 (Maintenance)" to work on the hard disk image, I had to press F8 and not load EMM386 or I will end up with a "Bad or Missing Command Interpreter" error. I can still boot from the drive without problems, but if the hard disk image is mapped as a RAM disk, then all of the contents inside the emulated drive will be lost once the system reboots. So, in order to get around this, I had to get a parallel port Iomega ZIP disk, install Windows 3.1 inside the ZIP drive (on drive D:) along with all of the software, install the Iomega ZIP utilities to lock the ZIP drive and treat it as a hard disk. And then after I exit Windows, the ZIP drive gets treated as a floppy disk again. In order to maintain the health of the ZIP disk, I had to disable the swap file. The end result is that with a lot of software installed on the ZIP disk along with Norton Desktop and the 1024x768 wallpaper, the total amount of memory was reduced to 11.6 MB. If I don't feel comfortable about that, I may have to increase the base of the RAM disk to 96 MB and leave 32 MB available. Booting MS-DOS from a hard disk image via GRUB4DOS should be done only for testing purposes. Because GRUB4DOS has problems with loading expanded memory managers in the CONFIG.SYS upon booting from the hard disk image, it's just too hard to get it to work properly. I had to either do the following: 1. Use the --mem parameter to map the hard disk image into memory which effectively reduces the total amount of system memory. 2. Don't use expanded memory managers at all. (I tested the 64 MB hard disk image when I booting successfully from the MSDOS.IMG hard disk image in a Windows for Workgroups 3.11 Virtual PC VM.) If this information is still overwhelmingly irrelevant, I don't know what else to tell you. I tried my best to get it to work as planned, but it's not 100% perfect, ya know. I'll look into other solutions to get MS-DOS working more perfectly inside GRUB4DOS in the foreseeable future.

Thank you for telling me. I'll check out the installer and run it when I have the time.

Thank you for telling me. However, the installer is in Japanese only. I was hoping that there is a English language version though. If there is, please let me know.

I installed Java 6 in the C:\Java directory and not in the C:\Program Files\Java\jre6\ directory as the installer does it by default...so, I'm afraid that it's not there. The problem here is that the installer in Java 6 Update 32 and above would not run correctly, because of the GetSystemWOW64Directory entry point is found regutils.dll.

Okay, in the stock Win2k VMware VM, I already have the GDI+, Visual C++ 2008 Runtime (both RTM and SP1) and .NET 2.0 SP2 installed already and still, Java 6 Update 37 would not install properly, complaining that regutils.dll is missing GetSystemWOW64DirectoryA couldn't be found in KERNEL32.DLL. Keep in mind that Java 6 was compiled using Visual C++ 7.1 and not Visual C++ 2008. I'm wondering if hex-editing out GetSystemWOW64DirectoryA or replacing the regutils.dll with the version from Java 6 Update 31 (file size: 278,528 bytes) will do the trick. I opened the EXE file using 7-Zip and it contains four files: zipper.exe, core.zip, regutils.dll and the zero-byte patchjre.exe. Simply replacing the regutils.dll with a older version was a no-go, because 7-zip threw up a error message, "Not implemented" and exits.

Do you have the English language version of the Java 6 Update 37 package that can be installed without the extended kernel or the UURollup? If so, let me know. I'm testing Java 6 Update 37 in a Win2K VMware VM and it still fails to install!

Option B doesn't work either as it throws a "Cannot find grldr in all drives. Press Ctrl+Alt+Del to restart.". Only Option C works. Thank you for explaining this. I didn't know that it was a warning message to begin with. I found some research regarding the issue and I'm gonna try to look into this issue more. Anyways, looking at the MSDOS.DSK file, I modified the MENU.LST to include the following: I added the --mem switch to /msdos.dsk on HD0 and MS-DOS would boot with EMM386.EXE enabled in CONFIG.SYS, however it took almost 40 seconds to boot from the hard disk image. As a consequence of using the --mem switch to map the hard drive, the amount of memory available was reduced from 144 MB to almost 16 MB. Unfortunately, since I mapped MSDOS.DSK to RAM, any changes made to the operating system inside a emulated hard disk will be lost when the system is rebooted! Without the --mem switch, EMM386.EXE would cause MS-DOS inside the VM to crash. I at point even tried a different DOS-based memory such as JEMM386 manager and it still wouldn't work. Is there a way to save the contents of the emulated hard disk image when a reboot is made? This is getting really frustrating.

You know, if the comments that I make are still overwhelmingly irrelevant, then I don't know what else to tell you and I can't blame you for that. Anyways, GRUB4DOS 0.4.4 2009-10-16 will NOT work at all on this laptop, period. If I try to install GRUB4DOS 0.4.4 2009-10-16, when I select GRUB4DOS from the boot menu, the computer will hang as I mentioned in my previous posts. It's that simple. But I boot GRUB4DOS 0.4.3, I will get the boot menu and select either MS-DOS, Memtest86+, the ability to reboot or to halt the machine. I have given up all hope to get GRUB4DOS 0.4.4 2009-10-16 (and later versions) to work on this old laptop. I'm sorry. As for the error that you described, thank you so much for telling me. I didn't know that this error about the hard disk image is by design. The hard disk image was created using QEMU-IMG using this command line: qemu-img create -f raw MSDOS.DSK -size 131072K. The hard disk image was created on this computer and it was transferred to the laptop over a network drive. The hard disk on the laptop is mapped as drive T on this computer. Now, why do I need such a large hard disk image of 128 MB? I only created the large hard disk image for testing purposes...and this is to just to install some software that was designed for MS-DOS and 16-bit Windows 3.1. That is all. As for the DOS error with EMM386.EXE, do you know what several different tests can I try to get around this error?

Yep, it is. It looks like that the newer versions of GRUB4DOS (GRUB4DOS 0.4.5 2012-10-02) is incompatible with this laptop. So...what worked is GRUB 0.4.3 released on 14 October 2007. I can now boot MS-DOS and run Memtest86+ without problems. Now that I have booted MS-DOS successfully, I'm gonna be installing Windows 3.1! Edit: jaclaz, I have a problem here when I try to run MS-DOS 6.22 from a hard disk image: The emulated disk image is writable, but the Bad or Missing Command Interpreter error only occurs when when I insert the C:\DOS\EMM386.EXE NOEMS in line 4 of the CONFIG.SYS file. And if I try to install Windows 3.1 in a emulated hard disk image, I will only be able to run Windows 3.1 in Standard Mode. Attempting to run Windows 3.1 by typing WIN throws this error message: I end up getting thrown back to the MS-DOS prompt inside the emulated hard disk image instead. Is there any way to fix this?

Okay, the exact version of the GRUB4DOS bootloader that I'm using is version 0.4.5c-2012-10-02 as this is the latest release of GRUB4DOS for version 0.4.5. Now, here's the deal. I migrated the files, DEFAULT, GRLDR, MEMTEST.IMG, MENU and MSDOS.DSK to a Windows NT 4.0 VMware VM. In the VMware VM, I left the original NTOSKRNL.EXE and NTLDR files intact. (Please note that these files are from Windows NT 4.0 SP6a.) In the VMware VM, I see the following boot menu options: "Microsoft Windows NT Workstation Version 4.0" "Grub4Dos" When I select Grub4Dos from the boot menu, I get these options: "Microsoft MS-DOS 6.22" "Memtest86+" "Reboot" "Halt" When I booted in to Memtest86+ or Microsoft MS-DOS 6.22, the VM was capable of booting the MSDOS.DSK probing 259 cylinders, 16 heads and 16 sectors per track for a total of 261,072 sectors. This was done on a single-core 2.4 GHz Pentium 4 machine. However, the situation is much different on the Toshiba Tecra 720CDT laptop. On the real laptop, I see the same options from the boot menu: "Microsoft Windows NT Workstation Version 4.0" "Grub4Dos" When I select Grub4DOS on the real laptop, I do NOT even get access to menu options from Grub4DOS that I'm familiar with. I get this error message and the system will NOT, I repeat will NOT proceed any further: This is often the case even if I replaced the NTOSKRNL.EXE and NTLDR files with the ones from Windows XP SP1, but it was a no go...so I reverted back with the files from Windows NT 4.0 SP6a. So the issue here is NOT a problem with Windows NT 4.0 itself, it has to be a problem with the fact that it might be hardware related and the fact that is a 133 MHz Pentium laptop. I mean is there anyways, to force Grub4DOS to disable A20 debugging in order to make it work on a 133 MHz Pentium laptop?

Thanks for the help. I appreciate it, but I am running into problems when attempting to load the GRUB4DOS menu now. In the boot.ini file, I added the following lines: I added the following lines in the menu.lst file in the root directory of drive C as well: But when I attempt to enter the GRUB4DOS menu, I got this output instead: What does the error code NTFS5: 2 mean? I copied the default, grldr and grldr.mbr to the root directory of drive C and now GRUB4DOS is now complaining that it cannot even find GRLDR in all drives? What did I do wrong here? Since installing GRUB4DOS on a Windows NT-based operating system is difficult, how can I correct this since getting GRUB4DOS to work on a NTFS partition?

I want to be able to triple boot between Windows NT 4.0, MS-DOS 6.22 and Memtest86+ via GRUB4DOS and here is what I have so far. 1. MS-DOS 6.22 is in a 128 MB hard disk image and it was created using QEMU. The filename is MSDOS.IMG and it is sitting in the root directory of drive C. 2. Memtest86+ is on a floppy diskette image on the root directory as well. The filename of Memtest86+ is MEMTEST.IMG. 3. The current version of GRUB4DOS that I'm using is version 0.4.4 with the build date of 2009-06-20. Drive C is formatted as a NTFS partition. I'm sorry if I'm not providing sufficient details, but I'm starting to feel tired. How can I modify the menu.lst file in the root directory of drive C in order for MS-DOS 6.22 and Memtest86+ to be listed and how can I get it to work? I'm new to using GRUB4DOS and multi-booting and I'm gonna need some help here.

Is that the driver that I'm using? Yes, it is. The card that have does not have a gold band, but rather than a silver one. The card itself is a 16-bit PCMCIA Type II device and it will fit in either a PCMCIA Type II slot or 32-bit CardBus slot on the right side of the clunky laptop. When I got the Linksys WPC11 v2.5 PCMCIA adapter from eBay, I downloaded the driver that you pointed out earlier, extracted the ZIP contents in a temporary directory and used a utility called ImgBurn to burn the contents into a CD-ROM image before burning it to a CD-RW disk. After I got the drivers, I used the CD to install the WPC v2.5 PCMCIA network card driver and configured properly after a couple of reboots. Yes, I did had to re-apply Service Pack 6a after installing the driver and yes, I am experienced with learning how to install the driver. The PCMCIA network card that I got from eBay neither had a CD-ROM nor a manual associated with it. The manual for the Linksys WPC11 can be found in \Manual\WPC11.pdf can be found on the CD-ROM. The network that we have at our house is only supporting WPA Encryption. The Encryption tab states that the WEP Encryption is disabled. Although, Windows NT is less user friendly, it is more stable thank Windows 95 itself! With that said, the problem is all fixed now!

Yep. I sure did. (One of the diskettes mentioned in the installation even overwritten the current versions of NTOSKRNL.EXE and EXPLORER.EXE with older versions! Luckly, I had to replace the older NTOSKRNL.EXE and EXPLORER.EXE with the backupI believe that it was the TOSNTSUB.Z file on disk 1 that caused that. I don't know for sure. )

I'm sorry if I was wasn't able to respond for a couple of days, but I admit that I was so utterly irrelevant in regards to my comments as I wasn't being 100% clear enough. Here's what I can try to explain as much as possible. 1. What exactly happened after booting with the PCMCIA slot empty? Windows NT 4.0 booted as usual after I pressed CTRL-ALT-DELETE to login. However, with no PCMCIA wifi card, I couldn't go online and browse the Google mainpage. 2. What exactly happened after boot with the PCMCIA slot with the card inserted? Moments after I pressed CTRL-ALT-DELETE to try to login, Windows NT 4.0 crashed with a BSOD STOP error 0x1E (KMODE_EXCEPTION_NOT_HANDLED) referencing to NTOSKRL.EXE. 3. What exact version of the drivers that I'm using? The driver is officially identifed as "Instant Wireless Network PC Card V2.5" with the driver files found in the WinNT40 directory on the Linksys WPC11 CD. 4. What exact version/type of card do I have? The version of the Type II PCMCIA card driver is version 1.3, dated 27 December 2001, available for WinCE, Windows 95, 98, Me, NT 4.0, 2000 and XP as well as Linux. On the back of the PCMCIA card, the MAC address is 000625AA59EB and as for the serial number, it doesn't even say. The page describing the Linksys WPC11 v2.5 driver can be found in these pages: A. http://homesupport.cisco.com/en-us/support/adapters/WPC11 (official) B. http://www.wireless-driver.com/linksys-wpc11-wireless-b-pc-adapter/ 5. So, what exactly happened after the BSOD went away? Immediately after BSOD, I had to unplug the PCMCIA card and restart the computer via a cold boot. After Windows NT 4.0 rebooted, I have to apply the KB835732 update (http://www.microsoft.com/en-us/download/details.aspx?id=6102). After applying the update, the NTOSKRNL.EXE kernel was updated and the STOP error went away. I can plug in the WiFi card into the PCMCIA slot without problems now. However, Windows NT 4.0 is much less user friendly than Windows 95. It has no plug-and-play support and you're gonna have to do the following in order to insert the PCMCIA card: A. Turn off the computer. B. Reboot into the boot menu if there is more than one operating system installed. C. Reboot and press the Space Bar to invoke the Hardware Profile menu. I sure hope that this is enough information, but if my comments are still overwhelmingly irrelevant, I honestly don't know what to tell you. I will explain more what updates to install if you are planning to reinstall Windows NT 4.0 either in a virtual machine or on a real PC.

The Linksys WPC11 2.4GHz Cardbus PCMCIA adapter that you linked to is a later version designed for Windows 98SE and up. The version of the card is v2.5 and it's designed for Windows 95 and later. I will have to pull the PCMCIA Cardbus out after I reboot once again. The drivers that were used were LSWLNDS.SYS and LSWL.DLL. The STOP 0x1E error went away when I applied the KB835732 update (WindowsNT4Workstation-KB835732-x86-ENU.EXE) which updated the date stamp for the NTOSKRNL.EXE file to 2004-03-18 02:20:02. As Windows NT 4.0 does not natively support PCMCIA, where can I find some third party drivers for the the Toshiba Tecra 720 CDT laptop?

Hey there again. As you may have already noticed, I recently got rid of Windows 95 on my Toshiba Tecra 720 CDT laptop and replaced it with Windows NT 4.0 Workstation and so far, I've been running into a bit of trouble here. So far, I applied Service Pack 6a with 128-bit High-Encryption Pack, Post SP6a security update rollup as well as installing Internet Explorer 4.01 SP2 and then Internet Explorer 6 SP1. In order to get the Linksys WPC11 v2.5 PCMCIA wireless network card to work under Windows NT 4.0, I had to install the appropriate drivers for Windows NT 4.0 and when the laptop rebooted, the lights went on, but when I pressed Control+Alt+Delete to login, Windows NT 4.0 crashes with this BSOD: I receive a STOP 0x1E (KMODE_EXCEPTION_NOT_HANDLED) with the offending driver ntoskrnl.exe, which as a DateStamp of 3B2800AE (2001-06-14 00:09:18). I have to use the tip of the fingernail clipper to do a hard reset of the computer. How can I fix this error that causes Windows NT 4.0 to crash when the PCMCIA wireless network card is plugged in?

Thank you so much! I'll apply the fix now and reboot. If there are any problems, I'll report back.

Thank you so much for telling me. I'll probably download a update to fix the problem and update it if there are anymore errors occurring. By the way, can I have a link to the updated file in question?

Hello! I was pretty much bored when I decided that I wanted to backup the contents of my Tecra 720CDT laptop with Windows 95 OSR2 installed. However, moments after Microsoft Backup tried to transfer the backup contents of the data from the hard drive onto one of the USB hard drives on my Win2k desktop when one of the directories on the drive is mapped as a network drive, a STOP 0x1E (KMODE_EXCEPTION_NOT_HANDLED) error occurs referencing to SRV.SYS (Server driver). The version of the SRV.SYS file (found in \WINNT\system32\drivers) is version 5.0.2195.7368 with a date stamp of 2011-08-27 01:08:22. Here are the stop errors that I received so far: 1. STOP 0x0000001e (0xc0000005, 0xbd339d1e, 0x00000000, 0x00000040) (srv.sys - Address 0xbd339d1e base at 0xbd32a000 DateStamp 0x4b20fa01) 2. STOP 0x0000001e (0xc0000005, 0xbd3b1d1e, 0x00000000, 0x00000040) (srv.sys - Address 0xbd3b1d1e base at 0xbd3a2000 DateStamp 0x4b20fa01) Version 5.0.2195.7368 of SRV.SYS (Server driver) is found in the UURollup v10c, which could be buggy and crash Win2k when transferring files over a network. Is there any way to fix this bug referencing to the SRV.SYS driver?

Why do you think that Java 6 Update 35, the newest release of Java 6 is worse than the previous release? Oracle has eventually extended the lifespan of Java 6 through sometime in February 2013.