Installation of WB3.1

[HyAmi]

Hi Folks,

I finally have the opportunity to setup my Amiga rig that I've been collecting the past two years. I haven't been able to play with it during that period. Now I want to make a fresh wb3.1 install on my A4000D. It's a standard A4000D with 040, 2MB chip, 4MB fast, A2320 and a 2GB WD Caviar disk.

I can use hdinstall from the Install disk, and I can make partitions. I just made one bootable partition. After making the partition I have to reboot. When I boot from the Workbench disk, I won't see the partition I made. When using the install disk, I first got partition on my workbench. (When I try it that way at this moment, nothing happens). At one point I was even able to install the complete set of disks. And after rebooting there wasn't anything to boot from. The partition doesn't show up in the early startup menu. When loaded from disks, I could see the installation at the harddisk.

I probably do something wrong, but I can't see what it is. So guru's; can you please help me?

[Amiduffer]

Try two partitions, just make hd0: 50megs or so, and leave the rest for hd1:

[Jope]

2GB is still within safe limits.

Is the dostype of your partition correct? Is the FastFileSystem installed onto the RDB?

[HyAmi]

What do you mean with the dostype? And how do I install the FastFileSystem to the RDB?

When I go to partition drive in HDToolbox, I see my 150MB partition with File System FFS International version 40.1

I changed the partition size a little, so I had to save the changes to the drive. After that follows the blabla that my oritinal partition will be destroyed. After that I have to reboot the system. When it's rebooted, there's no sign of the partition in Workbench.

So what's the next thing to do? Manually mounting the partition or something like that?

[Amiduffer]

I'm taking a guess, but what the heck.

After you partion it, do a format from your WB. Just click on the HD icon and use format from the icon menu.

Then, reboot the install disk and install the WB

This worked for me before.

[HyAmi]

I just wanted to reply: "that's the problem, there isn't an HD icon in workbench". But I thought, I'd better double check. And to my surprise this time an icon appeared of a non dos disk. I then formatted the partition. After rebooting, the partition was gone in workbench. By opening the hdtoolbox the partition was recognised again. So then I installed workbench succesfully. And after rebooting there isn't a bootable disk. When I enter the early startup menu, only the floppy drives are shown as bootable devices. So what can I do to make the computer boot from the HD?

[Amiduffer]

Anyone with an Amiga in front of them? There's something in the settings you choose when you have HDtoolbox up. It specifies if you want the partition to be bootable.

edit: This is a tutorial for installing a HD in an A1200, but see if it works for you.

Install Tutorial

[rkauer]

Hummmm, ermmmmm, ahannnnnn......

What exactly ROM do you have? 3.0?

If is, that's maybe the cause of the missbehaving. You reboot from hotreboot (CTRL+A+A) or coldboot (turn Amiga off, wait and then on again). Maybe the hd lost the RDB in every time you reboot, then the 4000 try to re-validate the hd.

Or maybe your old HD is going bad. It happened to me once with an IBM 2.5" HD. Partition, fine. Formatting, fine. Installing, fine. Play with it for 4~5 hours, fine. Turn off Miggy, in the other day the hd is totally lost/trashed.:pissed:

Try with another hd, maybe this is the cause of your problems.....

[AmiDude]

@HyAmi

Did you check the "Automount this partition" option
in HDToolBoxes Change settings? If you didn't, then
the system don't recognize the partition.

 

[theTAO]

Hopefully you can find your solution in the installation tutorial Amiduffer cited.  I browsed it, and it contains lots of good details.  If nothing there helps, here are a few thoughts...

1) Double-check your jumper settings and cabling.  Perhaps try another IDE cable.  Your description reminds me of a problem I had a number of years ago, trying to format high density floppy disks with (apparently) a faulty Catweasel controller.  In the end, I never got it working.  It was either a bad controller or too much noise coming from the motherboard.

2) The "Automount this partition" option is available if you tick "Advanced Options" and click "Change...", but this should always be enabled by default.  You said that you are setting the "Bootable" switch for your partition.  Under "Advanced Options", the Boot Priority should be "0".

3) If there is a valid partition on the drive, no matter if it's formatted or not, I believe it should be viewable from the Early Boot screen.  Bootable partitions should be listed to the left.  This is the part that bothers me most.  If you see no trace of the drive, and you immediately warm boot (Ctrl-LAmiga-RAmiga) and reenter the Early Boot screen, I assume you still see nothing?

Are you sure you have the 3.1 ROMs?  The 3.0 ROMs didn't pause long enough for some hard drives to finish their initialization spin, and so Kickstart wouldn't see them initially.  But a manual warm boot like above would fix the problem.

4) Don't worry about writing the FastFileSystem to the RDB.  In your case, this should be the same file stored in the ROM, and so should be optional.

5) If you connect the drive to a non-Amiga computer, I assume you can format it and use it normally?

Short of a weird incompatibility or fault with your hard drive (in which case you would never have gotten as far as you describe), I can't think of anything else to try.

Good luck,

Todd

[HyAmi]

Thanks for the replies!

I gave it another try today, and it seems like it's a odd jumpersetting problem. For my configuration, there are 3 possible methods to make the jumper settings:
1. Master
2. Master with special settings for well eh, something
3. Single drive

1 gives me most problems. Recognisable in hdtoolbox etc. This was the setting I was using.
2 works, but it first waits for the 30 second timeout before it boots. Annoying!
3 works very quick. But I'd like to add a cdrom drive, which seems difficult with a single drive config. But hey, I'll give it a try!

Oh BTW, I do have kickstart v40.068, so that part should be fine.