@SteffJay

Modem? Do you have ADSL? I have not used ADSL sense 2000, or was it 1998.

The word "modem" is short for modulator-demodulator. It's a device that converts digital signals from a computer or other digital device into analog signals for transmission over telephone lines

The port on your network card is digital, and it’s called an ethernet port, and its typical counted to a ethernet router.

@BSzili

What are you trying to do?

If I read your code correct, you allocated memory, you protect it, and then return memory after the MEM_GUARD_SIZE? what is that supposed to do?

Typically, if you have broken for loop or while loop… it’s the end of the memory you need to protect, not the beginning of memory. even if did protect end of memory. you have problem with the memory page size, [protected][data][alignment][protected]… you might not catch bug sense you likely to write into alignment part.

pointer are not well understood by many developers, a pointer is a element.
“Ptr+=10;” is the offset: “sizeof(*ptr) * 10”; 10 is not in bytes its number of elements of the pointer to increment, this why always need to cast to byte pointers, before doing any additions, unless you intend something else.


wont it be better to create a memory copy protect, concept instead..

APTR DoublicateAsReadOnly(APTR src, size_s size);
void FreeReadOnly(APTR addr);

1. Allocate memory,
2. copy memory,
3. protect memory.

Crashes are often caused by non-initialized offsets, or pointers. Random crap in memory, causing pointers to be set, or offsets being set to something else than 0. It should be one of the prime suspects. Besides making sure you actually got memory after an allocation. Also, se lot developers who do not set pointer to NULL after freeing. yeh sure it faster if you don’t but it’s not uncommon to create a cleanup routine and accidentally call it twice because you forgot a return or a break.
stack corruption can be a issue, lets say you array with 10 items, it’s easy to accidently writ 11 items into it and corrupt next variable in the stack, its easy add extra variable after the array with 0xCAFECAFE or something like that, if want to check that array do not overwrite next variable on the stack..

Crashes on addresses like 0xFFFFF424, is good indication of zero pointer somewhere in the code.

@AmigaOldskooler

Thanks for the update

@arfcarl

ACube-Systems have created other drivers.

@Rob

Quote:

MorphOS try’s to have same clock ticks as a Amiga 500, while AmigaOS4 decided to have a higher precision clock based on real time clock, (so it’s not dived down.)

In any case if the game was not broken, timing should work, only Nova Coder can fix the bugs in his game..

And nobody else them him know how it should work in his game.

@Rob

There are many ways time kept in AmigaOS, one is timer.device, timer.device can measure time in cpu clock cycles ticks or milliseconds, ticks are synchronized to refresh rate, so ticks are not same between NTSC and PAL Amiga computers and therefore should not be assumed to be fixed number of clock cycles. Doing so is a bug.

This hack should slow down your clock cycles ticks to old Amiga 500 pal amiga.

https://os4depot.net/?function=showfil ... tility/misc/timerhack.lha

Another way to keep time is cia chip a/cia chip b timer a and b, if hardware banging is used for timing then NallePuh, it should fix timing..

WaitTOF in graphics library we talked about before, should sync to video modes refresh rate..

refresh rate is behind the “@” in screen modes, typical this are auto detected using DDC.. but custom screen modes can be added to the screen mode icons. Refresh rate is typically 60hz on LCD, on CRT it can be as high as 90Hz. Old school Amiga 500 is typical 25Hz/33Mhz, for TV syncing.

https://forum.amiga.org/index.php?topic=63099.0

@Rob

I think vsync is a option in the monitor driver, check that’s it's enabled, if game only uses vsync, it can run too fast, sense vsync depends on the screen mode, or perhaps did something else, best to contact Nova Coder about the problem maybe he can explain. or fix the bug.

@Futaura

That makes it harder, I agree, but I think its possible to workaround that.

@Futaura

Can easily hack into amigaOS4 library api. AmiSSL has a big back door. Statically linking makes it harder to be man in the middle.

@Tuvok

Quote:

Don’t agree. TAB’s are replaced with spaces, this means it’s useless for makefiles (completely breaks makefiles actually), TextEdit does not have Goto line short cut, that makes it useless so you can't jump to line that has a bug.

OS3 TextEdit can’t be used for software development, Notepad in AmigaOS4, can.

@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.