Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: easy_john on May 08, 2009, 12:04:45 AM
-
Looking for "SFS_1.252.lha", because people at morphos forum say, that its latest SFS, than work with MOS..
-
Perhaps he can help you?
Linky to authors site (http://strohmayer.org/sfs/)
OR these guys if no one here can produce it quickly:
Another linky (http://amigans.net/modules/newbb/viewforum.php?forum=15)
-
@ easy_john
I still have that version.
PM your email adress, and I'll send it to you.
-
How can the new SFS cause MorphOS to crash?
Is the crashbug in MorphOS going to be fixed?
If the bug is not going to be fixed then can someone please tell me what the bug is, so that I can check my code for it and if found then "go around it".
I spent months of my life trying to work around all the bugs in WinUAE JIT. I think I have it all "worked around" now. I would hate for it to all go to hell now because of some other obscure bug.
Does the new SFS also crash WinUAE JIT?
Does the new SFS also crash WinUAE nonJIT?
Does the new SFS also crash Petunia OS4?
-
Who said anything about crashing? Anyway... MorphOS comes with a working version of SFS.
-
easy_john wrote:
Looking for "SFS_1.252.lha", because people at morphos forum say, that its latest SFS, than work with MOS..
Thats no longer true. The latest version works fine with MOS PUP.
-
direct link to file:
SFS 1.252.lha (http://strohmayer.org/sfs/files/SFS_1.252.lha)
oops.....does seem to be blocked now
-
@ChaosLord
How about figuring out the facts before switching into attack mode?
Speaking of JIT bugs, if you know any in Trance please let me know.
-
save2600, OSS542
On sfs official site no more old sfs available.
ChaosLord
i dont know, but many people say, that only old sfs compatible with MOS.
DJBase
but i still cant get it to work.
---
I spend few days(!) trying start Mos pup 1.4.5, and it still dosnt start. :(((
Maprom s alredy disabled.
I create empty SFS partition, 512mb, dh1.
I add SFS to RDB (1.277 version).
I format it under aos4.
I copy all CD to this partition.
I uncheck aos4 bootable flag, so Mos is first bootable partition.
I try to change some parameters in S-S:
- Add bootdevice (bootdevice=DH1).
- remove ">NIL" (no errors before first reboot)
- try module with ".idehack"
I try to manualy change SFS version in RDB to 1.252 or 1.202.
Nothing helps. Mos start, reboot, and theh hangs. hdd led allways on, but no hdd activity, display is blank (i wait few minutes every time).
I see all "Mos pup problem to boot" topics on morphzone.org, but still cant find answer..
-
@easy_john
What happens if you use FFS instead of SFS?
Just wondering if this is SFS problem in the first place...
-
Piru
Yes, first time i try to use FFS, but i have FFS version 51.10, from ao4.
Same blank screen.
-
@easy_john
FFS are compatible. Which means: SFS is not the problem.
Doesn't help you much with our non-boot problem however.
-
Piru
How i can find where problem is?
Is it possible to enable some bootlog or what?
-
It has been years (literally) since I last debugged MorphOS on PUP, but IIRC there was a way (I think it was a log written to RAM which could later be recovered. I really ought to remember as it was me who did the early debugging and alpha testing to get MorphOS running on BPPC in the first place). Unfortunately I no longer have my Amiga up and running so I can't help much.
Perhaps someone over morphzone.org can help?
-
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.
-
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.
-
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.
-
"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
-
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.
-
@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 :-(
-
I try to start on a4000....
-
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)
-
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 ?