@thread

I still get questions about this in irc, so one last time with all the info in one place:

Two versions are included for VistaPro 3.05. We'll use the .881 version and absolutely NO need to disable JIT, despite older posts indicating that.
I've renamed the .881 to "VistaPro3". File size is 598404.
Stack size in the icon is 50000 and there are no tooltypes.
There should be NO prefs file from a classic install as this could produce unknown results. Check both Program directory and s: to be sure.

ModePro - http://aminet.net/search?query=modepro

(01)Install ModePro. Currently I have it in WBstartup (OS4.0), but you can put it somewhere else. In that case you have to start the program PRIOR to running any program that requires its use. I strongly suggest just keeping it in WBstartup (OS4.0), so you don't have to even think about it. I have not seen any file conflicts in the 5 years I've used it.
For OS4.1 add ModePro to SYS:Prefs/WBstartup, if you don't keep a WBstartup drawer.

(02)Double click ModePro. Toggle the upper left gadget to say "Screen Names". Make an entry in the dialog box at bottom "Add" for the screen name. "VistaPro 3.0" (Please note there is a space between the "o" and the "3".
(03)Toggle the middle gadget of ModePro (Promotion) to show "screenmode".
(04)Use the selector to choose "P96-0:FAKENATIVE: 640 x 480.

*Added to avoid getting requestors. I needed to delete all mode promotions except VistaPro to determine this one was required to avoid a requestor.

(05)Click on "Add" to add another "Screen Name". Make an entry in the dialog box at bottom for the screen name "[left caret]No Name[right caret]".
(06)Toggle the middle gadget of ModePro (Promotion) to show "screenmode".
(07)Use the selector to choose "P96-0:FAKENATIVE: 640 x 512 HAM Interlaced.
(08)Save your prefs

Prefs/GUI

(01)Go to "controls" and checkmark the box "Planar screens on RTG"
(02)Save your prefs

You should be able to start VistaPro V3.x now by clicking on the icon.


To render in HAM8 from the VistaPro V3.x menus:

(1)Click right mouse button on menu item at top "GrModes"
(2)Select "Graphics Panel"
(3)Click and make active each of the following:
"Hires"
"SuperHires"
"Ham"
"Ham8"
"Interlace"
"Super72"
For overscan width and height click on 896x640.
Be sure the numbers in the checkboxes above for "image size" and "display size" also show 896x640.
(4)Click "ok" to exit Graphics Panel

From now on, When you click render, you should get a HAM8 896x640 screen with little to no visible Ham fringing.


I realize the directions are quite specific regarding program version (3.05) and settings, but I'd like to hear about any version V3.x. There are a few.
Please post any feedback, including your h/w, graphics card, monitor, so we can get this working for everyone and possibly on ALL V3.x versions. (there are many, there's even a V3.1, heh)


#6

Last edited by number6 on 13-Aug-2012 at 11:24 PM.
Last edited by number6 on 13-Aug-2012 at 10:29 PM.
Last edited by number6 on 13-Aug-2012 at 09:54 PM.
Last edited by number6 on 13-Aug-2012 at 06:27 PM.
Last edited by number6 on 13-Aug-2012 at 06:20 PM.
Last edited by number6 on 13-Aug-2012 at 06:11 PM.

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

@number6

Thanks for this tutorial number6. I will try it out on my X1000 as soon as the Olympics closing ceremony is over (meaning that the televising of it is over, here on the West Coast of the USA). I had planned on spending some time installing software on my X1000 this afternoon/evening anyway, so this just gives me one more program to try setting up so it will run.

Thanks again!

_________________
Amiga! The computer that inspired so many, to accomplish so much, but has ended up in the hands of . . . . . . . . . .

@number6

Thanks, 6! This is my kind of thread.

One behavior worth noting as it has existed on my VistaPro installations on three OS4 machines. If I run VistaPro and then immediately quit my computer will lock up tight as a drum within seconds. But if I quit the program after first doing some actual work (even just loading a DEM file), then I can exit cleanly without locking up.

Probably a coincidence, but the same thing occurs for me with ADPro. Launch, quit, lockup vs launch, work, quit no problem.

Last edited by mbrantley on 13-Aug-2012 at 05:12 PM.
Last edited by mbrantley on 12-Aug-2012 at 09:26 PM.

_________________

@number6

Great! VISTA in the past was listed as non working!

_________________
OS 3.x AROS and MOS supporter, fi di good, nothing fi di unprofessionalism. Learn it harder way!
SinclairQL and WII U lover :D
YT http://www.youtube.com/user/rasvoja

@vox

Quote:

Great! VISTA in the past was listed as non working!

erm...why?

I've had it working since 2006.

#6

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

@number6

You are right
http://www.intuitionbase.com/ossoftware.php?category=3&letter=v

Sometimes when workarounds are needed to get Classic software running, people get nervous :)

_________________
OS 3.x AROS and MOS supporter, fi di good, nothing fi di unprofessionalism. Learn it harder way!
SinclairQL and WII U lover :D
YT http://www.youtube.com/user/rasvoja

@amigadave

Monitor, graphics card, and perhaps more may determine your success rate.
I appreciate all feedback regardless in case there is something that can be added here.

@vox

I'm afraid the Intuitionbase material is very much out of date.

#6

Last edited by number6 on 12-Aug-2012 at 10:45 PM.

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

@number6

Awesome. I'm going to try to get vista installed and give it a go. Its one of the few programs from classic days that is still very useful and it doesnt run on morphos afaik.

@number6

Quote:

I'm afraid the Intuitionbase material is very much out of date.

Could we have some joint effort to bring it up to date?
Its one of first OS4 websites and yes, its in original A1 era, frozen.

_________________
OS 3.x AROS and MOS supporter, fi di good, nothing fi di unprofessionalism. Learn it harder way!
SinclairQL and WII U lover :D
YT http://www.youtube.com/user/rasvoja

@vox

Quote:

Could we have some joint effort to bring it up to date?

Ryu owns the site, ask him.

_________________
Hate tends to make you look stupid...

@number6

Why are old 68K apps like ModePreo that hack the system still needed when OS4 has this functionality built in? Is the OS4 screen promoter crap by comparison?

These days there should be no need to run ModePro than there is to run WBStartup+ on an OS4.1 machine.

I always got annoyed at people who ran ModePro on their Amigas who had an RTG card. Whenever I tried to run a program this annnoying requester would come up. I didn't know how the owner could put up with it!

OS4 must still be in sad state if 68k hacks must still be used. Which is pretty bad as old 68K hacks should not be used in a PPC OS4 Amiga!

Last edited by Hypex on 14-Aug-2012 at 03:22 PM.
Last edited by Hypex on 14-Aug-2012 at 03:21 PM.

@Hypex

Quote:

Why are old 68K apps like ModePeo that hack the system still needed when OS4 has this functionality built in? Is the OS4 screen promoter crap by comparison?

No. You've been in the other threads I've written, so you know I gave instructions using OS4.x prefs/screens, as well as using another fine promoter called Newmode.

ModePro simply offers more features and more control. Can you select HAM or Halfbrite modes in prefs/screens for example?
It's easy enough to start ModePro without harming your system, just to view the options and compare.

Quote:

I always got annoyed at people who ran ModePro on their Amigas who had an RTG card. Whenever I tried to run a program this annnoying requester would come up. I didn't know the owner could put up with it!

In the above instructions (VistaPro) you won't see a requester. But for those programs where a new screen is detected, the requester is just giving you the opportunity of defining how to handle it.

Quote:

Which is pretty bad as old 68K hacks should not be used in a PPC OS4 Amiga!

And yet I can run these programs I promote without affecting my PPC programs and conversely some of those who say they test with only PPC OS4.x can not. Go figure, eh?

Seems like an apt spot to repost the link to using Lightwave on AmigaOS4.x too:

My YouTube video about running LightWave on my X1000

#6

Last edited by number6 on 13-Aug-2012 at 03:45 PM.

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

@Hypex

Quote:

I always got annoyed at people who ran ModePro on their Amigas who had an RTG card. Whenever I tried to run a program this annnoying requester would come up. I didn't know the owner could put up with it!

Why would you be annoyed at anyone for running something on their computer?

I don't have these requesters popping up and I've used ModePro for years, first on my A1200 to force a couple of programs in Productivity mode and later on my A4000 with RTG card. Whether a requester pops up when a new screen is called is something that can be configured and it must not be the default behavior since I don't see 'em.

OS4 has screen promoting that's pretty good, but ModePro is downright handy too. And I run a lot of 68K code through my PPC processors -- lots of favorite old utilities, applications and games, as well as some new stuff written for 68K. Truth is, I'd starve on a pure PPC diet.

_________________

@mbrantley

Quote:

One behavior worth noting as it has existed on my VistaPro installations on three OS4 machines. If I run VistaPro and then immediately quit my computer will lock up tight as a drum within seconds. But if I quit the program after first doing some actualy work in (even just loading a DEM file), then I can exit cleanly without locking up.

I can confirm this behavior on my setup.
I also happen to know this is not related to VistaPro or use of Modepro.

Added a lot more to post #1 to be very specific, right down to filesize, tooltypes, stack, prefs, etc. Also added another defined screen to eliminate the requestor possibility.
Also updated thread title and reference within thread to the official V3.05 version from Virtual Reality Laboratories, as there seem to be some other V3.x versions floating around, which may behave differently.

#6

Last edited by number6 on 13-Aug-2012 at 09:56 PM.
Last edited by number6 on 13-Aug-2012 at 06:38 PM.

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

@number6

So, no one has a boxed V3.05 to test the tutorial and report?
I think any V3.x version will produce the same results actually, with exception of V3.1x.

btw-Makepath and Terraform can be promoted just fine as well.

#6

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

@number6

Quote:

(04)Use the selector to choose "P96-0:FAKENATIVE: 640 x 480.

Which P96-0:FAKENATIVE: 640 x 480?

I have 6 different screen modes all listed with this exact same name in Modepro. How do I figure out which one to use?

When I start VistaPro 3.0 (the fpu version with the filesize you specify) all I get is a requester that says "unable to open view screen" with "Oh no!" buttons that lock up the AmigaOne when selected.

Thanks!

Scott

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

I get 13 640x480 mode choices on the x1000.

All my fake modes:

ModeID Wdth Hght Dpth ScreenMode

$000F9024 640 480 8 BootVGA:Productivity
$00000000 640 480 8 P96-0:FAKENATIVE:HighRes
$00008000 640 480 8 P96-0:FAKENATIVE:HighRes
$00008020 640 480 8 P96-0:FAKENATIVE:HighRes
$00000004 640 480 8 P96-0:FAKENATIVE:HighRes
$00008004 640 480 8 P96-0:FAKENATIVE:HighRes
$00008024 640 480 8 P96-0:FAKENATIVE:HighRes
$00021000 640 480 8 P96-0:FAKENATIVE:HighRes
$00029000 640 480 8 P96-0:FAKENATIVE:HighRes
$00029020 640 480 8 P96-0:FAKENATIVE:HighRes
$00021004 640 480 8 P96-0:FAKENATIVE:HighRes
$00029004 640 480 8 P96-0:FAKENATIVE:HighRes
$00029024 640 480 8 P96-0:FAKENATIVE:HighRes
$00008400 640 256 8 P96-0:FAKENATIVE:HighRes DualPF
$00029400 640 256 8 P96-0:FAKENATIVE:HighRes DualPF
$00008404 640 512 8 P96-0:FAKENATIVE:HighRes DualPF Interlace
$00029404 640 512 8 P96-0:FAKENATIVE:HighRes DualPF Interlace
$00008440 640 256 8 P96-0:FAKENATIVE:HighRes DualPF2
$00029440 640 256 8 P96-0:FAKENATIVE:HighRes DualPF2
$00008444 640 512 8 P96-0:FAKENATIVE:HighRes DualPF2 Interlace
$00029444 640 512 8 P96-0:FAKENATIVE:HighRes DualPF2 Interlace
$00008080 640 256 6 P96-0:FAKENATIVE:HighRes EHB
$00029080 640 256 6 P96-0:FAKENATIVE:HighRes EHB
$00008084 640 512 6 P96-0:FAKENATIVE:HighRes EHB Interlace
$00029084 640 512 6 P96-0:FAKENATIVE:HighRes EHB Interlace
$00008800 640 256 8 P96-0:FAKENATIVE:HighRes HAM
$00029800 640 256 8 P96-0:FAKENATIVE:HighRes HAM
$00008808 640 128 8 P96-0:FAKENATIVE:HighRes HAM DblScan
$00029808 640 128 8 P96-0:FAKENATIVE:HighRes HAM DblScan
$00008804 640 512 8 P96-0:FAKENATIVE:HighRes HAM Interlace
$00029804 640 512 8 P96-0:FAKENATIVE:HighRes HAM Interlace
$00000008 320 128 8 P96-0:FAKENATIVE:LowRes DblScan
$00021008 320 128 8 P96-0:FAKENATIVE:LowRes DblScan
$00000400 320 256 8 P96-0:FAKENATIVE:LowRes DualPF
$00021400 320 256 8 P96-0:FAKENATIVE:LowRes DualPF
$00000404 320 512 8 P96-0:FAKENATIVE:LowRes DualPF Interlace
$00021404 320 512 8 P96-0:FAKENATIVE:LowRes DualPF Interlace
$00000440 320 256 8 P96-0:FAKENATIVE:LowRes DualPF2
$00021440 320 256 8 P96-0:FAKENATIVE:LowRes DualPF2
$00000444 320 512 8 P96-0:FAKENATIVE:LowRes DualPF2 Interlace
$00021444 320 512 8 P96-0:FAKENATIVE:LowRes DualPF2 Interlace
$00000080 320 256 6 P96-0:FAKENATIVE:LowRes EHB
$00021080 320 256 6 P96-0:FAKENATIVE:LowRes EHB
$00000088 320 128 6 P96-0:FAKENATIVE:LowRes EHB DblScan
$00021088 320 128 6 P96-0:FAKENATIVE:LowRes EHB DblScan
$00000084 320 512 6 P96-0:FAKENATIVE:LowRes EHB Interlace
$00021084 320 512 6 P96-0:FAKENATIVE:LowRes EHB Interlace
$00000800 320 256 8 P96-0:FAKENATIVE:LowRes HAM
$00021800 320 256 8 P96-0:FAKENATIVE:LowRes HAM
$00000808 320 128 8 P96-0:FAKENATIVE:LowRes HAM DblScan
$00021808 320 128 8 P96-0:FAKENATIVE:LowRes HAM DblScan
$00000804 320 512 8 P96-0:FAKENATIVE:LowRes HAM Interlace
$00021804 320 512 8 P96-0:FAKENATIVE:LowRes HAM Interlace
$00008420 1280 256 8 P96-0:FAKENATIVE:SuperHighRes DualPF
$00029420 1280 256 8 P96-0:FAKENATIVE:SuperHighRes DualPF
$00008424 1280 512 8 P96-0:FAKENATIVE:SuperHighRes DualPF Interlace
$00029424 1280 512 8 P96-0:FAKENATIVE:SuperHighRes DualPF Interlace
$00008460 1280 256 8 P96-0:FAKENATIVE:SuperHighRes DualPF2
$00029460 1280 256 8 P96-0:FAKENATIVE:SuperHighRes DualPF2
$00008464 1280 512 8 P96-0:FAKENATIVE:SuperHighRes DualPF2 Interlace
$00029464 1280 512 8 P96-0:FAKENATIVE:SuperHighRes DualPF2 Interlace
$000080A0 1280 256 6 P96-0:FAKENATIVE:SuperHighRes EHB
$000290A0 1280 256 6 P96-0:FAKENATIVE:SuperHighRes EHB
$000080A4 1280 512 6 P96-0:FAKENATIVE:SuperHighRes EHB Interlace
$000290A4 1280 512 6 P96-0:FAKENATIVE:SuperHighRes EHB Interlace
$00008820 1280 256 8 P96-0:FAKENATIVE:SuperHighRes HAM
$00029820 1280 256 8 P96-0:FAKENATIVE:SuperHighRes HAM
$00008824 1280 512 8 P96-0:FAKENATIVE:SuperHighRes HAM Interlace
$00029824 1280 512 8 P96-0:FAKENATIVE:SuperHighRes HAM Interlace

_________________
Hate tends to make you look stupid...

@scabit

Quote:

I have 6 different screen modes all listed with this exact same name in Modepro. How do I figure out which one to use?

I'll check that tonight, but the first one should do.

Quote:

When I start VistaPro 3.0 (the fpu version with the filesize you specify) all I get is a requester that says "unable to open view screen" with "Oh no!" buttons that lock up the AmigaOne when selected.

I've seen that every time if the 2nd screen is not defined.
Check to see you performed steps 5-7 please, and let me know.

@sundown

Thanks for the list. That will help.

#6

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

Yeah, I've also always seen a lot of duplicated fakenative screen modes and usually pick the first one. Never been a problem though I've wondered why the duplicates are there.

_________________

@number6

Quote:

ModePro simply offers more features and more control. Can you select HAM or Halfbrite modes in prefs/screens for example?

No you can't. But not because of Screens. But because of that stupid P96 VGA only Amiga mode emulation AFAIK.

Perhpas I should submit an enhancement request?

In any case why would you want to choose those modes? Halfbrite would have to be converted into a 256 CLUT anyway and then any palette changes emulated as Halfbrite. And as for HAM, well you need a hi colour mode at least, but then it should also be a CLUT mode which you won't get on RTG.

Since even the latest HD Radeon can't do these "primitive" Amiga modes I could seee why it isn't supported. If they had some kind of raster interrupt or copper list on these VGA cards then it would have been possible, but I don't kniow if they support such "Advanced" features.

Quote:

Go figure, eh?

Hmm, well, all they would do is patch OpenScreen() and OpenScreenTags() in the 68K side. Yes, hack was a bit extreme.

Quote:

Lightwave on AmigaOS4.x too:

Excellent. People with a Lightwave CD will be interested in seeing that on OS4. Or the opposite.

Last edited by Hypex on 15-Aug-2012 at 03:16 PM.