Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Acill on April 10, 2016, 07:04:20 PM
-
I decided to pull my CD-ROM drive off the internal A4000T SCSI and put it on my CSPPC so I can boot and install the 4.1FE classic install disk. It boots right up using the included boot floppy and I can get to the install screen. I can even choose boot from CD to check it out. It runs well from the CD so I know it is working.
My HD is partitioned into 4 parts. I have two 2GB partitions set as bootable.
DH0: is the first 2GB of the drive and is PFS formated with my 3.9 main install. (Priority is -4)
DH1: is also 2GB and is the 2nd partition. (Priority 74) I changed the file system on it to Smart File System as the manual shows, formatted it after a reboot then installed 4.1FE to it.
Shut down for 15 seconds as the installer tells me, hold both mouse buttons to get to the early boot screen so I can select DH1 as boot device. The colors flash just like they do using the boot floppy, I see the black OS4.1 boot screen come up and it reboots, does it again but hangs on the black screen with the 4.1FE screen just before it would boot from CD if I used the CD to boot. It never access the new drive I installed it to.
Is this because I have it on the 2nd partition and not on the first 4GB of the drive as I just read in the manual? I dont want to have to wipe out my DH0: partition to change it from PFS to SFS if I can do it from the DF1: partition.
-
I decided to pull my CD-ROM drive off the internal A4000T SCSI and put it on my CSPPC so I can boot and install the 4.1FE classic install disk. It boots right up using the included boot floppy and I can get to the install screen. I can even choose boot from CD to check it out. It runs well from the CD so I know it is working.
My HD is partitioned into 4 parts. I have two 2GB partitions set as bootable.
DH0: is the first 2GB of the drive and is PFS formated with my 3.9 main install. (Priority is -4)
DH1: is also 2GB and is the 2nd partition. (Priority 74) I changed the file system on it to Smart File System as the manual shows, formatted it after a reboot then installed 4.1FE to it.
Shut down for 15 seconds as the installer tells me, hold both mouse buttons to get to the early boot screen so I can select DH1 as boot device. The colors flash just like they do using the boot floppy, I see the black OS4.1 boot screen come up and it reboots, does it again but hangs on the black screen with the 4.1FE screen just before it would boot from CD if I used the CD to boot. It never access the new drive I installed it to.
Is this because I have it on the 2nd partition and not on the first 4GB of the drive as I just read in the manual? I dont want to have to wipe out my DH0: partition to change it from PFS to SFS if I can do it from the DF1: partition.
It may be the case, yes. During testing I did not test trying to boot from any partition beyond the 4GB, nor did I test at all with PFS. So it's written pretty "safely" in the manual on what configuration will work - although it may work in your setup.
The biggest issue was setting up SFS properly and setting the right File System identifier. If that isn't done properly it won't work at all.
Darren
-
You said that you installed 4.1 to the DH1 partition, which is 2GB. If this 2GB falls within the first 4GB of the drive then you've done nothing wrong and it's some other problem.
-
You said that you installed 4.1 to the DH1 partition, which is 2GB. If this 2GB falls within the first 4GB of the drive then you've done nothing wrong and it's some other problem.
Well that blows. Itnis in the first 4GB. I used the file system ID the manuals tells me and set the block size as the manual tells me. Maybe Ill install again and see. I didnt wait long to see if its just searxhing scsi devices. My 3.9 install takes forever to boot so maybe this does too.
-
Well that blows. Itnis in the first 4GB. I used the file system ID the manuals tells me and set the block size as the manual tells me. Maybe Ill install again and see. I didnt wait long to see if its just searxhing scsi devices. My 3.9 install takes forever to boot so maybe this does too.
Well that blows. Itnis in the first 4GB. I used the file system ID the manuals tells me and set the block size as the manual tells me. Maybe Ill install again and see. I didnt wait long to see if its just searxhing scsi devices. My 3.9 install takes forever to boot so maybe this does too.
If it's in the first 4GB, setup correctly, and set for the highest boot priority, it should work. But again we never tested it with a PFS partition present. Perhaps that is causing grief. I just don't know.
The other issue is that if you have the wrong version of SFS installed in the RDB, it won't boot. One that isn't compatible, or not 68k. That's another gotcha.
You could always try on a clean disk to see if you can get it to work...
-
Its installed on a SFS partition I made with the OS4.1 CD partition tool. I'll try it on a new disk with only SFS on it later next weekend I guess. I just got done trying again and no luck. As for being set as highest priority its not, but I would think it can be told to boot by selecting that partition in the early startup? It at least gets to the ROM loading if I do that because I see the flashing colors and then the black screen with the AmigOS 4.1 logo through my Radeon, but it reboots after that, repeats and hangs on that black screen.
-
sounds that you load Amiga OS3.9 after the second reboot... you have to enter the startup-menu TWICE ! first loading the kickstart and second time to load OS4.1 again!
-
sounds that you load Amiga OS3.9 after the second reboot... you have to enter the startup-menu TWICE ! first loading the kickstart and second time to load OS4.1 again!
I'll give it a try and see. Didnt think about that since I see the loading screen for 4.1 and it hangs there.
EDIT:
I got into the 4.1 early start menu just like you said. It starts to boot but I get a Grimm Reaper that mentions to insert volume ENV: now. If I select retry it gives another error and shows something about the PFS volume I have for my 3.9 install. I am thinking it just doesnt like having the pfs volume before it. i get the same errors even if I select to disable that partition in the early startup menu.
-
Its installed on a SFS partition I made with the OS4.1 CD partition tool. I'll try it on a new disk with only SFS on it later next weekend I guess. I just got done trying again and no luck. As for being set as highest priority its not, but I would think it can be told to boot by selecting that partition in the early startup? It at least gets to the ROM loading if I do that because I see the flashing colors and then the black screen with the AmigOS 4.1 logo through my Radeon, but it reboots after that, repeats and hangs on that black screen.
It has to be set highest boot priority otherwise after the reset (eg. after the AmigaOS4.1 kernel loads and the PPC takes over), the system will try to boot off the wrong partition.
You can - at that point, kind of right after the system resets and just as the Logo is coming up, hold down both mouse buttons to enter the AmigaOS 4.1 early startup menu and manually select the correct partition, but it is a bit tricky to get that screen and under FE it ONLY displays on the native amiga output (ECS or AGA), never on RTG. So you will need a 1084S or similar monitor hooked up to the system to see the AmigaOS 4.1 early startup screen...so all in all easier to set the partition with the highest priority ;-)
-
Didnt think about that since I see the loading screen for 4.1 and it hangs there.
Run a text editor and enter DH1, then save it as DH1:Kickstart/BootDevice. Now load DH1:Kickstart/Kicklayout-A4000T (or which ever applies to your machine) into the editor, find the line which reads ;BootDevice and remove the semicolon from it. After saving you should no longer need to enter the boot menu twice.
so all in all easier to set the partition with the highest priority ;-)
You'll have difficulties to boot OS 3.9 if you do this.
-
Run a text editor and enter DH1, then save it as DH1:Kickstart/BootDevice. Now load DH1:Kickstart/Kicklayout-A4000T (or which ever applies to your machine) into the editor, find the line which reads ;BootDevice and remove the semicolon from it. After saving you should no longer need to enter the boot menu twice.
Good point, that will work too :)
-
Thomas, can you clarify on this procedure a bit more? Um not sure I understand it.
HammerD, I do have a 2nd monitor for the native output I use, getting to the early startuo isnt a problem.
-
OS 4.1 allows you to override boot priorities by specifying the name of the desired boot partition in a text file with the special name BootDevice and adding this file to the Kickstart layout. Once Kickstart 4.1 has been loaded, it will boot from the partition named in the BootDevice file rather than that with the highest boot priority.
-
Run a text editor and enter DH1, then save it as DH1:Kickstart/BootDevice. Now load DH1:Kickstart/Kicklayout-A4000T (or which ever applies to your machine) into the editor, find the line which reads ;BootDevice and remove the semicolon from it. After saving you should no longer need to enter the boot menu twice.
You'll have difficulties to boot OS 3.9 if you do this.
Yes, that is correct. Someone made a script to run to change the priorities, I think it may have even been you. But I'm not 100% sure.
I always tried to argue to add the functionality to save boot priorities in early startup but sigh...
-
Well I made the BootDevise text file and cant get it to find the drive I guess. It returns an error and drops to a shell telling me it couldnt locate it. I tried all these formats.
DH1
DH1:
AmigaOS4
AmigaOS4:
It looks like my next step is to just try and use a spare drive and partition the entire thing as Smartfile System and see if it boots from another clean install.
-
Acill did you post on Hyperion forums and amigans.net? Lots of devs/beta testers there that can help
-
Acill did you post on Hyperion forums and amigans.net? Lots of devs/beta testers there that can help
I've waied ages to have my registration approved on hyperian forums. Its never been approved as of december.
-
I've waied ages to have my registration approved on hyperian forums. Its never been approved as of december.
I'll see if I can fix that for you. Your real name will help if you want to PM it to me.
-
I'll see if I can fix that for you. Your real name will help if you want to PM it to me.
Most everyone knows who I am so no big deal. Its Paul R. Rezendes
I've also looked for where I can register my serial number for my version of OS4.1FE Classic so I can get an updated version of the ISO. This is the original release and I am sure its not up to date.
-
Acill
Cant you Reg it on Hyperion's site? thats where i Reg'd my Os 4.1 cd. Then you get access to the forums too.
-
ok I've posted on the moderator forum on the Hyperion Forums. Hopefully one of he mods will look into it shortly.
-
Acill
Cant you Reg it on Hyperion's site? thats where i Reg'd my Os 4.1 cd. Then you get access to the forums too.
I was able to this time, still cant log into forums
-
I was able to this time, still cant log into forums
After you register the CD/ISO, it's a manual process to get forum access. So hopefully it is soon.
-
Maybe a silly question: Is it looking up the scsi.device to boot and gets confused by having to choose cybppc.device ?the 4000T also has the 2ndscsi.device if I remember right. I tried booting 4.1 from a CF and eventually gave up on it and stayed with 3.1
-
Maybe a silly question: Is it looking up the scsi.device to boot and gets confused by having to choose cybppc.device ?the 4000T also has the 2ndscsi.device if I remember right. I tried booting 4.1 from a CF and eventually gave up on it and stayed with 3.1
4.1FE classic doesnt support the internal scsi. So thats not an issue I would think.
-
Okay, so I downloaded the latest ISO after getting my registration working.
I've installed it to a new drive I just put in. Its a 32GB drive split into two partitions. The first is a 4GB and the 2nd is the remaining 28GB. Both are setup the way the manual instructs me to do it using the file system ID it lists.
The CD boots fine on my A4000T, I can see the drives and format them even if use the boot OS4 from CD option. Ive installed it to the 4GB partition that I named AmigaOS4 (DH0). Its set as the highest priority at -4. The install completes perfectly with no errors.
I next shut off the machine as directed, wait 15 - 20 seconds and power on. I can see the colors flash indicating the kickstart loads. The screen changes to the black one with the AmigaOS 4.1FE logo and it never boots further off the drive. This is the exact same thing it did on the other drive I have in my system! (The other drive isn't connected, only this new one)
Ideas? I don't get how the CD boots up fine into OS4.1 but not a hard drive properly setup.
-
Okay, so I downloaded the latest ISO after getting my registration working.
I've installed it to a new drive I just put in. Its a 32GB drive split into two partitions. The first is a 4GB and the 2nd is the remaining 28GB. Both are setup the way the manual instructs me to do it using the file system ID it lists.
The CD boots fine on my A4000T, I can see the drives and format them even if use the boot OS4 from CD option. Ive installed it to the 4GB partition that I named AmigaOS4 (DH0). Its set as the highest priority at -4. The install completes perfectly with no errors.
I next shut off the machine as directed, wait 15 - 20 seconds and power on. I can see the colors flash indicating the kickstart loads. The screen changes to the black one with the AmigaOS 4.1FE logo and it never boots further off the drive. This is the exact same thing it did on the other drive I have in my system! (The other drive isn't connected, only this new one)
Ideas? I don't get how the CD boots up fine into OS4.1 but not a hard drive properly setup.
Try following or verifying you setup everything according to my Blog post:
http://blog.hyperion-entertainment.biz/?p=210
Adding the filesystem to the RDB is a critical part of the setup, including setting the DosType, and making sure it saves, so make sure you read that part carefully.