ClassicWB (any OS3.X) and 3.1.4

[KKR75]

Originally Posted by Fendrix

Hmm, 68K version, OS 3.1.4 already installed in your System.hdf

Woops ! My mistake. This has been fixed. Link below:

ClassicWB 68K v3.0 Initial Release

[Fendrix]

Sweet, will test out now

[Fendrix]

Originally Posted by Fendrix

Sweet, will test out now

Works great so far

[Viceroy]

Sorry to seem thick but I'm getting a bit confused here?

ClassicWB-FULL v3.1.1 release

ClassicWB-68K 3.0 initial release

What's the difference between these 2, and which one should I be installing 3.1.4 on please?

[KKR75]

Originally Posted by Viceroy

Sorry to seem thick but I'm getting a bit confused here?

ClassicWB-FULL v3.1.1 release

ClassicWB-68K 3.0 initial release

What's the difference between these 2, and which one should I be installing 3.1.4 on please?

You should go on classiwb.abime.net and read the hardware requirements for all versions released by Bloodwych.

In a nutshell, the 2 versions I released are just updates to 2 of the versions that Bloodwych released.

The Full version is geared towards expanded ECS/AGA systems with 68020 or better processors, while the 68k version is aimed at specifically 68000 users.

Both packages are compatible with 3.1.4, that's the whole idea behind my work.

Best regards

[Viceroy]

Great thanks, I have every package already installed but thought you were just releasing 1 package for 3.1.4. I understand now ;-)

[Viceroy]

Which rom are you using with this please, If you use the one supplied with 3.1.4 you get Amiga ?.? AGA 20 in top left hand corner, if you use another 3.1 rom it displays fine?

[KKR75]

Originally Posted by Viceroy

Which rom are you using with this please, If you use the one supplied with 3.1.4 you get Amiga ?.? AGA 20 in top left hand corner, if you use another 3.1 rom it displays fine?

The ?.? Is a known bug with rom 3.1.4, you need to manually adjust it. Go to scalos top menu, prefs, titles and replace %os with 3.1.4 (yes, hard coded). There is no workaround for now. Or you can use %ov with displays the Kickstart revision 46.143.

[Viceroy]

Cheers for that KKR75 ;-)

[digiflip]

for this card https://sordan.ie/product/583/turbo-...ide-amiga-500/

i found changing jumper to octapussy ide driver for ks 1.3 resolved my issues with not seeing cf card and 2nd partition in pfs aio when running clasic wb 68k 3.1.4

[digiflip]

kkr75 scripts added to hstwb v1.30 beta,

youtube video classic wb full v3.11

[ Show youtube player ]

[monkat]

Great! Got it to work!

Not sure why it failed the first time.

Quick question - the 3.1.4 roms that come with it are not compatible with winuae? (Bin files)

Or is there a way to convert them to the right format?

Cheers


Sent from my iPhone using Tapatalk Pro

[PeterK]

Originally Posted by monkat

Quick question - the 3.1.4 roms that come with it are not compatible with winuae? (Bin files)

Or is there a way to convert them to the right format?

The bin files are for burning eproms. The files in the directory "unsplit_unswapped" can be used for WinUAE like the ROM "kick.a500.46.143" for example. Add the extension ".rom" to it and put it into your WinUAE Roms drawer. WinUAE will not detect it automatically, it needs to be selected with the file requester for "System ROM Settings" => "Main ROM file".

[frame]

Originally Posted by PeterK

The bin files are for burning eproms. The files in the directory "unsplit_unswapped" can be used for WinUAE like the ROM "kick.a500.46.143" for example. Add the extension ".rom" to it and put it into your WinUAE Roms drawer. WinUAE will not detect it automatically, it needs to be selected with the file requester for "System ROM Settings" => "Main ROM file".

monkat: Also make sure you disable "Start in Quickstart mode". Otherwise the selected 3.1.4 Rom will revert back to regular Roms. This took me a while to figure out.

[monkat]

Ah great! Thanks for the advice both worked great!


Sent from my iPhone using Tapatalk Pro

[digiflip]

tested on replay 060 clasic wb full v3.11 working fine with 3.1.4. what is the best way to change to 3.1.4 icons in classic wb?

[digiflip]

i was wondering if classic wb p96 and advsp versions going to be updated next, i used classic wb p96 on my replay before would like to update to 3.1.4 updates if possible

[KKR75]

Originally Posted by digiflip

i was wondering if classic wb p96 and advsp versions going to be updated next, i used classic wb p96 on my replay before would like to update to 3.1.4 updates if possible

my plan is to update and finalize 68k, polish full if necessary, then move on the advsp version and lite, then p96. unless there is big demand for p96 which i could possibly move up the list, but I don't use it as I only own classic integrated amigas like 500/+/600/1200. I've only tried P96 on winuae a few times. It certainly will get updated, however. Just give me time.

[digiflip]

Originally Posted by KKR75

my plan is to update and finalize 68k, polish full if necessary, then move on the advsp version and lite, then p96. unless there is big demand for p96 which i could possibly move up the list, but I don't use it as I only own classic integrated amigas like 500/+/600/1200. I've only tried P96 on winuae a few times. It certainly will get updated, however. Just give me time.

Ok we are lucky to get your support thanks

[KKR75]

New updated release for 68K version 3.1. Link below changelog.

CHANGELOG:

v3.1
	- Updated full WHDLoad package to latest beta prerelease v18.4, across ALL WB versions. The reason I opted for the latest beta is because v18.3 introduced a few bugs with certain games that was remedied in v18.4
	- Removed C:TagLiFE#?, C:PatchRAM#?, SYS:Update/ dir as no longer needed for v3.1.4
	- Removed LargeHD directory from MyFiles, also not needed with new ROM 3.1.4.
	- Removed references to TagLiFE, PatchRAM, BlazeWCP, and StackAttack in the ButtonMenu menus, only when under 3.1.4.
	- Cleaned up lots of stale .info files when using the WB1.3 theme under v3.1.4.

ClassicWB 68K 3.1.4 (Version 3.1)

Regards,

KKR75