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
3.9 KiB
HTML
30 lines
3.9 KiB
HTML
<HTML><HEAD>
|
|
|
|
<TITLE>Tool - Bulk Disk Image Converter</TITLE>
|
|
<OBJECT TYPE="application/x-oleobject" CLASSID="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
|
|
<PARAM NAME="Keyword" VALUE="bulk">
|
|
<PARAM NAME="Keyword" VALUE="convert">
|
|
<PARAM NAME="Keyword" VALUE="disk image">
|
|
</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">Bulk Disk Image Converter</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">The bulk converter works much like the <A HREF="t187.htm">single-image converter</A>, but it can process a large number of disk images with a few clicks. It's probably best to become familiar with the single-image converter before using this feature.</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">After you select this feature from the "Tools" menu, you will be asked to select the disk images to convert. All images must reside in the same folder. Select multiple files with the mouse, using shift-clicks to select a range of files or ctrl-clicks to add or remove individual files. You can select all files in the current folder by clicking on one and then hitting Ctrl-A.</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">Next, you will be asked to choose the output format. All images will be converted to the same format. Not all images can convert to all formats -- for example, you can't create 800K nibble images or 140K DiskCopy images -- so make sure you choose an appropriate format. CiderPress will not prompt you to specify sector ordering, so it's important for the images to have descriptive filename extensions (e.g. ".po" instead of the generic ".dsk").</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">Finally, select a folder for the output. Creating a new, empty folder is recommended. The converted files will have the old names but with the extension replaced, but in some cases the old extension might match the new. For example, converting a DOS-ordered 2MG file to a ProDOS-ordered 2MG file does not change the ".2MG" extension. CiderPress will not overwrite an existing file.</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 encounters a file it cannot convert, you will be shown an error message with the name of the file and given the opportunity to skip the file and continue or halt processing. Some messages, such as warnings about unreadable blocks on nibble images, are suppressed during bulk conversions.</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 you are converting to ShrinkIt .SDK archives, the files will be compressed with the current <A HREF="t29.htm">default compression method</A>. This provides an easy way to convert a large set of disk images to "deflate" format for reduced storage requirements, or back to LZW/2 for Apple II compatibility.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;">
|
|
</P>
|
|
</BODY></HTML>
|