OS 3.5 on the new Cloanto ROMS

frank_b · 17 December 2015, 09:34

Hi. I've installed the new 3.1 Cloanto ROMS on a spare 1200 and migrated my old OS 3.5 install to it. I'm not sure if I should use SKIPROMUPDATES or not since the new ROMS come with large disk support. I've seen wierdness on the machine where it won't boot the first time. Some apps are also crashing.
Any idea if I should just remove the ROM patching from the OS 3.5 startup setpatch command? Are these ROMS compatible with 3.5?

Daedalus · 18 December 2015, 10:26

Try removing the patches and then running Check4GB to make sure all your partitions are safe to use with the built-in ROM drivers. You can just skip the scsi.device ROM update if that's what is causing the problem. I'm a little suspicious of those ROMs since Cloanto give instructions that SetPatch should be skipped altogether when they're used, which seems a little lazy to me, and possibly indicates that you should do the same for 3.5. They do say they're really for use specifically with Workbench 3.1 so you don't need to patch things all over the place, so it may not be actually tested with 3.5 or 3.9.

Basically, it should work, but it's probably just a matter of fiddling around with what modules don't need to be patched. It's no harm to try disabling the 3.5 ROM update, and if it works, gradually adding back the modules you want from 3.5 until you find the problematic one.

frank_b · 18 December 2015, 14:21

Thanks. I'd never heard of Check4GB. That'll be handy.

FOL · 18 December 2015, 15:08

Quote:

Originally Posted by Daedalus

I'm a little suspicious of those ROMs since Cloanto give instructions that SetPatch should be skipped altogether when they're used, which seems a little lazy to me, and possibly indicates that you should do the same for 3.5.

My guess, this is a mistake.
The roms do support large drives, tested these about a year ago.

I would agree, skip scsi.device and see what happens.

HanSolo · 18 December 2015, 18:01

try rename or delete file - "devs:amiga rom update"

frank_b · 18 December 2015, 19:51

Quote:

Originally Posted by HanSolo

try rename or delete file - "devs:amiga rom update"

I booted with SKIPROMUPDATES=SKIPPROMMODULES

It reports that the system can handle disks > 4 gb.

FOL · 18 December 2015, 23:22

Quote:

Originally Posted by frank_b

I booted with SKIPROMUPDATES=SKIPPROMMODULES

It reports that the system can handle disks > 4 gb.

Only problem is your going to miss out on the other stuff updated that the rom doesn't contain.

frank_b · 18 December 2015, 23:23

That was just a test

I've left setpatch active

17 December 2015, 09:34	#1
frank_b Registered User Join Date: Jun 2008 Location: Boston USA Posts: 466	OS 3.5 on the new Cloanto ROMS Hi. I've installed the new 3.1 Cloanto ROMS on a spare 1200 and migrated my old OS 3.5 install to it. I'm not sure if I should use SKIPROMUPDATES or not since the new ROMS come with large disk support. I've seen wierdness on the machine where it won't boot the first time. Some apps are also crashing. Any idea if I should just remove the ROM patching from the OS 3.5 startup setpatch command? Are these ROMS compatible with 3.5?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A4000T won't boot with A4000T ROMs, but boots with A4000D ROMs	8bitbubsy	support.Hardware	15	29 March 2022 13:41
Cloanto debate	guru64	Amiga scene	282	11 January 2012 21:16
Why do you hate Cloanto so much?	AmigaBoingBall	Amiga scene	108	30 March 2010 19:01
Wanted pinouts of 3000T roms and 3000 roms	Vars191	support.Hardware	1	20 November 2008 10:38

18 December 2015, 10:26	#2
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,334	Try removing the patches and then running Check4GB to make sure all your partitions are safe to use with the built-in ROM drivers. You can just skip the scsi.device ROM update if that's what is causing the problem. I'm a little suspicious of those ROMs since Cloanto give instructions that SetPatch should be skipped altogether when they're used, which seems a little lazy to me, and possibly indicates that you should do the same for 3.5. They do say they're really for use specifically with Workbench 3.1 so you don't need to patch things all over the place, so it may not be actually tested with 3.5 or 3.9. Basically, it should work, but it's probably just a matter of fiddling around with what modules don't need to be patched. It's no harm to try disabling the 3.5 ROM update, and if it works, gradually adding back the modules you want from 3.5 until you find the problematic one.

18 December 2015, 14:21	#3
frank_b Registered User Join Date: Jun 2008 Location: Boston USA Posts: 466	Thanks. I'd never heard of Check4GB. That'll be handy.

18 December 2015, 18:01	#5
HanSolo Registered User Join Date: Aug 2014 Location: Gdynia/Poland Posts: 162	try rename or delete file - "devs:amiga rom update"

18 December 2015, 23:23	#8
frank_b Registered User Join Date: Jun 2008 Location: Boston USA Posts: 466	That was just a test I've left setpatch active

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