Welcome, Guest. Please login or register.

Author Topic: [UserReview] Vampire V2-128 received and it's just pure p0rn.  (Read 105233 times)

Description:

0 Members and 5 Guests are viewing this topic.

guest11527

  • Guest
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #674 from previous page: February 21, 2018, 02:24:13 PM »
Quote from: kolla;836397
So nothing new, just at last an FPU of some sort.
So you have no information on whether it will fully implement all 68882 instructions and features on the FPGA, or whether it trap those that are not implemented and feed them to a software emulator, like is done with 68040 and 68060 using their respective libraries?
As far as I got it, all of the FPU right now is just pure software anyhow, which might be fast enough, though. Given the amount of complexity, and the (in)-frequency of use of the transcendent functions, it is likely that at least the latter part remains in software for quite a while, as for the 68040 and 68060, though probably in a somewhat more robust way (i.e. no external library required). However, as far as I got the story, the integrated FPU is 64 bit only, which is again *often enough* sufficient, but not necessarily always.
 

Offline TrashyMG

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 36
    • Show only replies by TrashyMG
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #675 on: February 21, 2018, 02:37:48 PM »
Quote from: kolla;836397
So nothing new, just at last an FPU of some sort.
So you have no information on whether it will fully implement all 68882 instructions and features on the FPGA, or whether it trap those that are not implemented and feed them to a software emulator, like is done with 68040 and 68060 using their respective libraries? There was such a hoopla over how utterly crap solution it was to need such libraries, yet from what I can see, they're doing the exact same thing themselves.

I can't say for sure, this is what I've seen:

http://www.apollo-core.com/knowledge.php?b=4¬e=12178:

"In Gold 2.7, an MC68882 compatible set of FPU instructions will be available at boot time. It won't be necessary to load 68040.library or femu."


Quote from: kolla;836397

I guess there isn't any news after all then, just confusion and hyperbole (AMMX, AMMX2, AMMX2 + undocumented functions... which never seems to settle).

What do you expect from a small time development team working on this in their spare time. These guys have day jobs. Proper documentation can come when they solidify their cores.
 

Offline David Wright

Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #676 on: February 21, 2018, 02:59:03 PM »
I am reticent to criticize the Apollo team given the voluntary nature of the project.
Still, it seems they change direction from where they previously stated they were headed, or so it seems.
 

Offline Iggy

  • Hero Member
  • *****
  • Join Date: Aug 2009
  • Posts: 5348
    • Show only replies by Iggy
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #677 on: February 21, 2018, 03:56:43 PM »
Quote from: TrashyMG;836391
Gunnar is also really sarcastic at times, especially on IRC.


Unlike Kolla, I'm pretty sure Gunner regularly uses sarcasm.
BUT, around you demanding whiners, can you blame him?:hammer:
"Not making any hard and fast rules means that the moderators can use their good judgment in moderation, and we think the results speak for themselves." - Amiga.org, terms of service

"You, got to stem the evil tide, and keep it on the the inside" - Rogers Waters

"God was never on your side" - Lemmy

Amiga! "Our appeal has become more selective"
 

Offline grond

  • Full Member
  • ***
  • Join Date: Feb 2016
  • Posts: 154
    • Show only replies by grond
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #678 on: February 21, 2018, 05:06:56 PM »
@kolla: what point is there to explain things if you never understand them or intentionally omit the information provided?

 68882-support:  As has been explained many times before, the important difference is that all 882 instructions will work from cold-boot. Even though some instructions are emulated (V4: anything that is 882 but not 040, V2: a few instructions more), the emulation code is similar to a ROM but not only write-protected but also not visible to user code running on the CPU. This is a much better solution than the 680x0.library approach which need to be provided by an operating system of some kind and thus is not available during cold-boot. User code cannot tell a difference between a software emulated instruction and a hardware implemented one. A fsin or fcos is equally slow whether microcoded (68882) or emulated (040, 060, 080). Again: the important difference between 040, 060 on the one hand and 080 on the other is that the 080 will not trap on the fsin like the 040 and 060 will but comes with the emulation code included and invisible to anyone but the FPU. This is really a kind of microcode.

Disagreement in the team about the FPU:  

I don't know what you are referring to. The work on AGA was already very far when Gunnar put it aside for work on the FPU because Jari showed initiative with his wonderful FEMU. No hard feelings about that. The work on AGA is not lost and will progress soon.   There is no conflict over traditional FPU vs. next-gen FPU. You make that up. Again I have explained many times that the advanced FPU is the foundation on which the traditional one is built. It is easier to build something powerful and then add a limiting layer to it than to build something limited and then add functionality to it.  

AGA or SAGA:  

I have explained to you several times that the RTG part of the core implements the new graphics features in an Amiga-way. I.e. all the registers for the RTG modes are within the address range of the Amiga custom chips and can be written by the copper reimplementation and not only by the CPU as is the case with the P96 software layer. This means that you can have smooth hardware scrolling for chunky screens, chunky screens with copper palette, multiple chunky playfields and probably some more I forgot. All this already in the core. The only thing missing to complete SAGA is in fact lame old AGA. The "S" in "SAGA" is already there.
« Last Edit: February 21, 2018, 05:09:34 PM by grond »
 

Offline gregthecanuck

  • Full Member
  • ***
  • Join Date: Feb 2003
  • Posts: 169
  • Country: ca
    • Show only replies by gregthecanuck
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #679 on: February 21, 2018, 07:01:50 PM »
@kolla

Sometimes your comments are worthwhile, and sometimes not. On this thread you are back in the latter category again.

Grond has very diplomatically explained to you the background on some of the developments. This has been explained to you in various forms in the past, but somehow you continue to "forget".

May I suggest taking up a new hobby that doesn't involve posting bullsh!t?
« Last Edit: February 21, 2018, 07:46:42 PM by gregthecanuck »
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show only replies by Karlos
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #680 on: February 21, 2018, 08:41:35 PM »
A full 882 inplementation is a waste of gates. An 040 compatible FPU is all that is really needed. The 68882 transcendental instructions were so chronically slow anyway that you'd be certifiable to use then over any half decent software solution that uses simpler FPU operations. Some sort of trap and patch like oxypatxher/cyber patcher would be a nice way to get performant support for old 882 dependent code. It was good enough for the 040/060 after all.
int p; // A
 

Offline kolla

Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #681 on: February 22, 2018, 12:05:08 AM »
I'm not the one forgetting here, rewriting history is not the right thing to do, even if you do it "politely". One year ago, there already was FPU for V2, it just needed some "testing". I suppose the testing didn't go so well, because it didn't take so long before it was clear that the very much hyped FPU would not be... and anyways, Amiga don't need FPU, does it. So started the bashing of everyone expressing needs for FPU began. Then Gunnar came with AMMX, as a sort of "look, this is much more useful!". But there were people also inside the team that were unhappy about the lack of FPU, and there was a rather harsh discussion over it. Gunnar decided if he was to implement an FPU it would be the most awesome FPU ever, and it would require bigger FPGA, V2 be damned, let there be V3... heck V4! V2 owners can use some software emulation if they need FPU so badly. And this was the sentiment till Jari came with FEMU, pretty much proving that software FPU emulation is not desired. FEMU is far from perfect, and it was demonstrated how both productivity software and demos did not run well enough. So again focus was changed, to improve FEMU. And this has now been going on since last summer, and had CLEARLY been a priority. Despite previous rantings about how useless FPU is on Amiga and what idiots people are for wanting it. Jari says quite openly that after his initial 0.10 release, he's not really been the one working on improving it. Over time, more and more went into the FPGA, and from what I understand, it's currently on pair with 040. Meaning that there's still a bit of software emulation needed, which is fine. What's less fine is that this software is running outside the operating system, meaning noone else but Apollo Team can ever fix bugs or do improvements. But I suppose, like everything else Apollo Core, the code is perfect already. Like those libraries Phase5 put into ROM on their CPU boards. Bad for Phase5 and others, but good for Apollo Core. Always.

Imagine if Jari had not made FEMU, and where the project would have been now, what the outspoken sentiment would have been.

As for SAGA, it was announced that the SAGA FPGA core would be open source, but now it's not when clear what SAGA is, and half of the time it just refers to P96 support. Originally, SAGA was the Super AGA chipset that was to take over from the AGA Amiga chipset, being a superset of AGA. Pamela is the audio part of SAGA, taking over for Paula.
« Last Edit: February 22, 2018, 12:09:17 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #682 on: February 22, 2018, 12:13:55 AM »
Quote from: Karlos;836414
Some sort of trap and patch like oxypatxher/cyber patcher would be a nice way to get performant support for old 882 dependent code. It was good enough for the 040/060 after all.


No, this is not good enough. No patcher or trapper can be used, as this is taken care of outside the scope and reach of the hardware available from the operating system and any software running on the operating system.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline TrashyMG

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 36
    • Show only replies by TrashyMG
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #683 on: February 22, 2018, 01:40:18 AM »
Quote from: kolla;836419
I'm not the one forgetting here, rewriting history is not the right thing to do, even if you do it "politely". One year ago, there already was FPU for V2, it just needed some "testing". I suppose the testing didn't go so well, because it didn't take so long before it was clear that the very much hyped FPU would not be... and anyways, Amiga don't need FPU, does it. So started the bashing of everyone expressing needs for FPU began. Then Gunnar came with AMMX, as a sort of "look, this is much more useful!". But there were people also inside the team that were unhappy about the lack of FPU, and there was a rather harsh discussion over it. Gunnar decided if he was to implement an FPU it would be the most awesome FPU ever, and it would require bigger FPGA, V2 be damned, let there be V3... heck V4! V2 owners can use some software emulation if they need FPU so badly. And this was the sentiment till Jari came with FEMU, pretty much proving that software FPU emulation is not desired. FEMU is far from perfect, and it was demonstrated how both productivity software and demos did not run well enough. So again focus was changed, to improve FEMU. And this has now been going on since last summer, and had CLEARLY been a priority. Despite previous rantings about how useless FPU is on Amiga and what idiots people are for wanting it. Jari says quite openly that after his initial 0.10 release, he's not really been the one working on improving it. Over time, more and more went into the FPGA, and from what I understand, it's currently on pair with 040. Meaning that there's still a bit of software emulation needed, which is fine. What's less fine is that this software is running outside the operating system, meaning noone else but Apollo Team can ever fix bugs or do improvements. But I suppose, like everything else Apollo Core, the code is perfect already. Like those libraries Phase5 put into ROM on their CPU boards. Bad for Phase5 and others, but good for Apollo Core. Always.

Imagine if Jari had not made FEMU, and where the project would have been now, what the outspoken sentiment would have been.

As for SAGA, it was announced that the SAGA FPGA core would be open source, but now it's not when clear what SAGA is, and half of the time it just refers to P96 support. Originally, SAGA was the Super AGA chipset that was to take over from the AGA Amiga chipset, being a superset of AGA. Pamela is the audio part of SAGA, taking over for Paula.

Here we go again, yes you are re-writing history, your version is skewed from any facts and reality. You seem to have small nuggets of truth in the details, but you spin the version you want, the one where you're always right and the Apollo team is doing evil things to the Amiga community.
 

Offline kolla

Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #684 on: February 22, 2018, 06:43:42 AM »
Nothing evil going on, stop with the hyperbole. I was there on irc when all this went down, I still have the logs.
« Last Edit: February 22, 2018, 06:45:51 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline Niding

  • Hero Member
  • *****
  • Join Date: Sep 2004
  • Posts: 566
    • Show only replies by Niding
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #685 on: February 22, 2018, 07:28:16 AM »
@kolla; I was there too, and to be honest, I would have lost my patience long before Gunnar.

As Ive said countless of times by now; Its work in progress with limited resources/people.
Still we (myself included I should add) kept pushing Gunnar and the team about xyz issue and feature, instead of appriciating their efforts.
Look at what happened with Kipper2k. Flype did say at one point "we are only human, its hard to not get affected by the negativity".

Ive frequented IRC almost daily at times (alot of afk mind you), and Gunnar IS known to poke fun in his own way, be it sarcastic, annoyed or just for lolz.
Thats fine.

In THIS particular timeframe my PERSONAL take on it, the barrage on IRC and forums (apollo included) eventually got to Gunnar, and he just shut down the FPU conversation with "There will be no FPU!". I took the hint, and stopped pushing Gunnar and the team. Basically I thought "Its better to let them work their own roadmap, than to have people like ME that doesnt actually contribute constantly poke them in the eye".

Then Jari came along with his FEMU emulation project, and Gunnar (and team?) took intrest in the FPU again. Gunnar has said REPEATEDLY; "If you decide to actually contribute with actual effort beyond WORDS, we will help/adjust the roadmap".
So in that framing, Gunnar hasnt actually changed his tune. He just reacted to Jaris efforts in a way he has said repeatedly.

TLDR: If you put in REAL effort, they will put in REAL effort.
 

Offline grond

  • Full Member
  • ***
  • Join Date: Feb 2016
  • Posts: 154
    • Show only replies by grond
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #686 on: February 22, 2018, 07:53:24 AM »
Quote from: kolla;836434
Nothing evil going on, stop with the hyperbole. I was there on irc when all this went down, I still have the logs.

The fact that you keep irc logs tells more about you than about what was said on irc.
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show only replies by Karlos
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #687 on: February 22, 2018, 08:16:47 AM »
Quote from: kolla;836420
No, this is not good enough. No patcher or trapper can be used, as this is taken care of outside the scope and reach of the hardware available from the operating system and any software running on the operating system.


I think you are missing the point. Full 882 emulation is just a waste. Can you show me any software released since people first started putting 040 and 060 in their systems that still needs needs a full 882 and doesn't have a version compiled that either does not require an FPU at all or relies only on the 040/060 subset?

Even assuming no software solution could patch an 882 binary at runtime because "reasons", we are now in the realms of programmable hardware. Is there a valid reason why the FPGA implementation could not implement it's own patch to call out to a handler routine when an unimplemented opcode is  first encountered?
int p; // A
 

Offline grond

  • Full Member
  • ***
  • Join Date: Feb 2016
  • Posts: 154
    • Show only replies by grond
Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #688 on: February 22, 2018, 09:04:59 AM »
Quote from: kolla;836419
One year ago, there already was FPU for V2, it just needed some "testing".
 There was an FPU for *Apollo Core*. How much of it was available in any publically released V2 core is a different question. And testing a CPU is the biggest part of the work because there is an infinite number of possible cases that can go wrong. So your point is based on a false assessment of how much work it is to develop a section of a CPU (a lot and few people can do something like that) and then debug it ("just some testing"). Testing and debuggin a CPU requires: writing lots and lots of testcases (assembly code) which requires a lot of knowledge and pondering about the inner workings of the CPU, simulating every single one of the testcases, looking at hundreds of digital signals in the simulator for millions of clock cycles where you can never see more than a few dozens on the screen for each testcase, modifying the simulation environment because you perhaps don't model a real computing environment accurately and crashes you see in real life just can't show in the simulator, and when you eventually see something odd happening, trace it back to the root cause which means you basically have to dig through the entire CPU logic. It's not as simple as "oh, here we have an uninitialised pointer, let's fix it and then release our App to Goodle Play".  
Quote
I suppose the testing didn't go so well, because it didn't take so long before it was clear that the very much hyped FPU would not be...
 Again you are basing your conclusions on false premises. The "just some testing" did NOT mean that testing with the team was started ever. There was NO testing in the team at all until Jari started FEMU!  
Quote
and anyways, Amiga don't need FPU, does it.
 What are you trying to say? "Gunnar is stupid because he doesn't know that an FPU can and has been used in an Amiga"??? Do you have some kind of Asperger? The statement was basically "since nobody of you wants to do any work other than talking bull%&$#?@!%&$#?@!%&$#?@!%&$#?@! on forums, you obviously don't need an FPU". Then there was a discussion about V4 which was supposed to be available much earlier and features an FPGA that has 64bit FP macros. These macros mean that you can either have an extended precision (that "nobody needs") FPU at very slow speed (i.e. not using the 64bit FP macros) or an NG FPU with "just" 64 bit precision at one FOP per clock cycle (!!!) per FP macro. With those macros you can build SSE type FPU units easily. Then there was the usual "but it's incompatible!!!" outcry going on (yes, SSE is not 386 compatible, very clever observation...). Summing up, half of what you are mixing into your skewed view of this vicious project was actually discussion about a future hardware base.  
Quote
So started the bashing of everyone expressing needs for FPU began.
 No, bashing of people like you who only say "but this old Amiga program does not run without CPU feature X" began. This project is not about Amiga. It is about the 680x0 family of CPUs. It is run by Amiga enthusiasts, though. It does not take any work to point out that some program crashes. It is no valuable input to point out which unit of a CPU, be it MMU or FPU, is used by what software. CPU developers KNOW that kind of thing. But if you really want something, you will have to put some effort into getting it. You don't but still have the time to bicker about the project on all Amiga forums? Then you obviously don't need an FPU. Nobody did? Well, then the Amiga obviously does not need an FPU. Get it? Sometimes "honey, you look gorgeous in that dress" means "you should lose ten pounds but we'll be late if you change again".  
Quote
Then Gunnar came with AMMX, as a sort of "look, this is much more useful!".
 Because somebody actually wrote the code for RiVA piece by piece which meant there was somebody willing to put a lot of work into "just testing" AMMX. The same thing that had NOT happened for the FPU. Thus, AMMX was clearly more "needed". Jari came later and then the "just testing the FPU" started. FEMU has been a perfect tool for testing the FPU because you could move FPU instructions into the FPU one by one and test each one separately.  
Quote
But there were people also inside the team that were unhappy about the lack of FPU, and there was a rather harsh discussion over it.
 Surprise, surprise, the members of the team are Amiga users. And yes, you are right, an FPU is a useful CPU unit, even in an Amiga. Please save this to your logs, you were right all the time!!!!!! An FPU IS REALLY USEFUL!!! It was created to serve some purpose!!! The situation was that the team members who had written a lot of testcases for the integer part had very little knowledge about writing FPU code. So basically it was the same situation that became a public discussion: if nobody puts any work into it, it means you don't really want it.  
Quote
Gunnar decided if he was to implement an FPU it would be the most awesome FPU ever, and it would require bigger FPGA, V2 be damned, let there be V3... heck V4!
 The Vampire V2 known to the public is in fact the V3. There was an unreleased V2 precursor with just 64MB RAM and a 16 bit RAM bus that was "the V2" inside the team (I actually owned one and used it in my Amiga). The 128MB V2 is always referred to as the "V3" inside the team. Majsta named his product V2 anyway and Gunnar prefers V3. Since the V4 was developed by Chris, a friend and colleague of Gunnar's, it is called V4. Majsta would probably have called it V3. So your reading between the lines about how the next card is the V4 because of some personality problem on Gunnar's side fails again. And you knew all this already because I have explained it before why the V4 is the V4 and not the V3.  
Quote
FEMU is far from perfect, and it was demonstrated how both productivity software and demos did not run well enough. So again focus was changed, to improve FEMU. And this has now been going on since last summer, and had CLEARLY been a priority. Despite previous rantings about how useless FPU is on Amiga
 So all this is about your hurt feelings? Because you said "an FPU is useful" and Gunnar said "it's useless"? And then history proved what we all knew forever? That FPUs do serve some purpose and have actually been used in the Amiga?    
Quote
Meaning that there's still a bit of software emulation needed, which is fine. What's less fine is that this software is running outside the operating system, meaning noone else but Apollo Team can ever fix bugs or do improvements.
 Are you aware that the 68882 is full of software emulation? Only that the software is stored as a ROM inside the CPU and cannot be changed at all? The 080 also has some software FP emulation inside, as you observed, but as the FPGA is flashable, it can be changed. But it is nothing that a user would or should touch. Your argument is basically a pro-open source argument. Well, gifts are always nice but you can't demand them.  
Quote
Imagine if Jari had not made FEMU, and where the project would have been now, what the outspoken sentiment would have been.
 Imagine you would actually contribute to the project, where the project could be now.  
Quote
As for SAGA, it was announced that the SAGA FPGA core would be open source, but now it's not when clear what SAGA is, and half of the time it just refers to P96 support. Originally, SAGA was the Super AGA chipset that was to take over from the AGA Amiga chipset, being a superset of AGA. Pamela is the audio part of SAGA, taking over for Paula.
 What's the problem here? That you again do not understand what I explained? Pamela is already done and part of SAGA (and clearly not P96, right?). The chunky graphics features that currently are available to the Amiga software through P96 are implemented in a SAGA way. P96 does not know about hardware scrolling and many more features so using P96 you can only perceive this part of SAGA as a normal RTG feature. If you want, you can bang the registers and have chunky Amiga screen modes. It's already there. You can do this TODAY. Do you understand that you could make a P96 driver for AGA? In the case of the Vampire the P96 driver basically is a chunky variant of "P96 for AGA"
 

Offline OlafS3

Re: [UserReview] Vampire V2-128 received and it's just pure p0rn.
« Reply #689 on: February 22, 2018, 10:58:52 AM »
Quote from: kolla;836434
Nothing evil going on, stop with the hyperbole. I was there on irc when all this went down, I still have the logs.


Kolla you explained already thousands of times how unhappy you are with the direction of vampire and that Gunnar is a liar and you bought it with different expectations. I already asked you several times to sell your vampire so you have no longer reason to moan and cry on every amiga site, you get your money and there is a new vampire owner who is happy with what he gets. A win for everyone. You did not react on it instead you continue the same. To me it looks like spreading nonsense on websites is your main interest in your life. Very poor...