AdIDE how the...?

[Lokki]

Once again I'm grappling with something annoying...
Does anyone happen to have the AdIDE manual?
I'm having trouble setting up a 120 meg hard drive in my A500, got the driver disk but don't have the manual. Can't seem to find it anywhere.

[Lokki]

Doesn't look like they're talking to anyone anymore... my email gets bounced from those addresses.
Anyone out there who'd be interested in scanning their manual? You'd have my eternal gratitude... after days spent trying to make the interface boot properly I'm almost bald from the tearing of the hair and the stress.  :-(

[Lokki]

Mate, thank you very very much.
I think you've just saved my sanity!

[Lokki]

Still searching for a copy of the manual, anyone...  :-(

[Lokki]

Ah, thanks for pointing that out, I'd lost the link.
I had managed to find that post and some others but am still unable to get the system to boot from DH0. It should be possible with the 2.04 ROM I'm running... ? Most of my problem is the inability to write a 'proper' startup sequence for DH0: and no idea how to use the ICD install disk to make anything apart from verify, partition and install to happen... I've managed to muddle my way through it so far, but RTFM isn't possible.

[Lokki]

Oh ok, thanks for that. I'll double-check it tonight, I was under the impression the fast filesystem stuff was done automatically through the ICD partitioning program.
I've got the KS2.1 set of install disks but haven't been able to use HDinstall properly, it doesn't recognise DH0:

[Lokki]

I got further away this time I think.
The drive is added to the icdfmt.dat file, in correct form, drive zeroed, power off, jumper changed to 1.3, boot up the icd install disk.
Run ICD's format tool, detects drive properly, all set up right. Name: HardDrive, Partition: DH0, flagged FFS and BOOT.
Select Partition, program does it's job and installs workbench 1.3.
Exit program. HardDrive appears on workbench.
remove floppy, replace with install 2.1.
Reboot, hold mousebuttons.
Drive is in boot menu.
Booting to drive causes terminal guru errors if it's using workbench 1.3.
Booting to DF0: with Install 2.1 works well, HardDrive is visible on workbench. Try to us Install 2.1 tool and it gurus.
Whereas booting to workbench 2.1 and then doing a straight copy of everything seems to work. But I can't make it boot properly then, it'll have a fit at the Startup-Sequence and hang in AmigaDOS.
After that I can manually loadwb endcli and it's fine.
If I add icdmount to User-Startup on workbench 2.1 and boot from DF0:, the drive mounts perfectly and is usable.

I'm ready to kill the designer of this thing.

[Lokki]

Thanks for all the help everyone.
I'm running the latest version of the install disk, it also has a handy configuration program which reads the drive and updates icdfmt.dat with the drive details (although it wipes the drive when it does it).
It's the 3.5inch drive version, running a Seagate 130 Mb drive.
And with how user-friendly it's being at the moment I don't think I'd wish it on an enemy just now.
Unfortunately I've only got the one other wise I'd switch them to make sure it's not a bad unit. It shouldn't be, as the drive can get a certain distance into things before it gets upset, has to be a configuration problem.
I'll keep in mind that you're looking for one though, for when I'm ready to give up.  :-)
I'll have another crack at it in daylight, it's 3am and I've honestly had enough for the moment.

[Lokki]

Thanks, TJLazer! Hugely appreciated!

[Lokki]

Ah, interesting that.
It wasn't fixed in 2.05?

I'm unable to do warm reboot either, it still gurus... I'm going to have to start again I think.

[Lokki]

You know, that might do the trick. Thanks for the suggestion, mate.

[Lokki]

The plot thickens... I couldn't get 1.3 ROMs to function in my revision 6 A500, and couldn't be bothered modifying things, so I dragged out one of the Rev5 boards and installed the AdIDE in that. It boots to DH0. Consistently and well. Copied my Amiga Forever boot disk onto the drive (copy df0: dh0: ALL) and rebooted, works perfectly.
Now I'm going to fit the 2.04 ROM to this board and see what happens...

[Lokki]

Bah. As soon as I use my 2.04 ROM I start hitting problems.
It will boot to DH0: and do everything properly until I start a CLI... then we guru.
If I try to use my workbench 2.1 disk to boot.... then we guru.
At least I know it isn't the modified revision 6 board that's doing it.

[Lokki]

It's my untouched WB2.1 that I'm trying to boot to now and still no go. I'm starting to remember how much I hate the Guru screen.
I'm going to see if I can re-prep DH0 while the 2.04 ROM is installed and see what happens then, otherwise I'll reinstall KS1.3 and start from scratch with it, see if I can convince it to play nice.
Thanks for the offer, I bought a bunch of chips from a bloke in Germany and am just waiting for them to turn up so I can fit them. KS3.1, ECS Denise and Paula and a few others. Also a couple of spare KS2.04 ROMs, I'll try them also just to make sure it's not my ROM causing this.

[Lokki]

It has to be some sort of configuration problem, I've tried it in 7 different A500s (purely because I'm frustrated) and it works with 1.3 ROMs in each of these, but gurus with 2.04 ROM.
At least as an auto-booting drive.
If it's set to not boot (1.2 jumper) then it will load up fine and works quite well when I mount it in workbench 2.1