Looking for old sfs

[easy_john]

I install to rdb sfs 1.252, and ffs from aos3.9.
And now I completly can't boot to mos or 3.9...
Arrr.
Later i reinstall it from aos4 bootcd.

[Framiga]

easy_john wrote:
Looking for "SFS_1.252.lha", because people at morphos forum say, that its latest SFS, than work with MOS..

i guess you have got it in the wrong way.

1.252 is the one that gave problems with MOS for Pup

Install in the RDB the very latest one (1.279/68K) and QuickFormat the partition.

[Matt_H]

Huh? What I remember is that MorphOS ends up using a 68K SFS if it's in the RDB with a version greater than whatever is built into the MorphOS boot image - and this leads to lockups with 1.279. (When would that have been fixed?)

Can't verify, as my MorphOS drive died recently. I had been using SFS 1.84, though, which MorphOS would ignore and replace with its own version.

FFS isn't ideal because of its filename length limitation.

If you can't even get it to boot, it's more likely to be a problem with the startup-sequence commands.

[Framiga]

"Huh? What I remember is that MorphOS ends up using a 68K SFS if it's in the RDB with a version greater than whatever is built into the MorphOS boot image - and this leads to lockups with 1.279. (When would that have been fixed?)"

and so? Morphos for PowerUP starts with the 68k and requires a 68k filesystem in the RDB.

The "trick" you describe was intended to whom wish to use the native one (thats NOT a good idea in a multiboot enviroment)

The "problem" with failed boot, arisen with the SFS 1.252 os so (then fixed by the autor)

I have here SFS 1.279 all over the system without any problem

[easy_john]

I connect new hdd to onboard ide, create one sfs partition, format under aos4, install 1.279 sfs in RDB, copy all CD files to it, disconnect scsi hdd and cdrom, and try to boot from new ide drive.
Same problems. No errors before first reboot, but blank screen after reboot.

[doctorq]

@easy_john

I have the same problem as you describe here, with my A1200/PPC setup. Installing the same image on a A4000/PPC setup gives no issues what so ever (tested with various graphics cards).

I have tried all the boot options in the startup-sequence, but the computer still hangs after the first reboot :-(

[easy_john]

I try to start on a4000....

[Framiga]

have you tryed to play with different resetlevel values in SYS:S/Startup-Sequence? (and set bootdevice as well)

; Bootdevice can be used to specify the MorphOS partition if you have more than one
; bootable partition and the MorphOS one doesn't have the highest boot priority. Remember
; to use partition names, not volume names! This option requires the 'bootdevice' keyword
; like in the example below:
; set bootdevice "bootdevice=DH1"
; Leave the var blank if you want to boot from the default boot partition!

set bootdevice "bootdevice=CDH9:"

; The resetlevel and delay variables are there for you to tweak if MorphOS startup doesn't
; reboot the machine properly after loading MorphOS files.
;
; The possible resetlevel values are:
; 0 exec/coldreboot (System Reboot)
; 1 MMU switch off + normal reset in chipram (default)
; 2 MMU switch off + double reset in chipram
; 3 MMU switch off + Cyberstorm HW Reset in chipram
; 4 for (;;..waiting for manual reset by your hands:-)
; 5 MMU switch off + normal reset in fastram
; 6 MMU switch off + double reset in fastram
; 7 MMU switch off + Cyberstorm HW Reset in fastram

set resetlevel 5
set delay 1

ah ... and the very latest SYS:Boot/roms/module.com1 is bugged.

You have to use the one of the very first Morphos 1.4.5 release (10 August 2005)

[easy_john]

Framiga wrote:
have you tryed to play with different resetlevel values in SYS:S/Startup-Sequence?

no. my amiga allways do reset an resetlevel=5, so i don't try another levels.

(and set bootdevice as well)

yes, i try set and not set bootdevice.

ah ... and the very latest SYS:Boot/roms/module.com1 is bugged. You have to use the one of the very first Morphos 1.4.5 release (10 August 2005)

where i can get another module.com1 ?