What's wrong with this Kick13 setup?

jotd · 13 September 2015, 17:02

Hi,

Been trying to boot a 1.3 hard drive configuration. Created an image file with WinUAE, attached "fastfilesystem" as file, and started the config, it crashed, and crashed.
If I don't bind it to a given filesystem, I get a "checksum error", get the prompt, and no files are reachable (I copied wb13 files on it).

I have other boot disks using "modern" setups and they work fine, but that one does not.

thx!!

SYS13.zip
A500_13_harddisk.zip

Arnie · 13 September 2015, 17:32

I couldn't boot from the HD, drive errors, a quick run through with QBTools reports errors with the drive. This drive uses OFS, most Amigas use FFS.

Is this a copy of a real drive?

jotd · 13 September 2015, 17:38

Nope

Just formatted it with quick option
Did i forget to run "install" on it? Iir it was only for floppies

Toni Wilen · 13 September 2015, 17:38

It is OFS formatted and far too large for OFS. Errors are normal..

jotd · 13 September 2015, 18:57

You're right. Reformatting to FFS does not crash anymore. But I get the prompt and no commands are available, even if I copied WB13 disk onto the disk (so s, c, important dirs are there)

Toni Wilen · 13 September 2015, 19:32

Quote:

Originally Posted by jotd

You're right. Reformatting to FFS does not crash anymore. But I get the prompt and no commands are available, even if I copied WB13 disk onto the disk (so s, c, important dirs are there)

Sounds like you booted from some other drive.

EDIT: Your config has multiple zero boot priority directory harddrives, listed earlier than HDF. First listed drive boots (only if all are UAE drives, real HD controllers can't work differently) if there are multiple drives with same boot priority.

AMIGASYSTEM · 13 September 2015, 20:03

Quote:

Originally Posted by jotd

Hi,

Been trying to boot a 1.3 hard drive configuration. Created an image file with WinUAE, attached "fastfilesystem" as file, and started the config, it crashed, and crashed.
If I don't bind it to a given filesystem, I get a "checksum error", get the prompt, and no files are reachable (I copied wb13 files on it).

Attachment 45461
Attachment 45462

So, while you have the hardisk invalidated, this can depend the size too large, or by switching off the system when you are working. Am attaching a new Startup-sequence and put them in place of your (rename). The harddrive can be repaired with utilities or Disksalv Fixdisk, but it's worth it, better recreate a new and smaller. First start should not attach other Hardisk, enter them one at a time and be careful that does not have the same volume name. Remember Kickstart 1.3 does not support FFS filesystem

Toni Wilen · 13 September 2015, 20:30

I think you should have read all posts before replying, I don't see what your reply has to do with original problem. Which was using OFS with too large partition size, OFS has very small size limit. (And of course FFS can be used under 1.3)

zipper · 13 September 2015, 20:43

Was OFS max 52 MB or something like?

Toni Wilen · 13 September 2015, 20:49

Quote:

Originally Posted by zipper

Was OFS max 52 MB or something like?

I am not exactly sure, always wanted to find it out but it so boring..
More than 40M and less than 60M or so I think.

huepper · 13 September 2015, 21:33

If i trust Thomas, then this is only 8MiB for OFS.
Have a look at this:

http://thomas-rapp.homepage.t-online...syslimits.html

jotd · 13 September 2015, 21:49

Hi,

I wasn't particularly looking to use OFS, so FFS worked for me all right. Toni was right, one of the other attached partitions was tagged "bootable". Now it boots, thanks, and I'll be able to investigate some "kick1.3 only" stuff.

Toni Wilen · 13 September 2015, 21:49

It has to be larger than 8M because 20M drives existed before FFS was introduced and you weren't forced to create multiple partitions.

AMIGASYSTEM · 13 September 2015, 22:41

Quote:

Originally Posted by Toni Wilen

I think you should have read all posts before replying, I don't see what your reply has to do with original problem. Which was using OFS with too large partition size, OFS has very small size limit. (And of course FFS can be used under 1.3)

You are right, I just wanted to point out al'utente jotd the startup-sequence contained errors, HD was huge, I did not remember the maximum size supported HD.

Quote:

(And of course FFS can be used under 1.3)

Here I did not understand, I was not talking about OS 1.3 but Kickstart 1.3, that from what I know I can not start volumes FFS.

LocalH · 17 September 2015, 02:24

FFS on 1.3 is only for HDDs. 2.0 added the ability to use FFS on floppies.

AMIGASYSTEM · 17 September 2015, 02:29

Quote:

Originally Posted by LocalH

FFS on 1.3 is only for HDDs. 2.0 added the ability to use FFS on floppies.

Yes A590HD, Not HD (HardFile used on WinUAE)

Toni Wilen · 17 September 2015, 08:44

Quote:

Originally Posted by AMIGASYSTEM

Yes A590HD, Not HD (HardFile used on WinUAE)

Wrong. Why do you think so?

FFS floppies need mountlist.

AMIGASYSTEM · 17 September 2015, 09:31

Quote:

Originally Posted by Toni Wilen

FFS floppies need mountlist.

I want to understand, refer to a disk not boot?

Toni Wilen · 17 September 2015, 10:34

Quote:

Originally Posted by AMIGASYSTEM

I want to understand, refer to a disk not boot?

Yes. FFS floppy booting under 1.3 (or older) is impossible. (=without ROM patching). Only manual FFS floppy mounting after booting from some other floppy/HD can be done with mountlist.

AMIGASYSTEM · 17 September 2015, 11:04

OK, I was finally understood ! thanks to the usual patience

13 September 2015, 17:02	#1
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,161	What's wrong with this Kick13 setup? Hi, Been trying to boot a 1.3 hard drive configuration. Created an image file with WinUAE, attached "fastfilesystem" as file, and started the config, it crashed, and crashed. If I don't bind it to a given filesystem, I get a "checksum error", get the prompt, and no files are reachable (I copied wb13 files on it). I have other boot disks using "modern" setups and they work fine, but that one does not. thx!! SYS13.zip A500_13_harddisk.zip

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
What am I doing wrong?	NLS	project.Killergorilla's WHD packs	6	07 January 2008 09:48
Are there two sizes for kick13.rom?	MickJT	Amiga scene	3	15 August 2007 00:49
hackdisk.device a600+kick13	ppill	support.Apps	0	17 December 2006 23:03
What am I doing Wrong?	RMadrid	New to Emulation or Amiga scene	45	31 March 2005 15:59
What am I doing wrong?	AllIEverHad	New to Emulation or Amiga scene	15	05 February 2003 00:07

13 September 2015, 17:32	#2
Arnie R.I.P Smudge 18-08-16 Join Date: Aug 2005 Location: Leicester/UK Age: 66 Posts: 3,968	I couldn't boot from the HD, drive errors, a quick run through with QBTools reports errors with the drive. This drive uses OFS, most Amigas use FFS. Is this a copy of a real drive?

13 September 2015, 17:38	#3
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,161	Nope Just formatted it with quick option Did i forget to run "install" on it? Iir it was only for floppies

13 September 2015, 17:38	#4
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	It is OFS formatted and far too large for OFS. Errors are normal..

13 September 2015, 18:57	#5
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,161	You're right. Reformatting to FFS does not crash anymore. But I get the prompt and no commands are available, even if I copied WB13 disk onto the disk (so s, c, important dirs are there)

13 September 2015, 20:30	#8
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	I think you should have read all posts before replying, I don't see what your reply has to do with original problem. Which was using OFS with too large partition size, OFS has very small size limit. (And of course FFS can be used under 1.3)

13 September 2015, 20:43	#9
zipper Registered User Join Date: Mar 2004 Location: finland Posts: 1,837	Was OFS max 52 MB or something like?

13 September 2015, 21:33	#11
huepper Registered User Join Date: Nov 2009 Location: GDR Age: 49 Posts: 249	If i trust Thomas, then this is only 8MiB for OFS. Have a look at this: http://thomas-rapp.homepage.t-online...syslimits.html

13 September 2015, 21:49	#12
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,161	Hi, I wasn't particularly looking to use OFS, so FFS worked for me all right. Toni was right, one of the other attached partitions was tagged "bootable". Now it boots, thanks, and I'll be able to investigate some "kick1.3 only" stuff.

17 September 2015, 02:24	#15
LocalH Amiga user since 1990 Join Date: Aug 2004 Location: Kingsport, TN / USA Age: 44 Posts: 295	FFS on 1.3 is only for HDDs. 2.0 added the ability to use FFS on floppies.

17 September 2015, 11:04	#20
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	OK, I was finally understood ! thanks to the usual patience

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)