@thread

Since we are getting different results regarding failure of mode promotion from user to user, let's rule this out:
@sundown in irc mentioned he is using a TFT monitor.
I am using a CRT.

@Painter & @DWolfman (who have also successfully mode promoted VistaPro3.0)
What monitor are you using? (just so we can rule this out)

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

I'm using a Samsung SyncMaster 730b TFT monitor. I have an AmigaoneXE with 512 mb ram and all the mobo fixes (usb, etc).
Oh yes the first try at your settings for screen prefs did not work for me. I had to delete the Vistapro screen prefs reboot and then enter them again and it worked. I supect i did something wrong. Also it worked even with the vistapro prefs in S: i have sincve removed them.

painter

Last edited by painter on 24-Jan-2007 at 01:56 AM.

@number6

No help from that 3rd example either...

Nothing special in startup-sequences..

And no i don't have those promotion tools running same time or,
mode active in screens prefs same time with other promoters....

BUAAAAH!

_________________
Asus Maximus VII Ranger, i7-4790K@4.6, HyperX DDR3@1866, MSI GTX980, 120GB ssd, 1T, 2T hdd.

@number6

I downloaded NewMode and tried that.

The NewMode method works too, it is just the OS4 Screens method that for some reason seems not to want to work.

Bill.

@BillE


I have tried creating an entry in Screens with no user-startup and no WBStartup, in other words a very clean system and still had no luck. I just cannot create a Screens entry that works using the methods already mentioned.

I have found another way of getting Screens to promote VP however !

To do this I ran ModePro and VP runs. Once I had done that I ran the Screens Prefs. I then clicked Insert Open Screen and this created an entry called "Custom:VistaPro 3.0", and pre-filled in some details already.

The mode said something like Radeon 16bit 640x480 so I changed this and selected one of the Fake Native modes. I set the cycle to Always and Saved the settings.

I rebooted and lauched Vista Pro and it worked, Screens this time had promoted it without me having to run ModePro

ModePro still seems better though as that lets me render in more screen modes. Using Screens VP defaults to render in Multiscan mode but it can be changed to others. However, it does not seem to support 256 colour or HAM modes. ModePro could do 256 colour screens and the NewMode method even seemed to manage HAM.

Getting Vista to run without relying on any third party tools is at least a step in the right direction.


Bill.

@BillE

Good. You're getting "similar" results to mine now. However:

Quote:

However, it does not seem to support 256 colour or HAM modes. ModePro could do 256 colour screens and the NewMode method even seemed to manage HAM.

From my prior instructions for "modepro":
Quote:

(1)Under "program name" enter the exact name of your VistaPro program (2)In the center panel cycle "promotion" to "screenmode" and choose a "P96:0:FAKENATIVE:640x480" mode. (3)In the checkboxes underneath check "Force Planar". (4)Click "use" or "save" (5)Run VistaPro Interesting note: I just changed to "P96:0:FAKENATIVE:640x512 HAM Interlaced" Now under the "GRMODES" menu I can check "DBLPAL" "Hires" "No Flicker" "Interlace" and "HAM-8". This effectively gives a HAM-8 rendered landscape. No question that better control is achieved with modepro as regards the "render" screen.

Note the last part, selecting a HAM screen, NOT a standard fakenative.
This is what allows HAM8 rendering through the "modepro" method.

Have fun with your fully functional VistaPro!

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

> No question that better control is achieved with modepro as regards
> the "render" screen.

I missed that bit first time

Not that the render screen matters too much as you can save the image as a 24 bit IFF file that looks fine no matter how awful it looks on the render screen.

Quote:

Have fun with your fully functional VistaPro!

I am doing already, and I have managed to dig out the manual!


Bill.

PS.
Any idea why this thread even though getting new replies does not appear on the AWN front page ? I keep having to delve for it in the forums, under OS4 Software. Surely using VP must be more interesting reading than all the usual lack of hardware rants !

@BillE

Quote:

Not that the render screen matters too much as you can save the image as a 24 bit IFF file that looks fine no matter how awful it looks on the render screen.

Yes, but you have to admit it makes for a great preview compared to 256 color, and @scabit seemed to be looking for better output. Hopefully now he has it. (assuming he got VistaPro promoted without error)

Quote:

I am doing already, and I have managed to dig out the manual!

Heh! Yeah. It's an interest easily revived at this point. Especially when the render time under JIT is faster by a factor of 20-30 times over E-UAE.
btw-If you check the separate manual for scripting, you'll see why the file I spoke about is dangerous (vistapro.prefs). It would be perfectly ok to have a startup with for example some button settings in place. But IF you entered a video mode, I assure you, you would be back to errors again. This due to the fighting between modepro vs the video mode you might set in visapro.prefs.

I would still like to see some responses from others to see if any of our methods for promoting VistaPro have worked yet for them. Honestly, it is the key to getting "other" old apps up and running on final.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@BillE

Quote:

To do this I ran ModePro and VP runs. Once I had done that I ran the Screens Prefs. I then clicked Insert Open Screen and this created an entry called "Custom:VistaPro 3.0", and pre-filled in some details already. The mode said something like Radeon 16bit 640x480 so I changed this and selected one of the Fake Native modes. I set the cycle to Always and Saved the settings.

No help from that either.....

_________________
Asus Maximus VII Ranger, i7-4790K@4.6, HyperX DDR3@1866, MSI GTX980, 120GB ssd, 1T, 2T hdd.

@Jape

One last thing for you to try. 1st line of startup-sequence:
C:SetPatch QUIET ADDCHIPRAM=4

Why "4"?
Well...I was rendering 1280x1024 and changed the render size to 1600x1200, and I saw the "oh no" message. (cannot open screen)
When I changed this to "4" from my previous "2" VistaPro happily accepted the render size I entered of 1600x1200.
This seems to be necessary under the "modepro" method of mode promotion I outlined earlier in the thread.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@BillE

It seems that promoting with "modepro" and choosing a HAM8 screen, as I stated in one of my previous posts makes for a fine preview screen.
The main screen will, of course be in 32 colors, but you can get an almost "ham8 fringing free" screen by choosing the following settings in "GRMode":
"Hires" "SuperHires" "Ham" "Ham8" "Interlace" and "Super72"
Under "width" "height" for overscan choose 896x640.
Be sure the numbers in the checkboxes above for "image size" and "display size" also show 896x640.
When you click render, you will indeed get a HAM8 896x640 render with little to no Ham fringing.
You can check that this is really an 896x640 screen by using "screengrab", while leaving the rendered screen open. It will confirm this.
"Scout" also confirms this open screen of 896x640.
Switching back to a render screen of "Hires" "Ham" "Ham8" "Interlace" "PAL" will give you a 640x512 Ham8 render screen, and the Ham "fringing" will be more noticeable.

#6

Last edited by number6 on 29-Jan-2007 at 11:21 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Quote:

Yes, but you have to admit it makes for a great preview compared to 256 color, and @scabit seemed to be looking for better output. Hopefully now he has it. (assuming he got VistaPro promoted without error)

No...never got it to work with a HAM8 scren yet. I've tried using NewMode to do this but when I set up a regular 32 color screen for the first vistapro screen and a ham8 screen for the second one (640x512 I think), Vistapro opens and shows me an "Error opening render screen" requester and immediately closes.

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Please try my directions in post #32 for promoting with "modepro".
Then use the settings from my last post for the large HAM8 render screen, once the program starts.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

No help from adding chipmem either....

_________________
Asus Maximus VII Ranger, i7-4790K@4.6, HyperX DDR3@1866, MSI GTX980, 120GB ssd, 1T, 2T hdd.