Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
Don't Panic. Please wash hands.
-
With a P96 workbench screen, please open attached "DoggieBackground.lace" picture in Multiview and then use Multiview's menu item to open it up in a separate screen. I get the following MuForce hit "doglace.txt" and graphic corruption.
I'm not 100% certain if coming from P96 but seems like it could be since if I do the same from a workbench screen that is set to a native NTSC screen mode there is no issue.
doglace.txt
DoggieBackground.zip
-
Jens -- I just sent private message on my order number. Also, copying what Thor just mentioned here in this thread:
http://eab.abime.net/showthread.php?t=105576&page=20
"...I have something waiting for you. I don't think this is in the card file, it is rather that the library did not turn on the flicker fixer if switched away to a board outside the display chain.
-
This is P96 3.2.4 on AmigaOS3.2.1.with 3.2 ROMs.
CyberStormPPC/060 Accelerator from Phase5
Icomp X-surf and RapidRoad
Memory: 2MB chip, 16MB Motherboard fast, and 128MB on PPC/060
I'm using the onboard IDE (CD-ROM + 1 HD) and Phase5 SCSI (1 HD). At the moment I don't have anything hooked up to the on-board SCSI. It should have Buster rev 11. The A4000T is a 5/7/96 manufacturing date (think this was QuickPak manufactured?)
-
I've been seen some screen switching issues as noted in EAB forum: http://eab.abime.net/showthread.php?t=105576&page=20. I had some issue with CVisionPPC and PIV (as well as CVisionPPC and ZZ9000) but to remove any complications of the CVisoinPPC or ZZ9000, I did a comparison by only installing a CVision64 and a PIV card in my A4000T (all other graphic cards removed -- no CVIsionPPC installed and no ZZ9000). DISPLAYCHAIN=YES for PIV and DISPLAYCHAIN=NO for CV64. Then I did these experiments. This is not hitting exactly the same kind of case for the other combos but I do see issue in 1 case:
Note that WB=workbench screen
1) WB CV64 screen --> create PIV RTG screen. Good swapping back and forth between screens
2) WB PIV screen --> create CV64 RTG screen. Good swapping back and forth between screens
3) WB CV64 screen --> create Hires Laced. 1st time swap, flickerfixer on PIV output good. On 2nd and subsequent times, no flickerfixer output on PIV (black). If I again create PIV RTG, and then do Hires laced, it recovers first time and I see flickerfixer output. Subsequent times no flickerfixer output.
4) WB CV64 screen, keep a 2nd PIV RTG screen open, then open up a 3rd HiresLaced screen. I can swap back and forth between them and all is okay.
As mentioned in EAB forum Thor has an idea and can give a beta for me to check but need approval of my purchase.
-
This was a beta before Jan. 27th. I didn't know that the final 3.02 was released. I will have to give it a try. Thanks.
-
This is fixed now in beta that Thor sent me -- no more crash.
-
To close on this -- fixed now in the beta version that Thor sent me.
-
I tried the same beta for this issue and still see same:
rtg.library 42.570 01/07/21
3dlabspermdida2.chip 42.31 01/06/21
CVisionPPC.card 42.54 12/15/20
-
Thanks, I tried the beta version:
rtg.library 42.570 01/07/21
3dlabspermdida2.chip 42.31 01/06/21
CVisionPPC.card 42.54 12/15/20
I still get 8000 0004 software failure. I'm not sure if Thor's change was in that beta or not as the email I got from him was on 01/08/21 and the versions above are before that time.
-
Thanks -- I sent a private message with order ID.
-
CVisionPPC driver crashes if CSPPC boot options "c" or "p" are applied during boot (Software Failure 8000 0004). I contacted Thor privately and Thor has a workaround for this issue. I can test it out if possible.
-
When doing a Loadmodule for the graphics.library, it is causing P96 to force a fake mode. I privately sent mail to Thor and he has a fix to hopefully detect ram loaded graphic libraries.
-
Thanks Jurassicc. I had re-installed 4.1FE from scratch yesterday, with update 1 and then update 2 and still saw issue after installing poseidon fresh. Doing the blacklist for rapidroadxs100usb.devicesolved it! Thanks a lot -- working now.
-
I didn't do anything to remove I was trying to use SaferPatches from Thor to view the patches but could not determine anything. I don't have SaferPatches installed anymore when I was doing the FAKENATIVEMODES tooltype on/off checking.
The board I'm using is a phase5 CSPPC (not DCE) with the latest flash version from Ralph (not the official release one). Bootmenu and bootshell screens show on RTG but I don't think these are the patcches that P96 is looking for as FAKENATIVEMODES is enabled in Workbench. But if there is a way to find out what P5 patches I have, please let me know.
-
Thanks Jens,
Sorry for the confusion -- I was checking more on this. From what I'm seeing now, I *don't* have the P5 patches because normal NTSC modes are coming up with FAKENATIVEMODES =NO. When FAKENATIVEMODES =YES, fake modes do come up and then Overscan has issue. So FAKENATIVEMODES is definitely active. For the Overscan issue, I'm thinking now this might be more of a OS issue when overscan prefs sees 0 items in its screen list.
-
Seeing hit when running overscan prefs (when only having CVisionPPC and NTSC in monitor drivers) which I think is related to P5 patch and having CVisionPPC driver loaded that forces the fake native mode. Overscan list comes up empty in the GUI.
When not putting any monitor drivers into DEVS:Monitors, no issue and overscan prefs has 1 item in the list (NTSC). Some default one gets setup.
Also, if I put like PAL in monitor drivers with CVisionPPC and NTSC, then overscan prefs is okay as well.
-
-
This should say GET_DESCRIPTOR --> len 8.
-
I'm not able to get the RapidRoad to work with Poseidon as I'm getting this error.
9:09 PM| 0-poseidon.library: New hardware DEVS:USBHardware/rapidroadxs100usb.device/0 added (RapidRoadUSB Host Controller).
9:09 PM| 5-poseidon.library: GET_DESCRIPTOR (len failed: packet overflow (7)
9:09 PM| 10-poseidon.library: GET_DESCRIPTOR (len failed: packet overflow (7)
9:09 PM| 20-poseidon.library: Device enumeration failed, sorry.
9:09 PM| 20-poseidon.library: Root hub enumeration failed. Blame your hardware driver programmer.
-
Thanks Jen for the updates! SceneryAnimator not working well with the FakeNativeMode and so need to try the patch removal but not sure what tool that is.