Just as with Workbench disks, kickstart images required for WHDLoad are unfortunately still sold commercially and therefore illegal to distribute.
In order to obtain the required images, refer to the instructions provided.
If you are installing the ClassicWB on a hard drive greater than 2GB, be aware of the limitations imposed by Workbench 3.0/3.1
Various optimization patches are enabled by default, but can be easily enabled or disabled using either the Settings menu or the Tools menu in the top left corner of the screen.
"FBlit FText" move blitter functions to the CPU, increasing performance and reducing chipram usage. Both are enabled by default, but can be disabled using the Tools menu (top left hand corner of the screen) if compatibility problems arise.
Copper Demon has the potential to cause issues, so if you are running the 24bit colour backgrounds, try disabling Copper Demon (again, use the Tools/Settings menus mentioned above) and see if it cures your problem.
Low memory and other issues can be resolved by using the Multiboot Ability. From here you can boot a minimal standard Workbench or explore various launch options. Note that even in standard Workbench mode the "FBlit Ftext" setting still applies, so disable it first if you require maximum compatibility.
ENV-handler is disabled by default, but if you've enabled it to save RAM then try and disable it from the tools menu (top left hand corner of the screen) and see if the issue is resolved.
Finally, as mentioned under Bugs, some GUI archive programs have issues compared to the shell executables. If you are having problems, try unarchiving a pack using a different program.
They're probably Glow/OS3.5+ icons and require Workbench 3.5+ and Kickstart 3.1.
This is perfectly normal. NewIcons also contain normal Workbench icon images for systems that don't have NewIcon compatibility. What you're seeing is the old image which has been reduced to a dot in order to increase performance and reduce disk space that would otherwise be taken up by NewIcons. Copy the icons as normal and you'll see the desired result will still be achieved. Be careful not to change settings so that OldIcon image data is produced and saved - this will hurt performance.
NewIcons should always contain dots for old image data on systems capable of displaying NewIcons. If not, use "PeelOldIcon" (popup menu) or the "Peel Icons" scripts provided in order to change the old icon data into a dot.
The ClassicWB is extremely compatible with HDgames on a real Amiga. Issues in emulators are usually configuration orientated or due to Blitter/Copper timing. Emulated CPU speed can also be a factor. If a game fails to run properly, one of the first things to try is using a non-JIT CPU. Running the normal (680EC020) CPU or other models without JIT might alleviate the issue. Another major factor are the "Fast Copper/Immediate Blitter/Cycle Exact" settings. Disabling/Enabling may fix your problems but be warned - "Cycle Exact" will require a large amount of CPU power.
In the "MyFiles" folder you will find CDROM software ready to install. This will allow the ClassicWB to access your CDROM and installation is relatively straightforward. Be sure to call the device either the default CD0, CD or CDROM and you will end up with a nice Workbench icon. Also when asked to choose a CDDA program select "SongPlayer" in the programs directory. If you experience problems in UAE, make sure the "UAEscsi.device" box is checked under the Misc tab and a recent ASPI layer is installed on your Windows OS.
Dopus does not automatically detect volumes on your system. Instead it requires configuration by the user to tailor it for their specific needs. In order to do this, go to the "Project" menu and select "Configure".
The current setup has commonly used devices and volumes (DF0, DH0, Temp, Games etc) as well as those paths suggested for CDROM and PC access. The reason for using CD0: and PC: respectively is given above - special Workbench icons are present for certain device names. For instance, when I add a PC directory in WinUAE or mount a network like "Ami-PC" on a real Amiga, I make sure in both cases the device is called PC: This automatically ensures that the ClassicWB will use a pre-determined Workbench disk icon relevant to the device in question.
You can choose any icon or name for your devices by modifying those included in the "Expansion/Scalos/Icons" drawer. Simply rename or replace those present.
Rather than right-clicking on the highlighted files and choosing "Delete", try right-clicking on the window instead and select "Window-Delete Contents". This will deleted all files currently highlighted rather than a single file.
At the start of the "S/User-Startup" file, assigns were added so common folders can be accessed and referred to easily in file requesters, programs, CLI and Scalos scripts. They're in the format "A-x", where "x" is the folder name. The prefix "A-" was added so they appear at the top of file requesters. If any of these folders differ in location (eg games folder is on DH1: not DH0:) then feel free to edit these assigns. Once edited, popup menus, Dopus and file requesters will all automatically be updated with the folders new location.
Depending on the ClassicWB version, there can be either one or two programs under the icons popup menu to convert images. Once selected, an icon will appear on the Workbench. Simply drag a picture or screencap of the game in question over to the icon and it will be converted! A good place to get images is the HOL database.
Differences between the two programs are as follows:
Pic->Oldicon: This produces old (standard) icon data and as default is setup for low colour (fixed magicicon palette, max 8) high performance icons. It can, however, be setup to use whatever screenmode colours are available at the time of conversion - the max number of colours used and quality settings can be changed in the tools prefs. Problem is, unless the colours used are fixed in place using Scalos palette prefs (like the fixed magicicon palette currently setup), the icons may change when you swap screenmodes due to the way the Amiga works.
Pic->Newicon: Best method for high colour game icons as the most fitting colours out of those available in a given screenmode are automatically selected. This will produce the NewIcons shown in the pics, but you will obviously need higher screen mode colours when converting and displaying and performance will be slower. Best to have the icons in separate drawers as displaying one perfectly may require 32 colours, two 64 etc, so the more icons on display, the less available for each individual icon and quality will suffer.
Deliplayer is configured to load ALL its players to RAM at startup - this is how I prefer to use it. It means I can drag over almost any Amiga music file and have it play straight away. If it's causing you problems, either use Eagleplayer that's been setup to load players on a "as need" basis or remove some of the deli-genies/players you don't use, placing them in another directory. Read the Deliplayer help file for details.
The problem is they contain Amiga files that are not compatible with some PC file systems like "AUX", certain international characters and file attributes. Unzipping or copying the files onto a real Amiga file system would produce zero errors.
When I created the Workbenches, I did so on a HDF using WinUAE in order to preserve all filenames/attributes and avoid PC filesystem compatibility issues.