View Single Post
Old 05 April 2012, 22:29   #10
FrodeSolheim
FS-UAE Developer

FrodeSolheim's Avatar
 
Join Date: Dec 2011
Location: Førde, Norway
Age: 40
Posts: 3,750
Quote:
Originally Posted by PHabermehl View Post
Excellent international cooperation :-)
Indeed -I tested a bit more with your startup sequence. With BEAMCON0 hack disabled, it is still a bit weird - lots of bits in BEAMCON0 is set (12, 11, 9, 8, 7, 3) when starting sysinfo, existing UAE code logs a warning, and autoscaling custom limits return 0, 0, 0, 0, so the result is that the entire display with overscan etc is shown (but no graphic corruption).

Code:
L: Display Size: 724x444 Offset: 2x6
L: First: 29 Last: 312 MinV: 28 MaxV: 251 Min: 26
L: >   2   6 724 444
L: BEAMCON0 v = 7048 (0x041b88)
L:  - bit 12
L:  - bit 11
L:  - bit 9
L:  - bit 8
L:  - bit 7
L:  - bit 3
L: warning: 1B88 written to BEAMCON0 PC=00F8F6D4
L: BEAMCON0 0020 -> 1b88 PC=%08x
L: BEAMCON0=1B88 VTOTAL=023D  HTOTAL=0081
L:   HSSTOP=0015 HBSTRT=0001  HBSTOP=0021
L:   VSSTOP=000E VBSTRT=023E  VBSTOP=0016
L:   HSSTRT=000B VSSTRT=0007 HCENTER=004B
L: NTSC mode dblscan V=47.4564Hz H=27240.0000Hz (130x574+1) IDX=11 (NTSC)
L: >   0   0   0   0
By trial and error, it seems that an important factor is the following line in your Startup-Sequence:
Code:
C:FastIPrefs nowait nogauge nofullwb
Without this line, the system behaves "normally"...
FrodeSolheim is offline  
 
Page generated in 0.04261 seconds with 11 queries