|
Post by Pyrofer on Oct 19, 2020 8:21:49 GMT
I am pretty sure that if you are just writing multiple bytes to memory in sequence you never need to check ready after the first byte. Do some testing but in most of my stuff I don't check when writing more than 1 byte in squence into the VDC ram. It's only when doing new registers or block copy etc you need to check.
|
|
|
Post by Pyrofer on Oct 2, 2020 6:59:20 GMT
Oh now that is a pretty damn cool use of the extra memory!
I wish this sort of thing had come out back when the 128 was new.
|
|
|
Post by Pyrofer on Oct 1, 2020 7:31:57 GMT
That looks amazing!
What are the differences from a standard 128 to extended "REU" etc?
|
|
|
Post by Pyrofer on Sept 1, 2020 8:37:16 GMT
How easy is it to add this to one of the EF3 kits on eBay? I suddenly have a reason to buy one. I want it for the same reasons, developing on the PC and testing on my real 128 without messing about moving SD cards back and forth.
|
|
|
Post by Pyrofer on Aug 6, 2020 9:23:09 GMT
I have some waiting assembly. My apologies to all those waiting...
I have not been having a good year, I am sure many of you can understand when I say all delays are just "2020" doing it's job.
|
|
|
Post by Pyrofer on Jul 21, 2020 10:00:26 GMT
Is this for using a PS2 keyboard on the 128D that is missing a KB? Or for using your 128 Keyboard on a PC that has PS2 input?
your best bet for making a PS2 kb work as a 128 keyboard is to find a matrix switch. There are some nice ones that have 8x12 matrix on them and make it easy to interface to the 128 keyboard layout. Then it's just a few control lines to whatever Arduino you use. PS2 libraries exist already so should be easy to hook into. At that point its just a matter of watching for key down and key up messages and turning the correct switch on and off. This allows for keyboard scanning and joystick scanning to all work with no danger from the micro controller if you code something wrong.
|
|
|
Post by Pyrofer on Jul 12, 2020 18:10:38 GMT
Sounds like your key is a bit dodgy.. That's a latching key like shift lock and as such not part of the main KB, you can probably de-solder it and remove to clean the thing internally. Yes, re-seating chips is the number 1 fix for the 128
|
|
|
Post by Pyrofer on Jul 8, 2020 10:59:40 GMT
You sure the 40/80 key is down? Run some tests in 40col mode that test the VDC and check the values. Are you sure the monitor had the digital/analogue switch in the right position? Try just changing the colour of the screen/border on 80 col (you can do all this on the 40 col screen) Do you have a 128 test cart?
|
|
|
Post by Pyrofer on Jun 2, 2020 20:35:13 GMT
DO NOT USE VICE. It is hopeless and in no way represents the VDC. You can't do basic VDC coding with vice let alone anything like scrolling or Smooth scrolling.
|
|
|
Post by Pyrofer on Apr 2, 2020 8:30:37 GMT
Have you considered using a CGA to RGBs adapter? This would make the CGA output work on any normal analogue RGB monitor (Amiga style) or euro SCART TV. I have a load in my store atm.
|
|