Masjsta's A500 Vampire

[majsta]

What is exec.library? Where is that and for what purpose is used?

[SpaceMonkey]

It is software, by every definition. It's not a sequentially executed language like you feed CPU's & DSP's.

Apollo is software and more importantly it's an emulator, it happens to be a not very accurate one but that is by design.



That is the standard line, it Apollo can't run exec.library then someone can just patch it or write a new one.

So which of the instructions, address-modes do you believe are flawed.

http://www.apollo-core.com/index.htm?page=instructions

Or specific programs which don't work.

[wawrzon]

What is exec.library? Where is that and for what purpose is used?

Its one of the kickstart modules, a kernel so to say, but id expect you to know that better than me;)..

[guibrush]

@psxphill :
Please, stop spreading so much non sens. I have a vampire in my 600 and I have often uptimes as long as 30 hours, without rebooting, listening web radio, chatting on IRC with the team and using Ibrowse. This is something that my good old A4000 can't achieve. That's right, my vampire system is far more stable that my A4000 with cyberstorm 060. I think this is not bad at all for surch a non compatible CPU.... Or maybe is the 68080 more compatible with the 68k range than an 060 ? Guess what, buy yourself a vampire, make somes testing, and only after that come back and give us you opinion. Until then, this is just non sens.
Bye.

[majsta]

@wawrzon

[wawrzon]

Apollo is software and more importantly it's an emulator, it happens to be a not very accurate one but that is by design.

okay. but have you asked yourself, do this statements contribute anything useful to the effort or at least discussion? because if not, then stated once, we know your position on the subject. does that matter if one calls fpga or microcode "emulation"? especially as long as it reaches its goal? and if not, being "inacurate" its a field for improvment, that apparently is both possible and considered.

the actual problem would arise if there was no argumentation on thes subject allowed, or the issue was denied, but ist isnt the case, at least in my book.

[kolla]

It is software, by every definition. It's not a sequentially executed language like you feed CPU's & DSP's.

Then a sheet of paper coming out of a printer is software too.

Apollo is software and more importantly it's an emulator, it happens to be a not very accurate one but that is by design.

And the sheets of papers coming out of a printer are merely book emulators.

That is the standard line, it Apollo can't run exec.library then someone can just patch it or write a new one.

You are aware that most Amiga models have their own exec.library variants already?

[kolla]

Light bulbs - emulating candles for more than 200 years.

[psxphill]

That's right, my vampire system is far more stable that my A4000 with cyberstorm 060.

Sure it's better running some software, it unfortunately doesn't run the software I want to run so I won't buy one until it does. It would run 0 hours with Amiga BSD, Amix or Shapeshifter with TurboEVD video driver.

Then a sheet of paper coming out of a printer is software too.

No, paper is neither software nor hardware. But thanks for the straw man.

and if not, being "inacurate" its a field for improvment, that apparently is both possible and considered.

the actual problem would arise if there was no argumentation on thes subject allowed, or the issue was denied, but ist isnt the case, at least in my book.

Actually no discussion is allowed by people here and the issues are denied, the fanboi's won't let anything be said that isn't 100% positive. It's not just me who shares the same issues with Apollo.

[guest11527]

You are aware that most Amiga models have their own exec.library variants already?

That's a pretty misleading statement. What is different is not exec, but the bootstrap code that initializes motherboard memory. Actually, parts of expansion are also system-dependent, due to a compile-time variable.

The difference is that all these variants of exec - those CBM made - are configuration options of a single source code, and can hence be maintained jointly, i.e. fix a bug in the source code, get all versions fixed at once.

This is not true for external patches or replacements. It is really a matter of software deployment than a matter of "how many versions exist".

[guest11527]

Sure it's better running some software, it unfortunately doesn't run the software I want to run so I won't buy one. It would run 0 hours with Amiga BSD or Amix.

That's certainly correct, but one should also accept that just for this particular purpose, better hardware exist. My PC runs BSD just fine, so it's hard to justify the requirement. I do get your point, of course.

Concerning the software vs. hardware discussion: That's simply childish. As long as it runs my software, I do not care how I call the implementation. If it walks like a duck, and talks like a duck, it is a duck.

[SpaceMonkey]

Sure it's better running some software, it unfortunately doesn't run the software I want to run so I won't buy one until it does. It would run 0 hours with Amiga BSD, Amix or Shapeshifter with TurboEVD video driver.



No, paper is neither software nor hardware. But thanks for the straw man.



Actually no discussion is allowed by people here and the issues are denied, the fanboi's won't let anything be said that isn't 100% positive. It's not just me who shares the same issues with Apollo.

Ok lets discuss.

Lets start with a simple question. Which Amiga do you own.

So which specific part of the Apollo-Core do you believe to be defective or feature missing.

[IanP]

Sure it's better running some software, it unfortunately doesn't run the software I want to run so I won't buy one until it does. It would run 0 hours with Amiga BSD, Amix or Shapeshifter with TurboEVD video driver.

So your argument is that because the Apollo core doesn't currently run those non-Amiga operating systems people shouldn't buy Amiga accelerators that use the Apollo core. Does your argument also apply to all the other Accelerators using Motorola/Freescale CPUs without MMUs? Are they all incompatible/inaccurate too? Do you also go on Unix and BSD forums telling them not to buy x86 hardware as it can't run Amiga OS without emulation or classic Mac forums telling them their machines are useless because they don't have a the custom chips to play Amiga games natively?

I'm not sure you're argument will win over many people since the "failings" of the current Apollo core would seem to be insignificant to the vast amount of Amiga users who probably have no interest in running the software you want to.

[UberFreak]

This feels like kindergarten...

[kolla]

That's a pretty misleading statement. What is different is not exec, but the bootstrap code that initializes motherboard memory. Actually, parts of expansion are also system-dependent, due to a compile-time variable.

Sure, and how is the Vampire different in this context? I wrote _variants_, not versions.

[kolla]

It would run 0 hours with Amiga BSD, Amix or Shapeshifter with TurboEVD video driver.

Amiga BSD?

No, paper is neither software nor hardware. But thanks for the straw man.

Clearly a sheet of paper i hardware. Postscript is an example of a language that is used to describe how the print on the paper will be. Same for 3D printing, you program the model. Same for FPGA, you program the layout. You only need to run the programming once to get a sheet of printed paper done and ready for reading. You only need to run the programming once to get a 3D print done and ready for use. You only need to run the programming once to get an FPGA done and ready for use. The software (the "core") is only there to tell the FPGA how to lay out its gates, after that is done, the "software" is strictly no longer needed.