WinFellow crashes on Windows 7 with high resolutions

andreas · 24 July 2009, 23:31

Hi there,

any volunteers to retest?

Well I can utterly sense the remarks "What's the big idea? WinFellow on Win7?"; yet it's not about WinUAE bashing at all here (nor is it any silly "who's cooler" competition crap), but mere technical interest.

superturrican it was you who rekindled my interest on this because I weren't using WF for AGES.
Otherwise I would probably never have found out about the instability of WF on Win7...

To get the facts straight: I encountered a CRASH in 0.4.4 build 2 (latest).

I started off with a vanilla config folder.
Inserted Kickstart ROM, no other modifications except:

resolution 640x512
line mode: doubled

Everything works fine.

But once I try ANYTHING beyond that resolution, WinFellow will crash. (Even 640x576 will make it crash)

Can anybody of you guys reproduce this on his Win7 box?
This is really a very interesting issue. On Windows 2000 this worked fine even in 768x576.

TCD · 24 July 2009, 23:35

Sorry, but is there really a point on trying a program that wasn't updated for over two years on an OS that isn't even officially released yet?

PowerPie5000 · 24 July 2009, 23:37

I have not experienced this problem, I have not used winfellow in a long time and have just tried it with my Win 7 partition and it seemed ok with me

The system i am running it on uses an old Radeon 3870 GPU with Catalyst 9.6 drivers if that is any help? Also uses an Intel Core 2 Duo E6850 CPU. I have no problems with different resolutions and i also tested it with default Winfellow settings.

Maybe you should try changing your graphics drivers if any other versions are avialable for Win 7?

Edit: I also agree with CyberDruid

andreas · 24 July 2009, 23:39

I said it above: mere technical interest why it crashes on the new Windows.
(BTW this could also happen on Vista, which I don't have to hand, though)

Furthermore I'd appreciate it a lot if I'm not required to repeatedly explain myself henceforth, because I'd just like to know what might be causing this.

@PowerPie: come to think of it, yes it could *indeed* be a graphics driver issue.
Thanks for testing, by the way. So I should probably experiment a little with newer/older Detonator*) versions
(Nvidia FX5200 here; yeah still

)

The fact that the non-overscan resolution works might mean that WF finds the default resolutions, but not the more "exotic" ones

*) aka ForceWare

PowerPie5000 · 24 July 2009, 23:44

Quote:

Originally Posted by andreas

I said it above: mere technical interest why it crashes on the new Windows.
(BTW this could also happen on Vista, which I don't have to hand, though)

Furthermore I'd appreciate it a lot if I'm not required to repeatedly explain myself henceforth, because I'd just like to know what might be causing this.

@PowerPie: come to think of it, yes it could *indeed* be a graphics driver issue.
Thanks for testing, by the way. So I should probably experiment a little with newer/older Detonator versions
(Nvidia FX5200 here; yeah still

)

First of all i would check your graphics configs under Win 7 and adjust or change the drivers if necessary as it is a display related issue.

andreas · 24 July 2009, 23:49

"Check my graphics configs"? What do you mean by that exactly?

PowerPie5000 · 24 July 2009, 23:59

Quote:

Originally Posted by andreas

"Check my graphics configs"? What do you mean by that exactly?

Make sure your GPU has properly detected your display and all supported resolutions are availbale to windows, also check that all supported refresh rates are enabled and remove any resolutions and refresh modes that your display cannot handle - you can normally find this in your graphics driver panel.... this is just a suggestion and may not be the problem (are you getting a blank screen crash?) .

Edit: most GPU drivers will be quite buggy at the moment with Windows 7 and may work with some software and not others.

Shoonay · 25 July 2009, 00:02

@andre: is it asking/sending out a crash report for M$? if so all you can do now is wait a few months and they will fix it, i'm sure of that - they fixed my Space Hulk remake problems in Viśta after a few weeks

24 July 2009, 23:31	#1
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	WinFellow crashes on Windows 7 with high/overscan resolutions Hi there, any volunteers to retest? Well I can utterly sense the remarks "What's the big idea? WinFellow on Win7?"; yet it's not about WinUAE bashing at all here (nor is it any silly "who's cooler" competition crap), but mere technical interest. superturrican it was you who rekindled my interest on this because I weren't using WF for AGES. Otherwise I would probably never have found out about the instability of WF on Win7... To get the facts straight: I encountered a CRASH in 0.4.4 build 2 (latest). I started off with a vanilla config folder. Inserted Kickstart ROM, no other modifications except: resolution 640x512 line mode: doubled Everything works fine. But once I try ANYTHING beyond that resolution, WinFellow will crash. (Even 640x576 will make it crash) Can anybody of you guys reproduce this on his Win7 box? This is really a very interesting issue. On Windows 2000 this worked fine even in 768x576. Last edited by andreas; 24 July 2009 at 23:45.

24 July 2009, 23:39	#4
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	I said it above: mere technical interest why it crashes on the new Windows. (BTW this could also happen on Vista, which I don't have to hand, though) Furthermore I'd appreciate it a lot if I'm not required to repeatedly explain myself henceforth, because I'd just like to know what might be causing this. @PowerPie: come to think of it, yes it could indeed be a graphics driver issue. Thanks for testing, by the way. So I should probably experiment a little with newer/older Detonator) versions (Nvidia FX5200 here; yeah still ) The fact that the non-overscan resolution works might mean that WF finds the default resolutions, but not the more "exotic" ones ) aka ForceWare Last edited by andreas; 24 July 2009 at 23:46.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Screen resolutions	dtr1001	support.FS-UAE	2	22 August 2013 00:36
Winfellow on Windows Vista	rodi	support.WinFellow	83	13 November 2011 20:12
can you load WHD zip images (windows) on winuae/winfellow	carmel_andrews	support.WinUAE	1	03 December 2008 11:18
help with Mechforce screen resolutions	Unregistered	support.WinFellow	5	10 June 2005 22:11
Workbench 3.0 monitor resolutions	thinlega	request.Apps	6	23 October 2004 12:59

24 July 2009, 23:35	#2
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 31,615	Sorry, but is there really a point on trying a program that wasn't updated for over two years on an OS that isn't even officially released yet?

24 July 2009, 23:37	#3
PowerPie5000 Miggy Ate My Hamster! Join Date: Nov 2008 Location: Lancashire, UK Posts: 1,566	I have not experienced this problem, I have not used winfellow in a long time and have just tried it with my Win 7 partition and it seemed ok with me The system i am running it on uses an old Radeon 3870 GPU with Catalyst 9.6 drivers if that is any help? Also uses an Intel Core 2 Duo E6850 CPU. I have no problems with different resolutions and i also tested it with default Winfellow settings. Maybe you should try changing your graphics drivers if any other versions are avialable for Win 7? Edit: I also agree with CyberDruid

24 July 2009, 23:49	#6
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	"Check my graphics configs"? What do you mean by that exactly?

25 July 2009, 00:02	#8
Shoonay Global Caturator Join Date: Aug 2004 Location: Porando Age: 43 Posts: 6,107	@andre: is it asking/sending out a crash report for M$? if so all you can do now is wait a few months and they will fix it, i'm sure of that - they fixed my Space Hulk remake problems in Viśta after a few weeks

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