@cha05e90

Quote:

I might do a screen mode bounty for the right price, not promising any thing.

the Ethernet stuff is left for dead.

(DO NOT RUN BASILLISK II IN WINDOW MODE.)

@cha05e90

Quote:
Because I like to read crash logs I can understand, from user like your self, I don?t have 100 beta testers working for me, so there might be problems, and issues I have not yet found.
Quote:

Currently the display is drawn on to the screen whit 50hz interval, The larger the display the slower its displayed.

There might be possible to use trap handler (mmu) to convert the pixels on the fly, but this does not guaranty faster display refresh, the result is just going to be a different kind of slow down.

Less slow down when nothing is happening; more slow down when lots of things is happening, but it might be better for large screen modes.
But anyway its lots of work, I looked at it once and twice.

Quote:
Network does not even work in EUAE.
I have done my best, but can?t get this working, some one else might be able to.

@virge

Sam440ep might be too slow for CPU intensive tasks.

Sam440 flex 800 mhz might be able to emulate a 68020 30mhz cpu,

@cha05e90

And native OS4 video mode is not the same MacOS video mode, resulting slowdown converting from one format to the other, 16bit is faster then 32bit, use that and reduce screen resolution.

Use a real hard disk partition!

Do not use Hard files they are where slow!

MacOS CPU 680x0 is emulated under AmigaOS4.

BasiliskII uses the same CPU emulation as EUAE.

Contribute to the EUAE JIT bounty and you might get what you?re asking for.

Quote:
Please explain, what do you think should be done differently?

I have tried fixing the network support but it remains broken; I?m not going to invest more time on this, I have already wasted a lot of time and archived nothing.

@jahc

You should probably do some physical training and you should get some sleep, not stay up night coding, you work your self to the grave.

@Jeff

I think it's a power drain problem,

CDROM+1GRAM = Does not work.
CROM+512MB = Does work.
No CDROM+1GRAM = Does work.

I can't see any other logic the PSU being the problem.

@Hans

I use the AGP, I read some where that PCI66 slots will stop working after doing the fix, but I never tried the PCI66 slot after the fix.

@magic

LimePC = PowerPC
and LimePC is a small laptop

@Troels

These things should not be in the bounty, writing a JIT compiler is a hard task as it is, lets not change focus to unreleased things.

So please remove:

- Sharing the clipboard between the emulation and the host.
- Preferably use shared objects (especially for SDL).

@McDonald

And any good old book about 'C', there is the a C++ compiler but, AmigaOS was deigned for old 'C' so C++ is not going to where useful.

If you have some background knowledge about programing it going to help a lot, its going to be where hard journey if you don't, start whit simple programs, and then learn one library at the time, a good start might be to create some AmigaDOS commands, once you know how to do that learn Reaction, then intuition and graphics library, from there you might won't to learn AHI, you might find picasso96 interesting, but MiniGL or Cairo might be more useful, don't spend time on warp3d is going to become obsolete soon.

You might find some past experience in programing on Linux where useful, the Linux man files are where good, newlib / clib provide excellent options to dos.library file handling commands.

@McDonald

You don't need that old CD it's old and outdated, and comments documentations are most likely wrong or misleading, just download the OS4 SDK from Hyperion, thats all you need.

@nbache

I hope so

@McDonald

You don't need stormC4 and CubicIDE, all you need is GCC and notepad

Download the OS4 SDK and start hacking.

"C" it takes a lot of experience to make some useful, and SDK does not describe every thing, you will need ask for help to get started.

Check out:

http://utilitybase.com/

@trixie

I don't know if you know some thing about electronics, but there should be pull down resistors connected to the +D -D on the motherboard, maybe you can check, the lack of restores where the problem whit AmigaONE's.

Some devices will not work because they require vendor specific drivers.

@trixie

If it support “mass storage” then your safe, if does not don't buy it.
AmigaOS4 does support picture transferee protocol, I tried it once on my Camera, it worked until camera decided to turn it self off, and I don't know way, I gave up on ptp and switched back to mass storage.

If you have problems whit memory stick format it, and try again, don't copy files whit commons and keep the filenames short, then it should work, oh yes maybe there is problem whit protection bits (execution bit is not used in PC world).

@Dwyloc

SECURITY WARNING:

Note that in previous version, FTPUsers file contained entry "rest" which
was originally planned for use with MultiUserFilesystem under AmigaOS 3.1+
since this filesystem was not ported after AmigaOS 3.5 this part of the
program has been deactivated in this port and letting this entry was a
security hole as anyone was allowed to login.

@Antique

Antique there are some http servers on OS4Depot you can use, and you can use wget to download the files on client side.

CLIENT SIDE:
http://www.os4depot.net/index.php?fun ... lity/misc/wget-bin.tar.gz

SERVER SIDE:
http://www.os4depot.net/index.php?fun ... e&cat=network/server/http

there are lots of options,
GoAhead WebServer sounds cool,

ASP is the basic language for web, it should be easy implement some kind of file writing or read if that?s needed.
CGI can also be used for this, there are lots of example code on the net.

@jabirulo

I think ftpd need fixing, because you can list any file on your disk, because it uses an external command to list content on your disk, so in other words all user permissions are ignored

@freddix

LCD screens use 60hz signal, don?t worry about it, it wont flicker on the screen, that?s only some thing you see on CRT (cathode-ray tube) monitor there was beam drawing the screen.

Change all mode lines in tooltypes to 60hz and it should work (@60).

Warp3D might be using a different screen resolution.

@Mrodfr

Do you have OS4.0 or OS4.1?