Best ClassicWB on Amiga OS3.2

[NunoUFO]

I've tried installing Best Classic 2.0.4 both in a fresh 3.2 install and an existing one with always the same result where I'm no longer able to boot into Workbench.

Any ideas or experiences on how can I achieve this or working alternatives to Best Classic WB?

Thank you!

[TCD]

I found this thread: http://eab.abime.net/showthread.php?t=107410

[NunoUFO]

Originally Posted by TCD

I found this thread: http://eab.abime.net/showthread.php?t=107410

Thank you! it was the missing 3.2.1 update!
Its all working now

[BigD]

@Thread

I just installed BestClassicWB 2.0.4 under AmigaOS 3.2.1. I wholeheartedly recommend it! It pretty much recreates the AmigaOS 3.9 look over the top of the OS3.2 bugfixed system files (including a 'dock' system)! It also adds iGame, Personal Paint and DOpus programs! It's a bit of a download at 17 MB but nothing a Zip Disk can't handle!

I don't think that I'd be able to cope with OS 3.2 without it!

[oscillik]

I might have to give this a try, thanks! So many different WB packs out there…

[Photon]

Since (WB) 2.0, s-seq hides error statements. I personally don't think is a good idea for any OS. It's still relevant though, because of the hiding.

If you install any WB package, you can always put progressive echo statements in your startup to catch the point at which it fails, or at least stops before the LoadWB command. (The LoadWB command should either guru or load the WB with/without an error popup, or there is something wrong with your HW (or missing support software inserted in the startup for the HW you use, which means you can remove HW until it works.))

I've followed the developments and support the new ROM updates, but still recommend 3.1 (+any ROM extensions) and just ClassicWB and then add what you like from AmiNet to make it how you like it. <3

And even before ClassicWB 3.5/3.9 are valid options if you have 020+ and some Fastmem.

[No.3]

Originally Posted by Photon

...you can always put progressive echo statements in your startup to catch the point at which it fails, or at least stops before the LoadWB command.

I wonder what the "Trace Startup-Sequence" option in the OS 3.2 early startup menu might be good for...

[mfilos]

It's what the name says actually
It just runs the startup process line by line (starting from Startup-Sequence) asking you to accept or reject the line in order to troubleshoot possible errors by changing it.

[No.3]

You should repair your irony detector.