Installing new kickstart roms in a1200

BowToYourSensei · 21 July 2022, 06:07

So I recently decided to upgrade my a1200. I got a terrible fire 1230 card, which required upgrading my kickstart roms. I had 3.0 roms and got a set of 3.1 roms. Of course I put them in the wrong slots first time (I would think rom 2 would go in slot B, but I guess not). After installing them correctly I get an error on start up:

scsi.device version 46 already resisdent.

Loading scsi.device failed: object already exists.

C:LoadModule failed returncode 10

My Amiga has a compact flash hard drive, so I imagine it's having resource issues with the new roms and locating the hard drive. I'm hoping adjusting my startup sequence can resolve this issue. But I do not have enough experience to solve this. I also kept the Amiga OS version I previously had installed. I'm not sure which version was standard for 3.0 roms. I've read conflicting information. But I've also read that both OS 3.0 and OS 3.1 should work with 3.1 roms. Any help would be appreciated!

TCD · 21 July 2022, 06:48

Could you post your Startup-Sequence and user-startup?

BowToYourSensei · 22 July 2022, 01:14

Startup-sequence:
;$VER: Startup-Sequence_HardDrive 40.2 (25.2.98)
;Startup-Sequence for hard drive systems

C:LoadModule Devs:scsi.device REVERSE

C:SetPatch QUIET

C:Version >NIL:
C:AddBuffers >NIL:
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

RESIDENT >NIL: C:Assign PURE
RESIDENT >NIL: C:Execute PURE

ASSIGN >NIL: ENV: RAM:ENV
ASSIGN >NIL: T: RAM:T
ASSIGN >NIL: CLIPS: RAM:Clipboards
ASSIGN >NIL: REXX: S:
ASSIGN >NIL: PRINTERS: DEVS:PRINTERS
ASSIGN >NIL: KEYMAPS: DEVS:KEYMAPS
ASSIGN >NIL: LOCALE: SYS:Locale
ASSIGN >NIL: LIBS: SYS:Classes ADD
ASSIGN >NIL: HELP: LOCALE:Help DEFER

ASSIGN >NIL: FMS: Devs:FMS
ASSIGN >NIL: ST: Work:Samples

BindDrivers
C:Mount >NIL: DEVS

OSDrivers/~(#?.info)

IF EXISTS DEVS:Monitors
IF EXISISTS DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
EndIF

C:List >NIL: DEVS:Monitors/~(#?.infoVGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
Execute T:M
C

elete >NIL: T:M
EndIF

PatchOpenWB

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
Unset Kickstart

C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS: Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools/Commodities

ASSIGN >NIL: CON: DISMOUNT
ASSIGN >NIL: RAW: DISMOUNT

Mount CON:
Mount RAW:

IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:

BowToYourSensei · 22 July 2022, 01:15

Any obvious typos are on me, I'm just copying what I read and posting it with my phone.

BowToYourSensei · 22 July 2022, 01:21

User-startup:
;BEGIN NewIcons
Run <NIL: >NIL: c:NewIcons
;END NewIcons
;BEGIN DefIcons
DefIcons
;END DefIcons

TCD · 22 July 2022, 01:26

Just comment out the 'C:LoadModule Devs:scsi.device REVERSE' line in your Startup-Sequence using ';' in front of it. That should fix the error.

BowToYourSensei · 22 July 2022, 01:31

I tried that, and workbench loaded, but nothing else. No floppies or partitions.

TCD · 22 July 2022, 01:37

Okay, that destroys my theory. Hopefully with the info somebody else can identify the problem.

BowToYourSensei · 22 July 2022, 01:48

I tried that with both my TF1230 and my original 8mb expansion card, and had a blank WB screen both times. I tested this thinking maybe the TF1230 requires the onboard ide connector to be connected, but that wasn't the issue either.

Leon Besson · 22 July 2022, 04:15

Which 3.1 ROMs did you get? Original 3.1, Cloanto 3.1 or a higher 3.x version?

Sounds to me you may have a higher version which means that workbench.library isn’t included in the ROMs. In this case you need a copy of workbench.library in sys:Libs

Worth a read here to help to fix this for you Bromigo;

https://eab.abime.net/showthread.php?t=102054

BowToYourSensei · 22 July 2022, 07:16

I'll read that link. As for now, I didn't know there were different versions of 3.1. They have amiga forever badging on them.

Leon Besson · 22 July 2022, 14:09

Quote:

Originally Posted by BowToYourSensei

I'll read that link. As for now, I didn't know there were different versions of 3.1. They have amiga forever badging on them.

Best way of checking is booting up from a workbench floppy and checking the version.

Standard 1200 3.1 Kickstart ROM version is 40.68

BowToYourSensei · 22 July 2022, 23:59

Ok, well I just booted without a startup-sequence and typed "version". It's says I'm running kickstart 40.68, and workbench 40.42

Leon Besson · 23 July 2022, 00:39

Quote:

Originally Posted by BowToYourSensei

Ok, well I just booted without a startup-sequence and typed "version". It's says I'm running kickstart 40.68, and workbench 40.42

So the correct ROMs then Bromigo!

The only other thing to check is what do you have in WBStartup?

Is this a Classic Workbench setup, I.e it has extras already setup?

BowToYourSensei · 23 July 2022, 03:18

Quote:

Originally Posted by Leon Besson

So the correct ROMs then Bromigo!

The only other thing to check is what do you have in WBStartup?

Is this a Classic Workbench setup, I.e it has extras already setup?

I'm not sure about this. A little over my head. To be honest, I bought the Amiga already setup. Looking in my WBStartup directory, I have 4 files and their info files:
ClickToFront
MagicMenu
ToolsDaemon
VirusZ

Leon Besson · 23 July 2022, 23:06

Quote:

Originally Posted by BowToYourSensei

I'm not sure about this. A little over my head. To be honest, I bought the Amiga already setup. Looking in my WBStartup directory, I have 4 files and their info files:
ClickToFront
MagicMenu
ToolsDaemon
VirusZ

Okay so I’m guessing this is a ClassicWorkbench setup. The only issue here is that because you’ve changed to 3.1 ROMs then this has added some sort of conflict on that build of workbench.
When Classic Workbench is built up via a free download and a Owned copy of Workbench it asks which Workbench version / AmigaOS you are using. I can only surmise it was specifically built with Workbench 3.0.

I take it everything was working okay with the 3.0 ROMs? Why the change to 3.1?

Remember to get this working you need to take out the 3.1 ROMs and put the 3.0 ROMs back in but remember to j comment out the SCSI line in startup-sequence.

BowToYourSensei · 24 July 2022, 00:30

Ok, yes that makes sense. I was afraid of that. So the reason I needed to upgrade the kickstart was so I could use the tf1230 accelerator card I purchased. It requires 3.1 or higher. So I imagine the fix then is to put the old roms back in, format my workbench partition, reinstall the 3.1 roms and then reinstall workbench?

BowToYourSensei · 24 July 2022, 00:34

And it says I'm running workbench 40.42, which is workbench 3.1 correct? So previously I had kickstart 3.0 roms and workbench 3.1?

Leon Besson · 24 July 2022, 03:05

Quote:

Originally Posted by BowToYourSensei

And it says I'm running workbench 40.42, which is workbench 3.1 correct? So previously I had kickstart 3.0 roms and workbench 3.1?

According to this Bromigo! Yes;

http://wiki.classicamiga.com/History...h_and_Amiga_OS

Technically you have 3.1 ROMs with Workbench 3.1 so logically this should just work.
As this appears to be a bespoke workbench build with 3.0 ROMs, then I can guess something in the workbench build is making this work with 3.0 ROMs but NOT 3.1 ROMs.

The only things to try is move out each of the programs from WbStartup and put them elsewhere (DO NOT Delete them!)mto see if any of those are causing the issue.

The click to front program stems from 1987!

http://aminet.net/package/util/mouse/ClickToFront

So may not be 3.1 ROM compatible??

Toolsdaemon looks like it should work as it mentions using ROM 3.0 or higher;

http://aminet.net/package/util/boot/ToolsDaemon21a

I still think you have a missing workbench.library that should be in the ROM chips. Do you have a copy of workbench 3.0 or 3.1 disks?
If so I think it should be on the actual workbench disk or even Install disk in Libs: workbench.library. Try copying this in to
The Hard Drive/CF card Libs: directory.

Try on power up holding down the 2 mouse buttons until you get the early Kickstart menu and boot without startup. Type the following;
Version workbench.library

Technically if it’s in the ROM it should report back.

The better option is to contact the seller who you bought the ROMs from to check that he hasn’t provided dodgy ROMs.

If no luck there, then try buying another set if 3.1 ROMs. Can recommend this EBay seller who I bought Licensed Cloanto ROMs from;

https://www.ebay.co.uk/itm/132921768...mis&media=COPY

Or from here;

https://www.ebay.co.uk/itm/122128523...mis&media=COPY

Workbench 3.1 disks from here;

https://www.ebay.co.uk/itm/131589679...mis&media=COPY

BowToYourSensei · 24 July 2022, 04:19

Ok, so I already put my 3.0 roms back in. I don't have a proper rom puller, so this causes me anxiety every time! Haha. I own a physical copy of amiga forever, so I can get legit adf files for whatever I need. I'll report back on the version of the workbench library soon.

21 July 2022, 06:07	#1
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Installing new kickstart roms in a1200 So I recently decided to upgrade my a1200. I got a terrible fire 1230 card, which required upgrading my kickstart roms. I had 3.0 roms and got a set of 3.1 roms. Of course I put them in the wrong slots first time (I would think rom 2 would go in slot B, but I guess not). After installing them correctly I get an error on start up: scsi.device version 46 already resisdent. Loading scsi.device failed: object already exists. C:LoadModule failed returncode 10 My Amiga has a compact flash hard drive, so I imagine it's having resource issues with the new roms and locating the hard drive. I'm hoping adjusting my startup sequence can resolve this issue. But I do not have enough experience to solve this. I also kept the Amiga OS version I previously had installed. I'm not sure which version was standard for 3.0 roms. I've read conflicting information. But I've also read that both OS 3.0 and OS 3.1 should work with 3.1 roms. Any help would be appreciated!

22 July 2022, 01:14	#3
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Startup-sequence: ;$VER: Startup-Sequence_HardDrive 40.2 (25.2.98) ;Startup-Sequence for hard drive systems C:LoadModule Devs:scsi.device REVERSE C:SetPatch QUIET C:Version >NIL: C:AddBuffers >NIL: FailAt 21 C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ RESIDENT >NIL: C:Assign PURE RESIDENT >NIL: C:Execute PURE ASSIGN >NIL: ENV: RAM:ENV ASSIGN >NIL: T: RAM:T ASSIGN >NIL: CLIPS: RAM:Clipboards ASSIGN >NIL: REXX: S: ASSIGN >NIL: PRINTERS: DEVS:PRINTERS ASSIGN >NIL: KEYMAPS: DEVS:KEYMAPS ASSIGN >NIL: LOCALE: SYS:Locale ASSIGN >NIL: LIBS: SYS:Classes ADD ASSIGN >NIL: HELP: LOCALE:Help DEFER ASSIGN >NIL: FMS: Devs:FMS ASSIGN >NIL: ST: Work:Samples BindDrivers C:Mount >NIL: DEVSOSDrivers/~(#?.info) IF EXISTS DEVS:Monitors IF EXISISTS DEVS:Monitors/VGAOnly DEVS:Monitors/VGAOnly EndIF C:List >NIL: DEVS:Monitors/~(#?.infoVGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s" Execute T:M Celete >NIL: T:M EndIF PatchOpenWB SetEnv Language "english" SetEnv Workbench $Workbench SetEnv Kickstart $Kickstart UnSet Workbench Unset Kickstart C:AddDataTypes REFRESH QUIET C:IPrefs C:ConClip Path >NIL: RAM: C: SYS: Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools/Commodities ASSIGN >NIL: CON: DISMOUNT ASSIGN >NIL: RAW: DISMOUNT Mount CON: Mount RAW: IF EXISTS S:User-Startup Execute S:User-Startup EndIF Resident Execute REMOVE Resident Assign REMOVE C:LoadWB EndCLI >NIL:

22 July 2022, 04:15	#10
Leon Besson Banned Join Date: Feb 2022 Location: Anywhere and everywhere I have a contract Posts: 822	Which 3.1 ROMs did you get? Original 3.1, Cloanto 3.1 or a higher 3.x version? Sounds to me you may have a higher version which means that workbench.library isn’t included in the ROMs. In this case you need a copy of workbench.library in sys:Libs Worth a read here to help to fix this for you Bromigo; https://eab.abime.net/showthread.php?t=102054 Last edited by Leon Besson; 22 July 2022 at 04:25.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A1200 kickstart roms placement	MBG	support.Hardware	6	20 January 2021 21:41
Split/join ROMs (kickstart ROMs)	NLS	support.Other	7	09 September 2018 23:54
FS: Kickstart Roms 3.0 A1200	Dreamcast270mhz	MarketPlace	0	26 December 2009 21:47
WTB: kickstart roms for A1200	viz17	MarketPlace	1	13 December 2009 23:07
Installing A1200 ROMs - which is which?	alphonsus	support.Hardware	15	09 July 2008 17:45

21 July 2022, 06:48	#2
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 31,615	Could you post your Startup-Sequence and user-startup?

22 July 2022, 01:15	#4
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Any obvious typos are on me, I'm just copying what I read and posting it with my phone.

22 July 2022, 01:21	#5
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	User-startup: ;BEGIN NewIcons Run <NIL: >NIL: c:NewIcons ;END NewIcons ;BEGIN DefIcons DefIcons ;END DefIcons

22 July 2022, 01:26	#6
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 31,615	Just comment out the 'C:LoadModule Devs:scsi.device REVERSE' line in your Startup-Sequence using ';' in front of it. That should fix the error.

22 July 2022, 01:31	#7
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	I tried that, and workbench loaded, but nothing else. No floppies or partitions.

22 July 2022, 01:37	#8
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 31,615	Okay, that destroys my theory. Hopefully with the info somebody else can identify the problem.

22 July 2022, 01:48	#9
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	I tried that with both my TF1230 and my original 8mb expansion card, and had a blank WB screen both times. I tested this thinking maybe the TF1230 requires the onboard ide connector to be connected, but that wasn't the issue either.

22 July 2022, 07:16	#11
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	I'll read that link. As for now, I didn't know there were different versions of 3.1. They have amiga forever badging on them.

22 July 2022, 23:59	#13
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Ok, well I just booted without a startup-sequence and typed "version". It's says I'm running kickstart 40.68, and workbench 40.42

24 July 2022, 00:30	#17
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Ok, yes that makes sense. I was afraid of that. So the reason I needed to upgrade the kickstart was so I could use the tf1230 accelerator card I purchased. It requires 3.1 or higher. So I imagine the fix then is to put the old roms back in, format my workbench partition, reinstall the 3.1 roms and then reinstall workbench?

24 July 2022, 00:34	#18
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	And it says I'm running workbench 40.42, which is workbench 3.1 correct? So previously I had kickstart 3.0 roms and workbench 3.1?

24 July 2022, 04:19	#20
BowToYourSensei Registered User Join Date: May 2021 Location: Harlan Posts: 42	Ok, so I already put my 3.0 roms back in. I don't have a proper rom puller, so this causes me anxiety every time! Haha. I own a physical copy of amiga forever, so I can get legit adf files for whatever I need. I'll report back on the version of the workbench library soon.

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