Posts by Jens

As projects are completed (like Indivision ECS V4-RTG and ACA1260 release), this one steps higher and higher on the list

Jens

Interlacing isn't spec'd for VGA, so we haven't implemented an interlace-pass-through for Indivision AGA MK3. Yes, HDMI can do interlacing, and there may be a possibility to do that, but that's a niche that I wouldn't expect to get us any considerable uptick in sales. So one thing upfront: Output will remain all-progressive.

Happy to help with adjusting your setting to get closer to what capture cards require. Just upload your config file here, and I'll take a look.

BTW, just found an old eMail of yours where you've lost something on the train home. Did the train company ever get back to you?

Jens

We have C64 power supplies in the works, but a solution for C128 is still not done. The PSU itself is strong enough for C128 and expansions, so the most likely approach we'll take is to offer a replacement for the square DIN connector, which lets you use our C64 PSU on the C128.

Jens

First of all, make it work without VSync. The way we have to do VSync is propably very challenging for capture cards, as we have to insert/remove lines from a frame in order to stay in sync with the Amiga's VSync. This is out-of-spec of HDMI and VGA signals, so it's already a stretch for monitors. It might be even more of a stretch on capture cards, so again, make it work without VSync first.

Once you have that, you can tweak the pixel clock to be a whole-number multiple of the chipset clock.

However, it may be even easier to use the "auto resolution" feature, as that's most likely already what you want.

Jens

Drei Fragen, die nichts miteinander zu tun haben...

1. Flashen des Buddha Plus One ist nicht nötig. Bisher hat es keine Fehlerreports gegeben, die ein Update des Flash erfordern würden. Sollte es mal dazu kommen, werden wir das Update natürlich mit dem Flashtool ausrollen, aber es befindet sich auch schon auf dem DOM. Achtung: Nicht einfach irgendein bin-File flashen, denn es ist höchst wahrscheinlich für eine ältere Version der Hardware. Es würde zwar rudimentär funktionieren, aber Funktionen wie Unterstützung von drei IDE-Ports, Speicher und die GUI würden verloren gehen.

2. ein CF Adapter an einem langen Kabel, dann noch hot-plug tauglich, das ist weder hard- noch softwaremäßig vorgesehen. Ich rate davon ab.

3. FAT32-Formatierung ist in der Software nicht vorgesehen, und in der von Dir beabsichtigen Weise (von außen wechselbar) schon gar nicht, weil der Buddha nicht erkennt, ob die CF-Karte gewechselt worden ist. Es fehlt die Hardware für die "diskchange"-Erkennung, und weiters fehlt die Hardware um nach einem hot-plug die Karte in den TrueIDE-Modus zu versetzen. Softwareseitig fehlt ein Mounter für FAT32 den wir bewusst nicht implementiert haben, weil man damit nur suggeriert, dass das Wechseln von CF-Karten im Betrieb OK wäre - ist es nicht.

Wenn Du eine FAT32-Karte anstecken möchtest, kannst Du Dir natürlich eine Mountlist "bauen", die Fat95 verwendet. Deine Ergebnisse kannst Du gern hier im Forum posten, aber bitte erwarte nicht, dass es dafür von iComp Support gibt, denn das ist außerhalb der beworbenen Features. Wenn Du Daten wie im Jahr 1990 mit einem PC austauschen willst, steht es Dir natürlich frei das zu tun. Im Jahr 2025 bekommst Du von mir aber immer die Antwort "nimm' Netzwerk".

Jens

Quote from Erestor

Isn't Nordic Replay and improved version ?

The change from Retro Replay to Nordic Replay is very minor: It adds a mode where 8k ROM and 8k RAM can be activated at the same time, and that's done with a bit combination in the control register that is not used by the Action Replay and Retro Replay ROMs. That combination is exclusively used by the Nordic Power ROM.

So if you're after REU support, you need to run the Retro Replay ROM, which doesn't care if it's running on Retro Replay or on Nordic Replay hardware. To that ROM, the hardware is identical. So no need to spend any money - your U64 has everything it needs already.

Jens

Sorry for the delay. The Restore precedure indeed includes restoring the RDB of the DOM. Please be sure to run "restore_dom", not just "update".

Jens

I currently have the A500 on the table; will try the internal beta this week.

Jens

We're behind on returns - I'll take care of this this week.

Jens

That's known to be slow. Unfortunately, the 7-day period for making the declaration is already running now, so when that letter arrives, it's panic time, otherwise it gets returned.

Jens

Nope, there was no attempted delivery, and there is no note. Footage of the security camera doesn't show any delivery, not even mail for that day (needless to say that we weren't in on Saturday).

Jens

Benchmarking P96 on Indivision ECS V4 is mainly benchmarking the accelerator. The only thing that's truly relevant is the "percieved speed", IMHO. And that part would be the transfer from fastmem-framebuffer into Indivision ECS V4, which gets a major speedup from the ACA500plus CPLD update. However, that can't be measured, as current benchmarks will only measure how long it takes for the P96 API to return a function call. However, that's not when all the work is done - it's only the time when the API is ready to take the next command, but the changes still have to be transferred to the actual frame buffer.

For things that are done with the blitter, you win a little, but it's still "double work", as we need to keep two frame buffers (one in fastmem, and one for displaying). Since there is no blitter for the frame buffer in fastmem, the biggest influence on performance is with the accelerator.

Jens

Just made a quick module with the same A500/68030-33 setup, but the old CPLD version that does not allow 32-bit access to the frame buffer. Surprisingly, almost all benchmarks are the same speed, and only HiColour writepixel gains 38% with the faster access.

I did run with a slightly changed software setup, though, as the TCP/IP stack wasn't running. Some tests that should be identical (as they are not gfx related) are 7% faster. So the stack running in the background does eat some performance. I'll do future modules without network running, so we have an equal base, especially with older modules.

Jens

Quote from LineOf7s

so I'm hoping there's still stock when the time comes.

I'm confident that we'll make it all the way into next year with the currently-available stock. That's taking two "order rushes" into account: The one that I'm expecting when we release the new core and Picasso96 V3.6.0 and the usual Xmas rush. No need to hurry, no need to pay Scalper's prices, no need to buy on credit.

Jens

Quote from jaman

One more thought - could the issue be related to my BFG9060 CPU card? I'm wondering if there might be any known compatibility issues between the Buddha Plus One and this particular processor card?

The design is a straight Z2 card, and if that wouldn't work, you'd have lots of reports of Z2 cards not working with your accelerator. I doubt that the problem lies in the BFG9060. It would have to be a deliberate, complicated endeavour to make Z3 work right, but mess up Z2.

Jens

Quote from jaman

Is there anything else I should check or try?

The usual "clean all contacts", as that's the main reason why things may not work properly in a 30+ year old computer. Use alcohol (IPA from a pharmacy) and an old thoothbrush for the slot, a micro fibre cloth for the contact edge of the Buddha (which might have collected some dirt when you inserted it first). Don't let it dry, but insert the card when everything is still wet. No need to wait before powering on - voltages are very low on the Zorro slot, so that tiny bit of remaining alcohol won't harm operation.

If you're a smoker or you live close to a coast, slots need to be cleaned on a regular basis: Salt or nicotine in the air makes pluggable connections that are not sealed (like in automotive connectors) very unreliable.

Jens

There is stock left and you can order now. We can ship today (it's already Monday morning here - IIRR, you're downunder?).

It's just that the shop stopped taking orders for this particular product during the weekend because it detected a scalping attempt.

Jens

Each and every controller is not just passing a QC before it gets it's warranty ID, but it even copies it's own DOM, so the mere fact that you have the DOM on the card means that it worked completely before it left.

Is this a Re-Amiga, or an original Commodore unit? What about other Zorro cards, do they show up in early startup? Is Buster seated properly?

Jens

Looks like a safety setting has kicked in: Lots of unexpected sales for multiple units in a span of 8 hours from a single country has triggered the "someone is attempting to buy out remaining stock"-criteria. Looks like someone is smelling money before the price increase. I have now cancelled and refunded a bunch of orders that have a clear pattern.

I have re-enabled the product, this time with a lower maximum quantity per shopping cart. Feel free to order, but expect me to cancel an order if it looks like a scalping attempt (i.e. unknown customer is purchasing maximum quantity several times as a guest order).

Jens

Quote from Lokiist

How can existing ACA500 Plus Owners get the JTAG updated?

I'm making a small board that can be sent to existing customers (see post#104 on this page). However, the new CPLD version is not necessary by default. it's just slower with the older versions. That's also a thing that I'll benchmark next week.

Jens