Vampire 500 v2+ Dual-Monitor question

[drwhy]

Hi !

I´m using a Dual-Monitor setup on my Amiga 500.
DELL: VGA, indieECS (PAL-Mode)
ACER: HDMI, Vampire500v2+ Picasso96 (vampire.gfx)

I know to prevent the ACER-Monitor going to sleep, while a
program is running in PAL-Mode on the DELL-Monitor, I have to
set up "DEVS:Monitors/vampire.gfx - Icon/information/DisplayChain=No".
This works like it should and the Workbench is Visible on the ACER-Monitor
while running ASMOne for example.

OK.

but now:

Is it possible to do the same for my DELL-Monitor with PAL-Mode ?
Because for reading & comparing source code, it would be more
comfortable to have both screens up at the same time. Currently the
DELL-Monitor goes Black when i press Amiga+m to switch the
Mouse-Focus back to the Acer-Monitor (WorkBenchScreen).

I have tried to set it up the PAL-Mode with DisplayChain=No,
but this does not seem to work.

anyone knows a solution for this, or is it simply not possible ?

greetz

[drwhy]

No one here who‘s knowing a answer ??

[Mr-Z]

From the readme:

- NoSwitch=Yes/No
Default is No.

The driver allows to power off the monitor that lost focus,
when switching from Native video and Graphic card video.

Note:
Requires also to set the ToolType "DisplayChain=Yes".

Yes => The monitor that lost focus is NOT powered off.
No => The monitor that lost focus is powered off.

[drwhy]

... hmm ...

thank you for answering, but this does not work !

first: what readme ?!? I have no one in DEVS/Monitors
(also searched super72.lha & HighGFX40_6.lha)

second: do I have to write both commands in TOOL-Types for my
PAL-Mode ? (DisplayChain=Yes & NoSwitch=No)
I´ve tried different combinations but does not work for me !

thank you

[flype]

The 'Readme' is actually the 'Tooltypes' text file in the SAGADriver.v1.2.lha arhive.

http://www.apollo-accelerators.com/w...latest_drivers

Generally i use those tooltypes :



This allow dual monitor display.

Supported Tooltypes :

-----------------------------------------------------------
VampireGFX.card 

Supported ToolTypes in 
SYS:Devs:Monitors/vampiregfx.info
-----------------------------------------------------------

- BigSprite=Yes/No
  Default is No.

  When using Software mouse sprite, you can double its size
  by setting this option to 'Yes'.
  
  Yes => The Software sprite is doubled.
  No  => The Software sprite is NOT doubled.


- BoardType=vampiregfx

  This should be defined as this!


- NoAMMX=Yes/No
  Default is No.
  
  This option requires the 'NoBlitter=No' ToolType. 
  When the BLITTER mode is in use, you can ask the driver 
  to use 68K driven routines or AMMX driven routines.
  
  Yes => The BLITTER wont use AC68080/AMMX.
  No  => The BLITTER will use AC68080/AMMX.


- NoBlitter=Yes/No
  Default to No.
  
  The driver embeds own optimized drawing operations.
  To use them, set this option to 'No'.

  Yes => Drawing operations are handled by the P96 default CPU routines.
  No  => Drawing operations are handled by the VampireGFX driver itself.


- NoDPMS=Yes/No
  Default is No.
  
  The driver handles DPMS signals (STANDBY, SUSPEND, POWEROFF).
  To enable this feature, set this option to 'Yes', and
  install for example 'DPMSManager.lha', by Stefan Robl, hosted 
  on Aminet.
  
  Yes => The DPMS signals are NOT handled.
  No  => The DPMS signals are handled.


- NoSwitch=Yes/No
  Default is No.

  The driver allows to power off the monitor that lost focus,
  when switching from Native video and Graphic card video.
  
  Note:
  Requires also to set the ToolType "DisplayChain=Yes".
  
  Yes => The monitor that lost focus is NOT powered off.
  No  => The monitor that lost focus is powered off.


- SettingFile=SYS:Devs/Picasso96Settings

  This should be defined as this!
  Can points to any other valid Picasso96Settings file.

- SoftSprite=Yes/No
  Default is Yes (since version 1.12).

  SAGA-core embeds a Hardware sprite interface for the mouse.
  Using hardware sprite offers more fluent mouse movements,
  no mouse flickering at all, and also less CPU usage.
  
  Yes => The Hardware sprite is NOT used.
  No  => The Hardware sprite is used.


- VideoMemSize=1M/2M/3M/4M/5M/6M/7M/8M
  Default is 8M.
  
  The video memory size used by the driver can be configured
  with this ToolType. This video memory is borrowed from the
  Vampire board FastRAM. As a consequence, you might wants
  save unused memory, depending which maximum resolution you 
  intend to use.
  
  For example :
  1M = Up to ~  640 x  400 x 32-bit.
  2M = Up to ~  800 x  600 x 32-bit.
  4M = Up to ~ 1280 x  720 x 32-bit.
  8M = Up to ~ 1920 x 1080 x 32-bit.


- OverClock=Yes/No
  Default is No.
  
  This option forbids/allows to define Clock values >= 50.00 MHz, 
  from the 'Picasso96Mode' tool. Use this feature with caution.
  
  Yes => Clock: 20.26 MHz up to 74.72 MHz
  No  => Clock: 20.26 MHz up to 49.94 MHz


- Scanlines=Yes/No
  Default is No.

  This option enable/disable the SAGA SCANLINES hardware mode, for
  the low resolution RTG screenmodes (eg. 320x200, 320x240, ...)
  
  Yes => LowRes screenmodes will use hardware SCANLINES.
  No  => LowRes screenmodes wont use hardware SCANLINES.

[flype]

Hmm, i have read your question 3 times, now i understand what you mean. I have checked, either from vampiregfx tooltypes or PAL tooltypes or the PVS tool, and indeed it does not work. I do not know if it is possible. I will have to make some tests. Maybe a limitation of P96 or something else.

[drwhy]

ok, thank you anyway ...
i will continue my research for this at the weekend.

hope there is a solution for this.

[kolla]

It should also be possible to have the MacOS desktop use both display outputs at once when running Shapeshifter.

(I used to run MacOS with 3 outputs on my A3000 - CVPPC, CV64 and monochrome on the RGB)

[drwhy]

yes it is ...
i´ve noticed this in shapeshifter a few days ago too ...
which means it works in shapeshifter but not (like is should)
in ApolloOS!

[Cego]

is there any solution to this yet? RGB out will go black when I switch back to P96...