Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
I have seen several types of megachip adapters without the 8375 for sale in various forums through the years.
That's from sellers who don't even make financial planning for warranty repairs. You may be on your own in case of a defect while you'll have a reliable partner with iComp to help in case there's a problem. While warranty is regulated by law, the warranty can only be as good as the person or company that provides it.
Jens
We have to give warranty by law, so instead of just inserting the chip for testing, we need to remove it, AND take the risk of the unit being damaged by the new chip or it's possibly-wrong insertion.
In other words: This would mean an increased price, which is probably not what you're asking for.
Jens
Beware! Those instructions are for Keyrah V1 and V2, where the Vcc pin of the keyboard connector is really "NC" (not cnnected), and it may actually work if you wire a 5V source to that pin.
On Keyrah V3, pin#4 of the C64 keyboard connector carries an LED signal, so wiring 5V to that pin will inevitably cause damage to Keyrah V3. If you really want to use that keyboard with Keyrah V3, I suggest to use a custom cable that separates pin#4 from the connector - hard-wire this to the 5V source that you trust can handle load, which is unknown due to the LEDs that can be installed.
Further, Keyrah V3 won't be able to make a difference between the left shift key and the shift lock key. However, you can add a 75 Ohms resistor into the trace of the left shift key (68 Ohms may also work). This should give sufficient headroom for making out a difference between the to keys.
Jens
If the Mechboard requires +5V on the keyboard connector, it won't work.
Jens
How have other A1200 users dealt with this problem?
They go with the suggestion of the manual_ Remove the HD cradle. Keyboard is supported sufficiently be the case edges.
Jens
how do i program the F1-F12 keys ?
By default, F1-F10 send the same key code as the Amiga keyboard. If you want to change this assignment, please use Thor's Lyra3tool. All options are documented on the Lyra 3 Wiki page.
Jens
It's safe to try, though. The MK2 will revert to a safe 5V for the VIC chip for unknown values, but I believe the design doesn't even use the 12V line of the "old" VIC chips, so there's no danger of applying over-voltage.
Jens
Then I can confirm that I picked up the parcel on my way to A38, and it's safely at iCOmp HQ 
We'll be working on it after we return from holidays (coming Monday).
Jens
No specific mounting options, but a hint: If you use the HDMI/VGA output board upside-down, mounting will be easier.
A pure memory expansion for the A1200 is assuming that it's talking to a 68020 processor. That is not the case with the ACA500plus. It has nothing to do with "more money for iComp" - we do support properly-designed A1200 accelerators, as you can see on the Blizzard cards, which are supported, but won't change anything on our bottom line.
Jens
Does the icomp.de P96 work with a GBAPII++?
It's supported, but not part of the archive, as I don't own the rights to the driver. You need to download the card driver from the vendor.
I then assign it to the PiccoloSD64
Why would you do that? It's a re-make of the Picasso II.
Jens
Didn't check the pinout, but as you've found out, the A1200 bus is separate from the local CPU bus. There are two AS signals, one from the 68030, and another one generated by the CPLD, mimicing the 68020 side for the A1200 bus.
FPU select is happening based on addresses and function code. Termination of the access is purely done by the FPU with DSACKn. If you see FPU select happening, you already know that the FPU has been detected, as without FPUsense, you'd see a bus error instead of a chip select.
Jens
After a very successful Amiga 38 show in Mönchengladbach, Germany, we're taking a week off. We'll be back in the office on October 16th to ship orders that were placed in the meantime. Orders that have been paid until today (Sunday) 11:30am have been prepared for shipping and will be picked up by UPS on Monday, October 9th.
presumably this interference doesnt exisit when using the aga mk3?
It does not exist, right.If you use HDMI, then the whole transmission chain is digital, and you won't see any wavy lines.
Jens
The AGA chipset can't generate 1600 pixels per line. What you see is already maximum overscan.
I know the MK2 tool is a bit techy, but you can just spend some time to play with the numbers and try them out. It's not as comfortable as the MK3 tool (which is instand and fully graphical), but that's just called "progress" - MK2 was just more complicated to configure.
Jens
Does the card auto initialise itself now from a cold boot ? I saw a utube video a from a year ago suggesting you have to run the config tool from a floppy each time to get the card to be recognised , which i dont want to have to do ..
Indivisino AGA MK3 (as well as it's predecessor) has a flash ROM that stores the configuration. This is loaded automatically at power-up, no extra software needed.
What you've seen in that video is most likely one of the very few cases where the unit doesn't start at all from a cold boot, and the customer is running a "reset" tool which was published in this forum. The computers where this problem occurs are extremely rare - so far, the product has been available for over three years, and not a single one has surfaced in "mainland Europe" - until this week! One unit is in eastern Germany, and the customer agreed to help reproducing the error, so we can finally get to the bottom of it.
That said, the probability of the same thing happening at your place is very small. So far, we have less than five report of this problem, and there's an intermediate solution for it, so it appears like people are still OK with it, as it's just a tool you need to insert into your startup sequence (using the rescue disk is also an option, but not required).
Jens
Sounds like a bad contact - please re-seat the unit on the Lisa socket. Also, avoid using any non-standard accelerators, they often block access to the MK2 flash.
I believe your parcel is the one that could not be delivered here yesterday. Did you ship from Germany, very close to the Polish border? I may be picking up the parcel when I drive to Mönchengladbach later today.
Jens
Does that mean the v2 was implemented in another way?
Yes, fundamentally different. It had the six-key-limit, and there was quite some cross-effests with joysticks, especially if you use diagonal directions on two-player games. Back when I developed the first Keyrah (17 years ago), I just never thought that this would be used for anything more than an office prank. Then came the RPi, and Keyrah sales exploded
V2 isn't that much different from V1 - it only introduced the ACPI switch and added jumpers for the different keyboards. This reduced stock-holding complexity (only 1 version instead of 3). A few updated connector components made it scale better at higher quantities. V2 and V3 use mostly the same connectors.
V3 addresses all requests that we've ever had with Keyrah. I did prepare for quite some extensions with the DB25 connector being very flexible, but wouldn't have expected that an up-to-date-product fails on implementing something that's been standard for many years in PC Bios routines. You might want to drop that bit of information (the comparison to a PC Bios) with some product support/manager at Digilent. They should really update the PIC formware, as Keyrah V3 is not the only thing that will have trouble on their "USB host".
Jens
