Kick1.3+A600+DF1:=Bug?

ppill · 10 September 2008, 23:10

Ok, so I'm using an A600(1Meg) with the ROM chip taken from an A500(kick1.3).

No major issues just one bug Toni pointed out some time that prevents from using resident modules that can survive a warm reboot (like hackdisk.device).

Now I think I found another one. I've got an external drive that works fine with both my A1200 and the previously mentioned A600 using a 2.04 kickstart ROM.

With 1.3 the drive is not recognised on power-up. Resetting doesn't help.

It's only recognised when I'm booting(only tried Hombre and the Workbench disk) from DF0: and there's a disk sitting in DF1: at the same time. Weird...

UPDATE:
Resetting the machine one or two times after booting from DF0: works aswell

Surely, it wasn't meant to be like that.

Any ideas?

meega · 10 September 2008, 23:12

Why on earth would you want to use KS1.3 in an A600?

TheCorfiot · 10 September 2008, 23:25

If I remember correctly, Kick 1.3 requires you to add an "addbuffers df1:"statement in your startup sequence in order to be recognised at boot time without a floppy inserted.

Again why would you want KS 1.3 on an A600. If it's for games compatibility reasons then surely most of the games requiring it will probably get freaked out by the 1MB chipram present instead of 512KB chip & no fast mem in any case ?????

At least the KS2.05 lets you use the IDE interface

TC

ppill · 10 September 2008, 23:32

Quote:

Originally Posted by meega

Why on earth would you want to use KS1.3 in an A600?

Because it's takes up half the space of an A500 giving almost 100% compatibility... also I don't own one but need a 1.3 environment to work on Hombre since it's aimed at systems running that version of kickstart. I know it seems strange but hey it does the trick.

Quote:

Originally Posted by TheCorfiot

If I remember correctly, Kick 1.3 requires you to add an "addbuffers df1:"statement in your startup sequence in order to be recognised at boot time without a floppy inserted.

Doesn't work. Addbuffers needs the drive to be properly initiated before it can add/subtract buffers.

meega · 10 September 2008, 23:39

If you want an A500 I've got one I don't use. Yours at a reasonable price +postage.

Rabbit80 · 10 September 2008, 23:42

Quote:

Originally Posted by meega

If you want an A500 I've got one I don't use. Yours at a reasonable price +P&P.

What is a reasonable price? I'm looking for a miggy!

meega · 10 September 2008, 23:45

I'm talking to ppill at the moment (if he wants to PM me or post here)

ppill · 10 September 2008, 23:46

Quote:

Originally Posted by meega

If you want an A500 I've got one I don't use. Yours at a reasonable price +postage.

Shipping costs from the UK to Poland would probably buy me two A500s here at home

And I'm not after one anyway, but thanks for the offer

meega · 10 September 2008, 23:50

I thought it would be that way, it's usually better value to get one locally (if you're looking for one).

Do you want it Rabbit80? I've sent you a PM.

/threadjack

TheCorfiot · 10 September 2008, 23:52

Quote:

Originally Posted by ppill

Doesn't work. Addbuffers needs the drive to be properly initiated before it can add/subtract buffers.

Sorry my friend, I'll pull my A500 out on the weekend & find out if it behaves the same,
I fully understand now why you need KS1.3 in the A600.

Good luck

TC

ppill · 11 September 2008, 01:02

Figured it out. It seems the bootblock on the disk in DF0: is responsible for initialising DF1: under 1.3. I was using a custom bootblock(X-Copy) which apparently doesn't do a good job. Installed a standard bootblock and everything works as it should!

So you can't boot from DF1: under 1.3?

Jope · 11 September 2008, 09:32

You can't boot from df1: under 1.3 and it should be auto-detected with any normal dos boot block..

Something is wrong with your computer if trackdisk.device can't find DF1: as the computer starts up.

Try X-Copy.. Can you copy with DF1: as source?

ppill · 11 September 2008, 09:46

Quote:

Originally Posted by Jope

You can't boot from df1: under 1.3 and it should be auto-detected with any normal dos boot block.

Thanks for the confirmation. Like I wrote in my previous post the drive is working fine after I'd installed the default dos bootblock.

The X-Copy bootblock was to blame (the one that displays 'No virus on bootblock'). Maybe it got corrupted somehow? It wasn't a virus, I checked.

Too bad I spent nearly two hours trying different drives/jumper settings before realising what was wrong. Oh well... at least I've learned something new

TheCorfiot · 11 September 2008, 10:05

@ppill

Glad you got it sorted out

TC

10 September 2008, 23:10	#1
ppill CON: artist Join Date: Feb 2006 Location: Poland Age: 43 Posts: 1,250	Kick1.3+A600+DF1:=Bug? Ok, so I'm using an A600(1Meg) with the ROM chip taken from an A500(kick1.3). No major issues just one bug Toni pointed out some time that prevents from using resident modules that can survive a warm reboot (like hackdisk.device). Now I think I found another one. I've got an external drive that works fine with both my A1200 and the previously mentioned A600 using a 2.04 kickstart ROM. With 1.3 the drive is not recognised on power-up. Resetting doesn't help. It's only recognised when I'm booting(only tried Hombre and the Workbench disk) from DF0: and there's a disk sitting in DF1: at the same time. Weird... UPDATE: Resetting the machine one or two times after booting from DF0: works aswell Surely, it wasn't meant to be like that. Any ideas? Last edited by ppill; 10 September 2008 at 23:39.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Swapping DF0 and DF1 on A600?	CrazyIcecap	support.Hardware	41	07 October 2016 14:20
Mod or hardware to use DF1 as DF0 on A600?	Photon	support.Hardware	9	15 January 2011 18:33
small GUI bug: ghosting of "write protection" label df0/df1	rsn8887	support.WinUAE	1	23 August 2010 17:02
AMIAG 1200 & Kick1.3 Emulator...	ST Dragon	Retrogaming General Discussion	3	24 February 2005 09:13
Softkick using Kick1.3 ROM to Kick1.2 ?	gary	support.Hardware	5	28 March 2002 19:59

10 September 2008, 23:12	#2
meega Registered User Join Date: Dec 2007 Location: Oooh what a feeling yeaaah dancing on the ceiling Posts: 314	Why on earth would you want to use KS1.3 in an A600?

10 September 2008, 23:25	#3
TheCorfiot Amibay Senior Staff Join Date: Feb 2008 Location: Cardiff / Wales Posts: 1,302	If I remember correctly, Kick 1.3 requires you to add an "addbuffers df1:"statement in your startup sequence in order to be recognised at boot time without a floppy inserted. Again why would you want KS 1.3 on an A600. If it's for games compatibility reasons then surely most of the games requiring it will probably get freaked out by the 1MB chipram present instead of 512KB chip & no fast mem in any case ????? At least the KS2.05 lets you use the IDE interface TC

10 September 2008, 23:39	#5
meega Registered User Join Date: Dec 2007 Location: Oooh what a feeling yeaaah dancing on the ceiling Posts: 314	If you want an A500 I've got one I don't use. Yours at a reasonable price +postage.

10 September 2008, 23:45	#7
meega Registered User Join Date: Dec 2007 Location: Oooh what a feeling yeaaah dancing on the ceiling Posts: 314	I'm talking to ppill at the moment (if he wants to PM me or post here)

10 September 2008, 23:50	#9
meega Registered User Join Date: Dec 2007 Location: Oooh what a feeling yeaaah dancing on the ceiling Posts: 314	I thought it would be that way, it's usually better value to get one locally (if you're looking for one). Do you want it Rabbit80? I've sent you a PM. /threadjack

11 September 2008, 01:02	#11
ppill CON: artist Join Date: Feb 2006 Location: Poland Age: 43 Posts: 1,250	Figured it out. It seems the bootblock on the disk in DF0: is responsible for initialising DF1: under 1.3. I was using a custom bootblock(X-Copy) which apparently doesn't do a good job. Installed a standard bootblock and everything works as it should! So you can't boot from DF1: under 1.3?

11 September 2008, 09:32	#12
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,861	You can't boot from df1: under 1.3 and it should be auto-detected with any normal dos boot block.. Something is wrong with your computer if trackdisk.device can't find DF1: as the computer starts up. Try X-Copy.. Can you copy with DF1: as source?

11 September 2008, 10:05	#14
TheCorfiot Amibay Senior Staff Join Date: Feb 2008 Location: Cardiff / Wales Posts: 1,302	@ppill Glad you got it sorted out TC

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