GEOS download section
You should have a pretty good working GEOS system by now, however, maybe you need to be able to make some add-on hardware such as the CMD-HD or the RAMLink function with GEOS. Or maybe you don't have a Commodore 17xx series or compatible REU, but you have a geoRAM, or a BBGRam, or even a RAMLink to use as a ram expander. Well, here is where you will get the info and the files you need to configure those devices.
Before you go and make any changes to you new boot disk, make a backup copy of it first. This allows you to keep your original intact in case you need to start over with a disk that you know will boot up GEOS and work for you. Just use any good whole disk copier to copy your boot disk, or simply copy each file to another disk right from the GEOS deskTop. From here on, you will only have to change either CONFIGURE or GEOBOOT or both to get your additional hardware to work for you. Each of these CONFIGURE files will continue allowing you to work with a 1541, 1571, and 1581 in addition to various ramdisks.
NOTE: Never put more than one copy of CONFIGURE on a boot disk even if you give them different filenames. CONFIGURE is an AUTO-EXEC filetype in GEOS. This means that it is a program that will automatically run during bootup before the deskTop appears. You don't want two different CONFIGURE programs to run during bootup! Likewise, only one GEOBOOT file should be on your boot disk.
FD-2000 and FD-4000 DISK DRIVES
You've already got what you need to make the FD Series disk drives work. All versions of CONFIGURE will work with the FD drive as long as you are using a 1581 formatted disk. You can also use a high-density disk with two 1581 partitions on it. However, you can't access a native partition. Treat the FD drive like it's a 1581 and it will perform nicely in GEOS.
CMD HARD DRIVE
Configuring GEOS to work with the CMD-HD is simple. All you have to do is change the CONFIGURE file on your boot disk. Choose either the 64 version or the 128 version and copy it in place of your existing CONFIGURE file. As with the FD drive, only 1581 partitions can be used on the HD in GEOS. When you load and run CONFIGURE to initially configure your HD, you will select "1581". These updated configure programs can treat the HD just like a 1581.
Remember, GEOS works better with a ram expansion unit. If one is found, GEOS will use 64K of the REU for its own purposes such as for storing the additional disk drivers. You can have GEOS use the RAMLink for this purpose also. Just create a DACC partition of at least 64K (256 blocks) and then copy the CONFIG RL file to your boot disk in place of your existing CONFIGURE file. This also allows you to use the 1581 partitions on your RAMLink in GEOS. One thing you must do to use the RAMLink is it must have its device number set to 12 or higher. When you boot up GEOS and configure the RAMLink, you will be able to select "RL/RD 1581 part." from CONFIG RL's interface just like you would from a real drive. To GEOS, the RAMLink partition will be treated similar to a RAM1581 ramdisk. If you set up a large enough DACC partition in the RAMLink, you will also have a choice of configuring a ramdisk within the DACC partition. If so, you'll notice some ramdisk choices you can make.
To be able to boot from the RAMLink, you will first get the RAMLink working in GEOS as described, and then copy your boot files to the 1581 partition. This will include GEOS, GEOBOOT, CONFIG RL, and DESK TOP, or the 128 version of these files. You will use the version of GEOBOOT that you'll find on this page for the RAMLink. Now, before shutting down your system to test if you can boot from the RAMLink, first run CONFIG RL from the RAMLink. When it loads up, select "save configuration" from its menu. This way, the info for this partition will be saved and CONFIG RL will know where to point the driver to when you boot up. If you fail to do this, GEOS may or may not boot up correctly depending on how you have your RAMLink partitions set up.
GEORAM OR BBGRAM
It's quite easy to make the geoRAM or BBGRam work with GEOS, you simply replace both the GEOBOOT file and the CONFIGURE file. Just pick out the appropriate files here and replace them on your boot disk.
Here are some Configure files you can choose from:
CONFIGURE (22K) - Configure for the 64 and 17xx REU that adds support for the CMD-HD.
128 CONFIGURE (23K) - Configure for the 128 and 17xx REU that adds support for the CMD-HD.
CONFIGURE_r (23K) - Configure for the 64 and geoRAM/BBGRam that adds support for the CMD-HD.
128 CONFIGURE_r (23K) - Configure for the 128 and geoRAM/BBGRam that adds support for the CMD-HD.
64 CONFIG RL (23K) - Configure for the 64 and RAMLink that adds support for the CMD-HD.
128 CONFIG RL (24K) - Configure for the 128 and RAMLink that adds support for the CMD-HD.
These GEOBOOT files allow booting from various devices while using a geoRAM or BBGRam:
GEOBOOT (21K) - for booting the 64 from a 1541.
GEOBOOT (21K) - for booting the 64 from a 1571.
GEOBOOT (21K) - for booting the 64 from a 1581.
GEOBOOT (21K) - for booting the 64 from a CMD-HD.
GEOBOOT128 (38K) - for booting the 128 from a 1541.
GEOBOOT128 (38K) - for booting the 128 from a 1571.
GEOBOOT128 (38K) - for booting the 128 from a 1581.
GEOBOOT128 (38K) - for booting the 128 from a CMD-HD.
These GEOBOOT files allow booting from a CMD-HD while using a 17xx or compatible REU or a RAMLink DACC:
GEOBOOT (21K) - for booting the 64 from a CMD-HD.
GEOBOOT (38K) - for booting the 128 from a CMD-HD.
These GEOBOOT files allow booting from a RAMLink:
GEOBOOT (21K) - for booting the 64.
GEOBOOT (38K) - for booting the 128.
There's a lot more to GEOS than what you've experienced so far. You haven't even scratched the surface. On the next page, you can download some useful utilities, read some hints, tips, pointers, things to do, things not to do, and check out some other helpful sites on the internet. Continue on when you're ready.