@328gts

https://www.nxp.com/docs/en/fact-sheet/T2080FS.pdf

This one might even have AltiVec, unless T2080FS is not the same as T2080.

Max clock speed is 1.8Ghz just like PA-SEMI (X1000), I don’t know if it can be overclocked, but its running at 1.5Ghz now, it has DDR3 support, X1000 only support DDR2.

@OlafS3

Yeh… OS3.1 can be painful to setup, some error make no sense, I’m trying to get Ibrowse 68K working, getting guru error 80000004, but did install the generic 040.library, I spent yesterday setting up EUAE for 68040, only to run into this problem.

AmigaOS3.2 is also really barebone, it lacks Picasso96, mui, lots of libs.. and classes, it takes a lot of time to get it all working..

@Tuvok

If you are trying to display a 32bit or 16bit OS3.1 screen on AmigaOS4.1 8bit screen maybe? Well stop doing that… its stupid.

8bit modes can’t display that many colors. (it should be converted to gray scale... but ended up Winkey.) press CTRL+WIN+S to select a different screen mode.

Also a AGA screen can't be displayed on Picasso96 8bit screen,
HAM is 4096 colors a normal 8bit screen is just 256 colors.

AmiGfx works differently then what you might be used to on SDL, on SDL you do not have control over the destination screen, on AmiGfx you decide what output format is.. 16bit output screens are often faster then 32bit output screens, and it can be really noticeable on slower systems.

In any case… I can’t fix things, if I don’t know what the problem is… what is display output screens screen format? What is screen you have on AmigaOS3.1.... Bugs an issues in OS3.2 is not accepted.

If you what do the beta test, send me a PM.. and I send you a link to debug version. Sadly, I have learned I can’t share development openly.

@Maijestro

Have you installed AmiSSL under Aos3.1?

I think i did that.. but its not working..
i can only access a few web pages, where I can ignore security.

@Maijestro

I have only tested under AmigaOS3.1..
but what I found is that CPU emu should be set to 68040, CPU speed should be max.. when enabling JIT, because it’s not a debug version, this really hard to debug..

Can be mutex issue, try again…

the version of AWeb I'm using is Version 3.5.09

@Mr_byte

I know need to mount the .cue file, to get CDDA working.
do not mount the .iso file.

@Maijestro

try discounnect eth cable. maybe you have cable loop..

@balaton

The different kinds of USB chipsets I guess, but its also all software that use Amiga Input, that wont work. if the USB stack is replaced, and some flatbed scanners.

@trixie

No, ben was approachable, we talked about many things, and we agreed on many things, it was that he wanted me to work for him, I did not for many reasons.

I do things for fun, the moment I do something because someone else has asked me to, it goes from being a hobby to being actual work.

I feel sometimes a little bit burned out from my day job (I answer questions all day long). And I feel working in isolation won’t be good for me.

@trixie

Are you speaking of a client / server option, so it sends TCP packets Well as long as OS does not completely freezes because of corruption.

@orgin

I think most USB problems it’s not related to the USB stack,
XE/XE/Micro lacked pull up/down resistors on some of the signal lines.

some of the computers, have problems with underpowered USB ports.

I think benefit might be legacy software, iomega had some USB software I remember,
and maybe, I don’t know about gamepad support, but Amiga Input, has a flawed design.

@Crumb

isochronous transfers is supported in OS4.1 usb stack.
don't remember if its in beta or released.

@BSzili

There different approaches you can do narrow down the problem..

disable functionality, until the corruption stops.

#if gfx_enabled
#endif

#if sound_enabled
#endif

you also allocate more memory then you need, if the corruption stops, you can kind guess what caused it.

Some times C++ can help you find bugs.. compile with all warnings..

"-wall"

Make sure index and pointers are initialized proper before use.

what if index I is not initialized.

And you do offset = pointer+I, you assume I is 0, but it can be any value.

@BSzili

I had a problem in Amos Kittens, there was large table containing a function table lookup, as some point in the code, it got corrupted. I solved the issue, by making a checksum, at different intervals check if the checksum did not match. This way, I figure out when corruption happened.

@BSzili

write a c++ class, and check min/max, allocators and dealocators can also be overloaded, so you know if memory is freed and so on.

Write a macros, they easily hide boiler plate checks, and are easy to disable, when they are not needed anymore.

@joerg

Quote:

No I believe they added something extra, I got my driver noticed by AmigaOS, but crashes and does something strange when I select screen mode, I can’t get any help, because it was a secret I was told.

https://www.amigans.net/modules/newbb/ ... id=133940#forumpost133940

My idea was to create a alternative to the fake native modes.

Original P96 does not have composition, and that part is not documented for sure. Also AmigaOS4.x has DDC support, pretty sure that’s unique to OS4.x

https://github.com/khval/dummy.card

@jap

So, far as I know, the new AmigaOS4.x driver API is secret, you can’t build a driver, even if you want to, only the inner circle.

You know Nvidia is known to use binary blobs, this means it’s not fully open. Some parts were precompiled, this is why AMD graphics were the best option. Imagine, having to run partially the driver in a x86 emulator…

@MamePPCA1

Maybe because you have not calibrated it in Amiga Input, or maybe you have too many things connected to USB, a power USB hub can help… in any case pretty sure I answered this a few months ago.

@msteed

in that case, it is possible to log in using rs232..
if you have opened a shell in AmigaOS.

in user-startup I have:

run <>NIL: newshell AUX:

you log in using putty.

Should also work with USB adapters, but I think its better if you have RS232 on your computer.