[ITEM]
21.04.2020

Amiga Workbench 3.1 Hdf

48

After deleting a few non-essentials from my Workbench 1.3 disk like some fonts, printer drivers and notepad, I copied AExplorer from the RAM disk to the Workbench 1.3 disk as suggested in the setup directions. Clicking the AExplorer icon turns the Amiga into.

I decided to refresh my Workbench 1.3.3 HD install, after some issues, and run into many problems with installation. Long time ago, we used to copy FastFileSystem from WB1.3.3 and place it as FileSystem when mounting drive - if you do that now, disk does not get recognized. How to install libgcc 3.4.6 sol9 sparc local.

Amiga Workbench 3.1 Hdf

If you try to format it with FFS parameter, it does not work, creates NDOS disk.#If you just format it normally with any non Cloanto Workbench 1.3.3, you will get bunch of garbage in WB or for instance in Directory Opus.#If you use Cloanto - format and copying of files work fine, but some programs don't work, such as 'Say' in Utilities. (what makes me wonder what else does not work).Am I missing something or should there be better way to emulate Amiga 500 with A590 20MB drive??Here are some screenshots.

I decided to refresh my Workbench 1.3.3 HD install, after some issues, and run into many problems with installation. Long time ago, we used to copy FastFileSystem from WB1.3.3 and place it as FileSystem when mounting drive - if you do that now, disk does not get recognized.Which version of the fastfilesystem is that? Note that some versions, most notably those from 3.9 and 3.1.4 will not work under 1.3 as they require later versions of the kickstart. Also note that FFS does not work on disk drives under Kick 1.3 unless you set the mask and the bufmemtype value correctly.

Rin

Mask should be 0x00ffffff and bufmemtype should be 3. Since the regular kickstart mount entry for disk drives does not set these parameters, FFS will not work on floppies unless you have a custom mount file. The reason is that the 1.3 trackdisk device requires floppy buffers in chip mem as it uses the blitter for MFM decoding and encoding, and the FFS without further tuning passes the user-supplied buffers directly to the trackdisk.device. As they are typically in fast mem, disk transfer will not work. As for the fonts entry, this was already covered by Tony. There is a FastFonts replacement on Aminet that also works with topaz.9 and that does not have the bug you observed. If you need it, you'll find it there.

BetterWB release 4.3 - BetterWBis a new workbench pack, much like AIAB, Amikit, AmigaSYS, ClassicWB, etc.but applying a totally different aproach. It aims to be much like anenhancement, an updated extension to AmigaOS 3.1, without all those hardwarerequirement penalties typically associated with these kind of packs.

[/ITEM]
[/MAIN]
21.04.2020

Amiga Workbench 3.1 Hdf

94

After deleting a few non-essentials from my Workbench 1.3 disk like some fonts, printer drivers and notepad, I copied AExplorer from the RAM disk to the Workbench 1.3 disk as suggested in the setup directions. Clicking the AExplorer icon turns the Amiga into.

I decided to refresh my Workbench 1.3.3 HD install, after some issues, and run into many problems with installation. Long time ago, we used to copy FastFileSystem from WB1.3.3 and place it as FileSystem when mounting drive - if you do that now, disk does not get recognized. How to install libgcc 3.4.6 sol9 sparc local.

Amiga Workbench 3.1 Hdf

If you try to format it with FFS parameter, it does not work, creates NDOS disk.#If you just format it normally with any non Cloanto Workbench 1.3.3, you will get bunch of garbage in WB or for instance in Directory Opus.#If you use Cloanto - format and copying of files work fine, but some programs don't work, such as 'Say' in Utilities. (what makes me wonder what else does not work).Am I missing something or should there be better way to emulate Amiga 500 with A590 20MB drive??Here are some screenshots.

I decided to refresh my Workbench 1.3.3 HD install, after some issues, and run into many problems with installation. Long time ago, we used to copy FastFileSystem from WB1.3.3 and place it as FileSystem when mounting drive - if you do that now, disk does not get recognized.Which version of the fastfilesystem is that? Note that some versions, most notably those from 3.9 and 3.1.4 will not work under 1.3 as they require later versions of the kickstart. Also note that FFS does not work on disk drives under Kick 1.3 unless you set the mask and the bufmemtype value correctly.

Rin

Mask should be 0x00ffffff and bufmemtype should be 3. Since the regular kickstart mount entry for disk drives does not set these parameters, FFS will not work on floppies unless you have a custom mount file. The reason is that the 1.3 trackdisk device requires floppy buffers in chip mem as it uses the blitter for MFM decoding and encoding, and the FFS without further tuning passes the user-supplied buffers directly to the trackdisk.device. As they are typically in fast mem, disk transfer will not work. As for the fonts entry, this was already covered by Tony. There is a FastFonts replacement on Aminet that also works with topaz.9 and that does not have the bug you observed. If you need it, you'll find it there.

BetterWB release 4.3 - BetterWBis a new workbench pack, much like AIAB, Amikit, AmigaSYS, ClassicWB, etc.but applying a totally different aproach. It aims to be much like anenhancement, an updated extension to AmigaOS 3.1, without all those hardwarerequirement penalties typically associated with these kind of packs.