 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Unix on the Pico Computer 3
  Page 10 of 10 |
|||||
| Author | Message | ||||
Bleep Guru  Joined: 09/01/2022 Location: United KingdomPosts: 853 |
Hi Peter, Thanks for the explanation about THUMB_BUDGET & BCODE_ONLY, I have now got PETSCII running, though I still wonder if I'm not doing something wrong as I'm seeing a much greater slow down than 2.7X if I use BCODE_ONLY, I'm seeing about 10X slower? Also thanks for the pointer about the Frame bufferlayers, I forgot that Fuzix effectively uses the LCD model for layers. :-( I have also been looking at problems I am having using Vi. First thing I have found is that if I use Tera Term, Vi seems to behave well, but If I use just a USB keyboard and a HDMI monitor I have problems. 1. Vi doesn't work in Mode 1, it only uses the top half of the screen, and then does not scroll when the cursor gets to the last line of the file as displayed on the screen, that last line changes as you scroll down further, but the lines above it do not move up. 2. when using the monitor, in Mode 2 the first line of a file is missing, this puts all subsequent lines 1 line too high, so for example if I scroll down to a line and do yy (yank line to buffer) then immediately do p (put line(s) in buffer at cursor) the line that is inserted is not the one I (appeared to) copy from the screen, the inserted line also gets put in apparently the wrong place, so things now start to get very confusing, if you redraw the screen, I do it with G followed by 1G (go to end of file, go to line 1 of file) the positioning of the line is now corrected, but it is still not the line I yanked. This is a poor explanation, if you have both a terminal and a monitor going side by side it will become obvious. Getting Mode 1 would be nice, more screen area, but not essential, but getting it working in Mode 2 would be a nice minimum. Thanks. Regards Kevin. Edited 2026-09-11 04:07 by Bleep |
||||
| Arne Regular Member  Joined: 05/01/2025 Location: GermanyPosts: 62 |
Hello, I have connected an US keyboard and have the following problem, when I press the @ character I get “ and vice versa.The keys seem to be swapped ? Any idea? Arne |
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 9119 |
It looks like the US and UK settings are swapped. What do you get on Shift-3? Mick Zilog Inside! nascom.info for Nascom & Gemini |
||||
phil99 Guru Joined: 11/02/2018 Location: AustraliaPosts: 3376 |
US keyboard. Shift ~!@#$%^&*()_+ Normal `1234567890-= |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 9119 |
UK keyboard (mine anyway!) ¬!"£$%^&*()_+ `1234567890-= Mick Zilog Inside! nascom.info for Nascom & Gemini |
||||
| Arne Regular Member Joined: 05/01/2025 Location: GermanyPosts: 62 |
On Fuzix: ~!“#$%^& °1234567 Printed on keyboard: ~!@#$%^& `1234567 |
||||
Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3368 |
The keyboard defaults to UK. To get the US layout enter: picoctl keymap us The picoctl command can set the keyboard to a variety of layouts including us uk de fr es be. When you have got used to the editor in Unix you can add the picoctl command to the file /etc/rc and the keyboard will then be automatically configured when you login as root. Geoff Geoff Graham - http://geoffg.net |
||||
| Arne Regular Member Joined: 05/01/2025 Location: GermanyPosts: 62 |
With your hint: picoctl keymap us its o.k. Thanks, Arne |
||||
| Page 10 of 10 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2026 |
