ADH0 in any drive

I keep getting this requester every time I try to install anything.
Is this a bug or am I doing something wrong?

@SteffJay

I suspect there's a bit missing from that message. It should read "Please insert volume ADH0 in any drive"

What it's asking you to do, is find the disk called ADH0 and insert in into a disk drive.

What has more probably happened, is that you had a hard disk partition with the device name ADH0 which has been changed at some point.

What you need to do is identify when the message appears (is it on boot? When you launch a particular program?), and investigate that to see if there is any mention of ADH0:

If it is happening on boot you should have a look in s:user-startup for ADH0: first, and then have a look at your WBStartUp programs (if it is OS4 then there's a WBStartUp Prefs which you might find has an entry for ADH0:something-or-other).

@Chris
That is correct, it asks for it when I try to install anything really and I don't know how to stop it.
I had a spare partition and I renamed it to ADH0 but that didn't help any.
Then it goes on to say that something is missing and/or assign something.
Not a clue 😞

@SteffJay

Can you please post the content of your user-startup?

You can find these in SYS:S/

@SteffJay

this error can come from a sloft linked file, or it can come from a config file, it can be good idea identify the program asking for ADHO: use snoopy, should display all file opens and file locks.


You can also use the find tool to look for any file that has ADHO: inside..

Deleted duplicate

@Maijestro

;BEGIN MUI
if exists "SYS:MUI"
assign MUI: "SYS:MUI"
if exists MUI:Libs
assign add LIBS: MUI:Libs
endif
if exists MUI:Locale
assign add LOCALE: MUI:Locale
endif
version >nil: exec.library 39
if not warn
if exists MUI:Docs
if exists HELP:dummy ; do not remove
endif ; this entry!
assign add HELP: MUI:Docs
endif
endif
endif
;END MUI

assign tbimages: SYS:Prefs/Presets/tbimages

;BEGIN MultiEdit
Assign MultiEdit: "SYS:Utilities/MultiEdit"
;END MultiEdit
;BEGIN MultiViewer
Assign MultiViewer: "SYS:Utilities/MultiViewer"
;END MultiViewer
;BEGIN MUI ASL
if exists "SYS:MUI"
run <>nil: MUI:PatchASL
endif
;END MUI ASL

@Maijestro
Please see below.

@SteffJay

Hi,

would it be possible for you to:
1 - open a Shell (either by pressing Right-Amiga+e when the Workbench is active, or in your system partition, in the drawer System double-click on the icon "Shell") and
2 - then type in "info" (without the quotes) in the Shell and press Enter or Return.
3 - and lastly post the output in this thread.

maybe we can gather more information.

Perhaps you also have a program in WBStartup that searches for ADH0?

Or in the startup sequence?

Perhaps it's something in APPDIR: pointing to ADH0:

@Tuvok

Maybe the output of "assign" would be useful too.

@Chris

Yes, I second that. It would have been the next step, I didn't want to make it too difficult or confusing with too many AmigaDOS commands.

@Tuvok

New Shell process 9
9.System:> info
Mounted disks:
Unit Size Used Free Full Access Status Name DOS Type
APPDIR: 0K 0K 0K 100% 4 Read/Write APPDIR APD\01
DH0: 37G 704M 36G 2% -1 Read/Write System SFS\00
DH1: 99G 12M 99G 0% 0 Read/Write Work SFS\00
DH2: 109G 13M 109G 0% 0 Read/Write Storage SFS\00
DH3: 101G 12M 101G 0% 0 Read/Write LHAs SFS\00
DH4: 101G 56M 101G 0% 0 Read/Write Programs SFS\00
DH5: 103G 14M 103G 0% 0 Read/Write Backups SFS\00
ENV: 5,555K 5,555K 0K 100% 29 Read/Write ENV ENV\01
ICD0: No disk present
ICD1: No disk present
IDF0: No disk present
IDF1: No disk present
RAM: 47K 47K 0K 100% 10 Read/Write RAM Disk RAM\01
TEXTCLIP: 1,529M 0K 1,529M 0% 1 Read/Write TextClip FTXT
USB0: 28G 48M 28G 0% 0 Read/Write ADH0 DOS\00

Volumes available:
ADH0: [Mounted] <- I renamed my USB stick to this
RAM Disk: [Mounted]
Backups: [Mounted]
Programs: [Mounted]
LHAs: [Mounted]
Storage: [Mounted]
Work: [Mounted]
System: [Mounted]
9.System:>

ADH0: [Mounted] <- I renamed my USB stick to this


this is not useful and not solving the problem.
follow LiveForIt's advice and use snoopy to identify which
task call the ADH0 device/drive.

@SteffJay

When you say "install anything" do you when you run the Installer, or try to copy something to the hard drive?

If its the former, it could be Installer or one of its dependents is looking for ADH0. There's also, I believe, different Installers, between Hyperion and AEON and possibly other third party replacements

Run Snoopdos and look to see what's trying to access ADH0.

Do you recall ever having a volume with that name?