Welcome, Guest. Please login or register.

Author Topic: ClassicWB 3.9  (Read 1197 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline k4lmpTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2012
  • Posts: 255
    • Show only replies by k4lmp
    • http://www.k4lmp.org
ClassicWB 3.9
« on: June 12, 2012, 06:50:57 PM »
Anyone have any ideas why I can run AmigaOS 3.9 on my A2000 (details in sig.), but if I try to boot ClassicWB 3.9, it doesn't work?  I noticed with WinUAE setup the same as my A2000, it does the same thing, however, if I set it up as an AGA 1200, it boots fine.  Since WinUAE does the same thing, I don't think it is a hardware problem, just maybe the ClassicWB trying to load something my A2000 won't do.  Does it add something to regular AmigaOS 3.9 that my A2000 won't run?  Like I said, it runs regular 3.9 fine.

Thanks,
Jeff
 

Offline nyteschayde

  • VIP / Donor - Lifetime Member
  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 643
    • Show only replies by nyteschayde
    • http://www.nyteshade.com
Re: ClassicWB 3.9
« Reply #1 on: June 12, 2012, 07:53:40 PM »
Totally guessing, but perhaps it's a ROM update specific to the A1200? Or perhaps it's something else. I was thinking about writing a showexecute CLI command that basically would write out the line it's going to execute before executing it. It would help trouble shoot issues like these. It could also log a file to a RAD drive or something or any non-FFS drive; wouldn't want it to crash during a write and invalidate the disk; I swear FFS likes to invalidate itself if you just look at it funny.
Senior MTS Software Engineer with PayPal
Amigas: A1200T 060/603e PPC • A1200T 060 • A4000D 040 • A3000 (x2) • A2000 Vamp/V2 • A1200 (x4) • A1000 (x3) • A600 Vamp/V1 • A500
 

Offline Darrin

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: May 2002
  • Posts: 4430
    • Show only replies by Darrin
Re: ClassicWB 3.9
« Reply #2 on: June 12, 2012, 08:27:17 PM »
I have it running fine on my A2000.

From memory, set it up on WinUAE (configure UAE as best you can to match the specs of your A2000 - CPU, chipset, etc before you do the install), make sure you set your screenmode in prefs to something your A2000 and monitor can display (very important)!, copy the files over to your A2000's media (hard drive, CF card, etc), plug the media into your A2000 and boot.
A2000, A3000, 2 x A1200T, A1200, A4000Tower & Mediator, CD32, VIC-20, C64, C128, C128D, PET 8032, Minimig & ARM, C-One, FPGA Arcade... and AmigaOne X1000.
 

Offline mfilos

  • Hero Member
  • *****
  • Join Date: Aug 2005
  • Posts: 662
    • Show only replies by mfilos
    • http://mfilos.blogspot.com/
Re: ClassicWB 3.9
« Reply #3 on: June 12, 2012, 08:37:47 PM »
ClassicWB 3.9 has by default Copper enabled!
Since Copper is an AGA related program, you should disabled it prior using it on your A2000.
One quick method without using WinUAE is by booting without Startup-Sequence using the Early Startup Menu and on command prompt issue:
Code: [Select]
1> cd C
1> execute Copper_disable
Just to be safe, you can disable a lot of components using the menu made by Bloodwych like Copper, StackAttack, BorderBlank, CyberBugFix, Fblit/Ftext, BlazeWCP, IconBeFast etc and then enable one at a time once your system boots succesfully
« Last Edit: June 12, 2012, 08:40:35 PM by mfilos »
Visit my Amiga blog here
- A600: Vampire V3, 128MB, A604n, 16GB CF, Indivision ECS, RapidRoad, MAS-Player + Custom Audio Mixer (internal), HxC SD + Slim floppy (internal)