Is Classic WB Lite compatible with CGX4?

stefcep2 · 13 August 2010, 05:30

I'm just getting my A4000 set up after the MB caps and simm sockets were replaced. I have also just got an Indivision (great kit btw) and I'm taking its output and routing it to the pass through input of my CV64.

Native screenmodes work on the LCD I'm using. When I insall p96 within 3.1 ClassicWb Lite, the CV64 works. But P96 is noticeably slower than CGX4- I know this beacsue I have a seperate 3.9 with CGX 4 partition, which works fine. Well here's the thing: installing CGX 4 after removing p96 results in a grey screen or a crash with any CGX screen modes. i repeat P96 is fine. So is there anything in Classic WB Lite that conflicts with CGX (btw the same happened with the CV64/3D board)

stefcep2 · 14 August 2010, 03:04

ok so no-one used Classic WB with CGX?

BTW, I copied all the CGX files (libs, monitor drivers, prefs, CGXmode) from the working non-ClassicWB (OS 3.9) install and its STILL just gives a grey screen when selecting a CGX screen.

This is a MAJOR bummer, as I like ClassicWB, but P96 runs sooo much slower than CGX with the CV64.

Bloodwych · 14 August 2010, 23:16

It's going to be trial and error I'm afraid. I do all the setups in WinUAE these days and only test on an A1200 with fastram, so I'm a but stuck when people have issues on real Amiga setups with hardware I'm not familiar with.

If you look in the Run->Settings menu, there are components which can be enabled and disabled. Try playing around with those first, disabling as much as possible. If no success, try and comment out ( ; ) certain items in the startup files, which again can be found under the menus.

stefcep2 · 15 August 2010, 05:04

Quote:

Originally Posted by Bloodwych

It's going to be trial and error I'm afraid. I do all the setups in WinUAE these days and only test on an A1200 with fastram, so I'm a but stuck when people have issues on real Amiga setups with hardware I'm not familiar with.

If you look in the Run->Settings menu, there are componen.ts which can be enabled and disabled. Try playing around with those first, disabling as much as possible. If no success, try and comment out ( ; ) certain items in the startup files, which again can be found under the menus.

OK I''ll give it a try and see.. or I'll start from a fresh 3.1 install, and bit by bit add the bits I need.

Bloodwych · 15 August 2010, 13:58

Good luck.

Good idea to start from scratch and add stuff gradually from the pack. Let us know if you find out what it is causing the problem. It's always fun and games with Workbench.

stefcep2 · 02 October 2010, 13:18

OK I found that the "force chunky" option in CGXprefs needs to be deselected, and FBlit and Ftext need to be disabled. P96 works with Fblit and Ftext enabled, and it may be some setting within Fblit and Ftext that conflicts with CGX but not P96, but with all the Fblit and Ftext options thats too complicated for me to work out!

Mad-Matt · 02 October 2010, 13:31

I think the fact that fblit works with P96 was pure luck as the two shouldnt be used together as both will be patching os blitting functions.

Bloodwych · 02 October 2010, 13:43

As mentioned above, FBlit and FText are not required for graphics cards on the Amiga and should always be disabled, so ignore all those options. They basically allow the CPU to take over blitter operations to speed up Workbench and allow more free chipram. A graphics card does all this for you out of the box.

ClassicWB LITE has FBlit disabled by default, which is why I didn't initially suggest it. Thanks for the feedback about the force chunky option. Check out BlazeWCP - perhaps that has something to do with it and/or Smartwin. I think there are enable/disable options under settings in the LITE too.

stefcep2 · 02 October 2010, 16:31

Quote:

Originally Posted by Bloodwych

As mentioned above, FBlit and FText are not required for graphics cards on the Amiga and should always be disabled, so ignore all those options. They basically allow the CPU to take over blitter operations to speed up Workbench and allow more free chipram. A graphics card does all this for you out of the box.

ClassicWB LITE has FBlit disabled by default, which is why I didn't initially suggest it. Thanks for the feedback about the force chunky option. Check out BlazeWCP - perhaps that has something to do with it and/or Smartwin. I think there are enable/disable options under settings in the LITE too.

I did check Blazewcp, and found that it makes no difference on or off, as long as force chunk was disabled, CGX screens were fine. But FBlit and Ftext have to be disabled.

13 August 2010, 05:30	#1
stefcep2 Registered User Join Date: Dec 2009 Location: Melbourne/Australia Posts: 226	Is Classic WB Lite compatible with CGX4? I'm just getting my A4000 set up after the MB caps and simm sockets were replaced. I have also just got an Indivision (great kit btw) and I'm taking its output and routing it to the pass through input of my CV64. Native screenmodes work on the LCD I'm using. When I insall p96 within 3.1 ClassicWb Lite, the CV64 works. But P96 is noticeably slower than CGX4- I know this beacsue I have a seperate 3.9 with CGX 4 partition, which works fine. Well here's the thing: installing CGX 4 after removing p96 results in a grey screen or a crash with any CGX screen modes. i repeat P96 is fine. So is there anything in Classic WB Lite that conflicts with CGX (btw the same happened with the CV64/3D board)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Mouse wheel madness in Dopus (Classic Wb Lite v 24)	emuola	project.ClassicWB	9	26 September 2010 14:55
Classic WorkBench Lite	snoopy1992	project.ClassicWB	1	21 December 2009 07:40
Classic WB Lite on real standard amiga1200	Sparticle	project.ClassicWB	8	25 October 2009 17:48
Startup Errors on Classic Lite	kipper2k	project.ClassicWB	5	04 August 2009 02:23
Classic WB LITE	Smiley	support.Apps	5	05 March 2007 16:12

14 August 2010, 03:04	#2
stefcep2 Registered User Join Date: Dec 2009 Location: Melbourne/Australia Posts: 226	ok so no-one used Classic WB with CGX? BTW, I copied all the CGX files (libs, monitor drivers, prefs, CGXmode) from the working non-ClassicWB (OS 3.9) install and its STILL just gives a grey screen when selecting a CGX screen. This is a MAJOR bummer, as I like ClassicWB, but P96 runs sooo much slower than CGX with the CV64.

14 August 2010, 23:16	#3
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	It's going to be trial and error I'm afraid. I do all the setups in WinUAE these days and only test on an A1200 with fastram, so I'm a but stuck when people have issues on real Amiga setups with hardware I'm not familiar with. If you look in the Run->Settings menu, there are components which can be enabled and disabled. Try playing around with those first, disabling as much as possible. If no success, try and comment out ( ; ) certain items in the startup files, which again can be found under the menus.

15 August 2010, 13:58	#5
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Good luck. Good idea to start from scratch and add stuff gradually from the pack. Let us know if you find out what it is causing the problem. It's always fun and games with Workbench.

02 October 2010, 13:18	#6
stefcep2 Registered User Join Date: Dec 2009 Location: Melbourne/Australia Posts: 226	OK I found that the "force chunky" option in CGXprefs needs to be deselected, and FBlit and Ftext need to be disabled. P96 works with Fblit and Ftext enabled, and it may be some setting within Fblit and Ftext that conflicts with CGX but not P96, but with all the Fblit and Ftext options thats too complicated for me to work out!

02 October 2010, 13:31	#7
Mad-Matt Longplayer Join Date: Jan 2005 Location: Lincoln / UK Age: 44 Posts: 1,852	I think the fact that fblit works with P96 was pure luck as the two shouldnt be used together as both will be patching os blitting functions.

02 October 2010, 13:43	#8
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	As mentioned above, FBlit and FText are not required for graphics cards on the Amiga and should always be disabled, so ignore all those options. They basically allow the CPU to take over blitter operations to speed up Workbench and allow more free chipram. A graphics card does all this for you out of the box. ClassicWB LITE has FBlit disabled by default, which is why I didn't initially suggest it. Thanks for the feedback about the force chunky option. Check out BlazeWCP - perhaps that has something to do with it and/or Smartwin. I think there are enable/disable options under settings in the LITE too.

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