29 August 2020, 23:39 | #1 |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
DSI (Data Storage Interrupt) Crashes... Often!
Good evening,
Newbie here, I tried searching but my lack of knowledge may have rendered my search fairly useless... I have the newest Stable WinUAE installed, running an A4000 with AmigaOS 4.1 FE Update 1 I purchased from Hyperion... Everything seems to look and run fairly well, however when trying to launch applications, many, many applications, I get a DSI error... For example I attempt to run SysInfo (to get some benchmarks) and the DSI error pops up, I click "Kill" the screen flashes and SysInfo opens, however most of the fields are blank and I can't click on another, I also can't close it, it's pretty frozen, I have to shutdown WinUAE... If anyone has any ideas, or if there's more information I can provide let me know please... I've been working on this project for a couple of weeks now and I'm getting close... Solving 1 problem at a time haha... Thanks!! |
29 August 2020, 23:51 | #2 |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
Here's my config:
config_description=UAE default configuration config_hardware=true config_host=true config_version=4.4.0 config_hardware_path= config_host_path= config_all_path= comp_catchdetect=true win32.rom_path=./ win32.floppy_path=./ win32.hardfile_path=./ ; host-specific win32.middle_mouse=true win32.rtg_match_depth=false win32.rtg_scale_aspect_ratio=16:9 win32.soundcard=4 win32.soundcardname=Primary Sound Driver win32.cpu_idle=150 win32.expansion_gui_page=ide_mb ; common use_gui=yes use_debugger=false kickstart_rom_file=C:\Users\Public\Documents\Amiga Files\Shared\rom\amiga-os-310-a4000.rom kickstart_rom_file_id=D6BAE334,KS ROM v3.1 (A4000) kickstart_ext_rom_file= cpuboard_rom_file=C:\Users\Public\Documents\Amiga Files\Shared\rom\cyberstormppc.rom ide_mb_rom_file=:ENABLED a2065_rom_file=:ENABLED flash_file= cart_file= rtc_file= kickshifter=false floppy_volume=33 floppy0= floppy0type=1 floppy1= floppy1type=1 floppy2= floppy3= nr_floppies=2 floppy_speed=0 cd_speed=100 parallel_on_demand=false serial_on_demand=false serial_hardware_ctsrts=true serial_direct=false scsi=false uaeserial=false sana2=false sound_output=interrupts sound_channels=stereo sound_stereo_separation=7 sound_stereo_mixing_delay=0 sound_max_buff=16384 sound_frequency=44100 sound_interpol=anti sound_filter=emulated sound_filter_type=enhanced sound_volume=0 sound_volume_paula=0 sound_volume_cd=0 sound_volume_ahi=0 sound_volume_midi=0 sound_volume_genlock=0 sound_auto=true sound_cdaudio=false sound_stereo_swap_paula=false sound_stereo_swap_ahi=false comp_trustbyte=indirect comp_trustword=indirect comp_trustlong=indirect comp_trustnaddr=indirect comp_nf=true comp_constjump=true comp_flushmode=soft compfpu=true comp_catchdetect=true cachesize=0 joyport0=mouse joyport0autofire=none joyportfriendlyname0=Windows mouse joyportname0=WINMOUSE1 joyport1=kbd1 joyport1autofire=none bsdsocket_emu=false a2065=slirp synchronize_clock=false maprom=0x0 uaeboard=full+indirect parallel_postscript_emulation=false parallel_postscript_detection=false ghostscript_parameters= parallel_autoflush=5 gfx_display=0 gfx_display_rtg=0 gfx_framerate=1 gfx_width=1920 gfx_height=1080 gfx_top_windowed=0 gfx_left_windowed=31 gfx_width_windowed=1920 gfx_height_windowed=1080 gfx_width_fullscreen=800 gfx_height_fullscreen=600 gfx_refreshrate=0 gfx_autoresolution=0 gfx_autoresolution_vga=true gfx_backbuffers=2 gfx_backbuffers_rtg=1 gfx_vsync=false gfx_vsyncmode=normal gfx_vsync_picasso=false gfx_vsyncmode_picasso=normal gfx_lores=false gfx_resolution=hires gfx_lores_mode=normal gfx_flickerfixer=false gfx_linemode=double2 gfx_fullscreen_amiga=false gfx_fullscreen_picasso=true gfx_center_horizontal=none gfx_center_vertical=none gfx_colour_mode=32bit gfx_blacker_than_black=false gfx_api=direct3d11 gfx_api_options=hardware immediate_blits=false waiting_blits=automatic ntsc=false genlock=false chipset=aga chipset_refreshrate=49.920410 collision_level=playfields chipset_compatible=A4000 ksmirror_e0=false fatgary=0 ramsey=15 z3_autoconfig=true unmapped_address_space=zero ide=a4000 fastmem_size=8 debugmem_start=0x0 debugmem_size=0 mem25bit_size=0 a3000mem_size=8 mbresmem_size=128 z3mem_size=0 z3mem_start=0x40000000 bogomem_size=0 cpuboard_type=CyberStormPPC cpuboardmem1_size=128 gfxcard_hardware_vblank=false gfxcard_hardware_sprite=false gfxcard_multithread=false gfxcard_size=128 gfxcard_type=ZorroIII chipmem_size=4 cpu_speed=max cpu_throttle=0.0 cpu_type=68040 cpu_model=68040 fpu_model=68040 ppc_model=automatic ppc_cpu_idle=disabled cpu_compatible=false cpu_24bit_addressing=false cpu_data_cache=false ppc_implementation=auto cpu_cycle_exact=false cpu_memory_cycle_exact=false blitter_cycle_exact=false cycle_exact=false fpu_strict=false rtg_nocustom=true rtg_modes=0x212 debug_mem=false log_illegal_mem=false kbd_lang=us uaehf0=cd0,ro,:,0,0,0,2048,0,,scsi1_cpuboard,SCSI1 hardfile2=rw,DH0:C:\Users\Public\Documents\Amiga Files\WinUAE\a4000-os41.vhd,0,0,0,512,0,,scsi0_cpuboard,SCSI1 uaehf1=hdf,rw,DH0:"C:\\Users\\Public\\Documents\\Amiga Files\\WinUAE\\a4000-os41.vhd",0,0,0,512,0,,scsi0_cpuboard,SCSI1 filesystem2=rw,Shared:Shared:C:\Users\Public\Documents\Amiga Files\WinUAE\Shared,-128 uaehf2=dir,rw,Shared:Shared:C:\Users\Public\Documents\Amiga Files\WinUAE\Shared,-128 input.config=0 input.joymouse_speed_analog=100 input.joymouse_speed_digital=10 input.joymouse_deadzone=33 input.joystick_deadzone=33 input.analog_joystick_multiplier=15 input.analog_joystick_offset=-1 input.mouse_speed=100 input.autofire_speed=600 input.autoswitch=1 input.1.joystick.0.empty=true input.1.joystick.1.empty=true input.1.joystick.2.empty=true input.1.joystick.3.empty=true input.1.joystick.4.empty=true input.1.joystick.5.empty=true input.1.joystick.6.empty=true input.1.joystick.7.empty=true input.1.joystick.8.empty=true input.1.joystick.9.empty=true input.1.joystick.10.empty=true input.1.joystick.11.empty=true input.1.joystick.12.empty=true input.1.joystick.13.empty=true input.1.joystick.14.empty=true input.1.joystick.15.empty=true input.1.joystick.16.empty=true input.1.joystick.17.empty=true input.1.joystick.18.empty=true input.1.joystick.19.empty=true input.1.mouse.0.friendlyname=Windows mouse input.1.mouse.0.name=WINMOUSE1 input.1.mouse.0.empty=true input.1.mouse.1.friendlyname=HID-compliant mouse input.1.mouse.1.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#7&1e0cc0df&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} input.1.mouse.1.empty=true input.1.mouse.2.empty=true input.1.mouse.3.empty=true input.1.mouse.4.empty=true input.1.mouse.5.empty=true input.1.mouse.6.empty=true input.1.mouse.7.empty=true input.1.mouse.8.empty=true input.1.mouse.9.empty=true input.1.mouse.10.empty=true input.1.mouse.11.empty=true input.1.mouse.12.empty=true input.1.mouse.13.empty=true input.1.mouse.14.empty=true input.1.mouse.15.empty=true input.1.mouse.16.empty=true input.1.mouse.17.empty=true input.1.mouse.18.empty=true input.1.mouse.19.empty=true input.1.keyboard.0.friendlyname=WinUAE keyboard input.1.keyboard.0.name=NULLKEYBOARD input.1.keyboard.0.empty=false input.1.keyboard.0.disabled=false input.1.keyboard.1.friendlyname=USB Receiver input.1.keyboard.1.name=\\?\HID#VID_046D&PID_C52B&MI_00#7&35d04d24&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.1.keyboard.1.empty=true input.1.keyboard.2.friendlyname=Dell KB216 Wired Keyboard input.1.keyboard.2.name=\\?\HID#VID_413C&PID_2113&MI_00#7&34686ebe&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.1.keyboard.2.empty=true input.1.keyboard.3.empty=true input.1.keyboard.4.empty=true input.1.keyboard.5.empty=true input.1.keyboard.6.empty=true input.1.keyboard.7.empty=true input.1.keyboard.8.empty=true input.1.keyboard.9.empty=true input.1.keyboard.10.empty=true input.1.keyboard.11.empty=true input.1.keyboard.12.empty=true input.1.keyboard.13.empty=true input.1.keyboard.14.empty=true input.1.keyboard.15.empty=true input.1.keyboard.16.empty=true input.1.keyboard.17.empty=true input.1.keyboard.18.empty=true input.1.keyboard.19.empty=true input.1.internal.0.friendlyname=Internal events input.1.internal.0.name=INTERNALEVENTS1 input.1.internal.0.empty=true input.1.internal.0.disabled=false input.2.joystick.0.empty=true input.2.joystick.1.empty=true input.2.joystick.2.empty=true input.2.joystick.3.empty=true input.2.joystick.4.empty=true input.2.joystick.5.empty=true input.2.joystick.6.empty=true input.2.joystick.7.empty=true input.2.joystick.8.empty=true input.2.joystick.9.empty=true input.2.joystick.10.empty=true input.2.joystick.11.empty=true input.2.joystick.12.empty=true input.2.joystick.13.empty=true input.2.joystick.14.empty=true input.2.joystick.15.empty=true input.2.joystick.16.empty=true input.2.joystick.17.empty=true input.2.joystick.18.empty=true input.2.joystick.19.empty=true input.2.mouse.0.friendlyname=Windows mouse input.2.mouse.0.name=WINMOUSE1 input.2.mouse.0.empty=true input.2.mouse.1.friendlyname=HID-compliant mouse input.2.mouse.1.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#7&1e0cc0df&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} input.2.mouse.1.empty=true input.2.mouse.2.empty=true input.2.mouse.3.empty=true input.2.mouse.4.empty=true input.2.mouse.5.empty=true input.2.mouse.6.empty=true input.2.mouse.7.empty=true input.2.mouse.8.empty=true input.2.mouse.9.empty=true input.2.mouse.10.empty=true input.2.mouse.11.empty=true input.2.mouse.12.empty=true input.2.mouse.13.empty=true input.2.mouse.14.empty=true input.2.mouse.15.empty=true input.2.mouse.16.empty=true input.2.mouse.17.empty=true input.2.mouse.18.empty=true input.2.mouse.19.empty=true input.2.keyboard.0.friendlyname=WinUAE keyboard input.2.keyboard.0.name=NULLKEYBOARD input.2.keyboard.0.empty=false input.2.keyboard.0.disabled=false input.2.keyboard.1.friendlyname=USB Receiver input.2.keyboard.1.name=\\?\HID#VID_046D&PID_C52B&MI_00#7&35d04d24&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.2.keyboard.1.empty=true input.2.keyboard.2.friendlyname=Dell KB216 Wired Keyboard input.2.keyboard.2.name=\\?\HID#VID_413C&PID_2113&MI_00#7&34686ebe&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.2.keyboard.2.empty=true input.2.keyboard.3.empty=true input.2.keyboard.4.empty=true input.2.keyboard.5.empty=true input.2.keyboard.6.empty=true input.2.keyboard.7.empty=true input.2.keyboard.8.empty=true input.2.keyboard.9.empty=true input.2.keyboard.10.empty=true input.2.keyboard.11.empty=true input.2.keyboard.12.empty=true input.2.keyboard.13.empty=true input.2.keyboard.14.empty=true input.2.keyboard.15.empty=true input.2.keyboard.16.empty=true input.2.keyboard.17.empty=true input.2.keyboard.18.empty=true input.2.keyboard.19.empty=true input.2.internal.0.friendlyname=Internal events input.2.internal.0.name=INTERNALEVENTS1 input.2.internal.0.empty=true input.3.joystick.0.empty=true input.3.joystick.1.empty=true input.3.joystick.2.empty=true input.3.joystick.3.empty=true input.3.joystick.4.empty=true input.3.joystick.5.empty=true input.3.joystick.6.empty=true input.3.joystick.7.empty=true input.3.joystick.8.empty=true input.3.joystick.9.empty=true input.3.joystick.10.empty=true input.3.joystick.11.empty=true input.3.joystick.12.empty=true input.3.joystick.13.empty=true input.3.joystick.14.empty=true input.3.joystick.15.empty=true input.3.joystick.16.empty=true input.3.joystick.17.empty=true input.3.joystick.18.empty=true input.3.joystick.19.empty=true input.3.mouse.0.friendlyname=Windows mouse input.3.mouse.0.name=WINMOUSE1 input.3.mouse.0.empty=true input.3.mouse.1.friendlyname=HID-compliant mouse input.3.mouse.1.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#7&1e0cc0df&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} input.3.mouse.1.empty=true input.3.mouse.2.empty=true input.3.mouse.3.empty=true input.3.mouse.4.empty=true input.3.mouse.5.empty=true input.3.mouse.6.empty=true input.3.mouse.7.empty=true input.3.mouse.8.empty=true input.3.mouse.9.empty=true input.3.mouse.10.empty=true input.3.mouse.11.empty=true input.3.mouse.12.empty=true input.3.mouse.13.empty=true input.3.mouse.14.empty=true input.3.mouse.15.empty=true input.3.mouse.16.empty=true input.3.mouse.17.empty=true input.3.mouse.18.empty=true input.3.mouse.19.empty=true input.3.keyboard.0.friendlyname=WinUAE keyboard input.3.keyboard.0.name=NULLKEYBOARD input.3.keyboard.0.empty=false input.3.keyboard.0.disabled=false input.3.keyboard.1.friendlyname=USB Receiver input.3.keyboard.1.name=\\?\HID#VID_046D&PID_C52B&MI_00#7&35d04d24&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.3.keyboard.1.empty=true input.3.keyboard.2.friendlyname=Dell KB216 Wired Keyboard input.3.keyboard.2.name=\\?\HID#VID_413C&PID_2113&MI_00#7&34686ebe&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} input.3.keyboard.2.empty=true input.3.keyboard.3.empty=true input.3.keyboard.4.empty=true input.3.keyboard.5.empty=true input.3.keyboard.6.empty=true input.3.keyboard.7.empty=true input.3.keyboard.8.empty=true input.3.keyboard.9.empty=true input.3.keyboard.10.empty=true input.3.keyboard.11.empty=true input.3.keyboard.12.empty=true input.3.keyboard.13.empty=true input.3.keyboard.14.empty=true input.3.keyboard.15.empty=true input.3.keyboard.16.empty=true input.3.keyboard.17.empty=true input.3.keyboard.18.empty=true input.3.keyboard.19.empty=true input.3.internal.0.friendlyname=Internal events input.3.internal.0.name=INTERNALEVENTS1 input.3.internal.0.empty=true input.4.mouse.0.friendlyname=Windows mouse input.4.mouse.0.name=WINMOUSE1 input.4.mouse.0.custom=true input.4.keyboard.0.friendlyname=WinUAE keyboard input.4.keyboard.0.name=NULLKEYBOARD input.4.keyboard.0.custom=true |
30 August 2020, 12:32 | #3 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,505
|
AFAIK many low level benchmarks simply won't (and can't) work under OS4.
|
30 August 2020, 16:18 | #4 |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
|
30 August 2020, 22:12 | #5 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@Coreyoli
sysinfo is an application for 68k it is not for ppc it will hardly work. There are "benchmark" programs but you will need to organnize your OS 4.1FE first but they are relative. You should try the applications directly and see if they are slow or fast, they are the best tests you can do. |
30 August 2020, 22:53 | #6 | |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
Quote:
|
|
31 August 2020, 12:55 | #7 |
Registered User
Join Date: Aug 2014
Location: Zagreb / Croatia
Posts: 302
|
Benchmarks are not that precise and depends what you want to do. There are disk, 2D graphic, 3D graphic, text, math, ... benchmarks.
For Amiga OS 4.x maybe to try to search for benchmarks here: http://os4depot.net/index.php |
01 September 2020, 00:46 | #8 | |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
Quote:
|
|
01 September 2020, 20:23 | #9 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,505
|
Benchmarks usually don't tell anything useful when running on emulated systems. Some parts of system might be impossibly fast and some really slow.
|
03 September 2020, 17:52 | #10 |
Registered User
Join Date: Aug 2016
Location: Earth
Posts: 883
|
Completely agree with Toni. SysInfo is helpful with real hardware Amiga 4000. Though I don't run it often, it can be useful for some stuff..and checking hardware. Emulation, yeah..ppptthh...don't bother. Use your eyes (brain). Notice speeds that way.
I get DSI hits if I run E-UAE ( http://os4depot.net/?function=showfi...uae-amigfx.lha ), Directory Opus 4 or 5..at times. Choose to Ignore the hit and let the emulator finish. With the file managers...the current task, then reset machine/emulation. Usually DOpus doesn't cause it... There are bugs in OS 4.1.1, and the programs. Definitely with E-UAE's copying a file FROM E-UAE emulation to host Amiga. I haven't noticed any data damage from it..when I choose to ignore. Again, it happens with real hardware and emulation (WinUAE) since you're new to this. At first I was resetting the Amiga or emulation every time, but then did some research into it and personal checks. Not any data corruption. I sort of look at it as a false positive such as with many viri checkers for Windows. Just finish task..and reset machine. I switched to Ryzen 3600 and I can see a lot of speed differences vs my older 2010 Desktop. So, that's the best benchmark. |
03 September 2020, 18:33 | #11 | |
Registered User
Join Date: Aug 2020
Location: NY, USA
Posts: 18
|
Quote:
Thanks for the info!! |
|
03 September 2020, 19:10 | #12 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@AC/DC HACKER!
Hi, I'm glad you got the 3600 do you have time to do some tests with the 4.1FE? Odyssey alone would be enough, it is currently the heaviest application in the system. It would be enough for me to see its speed I would be happy with this Thank you. |
03 September 2020, 19:32 | #13 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@Coreyoli
in most cases the DSI are due to the instability created by the composite in the GUI If you reach a good configuration, you configure the applications well then you have to activate the "composite" in the GUI prefs and eventually lighten the transparencies. DSI will disappear completely even with multiple applications used simultaneously. Also when you have configured the sound card the sb128 sets it to 32 channels etc. The sound card if not configured well leads to many crashes. The whole system will no longer crash if set this way. separate note: the system must be configured well starting from the first aiss mixer packages etc. etc. In practice it is the composite that gives stability to the system. |
03 September 2020, 20:28 | #14 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@Coreyoli
Here you can see multiple applications used with GUI settings with active composite. Then in reality it is always me who want more and I exaggerate :-) here is Photogenics E-UAE amiAMP and other applications that work at the same time without slowing down, I can keep opening windows etc. The system is not affected in the least. this since I activated the composite in the GUI [ Show youtube player ] |
05 September 2020, 05:35 | #15 | |
Registered User
Join Date: Aug 2016
Location: Earth
Posts: 883
|
Quote:
Someone in the States!! YAAAY!! HAHA! Your message is a bit vague, but so far I'm following you. |
|
05 September 2020, 06:04 | #16 | |
Registered User
Join Date: Aug 2016
Location: Earth
Posts: 883
|
Quote:
You don't need to thank me profusely. Once is enough or not at all. Smiling. Here's an answer.. Odyssey isn't something I checked much yet.. For OS 3.5, 3.4.1+... Shogo is able to play in what seems realtime, vs my previous "PC" machine. Which beats my Picasso 4 with real A4K...with WinUAE (4.4.0). Make it clear, with current WinUAE Shogo plays at 3D speeds with Picasso 4 active without 3D graphics. That's impressive. Much more checking to do.. |
|
05 September 2020, 11:01 | #17 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@AC/DC HACKER!
I went beyond my expectations for the 4.1FE now the system is able to do everything that 3.xx does plus a better navigation with the youtube browser see for example twichtv etc. My goal was to replicate a 3.xx system with the use of 4.1FE which I never had. And simply a passion I said to myself why not use the 4.1FE as I did with the 3.xx. The system is stable and works when I have time I add applications. The path has often been full of contradictions but because it is the result of experiments and continuous tests. A real shame not being able to exchange experiences with those who use winuae with this operating system. Ok I can't use assembly programs and the like but this is not the purpose for which I use 4.1FE. Time has passed for this kind of applications. The 3D part of the operating system is not interesting to me. all this remains in the sphere of the amiga world because only those who have lived its operating system understand the speech of a project that was lost in its time. I'd like to see how fast Odyssey works with the Ryzen 3600 The 3.xx is there it works well I have no comments to make. But the 4.1FE is a great satisfaction to be able to use it. When you have time I will be happy to see some of your tests. |
05 September 2020, 14:56 | #18 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@AC/DC HACKER!
Odyssey currently works fine but resolutions are variable probably due to video compression 720x480 800x600 1024x768 with 32bit screen I have to go back and try to improve this. But I believe that we can not go further, if not precisely with a new latest generation processor. FFPlay currently works well online at 360p and 480p as well It would be interesting to see a 720p Shogo I have to put it back and try it with the new patch released and my new winuae configuration. I'm sorry to put videos that point to youtube but I have no other way to show you the tests I performed. [ Show youtube player ] |
06 September 2020, 03:53 | #19 | |
Registered User
Join Date: Aug 2016
Location: Earth
Posts: 883
|
Quote:
I've changed the GUI/Composite settings and it's not helping with not having DSI hits. I tried a mix of transparency and....still the same. I'm using Picasso 4 mostly. I'll check with UAGfx soon. I've also tried with my AmigaOne X5000 and...hasn't helped. It's storage related, so FileSystem is mostly probably why. I haven't looked deeply into it but..that makes more sense. |
|
06 September 2020, 10:16 | #20 |
Registered User
Join Date: Sep 2016
Location: italy
Posts: 1,480
|
@AC/DC HACKER!
Is the DSI error generic and random or does it happen with some specific applications? Here I did a test that is boring to do with a mobile phone because it is difficult to carry out in practical terms. So I used the video capture program and then for compatibility reasons I put winuae in full-window. So the performance is different but still good. Also games like quake 1 and 2 conflict with the full-window and I didn't put them. But you can still see the stability of the system with the active composite. I am attaching the uaegfx driver, the one I currently use. you can later check if there are any differences with what you use in terms of performance. The driver is for use with the following table 8 * bit all all A8R8G8B8 In the test there are also my settings of the composite and how I configured it. Here you can see how the system works without any DSI problem even with multiple applications open, the video is new and not static you see the use of the system in action moment by moment, I hope it is useful. :-) [ Show youtube player ] |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Blitter interrupt during VERTB interrupt | phx | Coders. Asm / Hardware | 38 | 01 October 2021 19:54 |
How to pass data to interrupt handler with VBCC? | strim | Coders. System | 3 | 18 January 2016 14:38 |
Interrupt 7 | BigT | support.WinUAE | 2 | 07 September 2013 22:25 |
OSCAR / TROLLS for DSI | plasmatron | Retrogaming General Discussion | 0 | 05 September 2009 18:31 |
The easiest way to transfer data between Amiga and PC using a mass storage | Another World | support.Other | 15 | 07 January 2009 04:51 |
|
|