Overview Features Instructions Performance Forum Downloads Products Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
VISIT APOLLO IRC CHANNEL



All TopicsNewsPerformanceGamesDemosApolloVampireCoffinReleasesLogin
Documentation about the Vampire hardware

Two Error: Missing Librarys and Picasso Context

John Fante

Posts 22
17 Aug 2019 16:40


I am new - and very happy - Vampire A600 owner. Very nice hardware :-)

CoffinOS runs very nicely so my setup is working and stable.

I have, however, also installed 3.1.4 on another CF card and have here two issues. They maybe down to me being a Vampire noob but here goes:

1) Missing CPU librarys
I map my A600 3.1.4 ROM via VampireMap314. The mapping works fine - at least as I can see. However when I updated to 3.1.4.1 the system began to complain about missing 68040 and 68060 librarys and would not boot. I fixed it by disabling CPU check in the startup-sequence. It boots fine now but not a very nice hack. Is this normal?

2) Picasso96: Could not create graphics board context for 'uaegfx'
I followed the instructions to get RTG and I have it. But I get the above error on boot. First it also complained about 'ueagfx' in Devs not being excutable but I fixed that. RTG works but the error messes up the icon position so I would like to fix it. As far as I can google it is an error relating to Picasso being started twice or something like that. Any suggestions?

Thank you in advance!


Gunnar von Boehn
(Apollo Team Member)
Posts 4185
17 Aug 2019 17:14


Benny Damsgaard wrote:

  1) Missing CPU librarys
  I map my A600 3.1.4 ROM via VampireMap314. The mapping works fine - at least as I can see. However when I updated to 3.1.4.1 the system began to complain about missing 68040 and 68060 librarys and would not boot. I fixed it by disabling CPU check in the startup-sequence. It boots fine now but not a very nice hack. Is this normal?
 

This sounds like a bug in OS 3.1.4
68080 needs no libs.
And OS 3.1.4 should not look for them.




Vojin Vidanovic

Posts 1429
17 Aug 2019 17:56


Gold 2.12rc2+ cores fixes 040 prob by simulating it in Kickstart. But prob is not to Vamp but to OS 3.1.4 and should be adressed in its future updates (please register and write here
EXTERNAL LINK 
essentially, hype and boys were aware of vamp, but did not implement 080 cpu I'd. So it's seen as 040 but does not need 040 libs. If you can continue after warn, do so or disable check as you did
 
  You would also need to register at Hyperions website and download update to OS 3.1.4.1 :) 
 
    Os 3.1.4 would also like to have latest p96 which is now buyable I Believe. (2.4.2+)
  EXTERNAL LINK 
   
    One in all, why not using Coffin
   


Stefano Briccolani

Posts 335
17 Aug 2019 19:44


In the thread on 3.1.4 we talked about the cpu library. If you disable cpu check the system works but cpu caches and fpu are missing (not only on vampires, even running in winuae have the same issue and need a cpu library). To solve for now you can put in libs the old commodore 040 library (rename it in 68040.library)
EXTERNAL LINK  Henrik Richter is aware of the problem and that will be solved with a new vampiremaprom tool, because vampire doesn't need a cpu library. Stay away from mulibs package! Bad thing is that BestWb will install this one. Gulliver is informed and will remove mulibs from bestwb on next release

For picasso96 refer to
http://wiki.icomp.de/wiki/P96#Operation_under_UAE


John Fante

Posts 22
18 Aug 2019 08:50


Thank you for all the good advice! Much appreciated!
 
  I solved the library problem with an old 68040 library from the 3.1 install disk. The version from Phase5 did not work with me. The original from 3.1 works fine.
 
  I have bought the Picasso96 software from iComp (version 2.4.2). It should be 3.1.4 compatible and it is a good way to support Jens and Co.
 
  So far updating did not solve the problem but I will dig a little deeper.
 
Thank you! Looking forward to 2.12 gold :-)


Stefano Briccolani

Posts 335
18 Aug 2019 09:03


In the phase5 archive there was the old commodore 68040 library. But then if you used the one of 3.1 is the same.
For ic picasso96 i had no problems..you have to install with one of graphics board presented in the list (es picassoiv). Then you go to devs/monitors, change the name of icon to "uaegfx" and change the first tooltype to "uaegfx", then proceed with SAGA install.


John Fante

Posts 22
18 Aug 2019 13:54


Stefano Briccolani wrote:

In the phase5 archive there was the old commodore 68040 library. But then if you used the one of 3.1 is the same.
  For ic picasso96 i had no problems..you have to install with one of graphics board presented in the list (es picassoiv). Then you go to devs/monitors, change the name of icon to "uaegfx" and change the first tooltype to "uaegfx", then proceed with SAGA install.

Strange. I did a complete 3.1.4.1 reinstall with the new Picasso96 2.4.2 just to be sure (the last was an update over a 2.1 version) but the problem is the same.

Are you running 2.12RC2?

When I use VampireMap314 it is with a A600 3.1.4 rom. In fact it is a A500 rom (that is the one supplied in the archive from Hyperion) but that should be supported according to the wiki.


Stefano Briccolani

Posts 335
18 Aug 2019 15:50


I use the 1200 rom, as suggested.


John Fante

Posts 22
18 Aug 2019 15:57


Stefano Briccolani wrote:

  I use the 1200 rom, as suggested.
 

 
  Ok. Maybe the issue is there. I will see if the "problem" remain after 2.12.
 
  Thank you for your help!


Stefano Briccolani

Posts 335
19 Aug 2019 07:14


Have you delete uaegfx (or picassoiv) monitor file from devs:monitor after Saga install?


John Fante

Posts 22
19 Aug 2019 17:26


No. I have PAL, uaegfx and vampiregfx in Devs/Monitors.
 
  Should I delete uaegfx?


Mr-Z EdgeOfPanic

Posts 181
19 Aug 2019 18:27


Benny Damsgaard wrote:

No. I have PAL, uaegfx and vampiregfx in Devs/Monitors.
 
  Should I delete uaegfx?

Move UAE gfx to storage/monitors may come in handy if for some reason you want to boot your config in UAE.


John Fante

Posts 22
19 Aug 2019 19:55


Cool. I moved ueagfx to storage and that took care of the "Picasso96: Could not create graphics board context for 'uaegfx'" error :-)
   
Maybe removing the ueagfx driver should be explained with the install SAGA instructions. It is not very obvious for a GFX noob ...
   
Now I only have one error left. I get an "Intuition is attempting to reset the Workbench screen. Please close windows, except drawers". It sits a couple of seconds on the standard pal output and then switches to HD ... Can not see any other error.
 
Can this be because of me updating the intuition library?
 
I am now using the A1200 3.1.4 rom with VampireMap (removed my a600 physical rom). 
 
I then copied (and renamed) the latest intuition library (from 3.1.4.1) to LIBS and made the following change in the startup-sequence (as it says in the FAQ):
 
  If Exists C:LoadModule
      C:Version exec.library version 46 >NIL:
      If Warn
        C:LoadModule ROMUPDATE
      Else
        C:LoadModule LIBS:intuition.library
      EndIf
  EndIf
 
Is that the way to do it on Vampire with VampireMap?


Henryk Richter
(Apollo Team Member)
Posts 105
20 Aug 2019 08:46


I've updated the MapROM guide in the Wiki with a HowTo on the Intuition V45 topic. See here EXTERNAL LINK 



John Fante

Posts 22
20 Aug 2019 18:17


Henryk Richter wrote:

I've updated the MapROM guide in the Wiki with a HowTo on the Intuition V45 topic. See here EXTERNAL LINK 
 

Thanks for the guide. Creating a new A1200 kickstart was no problem. Thank you! Saved me a reset :-D

I found out what caused the intuition error. I have Roadshow installed and that gives an intuition error with the Vampire on start up when it is started up in the startup-sequence.

I have internet so I think it is a speed issue of some sort. The Vampire is simply too fast on boot. I remember I some years ago had a similar problem on a CS68060 and fixed it with a wait command in the startup-sequence to give Roadshow time to connect. At the moment I have just commented roadshow out and connect manually.

One final question: How can I get the OS to go straight to HD output? Now it opens the RGB screen (pal low res) and then switches to HD a second after. It is not a big thing but a bit annoying since it messes up my icons.

Thank you for all your help! The Vampire is a fantastic piece of kit :-)


Henryk Richter
(Apollo Team Member)
Posts 105
21 Aug 2019 07:44


The most likely reason that you get a PAL screen first is something in your s:startup-sequence or s:user-startup scripts printing out text on the Console. In that case, the console will open on the default PAL screen. Only after the Workbench is loaded, the console will close and the OS can change the Screen mode of the workbench.

You need to find out which command prints out text instead of staying silent.


Vojin Vidanovic

Posts 1429
21 Aug 2019 10:44


One could always silent the outpout by using famous NIL: outpout
 
  example RUN >NIL: <command>.

General Roadshow introduction
EXTERNAL LINK 
Roadshow forum
EXTERNAL LINK


John Fante

Posts 22
21 Aug 2019 17:17


Henryk Richter wrote:

The most likely reason that you get a PAL screen first is something in your s:startup-sequence or s:user-startup scripts printing out text on the Console. In that case, the console will open on the default PAL screen. Only after the Workbench is loaded, the console will close and the OS can change the Screen mode of the workbench.
 
  You need to find out which command prints out text instead of staying silent.

You are right :-)

It was the console output from the version command before VampireMap that caused the problem. As Vojin Vidanovic proposed adding a >NIL to both Roadshow and the version command in VampireMap did the trick

Now the version commands goes:

Version >NIL: expansion.library 45

Thank you both Henryk and Vojin.

posts 18