Disk files not working in sedai linux

Page 3/4
1 | 2 | | 4

By ren

Paragon (1662)

ren's picture

26-01-2021, 15:48

Some idea: when you get a .dsk to work, and after that it won't anymore: has it changed somehow? (diff/cmp and/or checksum verification). Have permissions and/or ownership changed somehow?

(Does Sedai Linux have a source code repository btw? The website is rather sparse..)

By Juhahal

Supporter (9)

Juhahal's picture

26-01-2021, 16:14

I made video trying to load disk with FS-A1GT. Switching between computers seems helping if disk arent working

https://vimeo.com/504816486

By sdsnatcher73

Paragon (1519)

sdsnatcher73's picture

26-01-2021, 17:36

Okay, several things seem to be happening. First of all after you insert a disk (especially with games) you just reset the MSX and let it boot from the disk.

Some games require you to boot with the CTRL key pressed during boot (until the BEEP) this disables drive B: and frees some memory. Drive B: is always available as a virtual drive if no real one is present, the BIOS will prompt you to change disks when software accesses it. The software that prints the Japanese line of text probably requires you to disable drive B:

Then if you boot the MSX with shift pressed down you will disable the BDOS and have no disk drives. This can be useful when loading games from tape (or CAS file) but not so much on a turbo R (as it has no tape interface). openMSX will still allow inserting a disk (as you would be able to in a real MSX) but you won’t be able to use the disk drive. Hence the illegal function call when you execute FILES command. You can see in basic if BDOS is present by the line that is printed below the memory free counter, indicating Disk Basic 1.0 or 2.01 (for DOS1 and DOS2).

By Juhahal

Supporter (9)

Juhahal's picture

26-01-2021, 18:08

Sedai linux info says Main menu toggle should binded to SHIFT+F10.

Is it possible that breaks reset->OpenMSX think that i want disable BDOS.

By Vampier

Prophet (2381)

Vampier's picture

26-01-2021, 18:12

ps. don't boot with shift pressed but CTRL - disk basic doesn't load in some cases that's why the 'files' command doesn't work.

Look at the recording - disk basic not loading. That can only happen when you press shift while booting. Shift disabled the disk rom.

By Juhahal

Supporter (9)

Juhahal's picture

26-01-2021, 18:32

It was that menu button compo. Now OpenMSX loads disks.

By Vampier

Prophet (2381)

Vampier's picture

26-01-2021, 18:50

so it was 'shift'? Smile

By FiXato

Scribe (1694)

FiXato's picture

26-01-2021, 18:52

What that Sedai message says is that the Rpi400 doesn't have a physical menu key on its keyboard, and that if you want to open up the on screen menu with a keyboard combination rather than using the mouse on the top left Menu icon, you can assign the menu button to a different keyboard combination (they suggest Shift+F10), and instruct you (with one-time instructions) how to assign that keyboard combination to the menu controls:

Step 1: open the openMSX console by pressing F10
Step 2: type: bind SHIFT+F10 main_menu_toggle

After that, when you *press* shift+F10, (hit, not hold, and preferably not during boot as that affects the MSX boot process, as noted above), it will open/close the on screen menu; the same as you open by clicking on the top left on screen button.

Personally I'd bind it to a different key that doesn't require you to use shift or ctrl, so you can safely press it during booting...

By Juhahal

Supporter (9)

Juhahal's picture

26-01-2021, 19:06

well I didn't hold shift when i made that video. It is impossible press shift-F10-up-enter with one hand at same time.
I binded ALT+F10 and now it works.

By Vampier

Prophet (2381)

Vampier's picture

26-01-2021, 19:16

the SDL stuck key problem strikes again

Page 3/4
1 | 2 | | 4