Gotek Q&A

[bfollowell]

I'm curious about the OLED screen operation. I could've sworn I'd read somewhere in this thread about the disk image filename scrolling, but they do not on mine. If the filename is longer than the screen is wide, it's just cut off, and there is no text scrolling. I also see from the images in this thread that there is an S:0 on the bottom line. I'm not sure if that is for sector or side, but mine doesn't show that either. Mine shows T:00.0, where I'm assuming T is for track.

Does it make a difference which firmware we use? I'm using FlashFloppy 2.14. Does the display look different with the HxC firmware?

Not the end of the world or anything. I'm just curious why my results are a little different.

Thanks.

[tzok]

On FF name of selected image is scrolled when there is no drive activity. During folder navigation - after some time of inactivity (by default 0,3 s). You can configure this, by editing FF.CFG.

[bfollowell]

On mine, when there is no drive activity, my screen just turns off after a few seconds. No scrolling. There was also not a FF.cfg file on mine. I'll have to look back through the included files and see if I can find one.

EDIT:

OK, I found the FF.cfg file and there's a decent sized section related to LED/OLED screens. Lots of information and options. I'll play around with that. I'm assuming it goes on the root directory with the AUTOBOOT.hfe file? I've made some changes, but haven't seen any change in behavior yet. I'll keep playing with it.

Thanks for your help.

[stephen_usher]

The documentation is here:
https://github.com/keirf/FlashFloppy/wi ... ation-File

[DoG]

Some settings can be set by pressing F3 in flash floppy menu. You can also press HELP key to set some more info about flash floppy.

[bfollowell]

Well, I'm having no luck whatsoever getting the filename to scroll. I've attached the Display section from my FF.cfg file below. The FF.cfg file is stored on the root of my flash drive.

It looks like everything was setup to run correctly from the start except for changing the display-off-secs setting to 255, which causes the display to stay on the whole time. That is now working, but the filename isn't scrolling.

Did I miss something?

I am using FlashFloppy firmware v2.14, but I am using the HxC file manager. I think that's what most people with Goteks do, but I thought I should mention it, in case this could affect something.

Thanks.



##
## DISPLAY

# Display Type: <type>[-rotate][-narrow]
# auto: Auto-detect (7-seg LED, LCD, OLED)
# lcd-NNx02: NNx2 backlit LCD with I2C backpack (16 <= NN <= 40)
# oled-128xNN: 128xNN I2C OLED (NN = 32 | 64)
# -rotate: OLED view is rotated 180 degrees
# -narrow[er]: OLED view is restricted to Gotek display cutout
# (-narrow: 18 chars; -narrower: 16 chars)
# Values: auto | lcd-NNx02 | oled-128xNN[-rotate][-narrow[er]]
display-type = auto

# OLED Font. Narrow and wide options.
# Narrower 6x13 font permits:
# - More characters per row
# - Use of Gotek display cutout (eg. "display-type=oled-128x32-narrow")
# Values: 6x13 | 8x16
oled-font = 6x13

# OLED contrast/brightness.
# Values: 0 <= N <= 255
oled-contrast = 143

# Turn an LCD or OLED display off after N seconds of inactivity
# N=0: always off; N=255: always on
# Values: 0 <= N <= 255
display-off-secs = 255

# Automatically switch LCD/OLED display on when there is drive activity?
# Values: yes | no
display-on-activity = yes

# LCD/OLED long filename scroll rate in milliseconds per update
# Values: 100 <= N <= 65535
display-scroll-rate = 200

# LCD/OLED pause time at start/end of scroll, in milliseconds
# Zero means endless scroll
# Values: 0 <= N <= 65535
display-scroll-pause = 2000

# LCD/OLED long filename scroll rate during navigation (ms per update)
# Values: 0 <= N <= 65535
nav-scroll-rate = 80

# LCD/OLED long filename pause before scroll, during navigation (milliseconds)
# Values: 0 <= N <= 65535
nav-scroll-pause = 300

[bfollowell]

There's a user over on the AtariAge forums that is having an issue with his ST after setting up and installing a Gotek with the FlashFloppy firmware. He said that the keys he's pressing don't bring up the correct letter. Q comes out as A, W comes out as Z, A comes out as Q, Z comes out as W, M doesn't work. It sounds exactly like a French AZERTY keyboard to me. The thing is, the keys all bring up the correct character when using any ST application. They're all correct. He said he bought the 1040STE new in Australia and he attached a screenshot of SysInfo confirming that it has U.K. TOS v1.6.

Are there different language versions of FlashFloppy that he could have accidentally downloaded and flashed with? Has anyone ever heard of such an issue?

I've never heard of such a thing. I'd really like to help him, but I've reached the end of my limited knowledge.

https://atariage.com/forums/topic/30568 ... ard-issue/

[rubber_jonnie]

AFAIK, The version of FlashFloppy should have no bearing whatsoever on the keyboard operation. It only affects the Gotek which just appears to be a floppy drive to the ST. What I have seen before is that when you use the keyboard to launch software, rather than the mouse, if you happen to keep holding ALT down it can change the language to the softwares default. For example, with the HDDRIVER configuration software, if you hold ALT down, it starts in German, not English. Otherwise its a problem with the ST or TOS ROM. Can't be the Gotek.

[bfollowell]

That's what I thought too, but his STE is a U.K. model, with a standard QWERTY keyboard and U.K. TOS, and the keyboard works perfectly, as it should with any and all other apps.

Nothing about this makes any sense whatsoever. Very strange.

[rubber_jonnie]

That's what I thought too, but his STE is a U.K. model, with a standard QWERTY keyboard and U.K. TOS, and the keyboard works perfectly, as it should with any and all other apps.

Nothing about this makes any sense whatsoever. Very strange.

It can't be the Gotek, I just checked the site, and FlashFloppy makes no distinction with regions, plus it will only ever appear to the STE as a floppy disk drive, it doesn't work that way.

There is something else wrong with the machine, and it probably happened when opening up to fit the Gotek IMHO.