|
---|
| | Daniel Sevo
Posts 299 01 May 2016 22:29
| Hello,question about WinUAE settings.. After updating the Vampire to latest official core + P96 + latest SAGA,I can no longer boot from the CF card. Pretty much every GFX setting I tried ends up with a black screen (except one setting with a pure A600, no RTG, not even 020 CPU). Can anyone with the latest Vampire drivers share their WinUAE settings? (I guess,, primarily the GFX settings). Anything else Im forgetting? Thanx
| |
| | John William
Posts 566 01 May 2016 23:53
| Is it possible you have driver conflicts?
| |
| | Daniel Sevo
Posts 299 02 May 2016 22:14
| John William wrote:
| Is it possible you have driver conflicts?
|
Anything is possible I guess. But I do get different error messges in WinUAE depending on what card I choose from the list under RTG board. Are there any recommended settings in WinUAE that are good to know about? Thanx
| |
| | John William
Posts 566 03 May 2016 00:13
| Daniel Sevo wrote:
| John William wrote:
| Is it possible you have driver conflicts? |
Anything is possible I guess. But I do get different error messges in WinUAE depending on what card I choose from the list under RTG board. Are there any recommended settings in WinUAE that are good to know about? Thanx |
Playing with WinUAE is irrelevant as it is simply playing with the hardware configuration. If there is anything that is driver related conflict, ss error conflict, or something that is software related WinUAE setting will not help you. I mean...the only setting that you could play with is the RTG part of it..as changing from 68060 to 68040 will not solve your problem. Changing audio from mono to stereo will not fix your problem. Configuring your PAL/NTSC setting is pointless. You see what I mean? However, if you have actually configured this to work Vampire and install all the SAGA drivers, put the file of SAGA in monitor accordingly, install the devices, etc...then chances are you have sealed your CF to be no longer WinUAE supported. You need to remove everything for Vampire in order for it to work in WinUAE.
| |
| | Daniel Sevo
Posts 299 03 May 2016 22:19
| John William wrote:
| Playing with WinUAE is irrelevant as it is simply playing with the hardware configuration. If there is anything that is driver related conflict, ss error conflict, or something that is software related WinUAE setting will not help you. I mean...the only setting that you could play with is the RTG part of it..as changing from 68060 to 68040 will not solve your problem. Changing audio from mono to stereo will not fix your problem. Configuring your PAL/NTSC setting is pointless. You see what I mean?
|
Maybe you misunderstood the part where I talk about changing CPU.. Obviously for RTG I'm trying to find the right settings in UAE's RTG Tab, but the list of RTG devices in WinUAE is long, and I was mostly wondering if we are supposed to chose a particular one to be compatible with P96 driver installed on the CF. John William wrote:
| However, if you have actually configured this to work Vampire and install all the SAGA drivers, put the file of SAGA in monitor accordingly, install the devices, etc...then chances are you have sealed your CF to be no longer WinUAE supported. You need to remove everything for Vampire in order for it to work in WinUAE.
|
The reason for mentioning the CPU changes in config is that I can actually get the A600 CF to boot into WinUAE even with all the SAGA and P96 stuff and screenmodes set to SAGA 16 bit...IF I change CPU to 68000 in WinUAE. Because then the Picasso drivers don't load as they require 68020+ and after some error messages, WB loads and I can use it.. (Although stuff like Dopus wont run so file transfer is a bit clumsier).
| |
| | Nixus Minimax
Posts 416 04 May 2016 10:52
| I'm not sure I understand you correctly but I'd be very surprised if WinUAE had replicated the Vampire RTG subsystem already.
| |
| | John William
Posts 566 04 May 2016 16:51
| Nixus Minimax wrote:
| I'm not sure I understand you correctly but I'd be very surprised if WinUAE had replicated the Vampire RTG subsystem already.
|
I hope not.
| |
| | Daniel Sevo
Posts 299 04 May 2016 22:58
| Short version; WinUAE no longer booted with the CF from the A600 with the SAGA and P96 driver. What can be done to resolve it? FYI, there was an answer to this problem in AEB forum: AUTOMATIC METHOD: This method requires VampireTool in C: You also rename Picasso96Settings to Picasso96Settings_SAGA. Both monitor files (SAGA and UAEGFX) can stay in Storage. From Startup-Sequence you run VampireTool to Detect Vampire or Not so now if detected you can copy SAGA from storage/monitors to devs/monitors. If not detected you can copy UAEGFX etc.
| |
|