Partitions not mounting in OS 3.2.3 from my TF1260 fast IDE interface

  • Thread starter Thread starter Einherje
  • Start date Start date
  • Replies Replies 11
  • Views Views 532
Einherje

Einherje

Member
Joined
Apr 23, 2019
Posts
38
Country
Denmark
Region
Capital Region of Denmark
I need some new eyes on my setup and help understanding what I'm doing wrong.

I got a 3v/5v Apacer DOM on my TF1260 fast IDE interface from amigastore.eu. I can find and partition the DOM when booting from my OS 3.2 install floppy and running HDToolBox on ehide.device from that. However, when accessing the early startup control screen I cannot see and choose my bootable partition on ehide.device although I got a custom 3.2.3 rom with ehide.device patched in (also from amigastore.eu).

I then resign to boot from scsi.device from a no-name 16gb DOM that resides there. After installation, when I boot into the installed instance of OS 3.2.3, HDToolBox finds nothing on ehide.device. When I boot up on the OS 3.2 install disk it does however find and mount my partitions (2x ~16gb PFS) on the fast IDE interface when running HDToolBox on ehide.device.

I have tried pretending I don't have ehide.device in KS ROM and followed the instructions for modifying S/Startup-Sequence and I have also tried to add mount definitions in DEVS / DOSDrivers - both to no avail.

My amiga is a recently recapped 1.D.4 board (Cloanto Magic Pack) with an RTC module installed and nothing else atm.
 
Einherje said:
I need some new eyes on my setup and help understanding what I'm doing wrong.

I got a 3v/5v Apacer DOM on my TF1260 fast IDE interface from amigastore.eu. I can find and partition the DOM when booting from my OS 3.2 install floppy and running HDToolBox on ehide.device from that. However, when accessing the early startup control screen I cannot see and choose my bootable partition on ehide.device although I got a custom 3.2.3 rom with ehide.device patched in (also from amigastore.eu).

I then resign to boot from scsi.device from a no-name 16gb DOM that resides there. After installation, when I boot into the installed instance of OS 3.2.3, HDToolBox finds nothing on ehide.device. When I boot up on the OS 3.2 install disk it does however find and mount my partitions (2x ~16gb PFS) on the fast IDE interface when running HDToolBox on ehide.device.

I have tried pretending I don't have ehide.device in KS ROM and followed the instructions for modifying S/Startup-Sequence and I have also tried to add mount definitions in DEVS / DOSDrivers - both to no avail.

My amiga is a recently recapped 1.D.4 board (Cloanto Magic Pack) with an RTC module installed and nothing else atm.
Click to expand...

So the question is, what are your settings in HDtoolbox? Max transfer, PFS3 version etc…

Better to understand the issue by seeing some pictures.
 
DH1:

IMG_8592.webp


IMG_8593.webp


DH2:

IMG_8594.webp


IMG_8595.webp


File system:

IMG_8596.webp


DH0 resides on scsi.device (1GB FFS)
 
Okay. Settings look good. You are using a safe Max Transfer but that shouldn’t matter.
On the looks of it you are using version 19.2.

May I suggest downloading and trying the Beta 5 of Version 20.0 (3.2) for Toni Willen. I’ve been using this version now and have found it fixed a lot of issues.

 
Boing-ball said:
Okay. Settings look good. You are using a safe Max Transfer but that shouldn’t matter.
On the looks of it you are using version 19.2.

May I suggest downloading and trying the Beta 5 of Version 20.0 (3.2) for Toni Willen. I’ve been using this version now and have found it fixed a lot of issues.

Click to expand...
Cool! Didn't now about that :-)

No luck though. I might try switching the DOM out with a CF card on a buffered interface and see how I fare.
 
Something else you could try is Dopus. Yes believe it or not I have had issues with new drives not showing up before. But using Dopus 4 R16 and the right click options to format drives will show up the missing drives on Occassion.

Good luck going forward…
 
Everything works with a 32GB CF card (SanDisk Extreme PRO) on a buffered interface. Must be something with my DOM.
 
Boing-ball said:
Something else you could try is Dopus. Yes believe it or not I have had issues with new drives not showing up before. But using Dopus 4 R16 and the right click options to format drives will show up the missing drives on Occassion.

Good luck going forward…
Click to expand...
Thanks for all your input - especially heads up on new version of PFS3
 
My experience with Terrible Fire and CF cards / SD cards is this, use CF cards. I find that CF cards usually allow 2 attached to a channel, where SD cards dont. SD cards in my experience trick you into looking like they will work and then fail.

Hope you get it all working.
 
This drive will show up on early Boot ONLY if ehide.device is added to kickstart (You really need to use patched one to be able to boot from it).
 
Yes to boot from TF you HAVE to have eide.device in the ROM, or boot from something else and straightaway copy eide.dev into mapped rom and reboot.
 
Yes, but the problem will persist, early Boot is loaded directly from kickstart, not IDE, so ehide SHOULD present in rom, otherwise it'll not work!!!

However, You can leave one CF installed in MB IDE - it should have ehide.device on it, and modify startup sequence to load system from fast IDE after. Refer to FAQ how to set it up correctly:


Especially this part:
.."To use the IDE. You cannot “boot” from this. you need to have a boot device in the internal controller. but using Loadmodule (https://aminet.net/package/util/boot/LoadModule )
so unpack the driver (in windows I use 7zip. .. once for the gz and once for the tar) put the ehide.device to your DEVS: dir
add this to your S:Startup-Sequence:
loadmodule >NIL: devs:ehide.device"
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom