Not a DOS disk in device DH0:

jostberg · 08 September 2021, 11:54

Don't know if this has been mentioned before but I've spent many hours on this.

I had problems setting up a new drive with HDToolbox. I'm using SCSI2SD on the A3000 internal scsi controller.

As I have an Apollo 4060 in my machine I have to use the old 3.1 ROMS and Loadmodule. If I boot from either 3.1.4 or 3.2 install disk, partition the SD-card with HDToolbox and enable the checkmark "Long filename support" on the file system tab the partitions won't show up after reboot.

Strangely I can see the partions in Early Boot Menu on 3.1 ROMS

Boot from say a ZIP drive to 3.2 I can see my partions on the SD-card, format them, copy files to them, even boot from them as long as I have the 3.2 modules still in memory. Turn off the machine I get "Not a DOS disk in device DH0:"

Repartition the drive and not enable the long filename checkmark in HDToolbox works fine. I can format the drive with long filename support and it still works, just not enable the checkmark in HDToolbox on 3.1 ROMS.

Bug or feature? At least I could get it to finally work.

thomas · 08 September 2021, 13:47

You have to add FastFileSystem V47 with a DosType of 0x444f5307 to the RDB (Add/Update in HDToolbox). If it is missing, the partitions are only available with Kick 3.1.4 or 3.2, but not with 3.1.

It's neither a bug nor a feature. It's always been this way: a file system which is not in ROM has to be in the RDB.

jostberg · 08 September 2021, 20:35

Quote:

Originally Posted by thomas

You have to add FastFileSystem V47 with a DosType of 0x444f5307 to the RDB (Add/Update in HDToolbox). If it is missing, the partitions are only available with Kick 3.1.4 or 3.2, but not with 3.1.

It's neither a bug nor a feature. It's always been this way: a file system which is not in ROM has to be in the RDB.

That was about the first I did, maybe the DOSTYPE was wrong but I just went with the default. Might try with another ZIP just to see if I get the same error.

thomas · 08 September 2021, 22:39

Quote:

Originally Posted by jostberg

maybe the DOSTYPE was wrong but I just went with the default

There is no default, you always have to overtype the value if you add a new file system.

jostberg · 09 September 2021, 08:56

Ah.... now I get it. When "just adding" the the FS in HDToolbox, its DosType is 0x444F5303 and that's get written to the RDB.

When adding it AND changing DosType to 0x444F5307, the FS-Name changes from International (FFS) to Long Name (FFS)

I just assumed adding the FS and enabling the "Long names" checkmark on the partition settings was enough. Now, this explains it all. Thanks Thomas!

08 September 2021, 11:54	#1
jostberg Registered User Join Date: Aug 2018 Location: Gothenburg, Sweden Posts: 23	Not a DOS disk in device DH0: Don't know if this has been mentioned before but I've spent many hours on this. I had problems setting up a new drive with HDToolbox. I'm using SCSI2SD on the A3000 internal scsi controller. As I have an Apollo 4060 in my machine I have to use the old 3.1 ROMS and Loadmodule. If I boot from either 3.1.4 or 3.2 install disk, partition the SD-card with HDToolbox and enable the checkmark "Long filename support" on the file system tab the partitions won't show up after reboot. Strangely I can see the partions in Early Boot Menu on 3.1 ROMS Boot from say a ZIP drive to 3.2 I can see my partions on the SD-card, format them, copy files to them, even boot from them as long as I have the 3.2 modules still in memory. Turn off the machine I get "Not a DOS disk in device DH0:" Repartition the drive and not enable the long filename checkmark in HDToolbox works fine. I can format the drive with long filename support and it still works, just not enable the checkmark in HDToolbox on 3.1 ROMS. Bug or feature? At least I could get it to finally work.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A1200: not a DOS disk in device	jotd	support.Other	34	29 January 2017 12:46
Not a DOS disk in device DF0	XsamX1987	support.Hardware	8	24 October 2016 12:00
Error: Not a DOS disk in device df0 -- Help, please?	jenxbunni	support.WinUAE	6	11 February 2013 20:10
"Not a DOS disk in drive DH0"	orange	support.WinUAE	6	24 February 2011 18:56
Not a DOS disk in device DF0:	MoreGrog	New to Emulation or Amiga scene	10	23 July 2010 19:46

08 September 2021, 13:47	#2
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	You have to add FastFileSystem V47 with a DosType of 0x444f5307 to the RDB (Add/Update in HDToolbox). If it is missing, the partitions are only available with Kick 3.1.4 or 3.2, but not with 3.1. It's neither a bug nor a feature. It's always been this way: a file system which is not in ROM has to be in the RDB.

09 September 2021, 08:56	#5
jostberg Registered User Join Date: Aug 2018 Location: Gothenburg, Sweden Posts: 23	Ah.... now I get it. When "just adding" the the FS in HDToolbox, its DosType is 0x444F5303 and that's get written to the RDB. When adding it AND changing DosType to 0x444F5307, the FS-Name changes from International (FFS) to Long Name (FFS) I just assumed adding the FS and enabling the "Long names" checkmark on the partition settings was enough. Now, this explains it all. Thanks Thomas!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)