Ramdrive Menu | Ramwin 98 | Full screen |
OverviewThis is a Compressed drive which can contain Windows 95 or Windows 98 files. This can be a full installation with many optional programs as well. Once created, you can operate the computer with no hard drive installed. If you have Windows 9.x, you have most of what you need. You start by creating a compressed drive. Since Windows 98se's Drivespace 3 can create compressed drive up to 2gb, you are limited mainly by how much memory you have and how much storage space you have to work with. This Windows can be used as an emergency access to your computer if the installed Windows fails to boot. It can allow you to recover your files and save them to another drive. Depending on how much you install, it may or not work on another computer. Obviously if you install video drivers for the computer, another computer having a different video card would not be compatible. Also, if the the Ramdisk requirements exceed the availability of another computer, it won't work.
|
System RequirementsTo start with you will need either Windows 95 or Windows 98. You will need a computer with enough RAM to create a ramdrive big enough to contain the Windows on the compressed drive and have enough remaining memory for Windows. For Windows 98, I would recommend 512mb of RAM. I started out with a 300mb CVF. With 384mb RAM, you might get by with Windows 98. But there is no room for expansion. Windows 95 needs less space and less memory, so you could get by on less than 300 mb RAM. You will need a FAT 16 partitioned hard drive to install to. Drivespace files can neither be created nor run on a FAT 32 partition, which is the standard on most Windows 98 systems. I created mine on a 540 mb drive to begin with. You will need the Franck Uberto Ramdisk Utilities which will create Ramdisks up to 2gb in size.
|
Step 1: Installing the Ramdisk.While this is optional during installation, I recommend setting up the Ramdisk so you can make sure Windows will work with it. If you do not have the Franck Uberto Ramdisk Utilities you can do an internet search for fu_rd19i.zip. Or you can down load fu_rd19i.zip here. After you unpack the utilities you must make sure you have: In the AUTOEXEC.BAT file you need the line:
|
Step 2: Create a Compressed Drive.You must to have an operational Windows with Drivespace installed to begin with. Since the program will scandisk the drive first, this could take quite a while. The Drivespace file can only be created on a FAT16 partition. I like to create a Uberto Ramdisk and create the file there. However, I ran into a size limit of about 315mb that I couldn't break there. The "Blue Screen Of Death" would be the result. I had to use a hard drive to create my current 576mb CVF. I designate the file as R drive. You can specify another letter. It is advantageous to use a high letter so you won't conflict with fixed disk letters if you have several drives and/or partitions. NOTE: When you create a Compressed drive, and even sometimes when you mount an existing drive, a C:\DRVSPACE.INI file is created. When you restart the computer, the Drivespace Driver will be loaded in memory. This can sap your available memory and I have had it cause the computer to crash during bootup. Unless you are booting to a compressed drive, this file is not necessary. I added a line to delete the file at bootup. | |
1. | Click Start, Programs, Accessories, System Tools, DriveSpace. After a short system scan, the menu should open. All available drives should be listed. If you setup a Ramdisk, it should be there with the letter you assigned. |
2. | Highlight the drive you want the CVF to be created on. This must be a FAT 16 drive with enough free space to accommodate the file you wish to create. |
3. | Now click on the Advanced menu. Select Create New from the drop down menu. A screen should appear with the options for drive letter assignment and file size, and giving you an estimate of the space the drive will have. When you click Start, the existing drive will be tested and the compressed drive setup and finally mounted. If you do this on a Ramdisk, this may take 1 to 2 minutes. But if you create it on a hard drive, it may take more then an hour. When it completes, don't allow a restart as the CVF will be lost if on the Ramdisk. The CVF created will have a name DRVSPACE.001. If it is on the Ramdisk, again on the open the DriveSpace menu. |
4. | Highlight the compressed drive, click on the Advanced menu, then select Unmount. |
Now you can copy the CVF to a hard drive. Note that while you can copy the file to a FAT 32 partition, you cannot open it while it is on a FAT 32 partition. Windows may not let you copy the file. If you run into that, rename the file. Then you can copy or move it. You will have to name it back before you can use it. The file will also have the R, H, and S attributes set. You can remove these to make the file normally visible. |
Step 3: Setting Up The Computer For Installation Of Windows. It is preferable to install the Windows on a drive with nothing else on it. While you can have a Windows on C drive and install a new Windows on R drive, the boot files on your C drive will be replaced making your C drive Windows inaccessible. So you need to backup the: If you are installing to a clean drive, you only need 3 files on it: While you are installing the Windows, the CVF must be on a hard drive. Windows WILL reboot and if what was installed is to a Ramdisk, it will be lost and you will end up starting over. So at that point that line would be:
|
The Boot DiskYou need the same boot disk whether you want a bootable CD or to just boot from a floppy disk as you need a source for the bootable CD.
This will leave you plenty of room on the floppy for more optional files if you want to crowd it.
|
The DRVSPACE.INI file.
|
The CONFIG.SYS file.Since the files called up by this file are in the same directory on the same drive as this file, complete paths are not required. This makes it a little more flexible if the drive they are on is different.
|
The AUTOEXEC.BAT file.Files called up from this file can be executed from the command line. Since MSCDEX.EXE is in the same directory on the same drive, the path is not required. Note that SCANDISK is called from the CDROM. After the CDROM is available, files on the CDROM can be executed much faster than those on a floppy disk. So this speeds the process a little.
|
The CDROM.When the DRVSPACE.001 is prepared to be copied to the CDROM, it should be renamed as DRVSPACE.000 and have its attributes removed. When Scandisk mounts the CVF it only seems to recognize the 000. The DOS directory could have all of the DOS files. You could even have other programs and utilities/games stored on the same CD as long as there is room. So it could be a super Windows 98 Startup Disk.
|
Alternative Method 1The method outlined above is the easiest to setup. But it also uses the most conventional memory. Since the DriveSpace driver uses a lot of memory, a substantial amount of Conventional memory is used. And in order to copy the CVF from the CD to the Ramdrive, the CDROM driver and MSCDEX.EXE must also be loaded in memory. On my system, this results in less than 500kb remaining when Windows starts. When making a normal bootable CD, the boot partition is limited to the 1.44mb capacity of a floppy disk. Ahead Nero Burning Rom has an option to image a hard drive as the boot partition of the CDROM. For this you have to have an appropriately sized hard drive partition. This hard drive partition cannot be larger than the capacity of the CDROM. So if you have a 700mb CD, you have to create a 700mb or less partition on the hard drive. When this CD boots, it will be C drive. By setting all the files to copy from the C drive to the Ramdisk, instead of the A drive and CDROM drive, you eliminate the need for CDROM drivers. This eases up a lot of the Conventional memory usage. Windows will load the CDROM in a normal manner when it starts. I don't know yet if you will be able to change CD disks as the C drive would no longer be valid. This could create a problem for Windows. I have not tried this method yet.
|
Alternative Method 2
This method, like Alternate Method 1 above boots as C drive. However, it this version DriveSpace is not used either. This, therefore, uses far more space on the Ramdisk and in many ways more involved. You can still use a compressed drive to get the Windows set up. But once done you use the LFNBK utility to remove and store the long filenames. Now you copy all the files in open format, or, as I prefer, PKZIP them. At bootup, the files are unzipped from the CDROM to the Ramdrive. The LFNBK is run from the WINSTART.BAT as Windows starts, restoring the Long Filenames. In this method you have neither the CDROM nor the DriveSpace using up memory. I have not tried this method yet. |
As for the "Method 2" I haven't experimented with that yet. If you write to a 700mb CDR or RW, you would have to have a hard drive with a 700mb or less C drive partition which you would use for the CD. Therefore you would use that drive to perfect the boot process then copy it to the CD as a bootable CD. When you boot the computer from that CDROM, no drivers are needed. That CD will become your C drive regardless of your existing harddrive partitions. So your normal C drive would become D drive. Since you cannot boot Windows from a CDROM (as Windows wants to write to the host drive), you must copy the files to the RAMDISK and run Windows from there. If you copied the files directly from the CD to the RAMDISK, you would be limited to 700mb or less. However, using PKWARE's PKZIP DOS utilities, you can compress the files to the CDROM allowing a capacity most likely exceeding 1.5gb. This is where LFNBK comes in. If you set up your Windows on a Drivespace drive assigned letter R, once you have it working properly, you run LFNBK (located on the Windows Install CDROM at: Once you have all this accomplished, use: When the computer starts, the CD will be C drive without the need for drivers. The boot files set up a RAMDISK as R drive. Then the ZIP files are unpacked to the RAMDISK with (example): When you set up the source hard drive, you will not need the DRVSPACE.INI file nor the DRVSPACE.001 (if you had it on that drive) when you create the CD as these will no longer be needed. So that is more memory that will be freed up. Let me know how this goes as it will be a while before I have a drive available to perfect this with. I have to use a 540mb drive or make a 700mb partition on a bigger drive. Either way I have to backup the data. Hopefully this is all the information you need to get going. Note: When Windows 98 is run on a computer with more the 512mb of RAM installed, you will most likely get a memory crash. You should be able to get around that by adding the line: |
How It Works!After you create a properly working Windows on the DriveSpace drive, you can write that CVF to a Writable or Rewritable CD. You can can boot from a floppy disk which loads the CDROM drivers and have just a simple CD disk with the file on it. Or you can make a bootable CD using the same boot disk. When the bootdisk or CD boots, After loading the memory managers and the DriveSpace Driver, it creates a Ramdisk as drive R. The CD is made accessible. Then the CVF on the CD is copied to the Ramdisk R. When the copy is completed, scandisk /mount is executed which activates the compressed drive making it accessible. At this point Windows is now able to start, just as it would if the file was on a hard drive. The startup of Windows generally progresses much faster. And programs called up from the Ramdisk pull up faster. If you have a hard drive operating, a ZIP disk, Network drive, Writable CD or a floppy disk, you can save files to those. Anything on the Ramdisk will be gone forever if there is a power failure or the system is rebooted. This is pretty much what works. I will have to double check as I have been changing boot files trying to free up more memory. One method I tried is called Mar & Release. This program allows you to remove a driver from memory. It worked. I was able to unload the CDROM from memory after copying the CVF to the Ramdisk. However, the system would crash when I was running under the command.com. It tested under Norton's NDOS command processor. But although it freed almost 50kb of Conventional Memory, Windows would crash while starting. On my system I put the Windows swap file on my Ramdisk. I also put the Temporary Internet Files on the Ramdisk. When I ran this Ramdisk only system, I did not have a V drive (my Ramdisk) to swap to. So by default, Windows swapped to its own directory which maxed out my CVF almost immediately. Since I run a 576mb CVF on a 900mb Ramdisk,I need to redirect the Swap and Temporary Internet Files to the remaining space on the Ramdisk. I either have to set Windows up that way are add the SUBST command to overcome this problem. So when I get to it I will try Alternate Method 1. |
Comment to PoliTalk |
And That's My |