Are there files on the HDD that are precious?
If the answer is "No" you could simply start over. As such you would boot off Workbench disks, then fire up HDToolbox or HDInstTools. Then, you would format and partition the drive as you wish it to be (like DH0: and DH1: just like before). After that, you would open a CLI window (via the WB floppy) and copy WB from FDD to HDD. It would look something like this:
After that, you should be able to pop WB out of your floppy, reboot, and be looking at your new HDD ready to install various programs of your choosing.
If you're not ready or wanting to start over, another option would be to look inside your Startup-Sequence. You have to open a CLI and go to 'S' drawer.
I'd look in there and see if it is being Assigned. If it is, but you deleted part of the program, that could cause some funkiness for sure. I would also pop over to your mountlist file and look to see if Bootman was mounting anything funky over there, too. Those are the 2 key files
WB looks at during bootup.
To get to the "s" directory, you would call it up like this. Assuming you booted WB up off the floppy drive but want to work on your hard drives....
Even though you'll be booted up off the floppy, that will tell it to seek out DH0: and get to the 's' directory. From there, you could then load up your startup-sequence.
(It is not case sensitive.)
ED uses a built-in editor that allows you to read, edit and save text files. Startup-sequence is a very sensitive and special file. Look for anything that says "Bootman" in there. If you want to leave the file and NOT make changes, you hit "Esc" then the letter "Q". That will quit, and it will tell you if you do, you'll lose any changes (if you made any) and you'll say Yes.
If you do make changes in there (e.g. if you press CRTL and the letter B, it will delete an entire row) and you want to save those changes, you would hit the ESC key and then the letter X. That will save your changes to the file. You can reboot and see if your edits worked.
My guess is the Bootman program was being called somewhere in your Startup-sequence. There's a mild chance it might have even modified your user-startup file or the mountlist in DEVS.
But if you don't have precious files on there, you could just start from scratch and clear things out. Or, an even different approach would be to re-install Bootman
. But I'm guessing you probably won't really miss it.