HOW do you handle multiboot ? with OS3.9/MOS/OS4 ???

[keropi]

Damn it to hell!
how do you get by? It sux!
I have an OS3.9 partition, priority 0
MOS partition , priority -5
and OS4 , priority -6
all was fine until OS4...

I could keep my nice kickflash contents, and boot MOS whenever I wanted via early start-up menu... now with OS4 I had to erase completelly kickflash. and I select the OS4 partition in ealry-startup menu, it reboots, reads from disk for a while and then the drive just clicks with an empty screen. if I give a priority 1 on OS4 partition, I can boot again OS4 but NO 3.9... it just gives some recovable errors...
what is to blame I think, are the warm reboots 3.9/4.0 do that really screw-up the kickstart...
what did you do to solve the problem?
ofcourse I don't want an OS4 boot-only amiga...
and where is the OS4 kickstart for the kickflash btw?
 :-?  :-?

[Chain]

keropi wrote:

and where is the OS4 kickstart for the kickflash btw?
 :-?  :-?

 :lol:  

[keropi]

is there some sort of restriction in partitions?
I mean should they be UNDER the 2GB limit? 4GB limit? damn it!

[keropi]

what? noone has any probs? it all works great for you??? Am I the only one with those probs?  :getmad:  :getmad:  :getmad:

[AMC258]

OK, I'm still waiting for my copy of OS4.  But, my machine is already prepped for it.  I don't know the first thing about kickflash (yet).

I don't see why OS4 should affect any other partitions/drives/etc.  What filesystem(s) do you use?
I mean, I can totally corrupt a partition and 3.9 could care less.  As long as the 3.9 boot partition has priority, it boots.

I do have problems occasionally with the kickstart that 3.9 uses getting corrupted (due to a bad memory access or something) and I can't warm boot at all then.  But, all is well after the next cold boot.

[TetiSoft]

@keropi

To boot OS4 from a partition which has not the highest
boot priority, you have to enter bootmenu twice to select
the partition, because the OS4 BootLoader does a soft reboot
after loading the OS4 kickstart.

Its possible to predefine the partition which OS4 will use
for loading the OS4 WB, see Documentation/Kickstart/BootLoader.doc.

[Framiga]

mhhh! no mention that PFS3 is only partially supported by OS4?

It would be better to inform users about this "little" glitch! don't you?

Name     Volume       Size Device       Unit Version  DosType  Version   Big Check
DH0                  8700M cybppc          0 52.2     PFS3     18.5      yes * N
CDH0     MOS          357M cybppc          1 52.2     PFS3     18.5       no ok
CDH1     MacOS       1046M cybppc          1 52.2     PFS3     18.5       no ok
CDH2     DATA        1640M cybppc          1 52.2     PFS3     18.5       no ok
CDH3                 1103M cybppc          1 52.2     PFS3     18.5      yes * N
CDH4                 6249M cybppc          1 52.2     PFS3     18.5      yes * N
CDH5     SFS         3111M cybppc          1 52.2     SFS0     1.277     yes ok
CDH6     AOS4         330M cybppc          1 52.2     SFS0     1.277      no ok
CDH7     SFS_2       3194M cybppc          1 52.2     SFS0     1.277     yes ok
CDH9     System3.9    330M cybppc          1 52.2     PFS3     18.5       no ok
PAR                        parallel        0          0000                no ok
PRT                        printer         0 52.1     0000                no ok
MDH0     Emergency   2051M scsi            0 52.5     PFS3     18.5       no ok
MDH1                 6142M scsi            0 52.5     PFS3     18.5      yes * N
MDH2                 8193M scsi            0 52.5     PFS3     18.5      yes * N
MDH3                 8193M scsi            0 52.5     PFS3     18.5      yes * N
MDH4                 8193M scsi            0 52.5     PFS3     18.5      yes * N
MDH5                 8193M scsi            0 52.5     PFS3     18.5      yes * N
MDH6                   32G scsi            0 52.5     PFS3     18.5      yes * N
MDH7                 4422M scsi            0 52.5     PFS3     18.5      yes * N
CD0                    19M scsi            1 52.5     CD01     52.11      no ok
SER                        serial          0 52.1     0000                no ok
DF0                   880K trackdisk       0 52.3     DOS0     52.5       no ok

[Framiga]

mhhh! just wondering about the PFS3 issue ...

do from a shell

version cybppc.device full

do you have the latest cybppc.device 44.71?

[TetiSoft]

@Framiga

no mention that PFS3 is only partially supported by OS4?

Partially supported? Until now I assumed PFS3 would not
support OS4 at all and cause a crash during boot.
Switch to SFS. There exists no official list of software
which is incompatible to OS4 yet.

[A4000_Mad]

@ keropi

I just read this from a link to another thread posted by Hans in another thread :crazy:

I used a HDD that was already partitioned with several working DOS/3 partitions and OS3.9 installed. I decided to install OS4.0 on a spare partition and selected long file names which seems to produce a DOS/7 partition. You also need to edit the DOS Type from 444f5303 by changing the last number from 3 to 7 to give 444f5307.

Obviously you must make the drive bootable and save the changes back to the drive. (I may have missed this step?) The boot priority must be higher than the OS3.9 boot partition. Once the partition has been formatted (using QUICK) I was able to install OS4.0 and it worked fine on the reboot. I've also noticed that if I want to boot from the OS3.9 partition rather than OS4.0 you have to change the boot priority of the partition for this to work (rather than selecting the partition in the Amiga early startup sequence).

Hope it could be of some help :pint:

[Crumb]

I could keep my nice kickflash contents, and boot MOS whenever I wanted via early start-up menu... now with OS4 I had to erase completelly kickflash.

I don't know with kickflash, but with Algor/Romulus it boots normally. If you want to use Norway you simply disable flashrom contents using left mouse button and you are done.

Just change your OS4 kicklayout file so you set booting device to be OS4: (or whatever name you choosed). You have to create a small text file.

That way your system will boot normally OS3.9, and if you choose MOS or OS4 in the early boot menu it will boot OS4 or MOS. I don't see the problem.

[keropi]

@Crumb
no it won't load OS4 "normaly"
3.9 boots fine , but since OS4 does a WARM-REBOOT, then on the 2nd reboot it will try and read from the 3.9 partition and the result is that NO OS will boot OK until the next COLD-BOOT.
and I believe I have the latest CSPPC flash, since I use a G-Rex4000D with it and MOS works nicelly   :-)

[lord_rover]

@keropi

Please re-read "slowly" what Crumb has written...

If you go and edit the Kicklayout-Axxx file (which you will find in your OS4/Kickstart drawer) to recognise your OS4 partition, it will not boot OS3.9 after the reboot. Instead it will immediately boot into OS4.

I'm still checking if i can find a way to boot OS4 without accessing the Early-Startup or disabling the Kickflash contents.

RTFM :-D

Alex

[keropi]

thanks lord_rover, I completelly missed that part!
and thanks crumb!  :-D

it would be nice to have some sort of loader in the flash of kickflash, giving the option to boot normally 3.9 with flash-contents, or OS4/MOS but with disabled contents...

[keropi]

what EXACLTY do I modify on my KickLayout-A4000 file, so OS4 knows that it's partition is OS4:  :-?  :-?  :-?