Browsing this Thread:
1 Anonymous Users
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Missed a post that made this reply redundant.
Posted on: 2013/12/8 9:50
|
|||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
I'm glad you like the idea. Quote:
I'm sorry if my post caused confusion. The OP has opened several different threads of wanting to start bounties to AROS to run under different virtualizers and emulators. So perhaps I was addressing these issues in the wrong thread (it's very early in the morning here ![]() I just think it's a great idea to try to draw people from the outside in, esp. since it doesn't cost anything. I have never used AROS under QEMU and didn't know the x86 native runs already under it (I do know it runs under VMWare). So, if someone who does can write up instructions and get it listed in the QEMU web page would lead more traffic here. (This can be done by a non coder of course). My ideas on AROS 68K emu will go in that thread to avoid confusion...
Posted on: 2013/12/8 7:53
|
|||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Notice how I didn't say anything about classic mac support, because in that case you have actual hardware to run AROS on. This is a good idea!
I just don't see the point in targeting an emulator, which has less features, slower, and involves throwing out the majority of the software base. I also can't understand how you managed to get from "AROS already runs in QEMU" to "AROS needs to run in QEMU m68k to leverage the huge market, and bring more uses".
Posted on: 2013/12/8 7:42
|
|||
|
My AROS&MorphOS ports
Arguments that explain everything... explain nothing. |
||||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
That's great. Quote:
There is none. That's my point! Please read on: If you go tohttp://wiki.qemu.org/Manual you will see a section "How do I..." / "for users that target for a specific platform" with instructions for Windows XP, Linux and FreeDOS. Where is AROS? You see, my point was: In today's world a very large percentage of people have never even heard about the Amiga / AROS. But they use virtualizers (e.g. to run XP under Linux). If in the process perusing the QEMU web page, they notice there's another OS that they can try, they may check it out. I would bet money that the QEMU web site gets more hits in a year than AROS exec has since it's existence. Why not leverage that opportunity (and others) to bring new people into this small world which could lead to more development. This can only happen if a) something points that option out to them and b) it's made easy (link to the download section) and simple instructions to get going. Quote:
Yes, but it will potentially get a VERY LARGE number of people to run it which will get it tested, bug reports filed and lead new people to check out AROS.
Posted on: 2013/12/8 7:33
|
|||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
"More uses", "move forward", "free advertisement" - these are only buzzwords, without actually examining the consequences. i386-AROS already runs in QEMU, so did the x64 port, etc. This is nothing new. Where is the free advertisement and the flock of new users?
So you think a non-amiga m68k port is going to archieve that? What are the advantages? With a "generic" m68kport you lose all the non system friendly amiga software, a lot of speed, system integration, and so on.
Posted on: 2013/12/8 6:49
|
|||
|
My AROS&MorphOS ports
Arguments that explain everything... explain nothing. |
||||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
fatman2021 has the right idea. Like I mentioned in another posting, the trick to move AROS forward is to look outside the existing small/tiny Amiga centric world and try to appeal to the masses. Leverage the much larger market. For example, if AROS ran under QEMU, this could be mentioned on QEMU's web page with a link to AROS which could potentially bring more interest than the entire existing userbase just of that one link. This is FREE marketing! THINK LEVERAGE!
Posted on: 2013/12/7 22:39
|
|||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Just can't stay away
![]() |
QEMU has more users then ether FS-UAE or WinUAE. QEMU is used for everything from devoloping kernels and bootloaders to running entire operating systems.
Posted on: 2013/12/7 22:31
|
|||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
You don't have to use the custom chipset for display if you don't want to. Just use the uaegfx driver with high resolutions and color depths. I still can't see how this "generic" m68k distro would bring more AROS users. I highly doubt that users would prefer to mess with QEMU instead of just using FS-UAE or WinUAE. If your reasoning was valid, then QUEMU would be far more popular than VirtualBox or VMWare.
Posted on: 2013/12/7 22:09
|
|||
|
My AROS&MorphOS ports
Arguments that explain everything... explain nothing. |
||||
|
||||
|
Re: Get AROS m68k to run over QEMU(qemu-system-m68k)
|
||||
|---|---|---|---|---|
|
Just can't stay away
![]() |
Nothing. QEMU is used by more people. Not everyone needs nor wants support for components such as the custon chipsset.
For the most part this would be a genaric AROS m68k distro.
Posted on: 2013/12/7 21:51
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.








