mirror of
https://github.com/fadden/ciderpress.git
synced 2024-11-26 17:49:21 +00:00
250d1043e3
The original version of CiderPress used a WinHelp help file, built with an application called HelpMatic Pro. This app used a proprietary format, and had no facility for exporting to "raw" HPJ + RTF files, so I decompiled the HLP and imported it into HelpScribble. Using HelpScribble, I cleaned up the help file formatting a little, fixed up the table of contents, and exported as "raw" HtmlHelp (HHP, HHK, HHC, and a whole bunch of HTML). I also split the pop-up help text, which isn't supported by HelpScribble, into a separate text file that Microsoft's HTML Help Workshop understands. I'm checking in the files that HTML Help Workshop needs to generate a CHM, so anyone can update the help text. I'm also checking in the CHM file, rather than adding the help workshop to the build, so that it's not necessary to download and configure the help workshop to build CiderPress. This change adds all of the updated help, but only updates the Help and question mark button actions for one specific dialog. A subsequent change will update the rest of the dialogs. This change is essentially upgrading us from a totally obsolete help system to a nearly-obsolete help system, but the systems are similar enough to make this a useful half-step on the way to something else. The code will centralize help activation in a pair of functions in the main app class, so any future improvements should be more limited in scope. This also adds a build step to copy the CHM to the execution directory.
30 lines
4.0 KiB
HTML
30 lines
4.0 KiB
HTML
<HTML><HEAD>
|
|
|
|
<TITLE>Tool - SST Image Merge</TITLE>
|
|
<OBJECT TYPE="application/x-oleobject" CLASSID="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
|
|
<PARAM NAME="Keyword" VALUE="disk image">
|
|
<PARAM NAME="Keyword" VALUE="merge">
|
|
<PARAM NAME="Keyword" VALUE="SST">
|
|
</OBJECT>
|
|
<META NAME="AUTHOR" CONTENT="Copyright (C) 2014 by CiderPress authors">
|
|
<META NAME="GENERATOR" CONTENT="HelpScribble 7.8.8">
|
|
<STYLE> span { display: inline-block; }</STYLE>
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="4">SST Image Merge</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">This tool is used to combine two disk images created by the "SST" utility into a single ".nib" disk image.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">SST is "Saltine's Super Transcopy", a nibble copier modified to read raw nibble data from disks and write it to two floppy disks. The usual approach to creating .nib files is to run SST on a real Apple II, create images of the two disks, copy them to a PC, and then run SST in an emulator to copy the two sides onto a "blank.nib" file. The advantage of this approach over creating ShrinkIt or ".do" files is that in many cases the copy protection can be left more or less intact.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">CiderPress can't make the first half of the process easier, but it can simplify the second. Instead of running an emulated SST to combine the images, just use the "SST Image Merge" function from the Tools menu. You will be asked to locate the first side, then the second side, then asked for the name of the output file. The pieces are merged immediately. You are given the option of opening the newly-created disk in CiderPress, but as with all disk images this will only work if the disk has a recognizable filesystem. The NIB format is generally used for disks without filesystems, so you may have to test the image by booting it in an Apple II emulator.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">If CiderPress notices anything unusual about the images, you will be notified. A warning will be shown if they don't appear to be images of SST-created disks, or if they were specified in the wrong order.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">You can transfer the SST disk images from your Apple II in any format that CiderPress supports. The most popular are unadorned DOS-order files (.DO) or ShrinkIt (.SHK/.SDK). Since the disks don't have a recognizable filesystem, CiderPress' automatic sector order determination algorithms may not work, so it is important to use the appropriate filename extension on unadorned formats. If CiderPress can't figure it out, or if you have "Confirm disk image format" enabled, you will be prompted to enter it. (The "filesystem format" will usually show "Generic DOS sectors"; this is normal, and can be left alone.)</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">SST has some fancy features (nibble counting, track synchronization) that CiderPress does not try to emulate. If you need special parameters in SST, you will need to use the original method.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;">
|
|
</P>
|
|
</BODY></HTML>
|