Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
43 user(s) are online (32 user(s) are browsing Forums)

Members: 0
Guests: 43

more...

Headlines

Forum Index


Board index » All Posts (IamSONIC)




Re: Say or speech: in amigaos4?
Just popping in
Just popping in


@jap

Thank you!

Placing the file in DEVS:DOSDrivers and adding the tool type ACTIVATE=1 prevents "Say" from crashing.

Go to top


Re: Say or speech: in amigaos4?
Just popping in
Just popping in


@jap

Quote:

I can verify that the original Commodore narrator.device (version 37.7), speak-handler (version 37.4), translator.library (version 37.1), and SAY command (version 37.4) do work on AmigaOS 4.1 FE


Yes, the "Say" command works. I copied those files from a Workbench 2.05 Floppy Disk and have excactly the same versions as you have.

Quote:

The narrator device has a bug in closing the device which makes the SAY command (or any other program using the narrator device) to crash. However, the bug can be avoided by mounting the SPEAK device (which uses the narrator device) on system start-up. As long as the SPEAK device is mounted, the narrator device remains open and it won't crash.


I also copied the MountList file to DEVS:

SPEAK:     
    
Handler L:Speak-Handler
    Stacksize 
6000
    Priority 
5
    GlobVec 
= -1
#


and added "Mount SPEAK:" to the Startup-Sequence. The device is being opened on startup. However, "Say" crashes (..ramlib...) when closing.

How did you mounted the SPEAK: Device? Also using the MountList file? Which parameters?

Thx

Go to top


Re: 2023 - January - Amazing Voxel Bird Saga
Just popping in
Just popping in


My latest score:

Resized Image

Go to top


Re: 2023 - January - Amazing Voxel Bird Saga
Just popping in
Just popping in


My latest score:

Resized Image

Go to top


Re: 2023 - January - Amazing Voxel Bird Saga
Just popping in
Just popping in


My latest score:

Resized Image

Go to top


Re: 2023 - January - Amazing Voxel Bird Saga
Just popping in
Just popping in


My score:

Resized Image

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


The crash i've reported earlier is not bound to the Demo Version of Gorky 17. It also occurs in another app using MiniGL by showing the same (upper) calls in the Stack trace. In the second case it only needs longer to occur, approx 15 mins.

I've put that information into the Bug Report 933 i've created earlier. But i am not able to edit Title and Description there.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Just popping in
Just popping in


VERY interesting stuff has been published here

Seems to allow running Warp3D/MiniGL stuff inside emulation. Maybe also higher screen resolutions. I have not yet tested this on my own.

Go to top


Re: AmigaOS 4 Monthly Roundup - October 2022
Just popping in
Just popping in


@AmigaOldskooler

Well done! Thank you!

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


@Kas1e

Quote:
Do you have account on aeon's bugtracker ?


Bug Report 933

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


@kas1e

Quote:
Have a chance to test it with Warp3D_SI if you on RadeonHD ?


maybe next weekend

Quote:
i can test it on pegasos2 with original warp3d and radeon9250


Do you have the possibility to connect your peg2 to a monitor capable of 2560*1440. Theres a problem with WarpView when using resolution higher than 1920*1080. It will crop the screen. I don't know if this problem exists also with RadeonHD & W3D-SI because in the past i did not had a monitor supporting such a high resolution. This Problem has also been reported here by another user.

Quote:
Do you have account on aeon's bugtracker ?


Yes i'll create a bug ticket there soon.

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


@kaS1e

yes pointing to 3D and GFX driver stuff:

Crash log for task "Gorky 17 Demo"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x0183346C
Type of crash
DSI (Data Storage Interruptexception
Alert number
0x80000003

Register dump
:
GPR (General Purpose Registers):
   
001DE3C54 638BA800 00000002 0223A968 6F5A9160 00000000 00010000 0000001E 
   8
00000001 00000000 00000000 01DE4C24 33555335 624BC7E0 00000000 6FEF9978 
  16
624B4BA8 5EE5F294 00010000 61B10000 00000001 638BA840 02450000 0000004C 
  24
6FF6A3A6 6F5A9158 00000013 6F5A9160 00010000 00000000 6FF68018 0000001F 


FPR 
(Floating Point RegistersNaN Not a Number):
   
0:             -nan              0.6              0.6         0.603132 
   4
:         0.603152             0.75             0.75            0.625 
   8
:         0.574031            0.875              0.5            -0.75 
  12
:              256       -0.0361874    -4.21044e+201     4.95153e+166 
  16
:     1.42737e+181     1.08197e+186      7.0422e+190     1.94547e+164 
  20
:     5.77331e+167      3.88597e-41      2.6727e+171     4.84384e+188 
  24
:       2.631e+241     4.44909e+248     3.84682e+248     1.35007e+244 
  28
:              0.6              0.6              0.6              240 

FPSCR 
(Floating Point Status and Control Register): 0xA6302100


SPRs 
(Special Purpose Registers):
           
Machine State (msr) : 0x0002B030
                Condition 
(cr) : 0x5ACA0000
      Instruction Pointer 
(ip) : 0x0183346C
       Xtended Exception 
(xer) : 0x5AC9F134
                   Count 
(ctr) : 0x00570001
                     Link 
(lr) : 0x00000000
            DSI Status 
(dsisr) : 0x85027002
            Data Address 
(dar) : 0x5ACA7A44



680x0 emulated registers
:
DATA00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
ADDR
6FFA4000 85FFAD00 00000000 00000000 00000000 00000000 00000000 638BAA40 
FPU0
:                0                0                0                0 
FPU4
:                0                0                0                0 



Symbol info
:
Instruction pointer 0x0183346C belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
    
native kernel module kernel+0x0003346c
    native kernel module RadeonRX
.chip+0x00018f28
    native kernel module RadeonRX
.chip+0x00025bdc
    module LIBS
:Warp3DNova/W3DN_GCN.library at 0x7F436644 (section 0 0x10620)
    
module LIBS:Warp3DNova/W3DN_GCN.library at 0x7F4363B8 (section 0 0x10394)
    
module LIBS:Warp3D/HWdrivers/W3D_NovaBridge.library at 0x7F7A7D84 (section 0 0x6D60)
    
module LIBS:Warp3D/HWdrivers/W3D_NovaBridge.library at 0x7F7A7EB4 (section 0 0x6E90)
    
LIBS:Warp3D.library:_Warp3D_W3D_BindTexture()+0x5c (section 1 0x7044)
    
module LIBS:minigl.library at 0x7F8287CC (section 0 0x187A8)
    
module Gorky 17 Demo at 0x7F2D2D6C (section 0 0x25D48)
    
module Gorky 17 Demo at 0x7F2C9124 (section 0 0x1C100)
    
module Gorky 17 Demo at 0x7F343CCC (section 0 0x96CA8)
    
module Gorky 17 Demo at 0x7F3D164C (section 0 0x124628)
    
module Gorky 17 Demo at 0x7F3D1BB8 (section 0 0x124B94)
    
module Gorky 17 Demo at 0x7F3BA7A8 (section 0 0x10D784)
    
module Gorky 17 Demo at 0x7F3D9A14 (section 0 0x12C9F0)
    
native kernel module newlib.library.kmod+0x00002614
    native kernel module newlib
.library.kmod+0x00003340
    native kernel module newlib
.library.kmod+0x00003864
    Gorky 17 Demo
:_start()+0x170 (section 1 0x16C)
    
native kernel module dos.library.kmod+0x0002a458
    native kernel module kernel
+0x0005c18c
    native kernel module kernel
+0x0005c204

PPC disassembly
:
 01833464: 
81240000   lwz               r9,0(r4)
 01833468: 
81440004   lwz               r10,4(r4)
*0183346
c91490004   stw               r10,4(r9)
 01833470: 
81240004   lwz               r9,4(r4)
 01833474: 
81440000   lwz               r10,0(r4)

System information:

CPU 
 Model
Freescale P5020 (E5500 coreV1.2 
 CPU speed
1995 MHz 
 FSB speed
798 MHz 
 Extensions
:

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


Gorky 17 Demo (from OS4Depot) crashes always after a few mins of gameplay. Crash does not occur when playing using SW renderer.

Go to top


Re: NovaBridge compatibility thread
Just popping in
Just popping in


@mufa

same on my machine but unsure if related to NovaBridge.

Go to top


Re: Switch between many amigaos4 machines
Just popping in
Just popping in


@kAs1e

Quote:
Just between two computer x5000 and a1200 ? It's just mechanical switch, or all automatically ?


I had 3 devices connected to it. It automatically switches to the first device you're powering on. Additionally it has a button on it to switch manually.

Quote:
Not needs for manual button press ?


It has a wired button ­­~1m long. It remembers the last active Computer (1-4).

Both devices are electronical switches.

Go to top


Re: Switch between many amigaos4 machines
Just popping in
Just popping in


@kas1e

Quote:
At first i will be happy with just hdmi switch, as it pain to replug them in the dark :)

I basically will be happy with just mechanical switch controlled manually and only use one computer at time


Thats the HDMI Switch i used some time ago with X5000 (RadeonHD and Radeon RX):

HDMI Switch 3 to 1 with Amplifier

Even if product description says max resolution is 1080p It worked flawlessly using 2560x1440@75.

The USB Switch i am using is a "ATEN US 424". It offers support for 4 Computers and works like a charm* with X5000 and A1200 (+SUM USB).

*No problems even when switching often, in uboot, during boot, on WB, in Games, .... probably beacause it simply connects electronically the selected Computer while not intercepting/forwarding USB-HID like high end KVM devices do.

Go to top


Re: NovaBridge released!
Just popping in
Just popping in


@kas1e

Quote:
What is it ?


One of my most expected releases since you created that preview video last year

Quote:
Do I need that ?


YES!!!

Quote:
Daniel made some hackish attempts to fill the gap: he took the GL4ES and wrapped it in a wrapper, so RadeonRX had "minigl4gl4es," which was buggy, crashy


It was 'ok' and way better than nothing after switching from RadeonHD+W3D-SI to Radeon RX

Quote:
Benchmarks plz!


For real comparisons you could define the benchmark environment (default settings, customized, resolution, scene, ...)

My first impressions are quite positive:

- Seems not to eat much CPU cycles
- In general more fluid, correct and faster rendering
- Blender, again, finally

Quote:
Is it absolutely bug free ?


Probably not but thanks to your extensive testing it contains less bugs.

One thing i've noticed without deeper investigation so far: As a heavy user of WarpView i could finally switch back from SW to W3D rendering again. Unfortunatelly having W3D enabled in WarpView leads to a cropped screen when (horizontal) resolution is higher than 1920. Can someone confirm this?

Thanks to all involved!

Go to top


Re: Switch between many amigaos4 machines
Just popping in
Just popping in


@kas1e

Quote:
But for HDMI video, usb mouse/keyboard and speakers, want this KVM box, which can produce me 1920x1080x60 with no probs


Does it needs to be excactly ONE device, or would it be ok for you to have separate devices to switch USB and HDMI?

Everything that is "Active" can shows its own problems (USB HIDs not detected, Adding display lag...)

Go to top


Re: Odyssey scripts
Just popping in
Just popping in


Thanks walkero!

The Stack Overflow and GitHub scripts are really nice.

Go to top


Re: Porting OpenGL
Just popping in
Just popping in


@rjd324

Quote:
minigl cannot be used on X5000 with RX cards

Quote:
installing minigl is pointless right now for the X5 + Rx combination


Simply install MiniGL4GL4ES to get MiniGL support using a Radeon RX Graphics Card:

Resized Image

Quote:
How do I build a program that includes glut on an X5000 with RX card?

Quote:
What about: http://os4depot.net/share/driver/graphics/minigl4gl4es.lha. This seems to include GLUT that is built on GL4ES, so that it is usable, but there is no
link library, only a shared library and there are no include files.


Just link your app against regular MiniGL SDK. MiniGL4GL4ES is not a development library.

Go to top



TopTop
(1) 2 3 4 ... 10 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project