diff --git a/Create-CF-Volume.gif b/Create-CF-Volume.gif new file mode 100644 index 0000000..c388cd7 Binary files /dev/null and b/Create-CF-Volume.gif differ diff --git a/change-log.htm b/change-log.htm new file mode 100644 index 0000000..8bd21a7 --- /dev/null +++ b/change-log.htm @@ -0,0 +1,480 @@ + + +
+ + + + +CiderPress has five distinct components:
+In addition, CiderPress uses the NufxLib library to access NuFX (ShrinkIt) +archives, and zlib to compress and expand ".gz" and ".zip" files.
+Some common questions and solutions. Return to main +page.
+If the CF card was previously formatted for +Windows or a digital camera, it may still look like a valid volume, +and Windows will assign a drive letter to it even though the card holds +nothing but Apple II data. It may even allow you to try to open files with +garbled names. If try to use the CiderPress Open Device or Volume Copier +features by selecting the drive letter, you won't see your Apple II data. +
All you need to do is open the card as a physical (numbered) device +rather than a logical (lettered) device. Better yet, update the CF card +with the newer version of the utilities, available from Reactive +Computers; this will clear out the Windows volume data so the problem (and some others) +don't arise. + +
This isn't something that CiderPress currently helps with. There are, +however, a number of useful utilities, as well as sites with disk images. +Check the comp.sys.apple2 +FAQ site for information, especially this +section. ADT is probably the most popular program, but using ShrinkIt +to create disk images and transferring them over a null modem cable or AppleTalk +network works too.
+If you have a SuperDrive or floptical drive on your Apple II, you can read +and write 1.4MB floppy disks. To copy disk images, just create images with ShrinkIt, copy them +to a 1.4MB ProDOS-formatted floppy, then copy the disk images off with +CiderPress. If +you're planning to use them with an emulator right away, copy them off with the +"bulk" disk image converter so that they'll be in the format your +emulator prefers.
+While CiderPress supports ProDOS-formatted 720KB and 1.4MB 3.5" floppy +disks, it cannot support 800KB 3.5" disks or 140K 5.25" disks due to +limitations of the disk drives used on PCs. (A program called "disk2fdi" +provides some support for reading 5.25" and 3.5" Apple II disks on the +PC.)
+You need to convert the disk image to a format accepted by software on the +Apple II and then transfer it over. Check the links in the previous answer +-- software that helps you copy disk images to the PC will usually help you copy +them back.
+Check the Google +directory for a list of sites. AppleWin and KEGS are the most popular +for Windows.
+Possible reasons:
+When pasting files into a ProDOS disk image, you can choose the directory +into which the files should go. If the disk image doesn't have any +subdirectories, all of the files will be pasted into the volume directory, which +only holds 51 files. You need to paste the files into a subdirectory +("folder"), which can hold an effectively unlimited number of files.
+If you were copying from a set of nested subdirectories, and you want to preserve the +original structure, disable the "Strip pathnames when pasting +files" option in Edit->Preferences (or paste with Edit->Paste Special +and select "keep full pathnames"). If you were copying from a +single subdirectory, or you want all of the files to be pasted into one place, +you will need to create a subdirectory with Actions->Create Subdirectory +first, and then paste into that.
+You can see how much free space a disk has with the File->Archive Info +feature (just hit Ctrl-I after opening the disk image).
+CiderPress tries to correctly identify the sector ordering and filesystem of +every disk image, but in some cases it's not possible. The most common +reason is that the disk image isn't in a recognized format (DOS, ProDOS, Pascal, +CP/M, or RDOS). Many games were shipped with custom disk layouts, usually for +copy protection reasons.
+In some cases, disks with modified versions of standard file systems will fail to be +recognized. This is most common with "customized" DOS 3.3 disks +that have abbreviated catalog tracks.
+Disk images that can't be opened with "Open..." can usually be +opened with the Disk Viewer in the Tools menu. If the Disk +Viewer can't open the image, then either it's stored in a file format CiderPress doesn't +support, or it's not a disk image at all.
+ +The disk format auto-detection algorithms rely on finding the disk catalog +track. If it's very short, or partially damaged, CiderPress won't +recognize the disk. In some circumstances you can specify the format +manually:
+ +This can also be used to select which half of a hybrid DOS/ProDOS image to +use.
+ +CiderPress runs an extensive set of consistency checks on disk images before +it will allow them to be modified. Problems found might indicate damaged +files, or might only indicate the potential for damage.
+ +For example, if some of the sectors of a file are not marked as "in +use", the next file you copy to the disk could overwrite parts of the +existing file, corrupting it. CiderPress prevents you from making +damage worse by treating such disks as "read only".
+ +Some DOS 3.3 software shipped with "title" files in the +catalog. These were only meant to highlight portions of the catalog, not +hold data, so sometimes the software authors would use one sector in the catalog +track as the "storage" for all of the titles. CiderPress will +detect multiple files sharing the same storage, and mark them as +"suspicious", meaning that their data might be present but that +altering the files could have unforeseen consequences. +"Suspicious" disks are also marked "read only".
+ +Some ".hdv" files are undersized, and grow as you add files to +them. CiderPress thinks these are damaged, because the size that the +volume claims to be is much larger than the actual number of blocks in the +file. You can tell what the difference is by opening the volume and +selecting File->Archive Info (or hit Ctrl-I).
+ +To be able to write to these disks with CiderPress, you need to expand them +to their full size. One approach is to force your emulator to expand +them. To do this, launch a ProDOS block editor within the emulator, and +open the last block on the disk (e.g. 65534 on a 32MB image). Read the +block and write it back.
+ +Another approach is to create a new volume and copy all of the files +over. To do this:
+ +That's it. For some emulators it will be necessary to close the file in +CiderPress (File->Close or Ctrl-W) and then rename it from ".po" to ".hdv".
+ +Some (all?) DiskCopy utility programs on the Macintosh require the correct +file type and creator type values to be set on disk image files. If you +try to open a ".dsk" file with a generic file type, you'll get an +error message claiming that the file format isn't recognized. The correct values +are 'dImg' for the file type and 'dCpy' for the creator.
+ +You can use ResEdit, BBEdit, or Norton Utilities to change the type and +creator. If you're using PC Exchange on the Macintosh to copy the images +off of Windows-formatted disks, you can configure it to set the type +automatically for ".dsk" files. Take a look at this +page for more information.
+ +Copy a 720KB or 1.4MB ProDOS disk image to a PC-formatted floppy disk with +"Volume Copier" in the Tools menu. If you don't have a disk +image handy, create one with File->New->Disk Image.
+ +CiderPress does not perform low-level disk formatting, e.g. reformatting an +800K disk for 720K. From Windows, open My Computer, right-click on the +floppy drive, and select "Format".
+ +Sort of. It works reasonably well under Wine (http://winehq.org/), +though you need a copy of "windows\system32\mfc42.dll" from a Windows +system. Wine does crash occasionally, but many of the features work.
+ +Windows emulators, such as VMware, work +fully.
+ +Yes. Take a look at our feature request list.
+ + + + diff --git a/features.htm b/features.htm new file mode 100644 index 0000000..9b59166 --- /dev/null +++ b/features.htm @@ -0,0 +1,247 @@ + + + + + + + + +Full access to ShrinkIt archives (.shk, .sdk, .bxy, .sea, .bse) is provided, +including:
+It's like having "ShrinkIt for Windows". Viewing and extracting files from Binary II files +(.bny, .bqy) and AppleLink Compression Utility archives (.acu) is also +supported. ShrinkIt archive access is provided by NufxLib, the library used by the +NuLib2 archive utility since early 2000. +Archives created with NufxLib are nearly identical to those created with GS/ShrinkIt.
+ +CiderPress has the ability to identify nearly all Apple II disk image formats +automatically. Supported file formats include:
+The image file format, filesystem, and sector ordering are determined +automatically for most disks. The settings can be overridden if necessary. +Images larger than floppies, such as ProDOS and HFS hard drive partition +images, are fully supported.
+The +recognized filesystem formats are:
+DOS, ProDOS, HFS, and UCSD Pascal filesystems are fully supported. You can +view, add, extract, rename, and delete files, as well as create bootable blank +disk images. Change disk volume names and DOS volume numbers. Create +subdirectories and change file types on ProDOS disks. Files on CP/M and RDOS disks can be extracted and +viewed. CiderPress also recognizes the following "meta-formats":
+ +Direct Access to Physical Devices
+ +With CiderPress you can directly access physical devices on your PC. +For example:
+ +With the included volume copier, you can also copy partitions or +multi-partition volumes to and from physical media. This allows you to extract partitions +from CFFA cards, CD-ROMs, and hard drives, and use them with an emulator. +Back up your hard drive to a block image file in seconds, and restore the whole drive, +a single partition, or individual files quickly and easily.
+ +All of the above requires appropriate hardware, and some versions of Windows +work better with certain hardware than others. See the Hardware +Compatibility page for details about what you need and what you can expect.
+ +Built-in File Viewer/Converter
+The file viewer can convert several formats for easier viewing on modern +systems:
+In addition, any fork of any file can be viewed in its "raw" state +or as a hex dump.
+Text and graphics can be cut & pasted from the file viewer to +other applications, or sent directly to your printer. The file converters can be applied when extracting +files as well, allowing you to convert disks full of source code or images +easily. It takes the same amount of effort to convert one AppleWorks +document or one hundred.
+Unsupported formats with recognizable extensions, such as ".GIF" +and ".JPG", are displayed in an external viewer when double-clicked.
+ +Disk Image Creation and Conversion
+ +The disk image creation tool allows you to create blank, bootable disk image +for DOS 3.2/3.3, ProDOS, HFS, and Pascal disks. ProDOS volumes can have arbitrary sizes +up to 32MB, and HFS can go up to 2GB. Resize volumes by copying & pasting between them, or use +the one-step disk-to-file-archive and file-to-disk-archive features.
+ +The disk image converter easily converts disk images to any other suitable +format. Use it to add or remove 2MG headers, or convert .PO to .NIB and back + again. Convert your 800K ShrinkIt disk images to and from DiskCopy 4.2. +You can optionally add gzip compression for reduced storage size.
+ +If you have a large collection of images that you want to convert to a +different format, use the bulk image converter to migrate them all in a few easy +steps.
+ + + +CiderPress includes some other handy tools:
+ +Included as a separate application, Multi-Disk Catalog (MDC) +allows you to generate file listings from hundreds of disk images with only a +few mouse clicks. Just select the images and the automatic format +recognition does the rest.
+ + + + diff --git a/hardware.htm b/hardware.htm new file mode 100644 index 0000000..ea3738a --- /dev/null +++ b/hardware.htm @@ -0,0 +1,168 @@ + + + + + + + +CiderPress can access floppy disks, CD-ROMs, CF cards, hard drives, and other +devices. Whether or not it can do so on your system depends on the +specific set of devices you have and what version of Windows you're running. +Return to main page.
+As the saying goes, "your mileage may vary". The only way to +know for certain if something will work is to try it and see.
+Device | +Win2K/XP | +Win98/ME | +
Lexar Universal Card Reader (USB, model #GS-UFD-20SA-TP) | +Works. Card size in Open + Volume dialog is way off. | +Does not work. | +
SanDisk ImageMate SDDR-31 | +Works. | +Partially working. Data + can be read, but writes only pretend to succeed. | +
ETI card reader (USB, model # unknown) | +(not tested) | +Partially working. Data + can be read, but writes fail. | +
SanDisk 6-in-1 reader | +Works. | +(not tested) | +
IBM PCMCIA card adapter | +Works. | +(not tested) | +
SanDisk CompactFlash PC Card Adapter (model #SDAD-38-A10) | +Works. | +(not tested) | +
One common problem in Win98 is refusal by the CF reader driver to allow +access to unrecognized logical volumes ("logical volumes" are lettered +drives, like "C:"). In such cases, the card will not even show +up in the logical volume list. Win2K and WinXP are usually better about +this.
+Depending on your hardware and software configuration, you may be able to +open your card reader by name (e.g. "SanDisk Imagemate II Direct-access +device"), rather than drive letter. In this case +you're actually using the ASPI layer to access the device, which is a little +strange since CF card readers aren't SCSI and don't work like CD-ROM +drives. This does appear to work for reading, but fails for writing. +Depending on which ASPI implementation you have installed, writes may be +rejected or may appear to succeed but not actually go through.
+Thus far, no fully-functioning CF configuration for Win98/ME has been found.
+ + + + diff --git a/images/Thumbs.db b/images/Thumbs.db new file mode 100644 index 0000000..0468bb5 Binary files /dev/null and b/images/Thumbs.db differ diff --git a/images/awp-eagle.htm b/images/awp-eagle.htm new file mode 100644 index 0000000..f342684 --- /dev/null +++ b/images/awp-eagle.htm @@ -0,0 +1,31 @@ + + + + + + + +View documents and graphics. The above are file viewer windows +from two instances of CiderPress. The first is viewing a 3200-color image +of an eagle, using the full palette of the original. The second is an +AppleWorks 3.0 word processor document, converted for use in Windows. CiderPress supports many AWP formatting commands, including left +and right margins, text justification, and text face changes such as bold, +underlined, and +superscripted text.
+You can extract files in their original form or in converted form. The +eagle image extracts as a Windows BMP file, ready for use in any application +that handles graphics. The AWP document extracts in Rich Text Format +(.rtf), ready for use in most word processors. Both can be cut & +pasted directly from the file viewer, or sent to a printer with the +"Print" button. You can even change fonts.
+ + + + + diff --git a/images/awp-eagle.jpg b/images/awp-eagle.jpg new file mode 100644 index 0000000..b842e79 Binary files /dev/null and b/images/awp-eagle.jpg differ diff --git a/images/awp-eagle_small.jpg b/images/awp-eagle_small.jpg new file mode 100644 index 0000000..4427482 Binary files /dev/null and b/images/awp-eagle_small.jpg differ diff --git a/images/big-shk.htm b/images/big-shk.htm new file mode 100644 index 0000000..1b941b2 --- /dev/null +++ b/images/big-shk.htm @@ -0,0 +1,28 @@ + + + + + + +Manage large archives. This shows CiderPress viewing a large +collection of files -- in this case, a ShrinkIt file archive of a 20MB hard drive partition +with source code on it. For compactness, the archive was re-compressed with the gzip +"deflate" algorithm. (Re-compressing the entire archive took 3 +mouse clicks and about 10 seconds, and cut the compressed size significantly.)
+ShrinkIt archives up to 2GB and multi-partition hard drives up to 8GB are +supported.
+The file viewer is showing an Applesoft BASIC program, converted to text that +exactly matches the output of the "LIST" command. The color +syntax highlighting shown can be switched off. The file view can be +changed to a hex dump or a raw file dump with one click.
+ + + + + diff --git a/images/big-shk.jpg b/images/big-shk.jpg new file mode 100644 index 0000000..0fc526a Binary files /dev/null and b/images/big-shk.jpg differ diff --git a/images/big-shk_small.jpg b/images/big-shk_small.jpg new file mode 100644 index 0000000..ccb81a0 Binary files /dev/null and b/images/big-shk_small.jpg differ diff --git a/images/vol-copy.htm b/images/vol-copy.htm new file mode 100644 index 0000000..0f7f378 --- /dev/null +++ b/images/vol-copy.htm @@ -0,0 +1,25 @@ + + + + + + +Access physical devices. Open floppy disks, CF cards, and hard +drives directly. Cut and paste files between disks and disk images. +Copy partitions on and off with the volume copier.
+ +All CiderPress features are fully documented in the extensive help +files.
+ + + + + + diff --git a/images/vol-copy.jpg b/images/vol-copy.jpg new file mode 100644 index 0000000..df493a7 Binary files /dev/null and b/images/vol-copy.jpg differ diff --git a/images/vol-copy_small.jpg b/images/vol-copy_small.jpg new file mode 100644 index 0000000..7250b65 Binary files /dev/null and b/images/vol-copy_small.jpg differ diff --git a/images/wolfenstein.htm b/images/wolfenstein.htm new file mode 100644 index 0000000..fe9cfca --- /dev/null +++ b/images/wolfenstein.htm @@ -0,0 +1,28 @@ + + + + + + ++ +
Works with 13-sector disks. The above is from a nibble image of +the original, 13-sector still-copy-protected Castle Wolfenstein. CiderPress +automatically identifies 13- and 16-sector nibble images, and can "see through" +some mild forms of copy protection. Files can be added, deleted, and +renamed on DOS 3.2 disks -- even the copy-protected Wolfenstein disk image.
+ +The hi-res image above was automatically identified and converted when +double-clicked from the file list. Hi-res and double-hi-res images can be +displayed in color or black & white.
+ + + + + + diff --git a/images/wolfenstein.jpg b/images/wolfenstein.jpg new file mode 100644 index 0000000..351e784 Binary files /dev/null and b/images/wolfenstein.jpg differ diff --git a/images/wolfenstein_small.jpg b/images/wolfenstein_small.jpg new file mode 100644 index 0000000..6c45b4f Binary files /dev/null and b/images/wolfenstein_small.jpg differ diff --git a/index.html b/index.html index f1afed9..69cd123 100644 --- a/index.html +++ b/index.html @@ -1 +1,56 @@ -My Page + + + + + + + +CiderPress provides the features that Apple II enthusiasts need to manage +their disk and file archives. Open them, view their contents, and copy +files between them. There are other programs that provide access to disk and +file archives, but none have as many features or support as many formats as +CiderPress.
+CiderPress, introduced in March 2003, was developed and sold as shareware by +faddenSoft, LLC. The program was made free, and the source code released +under the BSD license, in March 2007.
+Key features:
++GitHub project page -- download sources or a Win32 executable, +file bug reports, etc.
+ +A tutorial is available, with some sample +files. In addition, Walt Perko has created an +animated GIF (1.8MB) +demonstrating how to put a 32MB ProDOS volume onto a CF card for use with +a CFFA (useful if your Apple II isn't able to format the CF card first). +
+ +Got questions? Check the FAQ and hardware +compatibility pages.
+ +The old requested features list has some +ideas. You can also view the original change log. + + + + diff --git a/mdc-out.txt b/mdc-out.txt new file mode 100644 index 0000000..7e68f3e --- /dev/null +++ b/mdc-out.txt @@ -0,0 +1,136 @@ +MDC for Windows v2.0.0 (DiskImg library v4.0.0) +Copyright (C) 2004 by faddenSoft, LLC. All rights reserved. +MDC is part of CiderPress, available from http://www.faddensoft.com/. +Linked against NufxLib v2.0.3 and zlib v1.2.1 + +Run started at Sun Oct 03 13:16:01 2004 in 'G:\disks\mdc-sample' + +File: APPLE1.IMG +Disk: Pascal APPLE1: + Name Type Auxtyp Modified Format Length +------------------------------------------------------------------------------ + SYSTEM.APPLE PDA $0000 03-Sep-85 00:00 Pascal 16384 + SYSTEM.PASCAL PCD $0000 03-Sep-85 00:00 Pascal 22528 + SYSTEM.EDITOR PCD $0000 03-Sep-85 00:00 Pascal 25600 + SYSTEM.FILER PCD $0000 03-Sep-85 00:00 Pascal 15360 + SYSTEM.LIBRARY PCD $0000 03-Sep-85 00:00 Pascal 19456 + SYSTEM.MISCINFO PDA $0000 25-Dec-83 00:00 Pascal 192 + SYSTEM.CHARSET PDA $0000 14-Jun-79 00:00 Pascal 1024 + SYSTEM.SYNTAX PTX $0000 01-Jul-85 00:00 Pascal 6144 + MORSE.TEXT PTX $0000 31-May-87 00:00 Pascal 5120 + MORSE.CODE PCD $0000 31-May-87 00:00 Pascal 3072 +------------------------------------------------------------------------------ + +File: D3150.sdk +Disk: [UNIDOS] + Name Type Auxtyp Modified Format Length +------------------------------------------------------------------------------ +*_DOS001:CANYON CLIMBER BIN $077D [No Date] DOS 33171 + _DOS001:HELLO BAS $0801 [No Date] DOS 899 +*_DOS001:FALCONS BIN $0800 [No Date] DOS 36096 +*_DOS001:SARGON II BIN $0300 [No Date] DOS 26112 +*_DOS001:HORIZON FIVE BIN $0810 [No Date] DOS 33016 +*_DOS001:SPITFIRE SIMULATOR BIN $0D00 [No Date] DOS 33024 +*_DOS001:AQUATRON BIN $07FD [No Date] DOS 36867 + _DOS001:Q-BERT BIN $4000 [No Date] DOS 20992 + _DOS001:SNAPPER BIN $07FD [No Date] DOS 28931 + _DOS001:LASER SILK BIN $07FD [No Date] DOS 31235 + _DOS001:CROSS COUNTRY RALLY BIN $0800 [No Date] DOS 31232 +*_DOS001:HOWITZER BAS $0801 [No Date] DOS 4297 +*_DOS001:PIG PEN BIN $0F00 [No Date] DOS 22528 +*_DOS001:SNOGGLE-JOYSTICK BIN $07FD [No Date] DOS 27408 +*_DOS001:CHECKERS BAS $0801 [No Date] DOS 4940 +*_DOS002:JUMPJET BIN $07FD [No Date] DOS 36116 +*_DOS002:HOUSE OF USHER BAS $0801 [No Date] DOS 25266 +*_DOS002:MAD-VENTURE BIN $0800 [No Date] DOS 30720 +*_DOS002:INVASION FORCE BIN $0800 [No Date] DOS 7318 +*_DOS002:BEZOFF BIN $08FD [No Date] DOS 37891 +*_DOS002:REAR GUARD BIN $0280 [No Date] DOS 37635 + _DOS002:STAR WARS BIN $0300 [No Date] DOS 27392 + _DOS002:HELLO BAS $0801 [No Date] DOS 917 +*_DOS002:NARNIA BIN $0800 [No Date] DOS 34816 +*_DOS002:EAGLE EGGS BIN $0800 [No Date] DOS 5889 +*_DOS002:ROAD PIZZA BIN $3500 [No Date] DOS 24832 +*_DOS002:BRAINTEASER BLVD BIN $0800 [No Date] DOS 22528 +*_DOS002:DRAW POKER BIN $1500 [No Date] DOS 11008 +*_DOS002:APPLE PANIC BIN $07FD [No Date] DOS 26640 +*_DOS002:PULSAR II BIN $1EFD [No Date] DOS 30467 +*_DOS002:TEMPEST BIN $1200 [No Date] DOS 24576 +------------------------------------------------------------------------------ + +File: D3455.sdk +Disk: ProDOS /D3455 + Name Type Auxtyp Modified Format Length +------------------------------------------------------------------------------ + PRODOS SYS $0000 02-Nov-88 18:03 ProDOS 19560 + MENU.SYSTEM SYS $0000 27-Jul-88 19:26 ProDOS 2808 + STAR.AVENGER BIN $0800 01-Aug-88 19:22 ProDOS 21164 + STAR.BLAZER BIN $0800 01-Aug-88 19:22 ProDOS 26955 + STAR.CLONES BIN $0800 01-Aug-88 19:22 ProDOS 32057 + STAR.CRUISER BIN $0800 01-Aug-88 19:22 ProDOS 17020 + STAR.DANCE BIN $0800 01-Aug-88 19:22 ProDOS 23271 + STAR.MAZE BIN $0800 01-Aug-88 19:22 ProDOS 30537 + STAR.THIEF BIN $0800 01-Aug-88 19:23 ProDOS 14786 + STAR.TREK BIN $0800 01-Aug-88 19:25 ProDOS 28646 + STAR.WARS.II BIN $0300 03-Nov-85 00:00 ProDOS 27392 + STARGATE BIN $0800 01-Aug-88 19:23 ProDOS 31036 + STARMINES BIN $0800 01-Aug-88 19:23 ProDOS 15117 + STRANGE.ODYSSEY BIN $0800 01-Aug-88 19:24 ProDOS 18318 + STUNT.CYCLE BIN $1100 02-Oct-88 04:20 ProDOS 7936 + SUCCESSION BIN $0800 01-Aug-88 19:23 ProDOS 14667 + SUPER.HUEY BIN $0800 01-Aug-88 19:23 ProDOS 29716 + SUPER.PUCKMAN BIN $0800 01-Aug-88 19:24 ProDOS 29741 + SYZYGY BIN $0800 01-Aug-88 19:24 ProDOS 30823 + TAIL.GUNNER BIN $0800 13-Nov-88 16:32 ProDOS 15829 + TAXMAN BIN $0800 01-Aug-88 19:26 ProDOS 27680 + TECHNO.RACING BIN $0800 01-Aug-88 19:27 ProDOS 26435 + TERITORY BIN $0800 01-Aug-88 19:28 ProDOS 11114 + THE.BILESTOAD BIN $0800 01-Aug-88 19:27 ProDOS 30122 + THE.COUNT BIN $0800 28-May-88 21:56 ProDOS 20336 + THE.ELIMINATOR BIN $0800 01-Aug-88 19:27 ProDOS 25761 + THIEF BIN $0800 01-Aug-88 19:27 ProDOS 26349 + THUNDERBIRD.GX BIN $0800 01-Aug-88 19:27 ProDOS 10688 + THUNDERBOMBS BIN $0800 01-Aug-88 19:27 ProDOS 21474 + TIME.TUNNELS BIN $0800 01-Aug-88 19:28 ProDOS 24005 + TORAX BIN $0800 01-Aug-88 19:28 ProDOS 7255 + TRACK.ATTACK BIN $07FD 05-Dec-87 02:18 ProDOS 36356 + TRANQUILITY.BAS BIN $0800 01-Aug-88 19:29 ProDOS 22083 + TRIAD BIN $07ED 24-Feb-88 23:12 ProDOS 31511 + TROMPERS BIN $0800 01-Aug-88 19:29 ProDOS 18167 +------------------------------------------------------------------------------ + +File: SYSTEM.MSTR.SHK +Disk: DOS 3.3 Volume 254 + Name Type Auxtyp Modified Format Length +------------------------------------------------------------------------------ +*HELLO BAS $0801 [No Date] DOS 1137 +*ANIMALS INT $0000 [No Date] DOS 4205 +*APPLE PROMS TXT $0000 [No Date] DOS 264 +*APPLESOFT INT $0000 [No Date] DOS 1142 +*APPLEVISION INT $0000 [No Date] DOS 6190 +*BIORHYTHM INT $0000 [No Date] DOS 4078 +*BOOT13 BIN $1700 [No Date] DOS 2288 +*BRIAN'S THEME BAS $0801 [No Date] DOS 1161 +*CHAIN BIN $0808 [No Date] DOS 456 +*COLOR DEMO INT $0000 [No Date] DOS 1921 +*COLOR DEMOSOFT BAS $0801 [No Date] DOS 1821 +*COPY INT $0000 [No Date] DOS 1834 +*COPY.OBJ0 BIN $02C0 [No Date] DOS 267 +*COPYA BAS $0801 [No Date] DOS 1844 +*EXEC DEMO BAS $0801 [No Date] DOS 2208 +*FID BIN $0803 [No Date] DOS 4686 +*FPBASIC BIN $D000 [No Date] DOS 12288 +*INTBASIC BIN $1000 [No Date] DOS 12288 +*LITTLE BRICK OUT BAS $0801 [No Date] DOS 6775 +*MAKE TEXT BAS $0801 [No Date] DOS 493 +*MASTER CREATE BIN $0800 [No Date] DOS 1791 +*MUFFIN BIN $0803 [No Date] DOS 6397 +*PHONE LIST BAS $0801 [No Date] DOS 12786 +*RANDOM BAS $0801 [No Date] DOS 2280 +*RENUMBER BAS $0801 [No Date] DOS 3046 +*RENUMBER INSTRUCTIONS BAS $0801 [No Date] DOS 9581 +*RETRIEVE TEXT BAS $0801 [No Date] DOS 331 +------------------------------------------------------------------------------ + + +Scan completed in 1 seconds. diff --git a/requested-features.htm b/requested-features.htm new file mode 100644 index 0000000..ac01fdf --- /dev/null +++ b/requested-features.htm @@ -0,0 +1,236 @@ + + +
+ + + + +In no particular order. Return to main page.
+Main application features:
+Ideas for tools:
+Disk image support:
+Physical devices:
+Application tweaks:
+File viewer and file converters:
+MDC:
+Thank you for giving CiderPress a try! We hope you find it useful and +easy to use. This page uses minimal formatting to be printer-friendly.
+This tutorial will get you started working with CiderPress. You will +need to download the sample files if you want to follow along. +These are stored in a ZIP archive because historically some browsers have +enjoyed corrupting SHK archives. ZIP archives can be unpacked with WinZip, +or under WinXP just open the "Zip folder" and copy the data out.
+This tutorial assumes that you are already familiar with using a computer and +with Microsoft Windows.
+Start by installing CiderPress if you haven't yet. There aren't really +any options to set, so just let it do its thing.
+You should create a "scratch folder" to put tutorial files in. Open +your "My Documents" folder, and create a new folder called "cpt" +(CiderPress Tutorial). To keep things simple, put the two +sample files (cp.sample1.bxy and cp.sample2.sdk) in this folder. If you +are using Windows' default "hide extensions of known types" feature, +these files will show up as "cp.sample1" and "cp.sample2" +after CiderPress is installed.
+ +Launch CiderPress. The easiest way to do this is to click on Start, +then Programs, then the CiderPress group, and finally on the CiderPress entry.
+Glance through the menus and toolbar buttons. As you select items from +the menu or move the mouse over a toolbar button, a description will appear on +the "status bar" at the bottom of the screen. Most of the items +are grayed out, because you don't have a file open.
+Let's fix that. Click on the "File" menu and select +"Open...". A standard Windows dialog appears. Change to +the folder where the sample files are, click on "cp.sample1", +and then click on the "Open" button. Your display will look +something like this:
+ +If you've used ShrinkIt on the Apple II, this display should look +familiar. If you haven't, you're looking at ProDOS files stored in a +ShrinkIt archive. The columns show the filename, some file type +information, and other useful stuff. The little yellow rectangle next to +"sample.text" means it has a comment.
+You can change the sort order of the files by clicking on the column headers +(e.g. click on "Size" to sort by size). Click a second time on +the same header to reverse the sort order. You can restore the original +archive sort order by clicking on the "Edit" menu, then +"Sort", and "By original order".
+Let's take a look at what we have in the archive. Double-click on +"sample.text", a simple text file. This opens the File Viewer +window:
+ +The title bar tells you the name of the file you're looking at, and specifies +the format converter that was used. In this case, "[Converted Text]" means +that the carriage returns found at the end of each line of the text file were +converted to Windows "CRLF" format, and any "high ASCII" +characters were stripped out.
+You can click on the "Comment" button on the left to view the +comment instead of the file contents. Clicking on the "Raw" +button changes to an un-converted view (no change will be visible under +Win2K/XP), and clicking on the "Hex" button changes to a hex +dump. The "Best" button switches back to Converted Text. +You can also select modes from the pop-up menu.
+Click "Done" to close the file viewer. Let's try this a +different way. Select all files in the archive by clicking on +"Edit" and then "Select all". Right click on one of +the highlighted file names to bring up a short menu of commands. Click on +"View...". The File Viewer is back, but this time the "Next" button is +enabled. Click on it to advance to the next file, and again to see the +third file. Move back and forth. One of the files is the text file +we looked at earlier, another is a hi-res graphic image of a "double Bessel +function", and the third is an AppleWorks word processing document.
+Use the "Next" and "Prev" buttons to find the AppleWorks +document ("SAMPLE.AWP"). Try resizing the window, and watch how +the margins, centering, and right justification work. Now switch to the +hi-res image. Using the pop-up menu, change the format conversion from +"Hi-Res / Color" to "Hi-Res / B&W". Notice how the +color fringes disappear, leaving a sharper image. Some graphics look +better in black & white than in color.
+When you're done, +press the "Done" button to close the window. (NOTE for Windows +98 users: right-justified text may not display correctly when the window is +resized. This appears to be a bug in Win98. You can cut & paste +from the file viewer window into Word or WordPad and see the correct text.)
+Adding files to and extracting files from Apple II archives is a little more +complicated than just moving files around. When adding files, it may be +useful to restore the ProDOS file type information. When extracting, it +may be necessary to convert the data into a different format for it to be useful +under Windows.
+We're going to extract and add the files twice. The first time we will +preserve the original files exactly, the second time we will convert them to a +format useful in Windows.
+Let's begin by extracting the files. Click on "Actions" and +then "Extract...". This brings up a dialog with lots of options:
+ +The first thing we need to do is choose where the files will go. The +folder listed at the top of the screen is probably not the one we want, so lets change +it. Click on the folder icon in the upper-right corner, next to the +filename entry field. This brings up the "Choose folder" +dialog. Navigate through the folders until the "cpt" folder you +created earlier is highlighted, and click "Select". (If you +created "cpt" under "My Documents", don't be surprised if +the name shown starts something like "C:\Documents and +Settings\UserName\". This is normal for Win2K and WinXP.)
+In the "Files to extract" box, select "Extract all +files". Make sure both checkboxes in the "miscellaneous" +section are unchecked. Finally, click on the large button near the bottom +that says "Configure to preserve Apple II formats". This will +configure the remaining options so that files extracted can be added to a new +archive that is as close as possible to the original.
+Once everything is set up as described (it should match the options shown in +the picture above), click the "Extract" button. On a +fast machine, you'll see little more than a flash as the files are extracted.
+If you open the "cpt" folder in Windows Explorer (open My Documents +from the desktop or Windows Start menu, then open "cpt"), you will see three new files:
+The junk starting with "#" that was added to the filename is a file +attribute preservation sequence. The first two digits are the ProDOS file type, +the next four are the ProDOS aux type. For DBL.BESSEL.PIC, it's $06 +("BIN") and $2000 (the typical load location of a hi-res image). +None of the files has a filetype that Windows recognizes, which makes sense: +none of the files is in a format Windows likes.
+You might think that "sample.text" is a text file, and Windows +likes text files, but it's not that simple. Rename "sample.text#04000" +to "sample.text#04000.txt". Now Windows recognizes it as a text +file. Double-click on it. If you have Windows +"Notepad" as your default text viewer, you will probably notice that +the file doesn't look right. Instead of line breaks there are funny little +rectangles. Because we told CiderPress to preserve the original file +formats, the carriage returns in the original file were left +unmodified. Double-clicking on the other files will most likely not yield +anything useful, because they're in formats that only an Apple II can readily +handle.
+We don't have to stand for that, however. Go back to CiderPress, and +click on "Actions" and "Extract..." again. This time, +click on the filename in the edit box, and hit the right arrow key until you're +all the way at the right of the filename. We're going to extract into a +sub-folder called "win", so type "win" at the end of the +name. (It should now look something like "C:\Documents and Settings\Administrator\My +Documents\cpt\win".) There's no need to create the folder ahead of +time, CiderPress will create it for us.
+Click on the large button labeled "Configure for easy access in +Windows". Make sure "Extract all files" is selected, and +leave the rest untouched.
+Click the "Extract" button. Stuff happens, probably faster +than you can see it. Open the +"cpt" folder in Windows Explorer again, and then open the new "win" +folder. Inside, you will find:
+(Again, if you have "known extensions" hidden, you won't see any of +the ".xxx" shown above.)
+Double-clicking on the first launches the default Windows bitmap editor, +where you can view the double-Bessel function in all its glory. +Double-clicking the second launches the default Windows Rich Text Format editor, +usually Windows WordPad or Microsoft Word. Double-clicking on the third +opens the text file, nicely formatted for easy viewing.
+Now that we've extracted some files, let's try adding them back into an +archive.
+Click on "File" and then "New" and move over to +"ShrinkIt archive". Create +a new archive called "test.shk" in the "cpt" folder. +Creating or opening an archive causes the currently open one to be closed, so +"cp.sample1.bxy" disappears and "test.shk" takes its place.
+Click on "Actions" and then "Add files...". This +brings up the Add Files dialog.
+ +Leave the "File attribute preservation" setting on "Use file +attribute preservation tags". +This tells CiderPress to look for the "#062000" stuff, but not to get +excited if it's not there. The remaining fields aren't important for what +we're doing now, so leave them alone.
+Select the three files with the funny "#062000" stuff in the +names. You can either click on the first and then shift-click on the last, +or click on the first and then control-click on the other two. When all +three have been selected, click "Accept". (You may notice a file +with a name like "CPtmp_12345" in the folder. This is a temporary file used +when ShrinkIt archives are opened, and can be ignored.)
+The files are added in a flash. Double-click on them to verify that +they are all intact. Note that the file types and modification dates match +the originals.
+Now lets add the second, converted set. Click "Actions" then +"Add files...". Make sure "Include subfolders" is +checked and "Strip folder names" is not checked. Click on +"win" once (don't double-click it, or the folder will open) and then +click "Accept". This adds everything in the "win" +folder to the archive.
+You will end up with three new files, each prefixed with +"win:". Your archive should look something like this:
+ +The file types of the three you just added are all "NON", and double-clicking on them in the +CiderPress file list is +disappointing. This is because these files have crossed over to the Dark +Side (i.e. they're in Windows formats now), and the File Viewer is only able to display Apple II formats. Once +you have converted files into Windows BMP or RTF files, it's more appropriate to +store them in a ZIP archive than a ShrinkIt archive.
+Generally speaking, when extracting files you can either choose to preserve +the original format or choose to put them in a format easily accessible in +Windows. CiderPress does not +know how to un-convert BMP or RTF documents back to hi-res or AppleWorks format, +so you should use one approach if you're planning to add the files back into an +archive for use on an Apple II, and the other approach if you want to include +them in Windows documents.
+Let's try an experiment. In the CiderPress file listing for the "test.shk" +we created above, click on "DBL.BESSEL.PIC". Click +"Actions" then "Extract...", and make sure the extraction +path is still set to the "win" sub-folder of our "cpt" +folder. Hit "Configure for easy access in Windows" and then check the +box labeled "Add file attribute preservation". Make sure the button +in "Files to extract" is set to "Extract 1 selected file".
+Click "Extract". You might expect to end up with "DBL.BESSEL.PIC#062000.bmp", +but instead you get a warning about overwriting "DBL.BESSEL.PIC.bmp". +Hit "Cancel" to cancel the extraction.
+Why didn't a file attribute preservation sequence get added to the filename? +Because we have file converters turned on, and those change it to Windows +format. Once the file is converted to a BMP, it's no longer an Apple II +file, and trying to preserve the "BIN" file type is no longer appropriate. The situation is similar for BASIC programs +converted to text listings and AppleWorks word processor documents converted to +RTF. If we added SAMPLE.AWP.rtf with an "AWP" file type, and +then tried to load the file in AppleWorks, we'd be greatly disappointed.
+We're done with this set of files, so select all files ("Edit" then +"Select all", or hit Ctrl-A), click on "Actions", then +"Delete...", and hit "OK" when asked to confirm the +deletion. Go to "File" and select +"Close". The empty archive is automatically removed.
+It's worth mentioning at this point that archives are not handled the same +way word processing documents are. You can't make a set of changes, undo +them, do some other things, and then save the results. (Technically +speaking, it's possible, but CiderPress doesn't work that way.) Any change you +make immediately modifies the archive, and there is no "undo".
+The ".BXY" extension is used for a ShrinkIt archive with a Binary +II header. CiderPress is capable of opening both ShrinkIt and Binary II +archives, so how does it decide which to open?
+CiderPress tries to guess what you want, but it's easy to make your choice +explicit. Click "File", +then "Open...", and look at the "Files of type" +selector. Click on it and change the setting to "Binary +II". Double-click on "cp.sample1", which is a .BXY file.
+This time, when the file opens, you see only one entry. "SAMPLE.SHK" +is the ShrinkIt archive embedded inside the Binary II file. If you want to +convert a .BXY to a .SHK, all you have to do is open the archive as Binary II +and then extract the ShrinkIt archive. CiderPress does not have the +ability to write to Binary II archives, which is why the title bar now also says +"(read only)".
+ShrinkIt archives are often found on disk images or inside other ShrinkIt +archives, so CiderPress provides a quick way of opening them. +Double-click on SAMPLE.SHK and watch as a new copy of CiderPress is launched. A +copy of SAMPLE.SHK was written into the system temp folder, and the new +CiderPress window opened it automatically. The file will be deleted when +the second window is closed, which is why the new window is also marked +"(read only)". Go ahead and close the second window before +continuing.
+Disk images are very different from ShrinkIt archives. They come in +many different file formats, can be written with sectors scrambled in different +orders, and can be in different filesystem formats (DOS, ProDOS, etc.). +With most programs you have to know a fair bit about a disk image before you can +access it, possibly having to convert it from one format to another, but with +CiderPress that's not necessary.
+ +Click "File" then "Open...", select "Disk +Images" in the "Files of type" selector, and double-click +cp.sample2. The disk image opens, and about 35 files are +displayed. Notice that in the "Format" column, some files are +listed as "ProDOS" and some as "DOS". This is because +the disk image is of an 800K ProDOS volume with a 200K DOS 3.3 volume embedded +in it. The title bar of the window now shows that this is a disk image of +a ProDOS volume called "/CP.TEST".
+++(For those interested in technical details: CiderPress passed +"cp.sample2.sdk" to the "DiskImg" library and asked it to +open the file. DiskImg opened the file, figured out that it was a +compressed ShrinkIt disk archive, and unpacked it to a buffer in memory. +The disk structure was scanned, and DiskImg determined that it was a ProDOS +volume in ProDOS sector order. It then examined the structure of every +file on the disk, and determined that there was an embedded volume. This +second volume was then opened, scanned, and found to be a DOS 3.3 disk in +ProDOS sector order. The contents of the DOS volume were scanned. Control +then returned to the CiderPress application, which took the list of files and +displayed them in the window. Don't try that on an empty stomach!)
+
The files are shown in a "flat" list, though the real disk has most +of the files in folders. For example, "Graphics:WORLD.MAP.PIC" +is actually a file called "WORLD.MAP.PIC" in a folder called +"Graphics". The files in the DOS 3.3 sub-volume aren't actually +visible from ProDOS, so CiderPress prepends "_DOS001:" to make the +separation clear.
+Try double-clicking on some files to view them. You should probably +start by double-clicking on "ReadMe",. a file in TeachText format that +describes the contents of the disk. Try some BASIC programs like +"STARTUP" in the ProDOS area or "ANIMALS" in the DOS area. +Use the conversion selector to turn color highlights on and off.
+You may notice that some of the files appear to be compressed -- the +"Ratio" column isn't 100%. This is because the files are +"sparse". ProDOS and DOS 3.3 have the ability to store empty +disk blocks without using lots of disk space. The difference between +"Size" and "Packed" represents the space saved by using +sparse blocks.
+If you double-click on "TestFiles:SPARSE", you will get an error +message from the File Viewer indicating that the file is too large. The +file is actually 16MB, but because it's almost entirely sparse blocks it only +occupies about 1.5KB. If you +want, you can view this file by increasing the file viewer limit. Click on "Edit", then +"Preferences...", then on the "File Viewer" tab. The +"Viewer file size limit" can be set in 1K increments. There are +a number of other configurable items in here, including settings that let you +default hi-res and double-hi-res graphics to black and white. Click on the "Help" button or use the question mark icon +in the window title bar to get more information about specific things. +Click on "Cancel" to close the dialog.
+Click on the "File" menu, then "Open...", change +"Files of type" to "ShrinkIt +Archives", and open "cp.sample2". You should see a +single entry, for an 800K disk image. (If you want, double-click on the +entry to pop open a second instance of CiderPress with the disk image contents +in it. Close it when you're done.)
+Click on "Actions" and "Extract...". Set the +extract folder to "cpt", and click "Configure for easy access in +Windows". Note that "Extract disks as .2MG" is +checked. Click "Extract".
+If you open the "cpt" folder with Windows Explorer, you will find a new file called +"CP.TEST.2mg" (or just "CP.TEST" if extensions aren't being +shown). Depending on how your file associations are +configured, you should be able to double-click this file and launch the default +2MG application (which is probably an Apple II emulator or CiderPress; file +associations can be set from within CiderPress by clicking "Edit", +"Preferences", and then the "Associations..." button).
+That was easy enough. Now let's try adding the disk image to an +archive. Click on the "File" menu then "New -> ShrinkIt archive", and create a new archive called "mydisk.shk" in the +"cpt" folder. Click on the "Actions" menu then +"Add disk image...". Navigate to the "cpt" folder if +you're not there already, click on "CP.TEST", and click +"Open". The disk image is added.
+Let's try a different way. Extract the disk image you just added (still +working in "mydisk.shk), but this time click on "Configure to preserve +Apple II formats.". Click "Extract" to create +"CP.TEST#000640i". (The "640" is the number of +blocks in hexadecimal, and the "i" indicates that it's a disk +image.) This file is a ProDOS-ordered sector image; if you check the +"Add type extension" box before extraction, it will be given a +".PO" extension and can be opened with the default +".PO" viewer (usually CiderPress or an Apple II emulator).
+Let's add it back to the archive. We could use the "Add +disks" menu item, but we have another option. Click on "Actions" +and then "Add files...". Make sure the "File attribute preservation" setting is on "Use file +attribute preservation tags", +click on "CP.TEST#000640i", and click "Accept". +When asked if you want to overwrite the file, click "Yes".
+Nothing appears to happen, but you've actually just replaced the disk image +that was in the archive with the new one. You were able to add the disk image +with the "Add files" dialog because of the file attribute preservation +strings (the "#000640i" part). If you had set "File +attribute preservation" to "Ignore file attribute preservation flags", you would +have added a file called "CP.TEST#000640i" instead of a disk image +called "CP.TEST".
+Working with disk images is a little different than working with ShrinkIt +archives. Filenames have limited lengths and may only contain certain +characters, file lengths are limited, and on non-ProDOS volumes the selection of +file types will be limited. On the plus side, disk images can be used +directly by Apple II emulators.
+Let's start by creating a disk image. Click on the "File" +menu, then "New -> Disk image...". This opens the Create Disk +Image dialog.
+ +Leave the values set to the defaults and click "OK" to create a +140K ProDOS image. When the "save" dialog comes up, type "testdisk" +into the "file name" field. Leave the file type set to +"DOS-ordered image (*.do)". Click "Save".
+Your brand-new ProDOS disk will open automatically. The disk has one +entry for the volume directory, called ":NEW.DISK". Let's add +some files.
+Click "Actions" then "Add files...". Select the +three files with "#123456" stuff in the filenames (DBL.BESSEL.PIC#062000, +SAMPLE.AWP#1ac0fd, and sample.text#040000.txt) by clicking on the first one and +control-clicking on the other two. Make sure "use file attribute +preservation tags" is set.
+You will notice that the "Text conversion" options are now +available. The files we're adding are from an Apple II, so we don't want +to mess with them. Click on "Don't convert text files". +Now click "Accept" to add the files. You should be back in the +CiderPress file listing, with four files on the screen (the volume directory and +the three files you just added). Double-click on them to verify that +they're all okay.
+You may notice that only "sample.awp" is in lower case. +That's because, by default, CiderPress adds files to ProDOS disks in upper-case +only. If you use a version of ProDOS 8 older than v1.8, you will get +errors on disks with lower-case names. (You can change this behavior from +the disk images preferences screen.) So why is "sample.awp" in +lower case? Because AppleWorks files have lower-case flags in their +"aux type" field. If CiderPress sees a file with type AWP, ADB, +or ASP, the flags in the aux type are used.
+One nifty thing about ProDOS disks is that you can tuck files into +subdirectories (usually called "folders" in Apple-speak). Let's +create one now. You have to tell CiderPress which directory the new +subdirectory will appear in, so start by clicking on the volume directory +(":NEW.DISK"). Click on "Actions" then "Create +subdirectory...". Type "My Stuff" as the name. Click +"OK". A new subdirectory, called "MY.STUFF", +appears. (If lower case were enabled, it would have been added as "My +Stuff" instead.)
+Suppose we want to add more files. Where do they go? In the +volume directory, or in MY.STUFF? Let's find out. Click on a blank +area of the window so that nothing is highlighted. (You may still see a +thin dashed line around one entry; that's okay.) Click on +"Actions" then "Add files...". You will see a dialog +that asks you to pick the location.
+ +As you can see, you are able to add files to the volume directory or the +folder you created. As noted in the "tip" at the bottom, you can +avoid seeing this dialog by clicking on the target subdirectory before you +select "Add files...".
+We don't really want to add anything here, so click "Cancel". +Close the disk image by selecting "Close" from the "File" +menu. Let's create another image, this time a DOS 3.3 disk. From +"File", select "New -> Disk image...".
+Click on the "DOS 3.3" button in the upper left. The ProDOS +volume name entry field is greyed out, the DOS 3.3 options in the upper right +corner become active, and our choice of sizes is now limited to just 140K +disks. Leave the defaults alone and click "OK". Click on +"testdisk.do" (the disk we recently created) and click +"Save". When asked if you want to replace the existing file, +click "Yes".
+Now we have open an empty DOS 3.3 disk image. Let's add a file. +Click "Actions" then "Add files...". Open up the +"win" folder inside "cpt", and select "sample.text" +(or "sample.text.TXT"). Click "Accept".
+The file has been added, but something is strange. Our text file has +type $F2. The reason this happened is because CiderPress didn't see it as +an Apple II file, and gave it a file type of NON. However, there is no +direct equivalent to NON for DOS 3.3. Instead, CiderPress used the DOS +file type 'S'. There's no ProDOS equivalent to 'S', so CiderPress displays +it as $F2. Because DOS 3.3 'S' files don't have an explicit file length, +the length is rounded off to 512 (two DOS sectors).
+Yuck. Fortunately there's a simple way around this. Click +"Actions" and "Add files..." again. This time, click +the "Use tags and guess type from extension" button. This tells +CiderPress that we want it to guess the type of the file from the filename +extension. Since we're adding a text file to a DOS disk, we also want it +to convert from Windows format (low ASCII, CRLF) to DOS 3.3 format (high ASCII, +CR), so click on the "Convert text files by file type" button.
+ +Click on "sample.text" again, and click "Accept". +When it asks you if you want to replace the previous file, say +"Yes". You should now have a text file with a reasonable +length. If you double-click on it and view it in hex dump mode, you'll see +that it's in "high ASCII" with carriage returns, as all good DOS 3.3 +text files should be.
+Select "Close" from the "File" menu to close the disk +image.
+CiderPress is a powerful tool with lots of features. Start with the +default settings and quick configuration buttons. The additional flexibility is there if you need +it. Click the "Help" button on a screen for detailed help on +that screen, or select "Help" then "Contents..." to start +from the beginning. In many screens you can click on a question mark +button in the title bar and then click on a button to get more information on +that button.
+ + + + + +