Help! Installed OS3.9 on Compactflash but won't boot up

[kidkoala]

Hey

I've installed os3.9 on my 2gb compactflash-card connected through the ide-interface.
The partition was set up in hdinsttools, and there were no error messages, it was set up to be bootable, ffs international, selection on, automount, and the partition is 300mb.

no errors when installing, but when told to boot, after removing the wb-floppy, i only get the simple amigados, and when running "dir" i get the os3.9 dirs and files listed. it asks for ENV when trying to run something.

in early startup the hd shows like normal, is enabled, and when trying to choose it and boot, i get the amigados windows.

whats wrong??

i'm going to try and get sfs over to a floppy and try installing that before reinstalling 3.9. thanks for any help.

[Lando]

If you type 'loadwb' at the Amigados prompt does it then load Workbench?

[kidkoala]

No it just says "Please insert ENV", when pushing cancel it says "Please insert LOCALE"..

I booted from a 3.1 workbenchfloppy when installing os3.9 to the clean card, does that do anything bad?

also:

when running Assign I get the following.

Volumes:
Harddisk2 [Mounted]

Directories:
ENVARC
SYS Harddisk2:
C Harddisk2:C
S Harddisk2:S
LIBS Harddisk2:LIBS
DEVS Harddisk2:DEVS
FONTS Harddisk2:FONTS
L Harddisk2:L

Devices:
RAM CON RAW SER PAR
PRT DH0 DF0 CF0



There is no Startup-sequnce in C:
There is only a few other files like user-startup

[motorollin]

kidkoala wrote:
I booted from a 3.1 workbenchfloppy when installing os3.9 to the clean card, does that do anything bad?

Yes. It means OS3.9 has not been installed correctly, which is probably why it refuses to boot. You should boot from an OS3.9 emergency disk to do it right.

I think the startup-sequence in OS3.9 is copied from the emergency disk. Because you didn't boot from one, it didn't get copied. This means that while most of the rest of the structure of the OS is there, it doesn't actually do anything when you boot it because there is no startup-sequence.

The best thing to do would be to boot in to OS3.1, mount your CD drive, run OS3.9 setup, select the option to create an emergency disk, then boot from the emergency disk, reformat your CF card, and then reinstall OS3.9 (still booted from the emergency disk).

--
moto

[kidkoala]

motorollin:

Ah. I see! Thanks a lot pal Solved.

(Haven't tried but guess that's it so)

EDIT: But how come it worked with my 60mb hdd the other day? To boot up from 3.1 and installing like normal, the emergency disk is an option right`, not something you "must" do?

[motorollin]

kidkoala wrote:
EDIT: But how come it worked with my 60mb hdd the other day?

Luck? :-) Honestly, I can't explain why.

kidkoala wrote:
To boot up from 3.1 and installing like normal, the emergency disk is an option right`, not something you "must" do?

No. You should never install 3.9 from within 3.1. You should always boot to the emergency disk first.

--
moto

[kidkoala]

Ok now I'm installing again booting up from the emergencydisk.. but this turned into a bit of a mess, cause when starting the os3.9 install, and choosing create emerg. disk it asked for the wb3.1 disk )since i booted up from that), i put it in and just waited cause i figured it needed a couple of files before it could make the emerg. disk. but then i realised it was formatting my original wb3.1 disk! what the hell..where can i get a new one downloaded? it's the original escom one.

[motorollin]

Hmmm, that's why you should keep your WB disks write protected (and back them up). Sorry but it's not permitted by the site's policy to link to a download location. Try Google.

You will have to install 3.1 to hard disk first. The boot from it. Then run the 3.9 installer and create the Emergency Disk.

--
moto

[kidkoala]

Ok, new problem

The os3.1 installation can't find my harddrive since it's a type 7. th drive is already partitioned anf formatted, but when installing 3.1 you have go through the step where it searches between 0 and 6 for your drive, but then it can't find my drive in any of the numbers..what now?

are you sure i have to install 3.1 before 3.9?

[kidkoala]

SOLVED.

But new problem;

When finished installing 3.9 on top of 3.1 on a compactflash-partition with the sfs filesystem (haven't tried it before), I get an error when booting up saying something about "ramlib", then it stops. before even getting the real 3.9 wb-screen.

[motorollin]

You need to have 3.1 installed initially in order to create your Emergency Disk. Once you have that, you can get rid of the 3.1 install by booting to your Emergency Disk, formatting the System partition, and installing a fresh copy of 3.9 on to the empty partition.

--
moto

[kidkoala]

ah ok..thought i weren't supposed to install 3.9 onto an empty partition, the emergency disk i've created many days ago hehe..

will try this then..looking forward to when all this works

[motorollin]

When you run the 3.9 installer there are two options for the install: one for an upgrade over the top of 3.0/3.1, and the other for a full install on an empty partition. If you don't have anything you need in your 3.1 install, I would recomment the latter.

Re the ramlib error, ramlib is upgraded in the AmigaOS ROM Update, so check the kickstart version to make sure the ROM Update worked properly.

--
moto

[kidkoala]

thanks, and how and when do i check the kickversion?
if the ramlib error turns up i can't do much checking, boot without startup seq. and running info?

the ramlib-error didn't turn up when using ffs, only when starting to use sfs.

[guru-666]

is it possilbe to do this compact flash thing on the 4000's?
How mush faster the HD's are they?
What exactly do I need to get to hook one up?