Workbench not working after installation
 

Hi again guys.

I was wondering if you could help me with a quirky issue that I have been experiencing.

Issue:
I am using FS-UAE, and I'm trying to install Workbench 3.1 to an emulated hard drive.

I am using the official 6 disk floppy set (digital ADF versions) recently
bought from Amiga Forever (Version 9 - 2021).

1. Im trying to install this on an emulated Amiga 4000

2. It does "appear" to work properly, however, when I complete the installation
It boots to a "Workbench-like screen" with a CLI command box
(see screenshot):https://imgur.com/a/hi3b6Ge


3. I've tried to install it to both a directory hard drive
and a HDF image. They both end up the same (as in point 2)

4. Interestingly, I have been successfull in being able to install Workbench 3.1
to an A-1200 config (multple times) on both a directory hard drive, and an HDF.
Which worked flawlessly.

TBF I dont think it's an issue with FS-UAE, or the install media.

Does anyone have any idea what might be causing this ?

TIA for any help or advice.


Useful information:
Amiga emulator: FS-UAE 2.8.3 (downloaded from Synaptic)

PC details
OS: Ubuntu 18.04 LTS
OS type: 64-bit
DE: KDE 5.12.9
Kernel: 4.15.0-99-generic
CPU: 4x Intel Core-2 Q8200 (@2.33 Ghz)
RAM: 8GB

The screenshot is what you get when the Amiga boots from a partition without the standard startup-sequence present. This could be because Workbench was installed to a different partition. Do you have multiple partitions on the setup? Make sure any that don't have Workbench installed are marked as non-bootable, or at least as a lower priority than the Workbench partition.

@Deadalus: I think you've cracked it !

5. (This current version) is a 512 MB HDF with one partition on it

6. I cant remember checking a box to make it bootable (at the time I formatted
the disk).

7. Is there anyway to make it bootable after I've formatted the drive, and installed
WB onto it ?

Thanks very much for your insight !

If that screen comes up it means your disk is bootable, it could be that your S directory doesn't have the file "startup-sequence" or it's corrupted:

From the prompt try typing this:

Assign ENV: RAM:
LoadWB
EndCli

@AMIGASYSTEM
That seems to have fixed it !

Thanks very much to you both.
It's very much apprecaited

Can you make a „dir S:“ from this prompt?