fachat / xd2031 Goto Github PK

Allow to use a ".xd2031" file to control the display of the directory. For example to define which file is first, order of other directory entries, etc.

Was hältst Du von der Idee, eine .xd2031 - Datei im aktuellen Verzeichnis zu unterstützen?
Das könnte eine reine Text-Datei sein, die beim Wechseln in das Verzeichnis eingelesen wird und neben #;Kommentaren eine Reihe von Befehlen beinhalten kann.
Mit *=DATEI könnte man dort die "erste Datei" zuweisen.
Später könnte man dort auch andere Optionen geben, die zum Betrieb des darin enthaltenen Programms notwendig sind, wie etwa Disk-Change-Informationen, wenn sich ein Programm über mehrere Disketten-Seiten erstreckt.

works on IEC though

If the device is powered by the CBM (e.g. petSD connected to tape port) and the CBM doesn't have a reset key, a power cycle will disconnect the device. fsser stops exection then without a word what happend.

A user might not expect that a "reset" (okay, it's a power cylce) will stop XD-2031.

fsser should try to re-open the device. This could be difficult if it started with root rights and droped rights later. At least, it should give a hint, why it stopped.

Looks like parse_filename() ignores '@'

cd:Projekte fails, cd 0:Projekte works.

-----8<----------8<----------8<----------8<----------8<----------8<-----

: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
ERR:Did not find provider for cd:Projekte
: COMMAND: CD:{d0}ROJEKTE
: Setting status to: 68,GENERAL FAULT,00,00
: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
INF:CHDIR(Projekte)
: COMMAND: CD 0:{d0}ROJEKTE
-----8<----------8<----------8<----------8<----------8<----------8<-----

should give a "file exists" error instead

Wanted: progress bar with some extra information (start address, % of file pointer) when loading files.

This would be especially useful for the rather slow IEC bus.

All we see at the moment is:

INF:OPEN_RD(16->fs:dangerfreak)
INF:open file for fd=16 in dir /home/pi/XD2031/tools with name dangerfreak
INF:CLOSE_SEND_EOF(16)
INF:CLOSE(16)

Wanted: fsser command line option that enables logging of the complete bus traffic / file contents.

This is the server output of a single '@':
-----8<----------8<----------8<----------8<----------8<-----

: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
: COMMAND:
: Setting status to: 30,SYNTAX ERROR,00,00
: Received error on open/cmd!
-----8<----------8<----------8<----------8<----------8<-----
Haven't checked this yet--maybe an "empty" command doesn't contain a valid one and thus gives a 30,SYNTAX ERROR?

... because where is the EOF on those ones?

Just came from implementing FS_RENAME for the FAT provider.

It works just like Linux mv command, meaning: it can rename/move files/directories. Tested: yes, it can even move and rename directories at once, e.g: @r:/foo=/somewhere/else/bar

Instead of limiting the command capabilities by checking if the command contains a path separator, I'd further like to rename FS_RENAME to FS_MOVE and allow this "officially". This implies a few changes to pcserver/fs_provider, since rename() cannot move files across file systems.

Approval?

Commodore DOS obviously did.

This breaks Ctrl-D "toggle active drive"

Running the "u1test" test code, the IEC on the C128 gives DEVICE NOT PRESENT on random stages of the program. The program runs fine on the C64.

... to allow seek() for any file

• P
  Positioning doesn't just work for REL files but also for regular
  files on a FAT partition. When used for regular files the format
  is "P"+chr$(channel)+chr$(lo)+chr$(midlo)+chr$(midhi)+chr$(hi)
  which will seek to the 0-based offset hi_2^24+midhi_65536+256*midlo+lo
  in the file. If you send less than four bytes for the offset, the
  missing bytes are assumed to be zero.

Sending the -X command options automagically from the server to the device is not request/response and has problems with reentrancy.

Probably make it so that after RESET or trigger from the server, start pulling in the options one by one.

What about reloading the pcserver part - should the device always reset here to get the default values?

: COMMAND: CD:/
: CMD=CD
: DRIVE=-
: NAME={ff}/
: ACCESS=R
: TYPE=-
DBG:Change dir to: /
INF:Calculate new dir path: /Users/j/Projekte/tmp//
DBG:Checking that new path '/Users/j/Projekte/tmp' is under base '/Users/j'

file size 1541: 142 blocks
file size fsser: 140 blocks

... e.g. with an assign option to the directory path (see other issue about wildcard option)

Support direct buffers in the AtMega firmware, as this seems to be the only way to really support it - buffers can be shared across drives, so the firmware is the only place to do it.

CBM DOS allows multiple dir masks, separated by commas.

If three files TEST, TEST1 and TEST10 would exist, LOAD"$:TEST1?,TEST" would give TEST and TEST10, but not TEST1.

Beyond that, CMD and sd2iec interpret some dir masks allowing passing of options:

=H --> include hidden files (not included by default)
=T --> include time stamps
=B / =D --> show only directories
=P --> show partitions (IHMO not applicable for XD-2031), but
=A could show what is assigned to each drive

edit 2012-05-07:

Further options for sorting the directory (alphabetically / chronologically) would be nice.

Static "1 blocks free" breaks COPY-ALL, because it thinks there isn't sufficient free space.

Free space could be determined with statvfs(), but must not be greater than 63999 blocks free.

... so you can leave the "other" bus switched off when you only want to use one.

Currently IEEE hangs when switched off IEC devices are connected and vice versa, because ATN (and all other lines) are constantly pulled low

First implementation on server side, but such that it can be shared with firmware

Implement relative file support. Open files like relative files enables the FS_SEEK functionality

Maybe Pi?

But that there's at least the CBM UK business keyboard lacking the Pi.

The wireformat cmd IDs still reflect the original OS/A65 numbering, where the read/write/eof are added as an afterthought, as in OS/A65 they are on a separate channel. However, with the addition of the drive byte as first byte of a name, they are not compatible anymore anyway.

We should
a) straighten out the numbers of the FS_* to let them start from 1 and all positive
b) put wireformat.h and errors.h into a /common directory to be included in firmware as well as in pcserver

I think this should be done before any larger announced version, so we stay (more?) compatible in later releases.

Agreed?

SAVE"/NOTTHERE/",8 gives:

: OPEN FILE: FOR CHAN: 1 WITH NAME: /NOTTHERE/
: NAME=/NOTTHERE/
: ACCESS=R
: CMD=0
INF:open file for fd=1 in dir /Users/j with name /notthere/
DBG:malloc_path: base=/Users/j, name=/notthere/
INF:Calculate new dir path: /notthere/
DBG:Check that path '//' is under '/Users/j/'
ERR:Path '//' is not in base dir '/Users/j/'
ERR:ERROR RETURN: 67
: provider_lookup for {7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}{7f}
DBG:Got 0 options to send:
: Config read from EEPROM
: sent reset packet on fd 125
:
:
: ### PETSD/XD2031 v0.9.1 ###
: 14425 Bytes free, 18432 kHz
: Fuses: l=F7 h=D2 e=FF l=FF
:
:
:
: channel_close(0 -> 1), push_state=2

Like 'OPEN1,8,2,"HTTP:HOSTNAME:PATH" instead of the assignment to a drive and then the open on the drive.

Unlike *NIX/DOS/Windows, Commodore DOS ignores everything after *.
The user should have the option to choose among these behaviors with a X-command.

dr-xr-xr-x 2 j staff 68 23 Okt 00:08 newdir/

... because of prepended "0:" in the from path