ppgrainbow

Thanks for the heads up. I'm currently using the UURollup and might want to investigate what could be causing the title bar to not display...

Thank you for telling me. I will be testing the latest version of UURollup in a VMware VM to make sure it at least works. As far as I know, a temporary workaround would be to use a icon editing utility and remove alpha transparency, which only works on Windows XP and above and then save the file as a ICO extension. I'm also looking into other clever ideas to get alpha transparency removed also.

Has anyone installed Firefox 23 yet on Windows 2000? It was on Mozlla's FTP servers hours ago. Firefox 23 does work with the current revision of UURollup v11 (released on 2013-02-23). However, what I'm seeing is that the Firefox icon logo now has a black background surrounding it. In Firefox 22, the background used to be transparent. Also, when you select Help > About Firefox in the menu, the Firefox text no longer appears. Is there a way to fix the issue with the black background surrounding the Firefox logo? By the way, I might have to provide screenshots for proof... Edit: I checked the website where it has the daily updates and found that Windows2000-UURollup-v11-d20130616-x86-ENU.7z is the latest daily UURollup release. However, I don't know if it's stable enough to use. Also, I checked the release notes and found that Mozilla developers updated the Firefox logo to use alpha transparent true colour icons for Firefox 23 and beyond, for which it displays a black background instead of a transparent one. I'm wondering if there are anymore updates to UURollup, btw.

Thank you so much for providing the update to Java 6. I appreciate it. Enterprises still running Java 6 will continue to have Premier Support until December of this year, but the bad news is that Extended Support for Java 6 will ultimately end on December 2016...after that date, Java 6 will go into Sustaining Support for a indefinite period of time. This means that Oracle will no longer provide paid updates nor paid support for Java 6 after December 2016. Also, during this time frame software vendors that rely on Java will start dropping Java 6 support.

Thank you very much for the info.

For a while, I've been experiencing ways how to run the MS-DOS operating system in both a virtual machine and natively. In this example, I created a MS-DOS 7.1 virtual machine under DOSBox and I linked the disk image in GRUB4DOS so that I can natively boot the OS. Here's how you can do it: INSTRUCTIONS 1. For hard disk image and proper CHS geometry support, download DOSBox Megabuild 6 (DOSBox MB6), if you haven't already done so. 2. Download the latest stable version of GRUB4DOS. While the latest version of GRUB4DOS is version 0.4.6, I wouldn't recommend constantly updating the bootloader. 3. I used Windows 2000 as the example host OS to dual boot between Win2K and GRUB4DOS. Extract that GRLDR file onto the root directory of the boot drive. Unset the attributes and modify the boot.ini file to include the following: 4. Place the MENU.LST file in the root directory of the boot drive in order to make the dual booting work. 5. Execute DOSBox MB6, then in the DOSBox prompt type in IMGMAKE X:\BOOT.IMG -t hd -chs c,h,s -nofs to create the hard disk image. Disk geometry is limited to 1,023 cylinders, 255 heads and 63 sectors per track. However, the IMGMAKE utility is limited to 2,047 MB (520 cylinders, 128 heads and 63 sectors per track). The -nofs parameter is important as you need to create a blank disk image in which it will be prepared using FDISK and formatted later on. The best example is creating a hard disk image that has 1,000 cylinders, 4 heads and 17 sectors per track as follows: IMGMAKE C:\BOOT.IMG -t hd -chs 1000,4,17 -nofs The end result is that it will create a hard disk image with 68,000 sectors for a total hard drive capacity of 34,816,000 bytes (33.2 MB). 6. Go to Bootdisk.com and download either the Windows 98 or Windows 98 Second Edition boot disk image. You can find boot disk images at this page here: http://bootdisk.com/bootdisk.htm Using the Windows Millennium boot disk (either the one found on BootDisk.com) or the files that were created from a Windows XP boot disk is not recommended. Also, be aware that using MS-DOS 6.22 (or below) to natively boot GRUB from on modern computers will not work properly, if not at all. 7. Now that you're all set, open up the dosbox.conf (or any other DOSBox configuration file) and in the [autoexec] section, add the following in the [autoexec] category. This example will be the boot.conf file in the C:\DOSBOX directory. 8. Execute the following command to properly access the floppy disk image and the hard disk image: This will take you to the A:\ prompt in the DOSBOX MB6 VM. 9. Type FDISK to set up the hard disk image. When doing so, you'll be greeted with this message: To create a drive letter inside the hard disk image, all you have to do is select Option 1 and by doing so, this will take you to the following menu: Once again, select Option 1 to create a primary DOS partition and by doing so, this will setup a primary partition of size specified by the user. The boot drive will be drive C. If for some reason, you want to create additional drive letters inside the hard disk, don't use all of the available disk space and leave the rest for a extended DOS partition. Select Option 2 to setup an extended DOS partition to reclaim the remaining disk space on the hard disk image and lastly select Option 3 to setup the logical DOS partitions for which it will make up the available disk space within the extended DOS partition. And now that the partition(s) on the hard disk is created, you will have to make the drive Active. Press Escape from the DOS Partition menu and select Option 2 from the main menu. Once you have set up the drive(s) and set the main drive active, shut down DOSBox MB6, by pressing CTRL + F9. Do NOT press CTRL + ALT + HOME to reboot as you will lose the partition information that you created and you will have to start all over again! 10. Rerun DOSBox MB6 and boot from the floppy disk image. Type FORMAT C: /S to format the hard disk image and make it bootable. When you're finished, shutdown DOSBox MB6. In the botton line of the [autoexec] category of boot.conf change the boot parameter to read "boot -l c" in which it will change the boot drive from Drive A to Drive C. 11. Use WinImage to extract and edit the contents of the MSDOS.SYS file. Now since DOSBox has problems displaying the Windows 98 boot logo, you need to edit the file to read the following: Since there is no Windows installation installed on the boot drive, this edit will (1) prevent MS-DOS from booting the GUI, (2) displaying the Windows 98 logo and (3) will disable the log. The lines below it are required for compatibility with other programmes and must not be removed. MSDOS.SYS needs to be 1 KB or greater. Lastly, copy all of the DOS-based files from a Windows 98 installation (can be found under C:\WINDOWS\COMMAND directory) and place it in a temporary directory such as C:\WIN98.TMP. Using WinImage, make a directory inside the BOOT.IMG hard disk image called \DOS and insert the files in that directory. 12. Now that you're finished installing the files required to run MS-DOS 7.1, you have to use GRUB in order for it to boot the drive natively. Edit the MENU.LST file in the root directory with the following: With this edit, it will access the BOOT.IMG file with 4 heads and 17 sectors per track, use the RAM drive value to 0x9F set the --rd-base and --rd-size values to 0x1000000 thus reducing the RAM available to 16 MB. 16 MB is the bare minimum for booting DOS inside GRUB4DOS on a modern PC. Set anything lower than 0x1000000 and MEM will improperly report how much memory is available to the end user. Additionally, only one floppy drive and one hard drive will be accessed. If you receive a error message "Error 60: File for drive emulation must be in one contiguous disk area" use the Contig utility to defragment the drive and make the specified file contiguous on the disk image. When that's done, you will be able to succesully boot off of the BOOT.IMG image natively. To restart the computer out of MS-DOS, press CTRL+ALT+DELETE. RESTRICTIONS Unlike booting MS-DOS from a virtual machine, booting MS-DOS from GRUB4DOS as a dual boot option has restrictions. 1. You cannot use a expanded memory manager (such as EMM386.EXE) on the hard disk image. Doing so will throw in a "Bad or Missing Command Interpretor" error message and it will ask to insert a boot disk with COMMAND.COM. As far as I know, base memory is limited to 629 KB. To conserve base memory, use as few device drivers as possible such as a CD-ROM or a mouse driver. 2. Windows 3.0 will only work in either Standard Mode or Real Mode and will hang if more than 16 MB of system memory is available. This is the case when many modern PCs have far more than 16 MB of memory installed. In Windows 3.1, Standard Mode is the only option as Real Mode support was dropped. With the lack of expanded memory manager support, Windows 3.0/3.1 will treat the PC as it if was a Intel 80286. You will have to remove files that require Intel 80386 (or compatibile) support in order to make it run in Standard Mode or Real Mode (Windows 3.0 only). Windows for Workgroups 3.11 will NOT work at all when booting under GRUB4DOS as Standard Mode support has been removed. 3. To make Windows 3.0 and Windows 3.1 work under MS-DOS 7.1, use the utility called OSR2FIX. This patch will enable Windows 3.0 or Windows 3.1 to run under MS-DOS 7.1 and on a FAT32 partition. 4. Most modern video card vendors stopped providing video driver support for Windows 3.0 and Windows 3.1. Under Windows 3.1, if you want high resoultion graphics, use the generic SVGA driver and download the vgapatch tool to make it work. 5. There is no support for sound card or network drivers (either under MS-DOS or Windows 3.1) when run under GRUB4DOS. I apologise if this tutorial is vague, but I hope that this is enough information for this experience. If you have any questions, comments or suggestions for improvements in this tutorial thread, please let me know.

Thank you for telling me. The TCP/IP protocol has already been installed and it still failed to obtain a DHCP address. Instead, I had to enter the IP address manually and for some reason, Windows 95 networking still doesn't work under Bochs. I did a search for "TCR write, loop mode x not supported" and networking related problems in Bochs and it turns out that users are seriously having a hard time getting networking working properly under Bochs. The VM was setup on the Windows Vista Home Premium host OS, btw. Update: I ran the Bochs Debugger (bochsdbg.exe), entered "info device 'ne2k'" in regards to the state of the NE2000 card and this is what I found. The data below is pretty complicated and hard to decipher: I'm starting to see a lot of zeroes on all of the NE2k registers and I find that either the card is configured incorrectly or something could be wrong with the NE2K card itself.

Okay, I recently set up a Windows 95 OSR2 VM under Bochs 2.6 with 64 MB of system memory allocated to the VM. I installed the OS and applied the updates associated with it, including Internet Explorer 5.5 and I already have the NE2000 network card emulation set up. But for some reason, even if I have networking setup under Bochs, the network card in the VM doesn't work. The networking is set to DHCP mode and Bochs is failing to detect a IP address and a subnet mask (using winipcfg). The IP configuration is reading: When I go to Network options in the Control Panel, I end up having to set the IP address configuration manually as follows: And still, it doesn't work. I can't even browse the internet using Internet Explorer at all...all I get is a "This page cannot be displayed". I enabled the logs to see what could be the problem here and this is what I found and the logs have to do with the NE2K device. The full version of the logs can be found here: Here's a snippet: 00000252000e[NE2K ] device not ready to receive data 00006048000e[NE2K ] device not ready to receive data 00078624000e[NE2K ] device not ready to receive data 00091476000e[NE2K ] device not ready to receive data 00100044000e[NE2K ] device not ready to receive data 00105840000e[NE2K ] device not ready to receive data 00125748000e[NE2K ] device not ready to receive data 00137844000e[NE2K ] device not ready to receive data 00152208000e[NE2K ] device not ready to receive data 00172872000e[NE2K ] device not ready to receive data 00208908000e[NE2K ] device not ready to receive data 00230580000e[NE2K ] device not ready to receive data 00235620174e[NE2K ] DCR write, loopback mode selected 00235620174i[NE2K ] DCR write - AR set ??? 00235620201i[NE2K ] RCR write, monitor bit set! 00235774446i[NE2K ] TCR write, loop mode 1 not supported 00238339581i[NE2K ] TCR write, loop mode 1 not supported 00238339724i[NE2K ] Physical address set to b0:c4:20:00:00:01 01387833607i[NE2K ] TCR write, loop mode 1 not supported Here's the current configuration of what the Windows 95 Bochs VM looks like: Is there any way to get networking working properly under Bochs? I already installed the latest version of WINPCAP and configured Bochs with the Novell 2000 compatible adapter settings that niclister.exe showed me, but it turns out that NE2000 is not properly initalised.

Hello, I'm trying to experiment the ability to gain direct access to my 250 MB Iomega Zip drive which is located on PHYSICALDISK2. When I try to run the LockDismount 0.3.0 utility under Windows 2000, I end up receiving this error message: Moments after receiving this error message, I get another error message as well. For some odd reason, this utility works under Windows Vista and even on Windows XP, but not on Windows 2000 despite the fact that LockDismount is compiled using Visual Basic 6 (using MSVBVM60.DLL). When I created a virtual disk image from a physical drive, Virtual PC is reporting that the drive is not mounted. Furthermore, I placed the LockDismount in a directory on the NTFS-formatted drive E and it still doesn't work. I'm sorry if I'm not providing sufficient information here, but is there any way to fix this this issue? If not, are there any other utilities that will lock a physical disk so that it can directly gain access to it?

Thank you for telling me. I found that Shockwave Player 12 uses EncodePointer and DecodePointer from MSVC++ 2010 and at absolute minimum, the CRT included with MSVC++ 2010 requires at least Windows XP Service Pack 2 or Windows Server 2003 Service Pack 1.

It looks like that the bug 7166889 has been removed and GetSystemWow64DirectoryA will eventually not be removed in Java 6 as it is nearly End of Life. And Java 6 Update 41 is going to be the last planned publicly released update. After this month is over, enterprises still running Java 6 will have to sign up for a contract with Oracle that will last through December 2016. Unfortunately, at that point, enterprises will be clearly out of luck. Furthermore, Extended Support for Java 1.4.2 is coming after this month after which it will no longer be support at all.

Microsoft Windows Fundamentals for Legacy PCs (Windows FLP) is based on the Windows XP Embedded codebase and is designed for older and less powerful hardware. Windows FLP is not a full-fledged operating system and only made available to Microsoft Software Assurance Customers and it is neither available to retail nor OEM. Released on 8 July 2006, Windows FLP is designed as a inexpensive upgrade towards organisations that had a number of Windows 98/Me computers (that was on the brink of losing all support from Microsoft at the time) in their corporate organisation, but lacked the hardware that is necessary to run Windows XP at the time of its release. Windows FLP requires about 610 MB of disk space (as opposed to the 1.5 GB disk space requirement for Windows XP) and it has a smaller feature set than Windows XP. The downside is that Windows FLP does not include Paint, Outlook Express and Windows games such as Solitaire. Another limitation is the absence of the Compatibility tab in the Properties... dialog box for executable files. Windows Thin PC (based on the Windows 7 codebase) replaced Windows FLP on 6 June 2011 as Windows XP was being phased out.

I do not have the following lines are not present in the [386Enh] section of the SYSTEM.INI file And the swapfile has already been is disabled. As Windows 3.1 is on a FAT32 partition under MS-DOS 7.1, it will not accept a permanent swapfile due to INT13 and 16-bit FAT restrictions. It's just that Windows 3.1 hangs when it is run on two or more cores or on some chipsets.

First of all, (1) The MS-DOS 7.1 IO.SYS has already been patched using Win3xStart to allow Windows 3.0 and Windows 3.1x to run under MS-DOS 7.1. And (2), I already patched WIN386.SYS to avoid the Current Directory on Exit bug when using Windows 3.1. The size of the USB flash drive that I'm running Windows 3.1 on is 4 GB (3.84 GB) in capacity and it's formatted FAT32. The only problem is that Windows 3.1 hangs at the splash screen when attempting to run in 386 Enhanced Mode. It's not a problem when it's done in Standard Mode. Am I missing something in regards to modifying IO.SYS to allow Windows 3.1 to run in Enhanced Mode here?

I agree. MS-DOS and Windows 3.1 is only designed to run on one core. Do you or others have any idea what timing issues are being unreported in Windows 3.1 that causes the GUI to freeze when attempting to start up in 386 Enhanced Mode?

Okay, here's what I did. In the CONFIG.SYS: 1. In line 3, I added "stacks=9,256". 2. In line 5, I added "REM device=c:\dos\emm386.exe noems i=b000-b7ff /verbose" so that EMM386 wouldn't load. 3. In line 6, I replaced EMM386 with UMBPCI by adding "device=c:\dos\umbpci.sys". When I rebooted, I found that UMBPCI.SYS driver ends up using D400-DFFF for its upper memory and that it found the Intel 965M chipset. 4. And in line 7, I also removed "auto" from "dos=high,umb as well". Here's the final result so far: I did not do much change in the AUTOEXEC.BAT file. All I did was to REM out "lh mouse" in line 5 and "idle" in line 8. When I followed your procedure, I though that it would work, but when I typed "win" or "win /3" at the DOS prompt, Windows 3.1 would STILL hang at the splash screen. I forgot to note that I'm booting MS-DOS 7.1 on a dual-core processor. While MS-DOS 7.1 has detected CPU 0 and CPU 1 at boot, it will only use CPU 0 (the first core of the first CPU) due to OS architectural limitations. At this perspective, I suspect that this might cause some problems when attempting to run Windows 3.1 in 386 Enhanced Mode. Is there a way to get around this issue here?

Has anyone gotten Adobe Shockwave Player 12 and Adobe Flash Player 11.6 installed with the latest daily UURollup? If so, did it work? If you have Windows 2000 installed without UURollup or KernelEx applied, can we look into what entry point dependencies Shockwave Player 12 uses that do not exist on Windows 2000? I just noticed that Adobe used MSVC 2010 on its Shockwave Player now.

I recently experimented my attempts to boot MS-DOS 7.1 off of a Ativa Flip 4 GB flash drive and in all, things were successful. However, when I attempted to run Windows 3.1 while in pure DOS residing on the USB flash drive, the 16-bit OS stops responding (hangs) on the Windows 3.11 splash screen when run with the WIN /3 command to run Windows in 386 Enhanced Mode. To correct this, I had to press CTRL-ALT-DELETE to reboot. Windows 3.1 was set up through VMware Player with the drive locked so that VMware Player can gain direct access to the USB flash drive. Here's what I've done so far when I set up the boot device under VMware: 1. I got Windows 3.1 installed using 6 floppy diskette images and applied updates to it. 2. I used a utility Win3XSTART to make Windows 3.x run under MS-DOS 7.1 and on the FAT32 formatted USB flash drive. 3. I used the generic Super VGA driver and patched the driver to make it work under Windows 3.1. 4. I used a hex-edited WIN386.EXE so that no data corruption exists in the \WINDOWS directory pointer. 5. I used a utility called HIMEMX.EXE to limit the total system memory to 64 MB even though DOS is reporting 66,512 KB of memory available to the system. Here's what I got down in the CONFIG.SYS: And for the AUTOEXEC.BAT file, here's what I got so far: Other than that, Windows 3.1 works when 1. Running under VMware Player. 2. In native MS-DOS and in Standard Mode (WIN /S). 3. And running it on the Compaq TC1000 by selecting the USB flash drive as the boot device. I'm sorry if I failed to provide sufficient information, but is there a way to fix the hanging issue so that Windows 3.1 can run on a USB flash drive? If the fix is successful, I will provide instructions on how to natively boot MS-DOS and Windows 3.1 on a unsupported motherboard. The laptop that I'm using is a ASUS G1S-B1 gaming laptop with a 2.4 GHz Intel Core 2 Duo T7700 processor with 2 GB of DDR2 memory. By using the MS-DOS 7.1 version of HIMEM.SYS, the Windows 3.1 in Standard Mode will only be able to address up to 512 MB of system memory.

When I try to display the sample page that you provided, I get this error message: But other than that, the latest version of Microsoft Silverlight works on other websites that I go to.

I'm using the main desktop PC which as Windows 2000 on it. The laptop that I'm currently using has Windows Vista Home Premium (32-bit) and so far so good, the laptop is working as is.

The USB drivers found on the DataBook CD-ROM provide connectivity through either a USB 1.1 or USB 2.0 port under Windows 98. The PCMCIA drivers are the legacy plug-and-play drivers can connect through an available 16-bit or 32-bit PC Card (PCMCIA) slot under Windows 95 OSR2 and Windows NT 4.0. The PCMCIA drivers are known to also work under Windows 98, Millennium, 2000 and XP. I'll probably find the CD so I'll see what I mean by this.

That's correct. There is a small circle found on the back of the Travelstar 8E unit where you have to connect to the adapter with. As for a PCMCIA-to-USB adapter, I will look getting a PCMCIA-to-USB adapter and how to get it working on the ASUS G1S laptop.

I checked the manual for the ASUS G1 laptop and on page 16, I find that it does have a PCMCIA 2.1 compliant PC card. So how am I connecting the unit to one of the USB slots? I had to use the DataBook 5 volt AC/DC outlet power plug connected to a surge protector and then plug it into a USB slot. The Travelstar 8E connects to a PCMCIA slot on the Compaq TC1000 and it works well without any problems. If I still won't clearly answer more or if I complicated things of what I answered...I just don't know what to tell you. I find that it's just way too much work to get the Travelstar 8E device to work correctly under Windows Vista. I'm sorry jaclaz and submix8c, but I'm gonna have to give up here.

If you're referring to the Microsoft WPD Filesystem Volume driver, the VEN_DEV listed in drive properties...it does not even have any information at all. It's just blank. Is the VEN_DEV variable found in Hardware IDs under the Details tab in the Device Manager's Driver Properties? Just curious to ask. In order to connect the IBM Travelstar 8E drive, I have to use one of the USB 2.0 devices and the unit is connected for the first time, I have to use the CD to get the drivers installed and it just will not work correctly under Windows Vista and higher due to lack of driver support. I can't use PCMCIA, because it doesn't have it. It only has a Express Card slot and you can't use PCMCIA cards in a Express Card slot.

Thank you for the info. The Travelstar 8E is the rugged enclosure for the IBM DYLA-28100 hard drive. Datazone Corp provided the drivers for the DataBook USB and PCMCIA devices. When I attempted to install the drivers that you provided, I got this error message: I must be doing something wrong here to attempt to get the unit working. The driver that I downloaded didn't even provide instructions for it at all. Would I either have to: 1. Manually copy the files to the \WINDOWS\SYSTEM32\Drivers directory? 2. Get the generic USB storage device drivers that will work with the Travelstar 8E under Windows Vista? Let me know what you can come up with.