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.